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
SysML keywords
Requirement
DeriveReqt
AbstractRequirement::id
AbstractRequirement::text
Keywords
Slide kind
MagicDraw/Cameo: table
Click on the image to view it full size
Nobody (informed) said that SysML (or even UML) modelling and MBSE is only about graphical modelling, notations, and diagrams! Information can be extracted in many different ways and presented in many different formats from the underlying model!

This is a composite image with 2 separate query tables. The tables generated in MagicDraw SysML Plugin or Magic Cyber-Systems Engineer ® (Cameo Systems Modeler®) necessarily are visually slightly different from those in the spec.

In the 1st image an additional column for derived requirements is included (it's available out-of-the-box in the tool just be selecting that column type as visible).

The 2nd image demonstrates the powerful derived relationship and metachain navigation features. The column names chosen are indicators only.

The 2nd figure is very tricky to achieve:

  • The scope of the query had to be tediously set to include exactly each of the rows, rather than using, say, the parent Performance and Capacity Requirements. (There may be a more elegant way of doing this using filters.)
The derived id column 'D.ID' here does not show the ID on the FuelEconomy row (which is the source of multiple DeriveReqt) MagicDraw metachain seems to struggle with multiple rows (at least as used here).
The SysML-1.6 figure seems to be missing the DeriveReqt from PowerSourceManagement to FuelEconomy
The SysML-1.6 figure has the ID for both Range and PowerSourceManagement set to 'd.2'; to solve this the ID for Range is set here to 'd.3'
Up next
Figure D.15 - Defining the Automotive Domain (Automotive Domain Breakdown)
Notes
[CAPABILITY, FEATURE, TOOL] Magicdraw/Cameo has powerful query view tables, maps, and dependency matrix diagrams!
[FEATURE, TOOL] SysML: MagicDraw/Cameo can optionally indicate Requirement IDs in tables
[CAVEAT, FEATURE, TOOL, VARIATION] MagicDraw/Cameo query tables use a single row (with a group of elements) to represent multiple targets/hits from a relationship, rather than one row per hit.
[FEATURE, TIP, TOOL] MagicDraw/Cameo derived relationships and metachain navigation are very powerful and worth exploring
[CAVEAT, DISPLAY, STYLE, TOOL] MagicDraw/Cameo: the coloured stereotype icons for some kinds of elements can't be removed from all diagrams, tables, or matrix views
Snippets (quotes/extracts)
  [SysML-1.6] Figure D.14 contains two diagrams that show requirement containment (decomposition), and requirements derivation in tabular form. This is a more compact representation than the requirements diagrams shown previously.
  [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.
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)
A basic Requirement is an AbstractRequirement
Derived requirements and the DeriveReqt relationship
Refining requirements
MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (all)
MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block and PartProperty (relations only)
Visit also
Visit also (backlinks)
SysML: MagicDraw/Cameo: Use query view tables, matrices, and maps, use them a lot! They help communicate well with other stakeholders. Learn how to use the Generic Table diagram type, custom relations, Simple Navigation & Metachain Navigation (expert)!
Nobody (informed) said that SysML (or even UML) modelling and MBSE is only about graphical modelling, notations, and diagrams! Information can be extracted in many different ways and presented in many different formats from the underlying model!