Beginners Guide to Model-Based Systems Engineering

12/18/2018

hierSpecificRequirements

R.2

Mapping Requirements Hierarchies

Specific Requirements

refinedby

refinedby

R.2.1

R.2.2

AcceptRequests fromCertified Customers

Retain Inventory andProvide Products

elicits

Requirement

Use Case

elaboratedby

refinedby

basedon / specifiedby

verifiedby

R.2.1.1

R.2.2.1

specifiedby

includes/ extends/ kindof

refinedby

refinedby

AcceptRequests

Retain Inventory

Verification Requirement

verifiedby

fulfilledby

involves/ describes

R.2.1.3

R.2.2.2

executedby

Verification Event

refinedby

refinedby

ValidateCertified Customers

Provide Products

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

Level of Detail: Low Audience: General

inputs/ outputs/ triggeredby

Exit

Interface

Port

decomposedby

includes

comprisedof

Content: Names and relationships Use: Multi-level decomposition of requirements; traceability

Event

Transition

responsible for

connectsto

triggeredby

Link

Item

transfers

includes

decomposedby

constrains/ usesparameter from

generates

results in

causes

assignedto

Organization

Constraint Definition

Concern

Risk

65

Requirements Diagrams

• Expand classic hierarchy diagram to represent key aspects of requirements • Graphical format often complemented with tabular representation • Usage largely limited to providing context for a few requirements

66

33