MBSE with Genesys 120222

Requirements Diagrams

• Expand classic hierarchy diagram to represent key aspects of requirements • Graphical format often complemented with tabular representation • Usage largely limited to providing context for a few requirements

163

Key Semantics of Requirements Diagrams

• Nodes represent objects

• Type, name, and description standard

• Lines represent relationships • <> - partitioning of a complex requirement without adding meaning • <> - more detailed requirement arrived at via analysis • <> - assertion that a model entity satisfies the requirement • <> - reference to a test case or verification aspect

Additional information available in Chapter 13 of A Practical Guide to SysML

164

MBSE with GENESYS