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 SysML keywords Requirement DeriveReqt composite (compound) requirement AbstractRequirement::text AbstractRequirement::id Slide kind SysML Requirement Diagram Click on the image to view it full size Up next Figure 16-3: Links between requirements and design Notes [ISSUE] SysML-1.6: text on Requirement 'Test and procedure conditions' is mangled in 'Figure 16-2: Requirements Derivation' (was OK in SysML-1.5) [and also on Figure 16-6] [ISSUE] SysML-1.6: 'Figure 16-2: Requirements Derivation' indeed shows DeriveReqt but spec text refers to it only as 'an example of a compound requirement' [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 [TIP]{SUGGESTED} SysML: Webel recommends use of an additional custom «requirementGroup» stereotype for compound Requirements that serve as owning Namespaces and are subject to the satisfaction policy that all child requirements must be satisfied. Snippets (quotes/extracts) [SysML-1.6] The diagram in Figure 16-2 shows an example of a compound requirement decomposed into multiple subrequirements. [SysML-1.6] Compound requirements can be created by using the nesting capability of the class definition mechanism. [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] A DeriveReqt relationship is a dependency between two requirements in which a client requirement can be derived from the supplier requirement. [SysML-1.6] For example, a system requirement may be derived from a business need, or lower-level requirements may be derived from a system requirement. [SysML-1.6] As with other dependencies, the arrow direction points from the derived (client) requirement to the (supplier) requirement from which it is derived. [SysML-1.6] DeriveReqt::1_supplier_is_requirement The supplier shall be an element stereotyped by a subtype of AbstractRequirement. [SysML-1.6] DeriveReqt::2_client_is_requirement The client shall be an element stereotyped by a subtype of AbstractRequirement. 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-2: Requirements Derivation Previous Up Next
