MBSE with CORE 100821

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 element satisfies the requirement • <> - reference to a test case or verification aspect

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

161

Mapping Requirements Diagrams

Level of Detail: Medium Audience: System/software engineers Content: Names, relationships, and descriptions Use: Limited (toy representation); context for limited set of requirements

162

MBSE with CORE