|
|
|
|
|
Key
These lines were removed. This word was removed.
These lines were added. This word was added.
|
View page history
|
There are 1 changes. View first change.
| | *Title* "Capturing Requirements for Real-Time and Embedded Systems" |
| | |
| | *Authors* Bruce Powel Douglass |
| | |
| | *Reference* Ilogix whitepapers |
| | |
| | *Year* N/A |
| | |
| | *URL* [Please see attachment|Capturing Requirements for Real-Time and Embedded Systems^Capturing_RT_Requirements.pdf] |
| | |
| | *My Summary* |
| | The author talks about how requirements can be captured and applied to real-time embedded systems. It starts by explaining how requirements can be fit into the development process; it continues by defining different types of requirements, how we can capture them using use cases. Showing how to go from requirements to the Design is an important part of the article; UML stands at the core of all this. At the end, the author shows how to scale the methodology of specifying requirements to large, complex systems. |
| | |
| | *Methods* |
| | The paper relates to specifying requirements, working with UML, and Rhapsody. |
| | |
| | | *OPP Relevance* |
| | | *Systems Integration Relevance* |
| | Part of our work focuses on how to capture requirements and integrate them in our OPP Design flow. |
| | |
| | *Keywords* |
| | Requirements, System Design, UML, Rhapsody |
|
|
|
|
|
