Beginners Guide to Model-Based Systems Engineering

12/18/2018

Requirements in Context

Color Code

elicits

Requirement

Use Case

Requirement Element

Functional Element

elaboratedby

refinedby

basedon / specifiedby

verifiedby

specifiedby

includes/ extends/ kindof

Physical Element

Interface Element

Verification Requirement

verifiedby

Verification Element

Other Element

fulfilledby

involves/ describes

executedby

Verification Event

Resource

employs

includes

Test Configuration

Test Activity

captures/ consumes/ produces

formedby

Test Procedure

decomposedby

Component

Function

performs

incorporates

exhibits

exitsby

built from / kindof

exposes

decomposedby

joined to

State

enters

exitedby

inputs/ outputs/ triggeredby

Exit

Interface

Port

decomposedby

includes

comprisedof

Event

Transition

responsible for

connectsto

triggeredby

Link

Item

transfers

includes

decomposedby

constrains/ usesparameter from

generates

results in

causes

assignedto

Organization

Constraint Definition

Concern

Risk

63

Hierarchy Diagrams

• Classic representation of relationships between several layers of objects • Most frequently used to represent composition or traceability • Nodes represent objects • Numbers and names standard • Object type often shown if diagram includes multiple types • Lines represent relationships • Implied flow based upon culture • Minimal symbology • Upper-left block - additional detail hidden • Upper-right block – entity repeated • “Generic visual query” • Represent any relationship set

64

32