DeriveReqt

SysMLv1 (or v2): CHALLENGE EXERCISE: Simplified Parsing Analysis breakdown of 'Build an Airport' with variations

The requirement diagram is a new SysML diagram type. A requirement diagram provides a modeling construct for text- based requirements, and the relationship between requirements and other model elements that satisfy or verify them.

Source

OMG Systems Modeling Language (SysML) 1.6

Derived requirements and the DeriveReqt relationship - compartment styles

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

16:01: Requirements engineering in SysML

Slide kind

SysML Requirement Diagram

Derived requirements and the DeriveReqt relationship

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

16:01: Requirements engineering in SysML

Slide kind

SysML Requirement Diagram

16:01: Requirements engineering in SysML

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Slides in this section

If you want to navigate the entire section including the additional explanatory text click on the title link of the first slide to view the full slide page, then use the next links to move through the slide pages. If you just want to view the slide images only in sequence, click on any slide to view it larger in a viewer, then click again to move through each slide in this tutorial trail section.

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 (relations only)

MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block and PartProperty (relations only)

The non-normative extended requirements

These include relationships for defining a requirements hierarchy, deriving requirements, satisfying requirements, verifying requirements, and refining requirements.

Source

OMG Systems Modeling Language (SysML) 1.6

Several requirements relationships are specified that enable the modeler to relate requirements to other requirements as well as to other model elements.

Source

OMG Systems Modeling Language (SysML) 1.6

The requirements modeling constructs are intended to provide a bridge between traditional requirements management tools and the other SysML models.

Source

OMG Systems Modeling Language (SysML) 1.6

The requirements diagram described in this clause can depict the requirements in graphical, tabular, or tree structure format. A requirement can also appear on other diagrams to show its relationship to other modeling elements.

Source

OMG Systems Modeling Language (SysML) 1.6

SysML provides modeling constructs to represent text-based requirements and relate them to other modeling elements.

Source

OMG Systems Modeling Language (SysML) 1.6

The diagram in Figure 16-3 shows derived requirements and refers to the design elements that satisfy them. The rationale is also shown as a basis for the design solution.

Source

OMG Systems Modeling Language (SysML) 1.6

Figure 16-3: Links between requirements and design

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

Slide kind

SysML Requirement Diagram

MagicDraw/Cameo: How disable icons in requirement relationship compartments and tagged values compartment on Requirement symbol?

DeriveReqt::2_client_is_requirement The client shall be an element stereotyped by a subtype of AbstractRequirement.

Source

OMG Systems Modeling Language (SysML) 1.6

DeriveReqt::1_supplier_is_requirement The supplier shall be an element stereotyped by a subtype of AbstractRequirement.

Source

OMG Systems Modeling Language (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.

Source

OMG Systems Modeling Language (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.

Source

OMG Systems Modeling Language (SysML) 1.6

A DeriveReqt relationship is a dependency between two requirements in which a client requirement can be derived from the supplier requirement.

Source

OMG Systems Modeling Language (SysML) 1.6

Figure 16-2: Requirements Derivation

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

Slide kind

SysML Requirement Diagram

Figure 16-1: Abstract Syntax for Requirements Stereotypes

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

Slide kind

UML Profile Diagram

Figure D.14 - Requirements Relationships Expressed in Tabular Format (Table)

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: HSUV sample

Slide kind

MagicDraw/Cameo: table

Figure D.13 - Acceleration Requirement Relationships

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: HSUV sample

Slide kind

SysML Requirement Diagram

Note also that rationale can be attached to the «deriveReqt» relationship. In this case, rationale is provided by a referenced document “Hybrid Design Guidance.”

Source

OMG Systems Modeling Language (SysML) 1.6

Various other model elements may be necessary to help develop a derived requirement, and these model element may be related by a «refinedBy» relationship.

Source

OMG Systems Modeling Language (SysML) 1.6

Derived requirements, for the purpose of this example, express the concepts of requirements in the HSUVSpecification in a manner that specifically relates them to the HSUV system.

Source

OMG Systems Modeling Language (SysML) 1.6

Figure D.12 shows a set of requirements derived from the lowest tier requirements in the HSUV specification.

Source

OMG Systems Modeling Language (SysML) 1.6

Figure D.12 - Establishing Derived Requirements and Rationale from Lowest Tier of Requirements Hierarchy

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: HSUV sample

Slide kind

SysML Requirement Diagram

Subscribe to DeriveReqt