MBSE with CORE 100821

Requirements in Context

triggered by

Transition

Event

entered by / exited by

Resource

Exit

State

captures / consumes / produces

exits by

built from / kind of

exhibits

incorporates

decomposed by

Component

Function

performs

elaborated by

involves / describes

Use Case

decomposed by

includes / extends / kind of

basis of / specifies

inputs / outputs / triggered by

elicits

specifies

Requirement

exposes

refined by

verified by

verified by

verified by

verified by

Port

Verification Requirement

basis of / specifies

verified by

specifies

verified by

Color Code

connected to

Requirement Element

Functional Element

Test Configuration

Test Activity

employs

responsible for

accomplished by

decomposed by

Physical Element

Interface Element

Verification Event

includes

Link

Item

transfers

Verification Element

Other Element

constrains / uses parameter from

includes

decomposed by

generates

results in

causes

assigned to

Organization

Constraint Definition

Concern

Risk

157

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 – element repeated • “Generic visual query” • Represent any relationship set

158

MBSE with CORE