1/4/2023

ĐẠI HỌC QUỐC GIA TP.HỒ CHÍ MINH

TRƯỜNG ĐẠI HỌC BÁCH KHOA
KHOA ĐIỆN-ĐIỆN TỬ
BỘ MÔN KỸ THUẬT ĐIỆN TỬ

Embedded System Design

Chapter 2: Develop a project of embedded system design

1. Challenges and Difficulty

2. Requirement Statement

Challenges
• Safety
Minimize the frequency of mishaps
Require strict requirements and limitations in terms of quality,
testing, and engineering expertise
• Stability
• Long-term stable performance;
• Security
• Design Limitations
• Small form factor;
• Low energy;
• Real time Requirement;
• Cost
• Compatibility and Integrity
Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 2

Chapter 2 1
 1/4/2023

Difficulties in Design and Development

• Complex testing
Run a real machine to have proper data
System must be tested in the embedded machine
• Limited observability and controllability
Sometimes no keyboard or screen!
In real-time systems it’s not easy to stop the system to see
what is going on
• Restricted development environments
Much more limited than in PCs
Usually compile code in PC and download it to embedded
system
• Pace Of change
Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 3

Embedded System Design Process

CAD tools Requirement definition Customers

System specification System

architects
System partitioning

SW development
HW design
•Application SW Interface design
•HW architecture
•Device Driver •User interface
•Physical design
•Operating System
SW developer HW designer
Integration and testing Reused
components
No Meet
requirement?
Yes
Delivery and maintenance
Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 4

Chapter 2 2
 1/4/2023

1.1. System Specification

Documents for System Specification

1. Product Requirement Describe how the product will be.

2.Design Specification Describe hardware modules,

subsystem, and functions will be used.

3. Hardware Specification Describe how the board will be

implemented and how it works.

4. Software Specification Describe how the software will be

implemented.

5. Test Specification Describe how the system will be tested.

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 5

Design Goals

Performance 1. Product Requirement

Overall speed, deadlines 2.Design Specification

Functionality and user interface 3. Hardware Specification

Manufacturing cost 4. Software Specification

Power consumption 5. Test Specification

Other requirements (physical size, etc.)

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 6

Chapter 2 3
 1/4/2023

Stepwise Refinement

• At each level of abstraction, we must

analyze the design to determine
characteristics of the current state of the 1. Product Requirement
design
refine the design to add detail 2.Design Specification
verify that it meets all system goals
3. Hardware Specification
cost, speed, . . .
4. Software Specification

5. Test Specification

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 7

Identifying the Requirements

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 8

Chapter 2 4
 1/4/2023

Requirements
A user requirement is a statement that specifies WHAT a product
should do, but it does not define HOW it should do it

WHAT:

The device shall decrease the temperature of the

skin

HOW:

The device shall apply moisture to cool down the

skin.

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 9

Requirements
[While/Where ] [when/if then] shall
 Ubiquitous: The touch screen shall have a response time of less
than 250 msec.
 State-driven: WHILE an external speaker is connected, the internal
speaker shall mute.
 Event-driven: WHEN a card is inserted, the card reader shall verify
credentials.
 Optional feature: WHERE a convertible roof is installed, a park/roof
motion interlock function shall be provided.
 Unwanted: IF an invalid value is entered THEN an error message
shall be displayed.
 Complex: combinations of the above

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 10

10

Chapter 2 5
 1/4/2023

Good Requirements
Precise and minimally constrained
 Describes what system should do, not how it does it
 Uses “shall” to require an action; “should” to state a goal
 If possible has a numeric target instead of qualitative
term
• Has tolerance (e.g., 500 msec +/- 10%, “less than X”)

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 11

11

Good Requirements
Traceable & testable

• Each requirement has a unique label (e.g., “R-7.3”)

• Each requirement cleanly traces to an acceptance test
Requirement satisfaction has a feasible yes/no test

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 12

12

Chapter 2 6
 1/4/2023

Functional vs. Non-functional

Requirements
Functional requirements
output as a function of input

Non-functional requirements
time required to compute output
cost
size, weight, etc.
power consumption
reliability

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 13

13

Non-functional Requirements
Performance
Major consideration for the usability of the system and
its ultimate cost
May be a combination of soft performance metrics and
hard deadlines
Cost
Manufacturing costs (e.g. components, assembly)
Nonrecurring engineering (NRE) costs (e.g. personnel,
designing the system)
Environment and Installation
The environment that the device will operate
How to install the device
Those requirements are important for designing the
PCB, the enclosure.
Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 14

14

Chapter 2 7
 1/4/2023

Non-functional Requirements
Physical size and weight
Depends on the application
Power consumption
Important not only in battery-powered systems
Specified in terms of battery life or Wh

Certification
For international market, device need to have
certification to enter the market.
Several important certifications are UL, FCC, CE,
ROHS, IP

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 15

15

Validating The Requirements

• Requires understanding what people want

and how they communicate it
• User interface requirements can be refined by
using a mock-up
may be executed on a PC
• Physical, nonfunctional models of devices can
also help
better idea of size and weight

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 16

16

Chapter 2 8
 1/4/2023

Validating The Requirements

Requirements
o name
• The requirements form should be the
introductory of a longer document o purpose

• After writing the requirements you should o Functions

check for internal inconsistency o performance

• forget to assign functions to an o manufacturing

input/output? costs

• considered all modes of operation? o power

• unrealistic number of features into a o physical

battery-powered, low-cost machine? size/weight

o Installation
o Certification

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 17

17

Requirements Validation
• Validity checks: The functions proposed by stakeholders
should be aligned with what the system needs to perform.
• Consistency checks: Requirements in the document shouldn’t
conflict or different description of the same function
• Completeness checks: The document should include all the
requirements and constrains.
• Realism checks: Ensure the requirements can actually be
implemented using the knowledge of existing technology, the
budget, schedule, etc.
• Verifiability: Requirements should be written so that they can
be tested. This means you should be able to write a set of
tests that demonstrate that the system meets the specified
requirements.

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 18

18

Chapter 2 9
 1/4/2023

Chess Clock
• Description:
The chess clock is used to keep track of the total time each player takes
for their own moves and ensure that neither player overly delays the
game. Chess clocks are set at the start of the game to count down from
the agreed time. Just one of the two clocks runs at a time, with players
starting their opponent's clock (and pausing their own) by pressing a
button after making each move

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 19

19

Chess Clock
• Functional Requirement:
Number Description Note
PR1.1 Shall be able to set the limit game time
PR1.2 If limit move time is enabled, shall be able to set the limit
move time
PR1.3 Shall display remaining time of 2 player, format is hh:mm:ss

PR1.4 If limit move time is enabled, shall display the remaining

time for each move, format is mm:ss
PR1.5 Shall generate alarm time if remaining time is less than a
configurable time
PR1.6 Shall start counting down after one player press his button

PR1.7 Shall store game history in SDCARD

PR1.8 Shall be able to configure and control using mobile app via
bluetooth
Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 20

20

Chapter 2 10
 1/4/2023

Chess Clock
• Non-functional Requirement:
Number Description Note
PR2.8 Time accuracy is +-1 sec per hour
PR2.9 Shall have LCD display, no smaller than 2 inch
PR2.10 Buzzer sound pressure at distance of 1 m is 60dB

PR2.11 Shall response to button no longer than 0.01sec.

PR2.12 Shall operate in humidity levels
between 25% to 80% relative humidity
PR2.13 Shall operate in temperature from 0 Celsius to 60 Celsius
Degree
PR2.14 Shall store game history in SDCARD

PR2.15 Shall operate with single power supply from 7V to 12V

PR2.16 Shall operate with battery 9V

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 21

21

Chess Clock
• Non-functional Requirement:
Number Description Note
PR2.17 Shall last more than 1 week with battery 9V 300mAh
PR2.18 Size is smaller than 14x10x5 cm
PR2.19 BOM cost (only components) less than 20 USD/device
with manufacturing quantity of 1000

Bộ môn Kỹ Thuật Điện Tử - ĐHBK Chapter 2 22

22

Chapter 2 11