Explore chapters and articles related to this topic
Automotive Architecture Description Languages
Published in Nicolas Navet, Françoise Simonot-Lion, Automotive Embedded Systems Handbook, 2017
SysML extends UML2 with new modeling concepts and diagrams for systems engineering. It also identifies the parts of UML2 that are relevant for systems engineering modeling. The new concepts concerns requirements, structural modeling, and behavioral constructs. New diagrams include requirement diagram and parametric diagram, and adjustments of activity, class, and composite structure diagrams. Tabular representations of requirements or allocations, for example, are also included as an alternative notation.
Models and Tools for Complex Embedded Software and Systems
Published in Luciano Lavagno, Igor L. Markov, Grant Martin, Louis K. Scheffer, Electronic Design Automation for IC System Design, Verification, and Testing, 2017
Requirement diagrams are used to define a classification of requirements categories (e.g., functional, interface, performance) or a hierarchy of requirements, describing the refinement relationships among requirements in a specification. Requirement relationships include DeriveReqt, Satisfy, Verify, Refine, Trace, and Copy. An example of requirement diagram is shown in Figure 9.33.
Data and model-based triple V product development framework and methodology
Published in Enterprise Information Systems, 2022
Qing Li, Hailong Wei, Chao Yu, Shuangshuang Wang
The Requirement Diagram of SysML or other professional requirements management tool, such as IBM Rational DOORS, is used to construct the DCS requirement model, and then catch stakeholder’s requirements and translate them into system requirements. Next, system use cases are defined and assigned system requirements through Use Case Diagram of SysML. For ease of analysis, we only focus on firefighting use case and its realisation in this section, as shown in Figure 12.