Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 16 Requirements Tags and keywords UML keywords Stereotype metaclass Extension Generalization Trace Refine NamedElement Operation Behavior Class SysML keywords Requirement Trace Copy DeriveReqt Verify Satisfy Refine DirectedRelationshipPropertyPath TestCase AbstractRequirement AbstractRequirement::id AbstractRequirement::text AbstractRequirement::/derived AbstractRequirement::/derivedFrom AbstractRequirement::/satisfiedBy AbstractRequirement::/refinedBy AbstractRequirement::/tracedTo AbstractRequirement::/verifiedBy AbstractRequirement::/master Slide kind UML Profile Diagram Click on the image to view it full size Up next Figure 16-2: Requirements Derivation Notes [CAVEAT, TOOL] UML4SysML is a specification abstraction (concept) only, it does not find direct expression (such as via a namespace) in tools like MagicDraw/Cameo [DISPLAY, ISSUE, STYLE] SysML-1.6: Consistency: either show the [metaclass] on all Stereotype symbols in profile diagrams or on none [NAMING, TOOL] MagicDraw/Cameo: By implementation the name of some Stereotype attributes and operations is UpperCase instead of lowerCase like in the UML and SysML specs Snippets (quotes/extracts) [SysML-1.6] A requirement is a stereotype of both Class and Abstract Requirement. [SysML-1.6] A requirement specifies a capability or condition that must (or should) be satisfied. [SysML-1.6] A requirement may specify a function that a system must perform or a performance condition that a system must satisfy. [SysML-1.6] Requirements are used to establish a contract between the customer (or other stakeholder) and those responsible for designing and implementing the system. [SysML-1.6] The default interpretation of a compound requirement, unless stated differently by the compound requirement itself, is that all its subrequirements shall be satisfied for the compound requirement to be satisfied. [SysML-1.6] Subrequirements shall be accessed through the "nestedClassifier" property of a class. [SysML-1.6] The containment (cross hair) relationship, for purposes of this example, refers to the practice of decomposing a complex requirement into simpler, single requirements. Visit also Visit also (backlinks) Related slides (includes other tutorials) Related slides (backlinks, includes other tutorials) A most basic Requirement with a 'name', an 'id', and 'text' A basic Requirement is an AbstractRequirement Derived requirements and the DeriveReqt relationship Derived requirements and the DeriveReqt relationship - compartment styles Refining requirements Satisfying Requirements and the Satisfy relationship Requirements and the Trace relationship - metamodel Trace used for model element elicitation - callout style Trace used for model element elicitation - tagged value and element property styles TestCase and Verify metamodel TestCase and Verify example - callout style Composite (a.k.a. "compound") Requirements The Copy relationship MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (all) MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block and PartProperty (relations only) Flags Book traversal links for Figure 16-1: Abstract Syntax for Requirements Stereotypes Previous Up Next
