Specifying Behavior of Embedded Systems

What makes a good requirement?

The criticality of correct, complete, testable requirements is a fundamental tenet in software engineering. Both functional and financial success is affected by the quality of requirements. So what is a requirement? It may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification. Requirements are needed for several reasons:

• Specify external system behavior

• Specify implementation constraints

• Serve as reference tool for maintenance

• Record forethought about the life cycle of the system, i.e., predict changes

• Characterize responses to unexpected events

The system designer must understand ...

Get DSP for Embedded and Real-Time Systems now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.