Definitions & Usage
A growing reference for every artifact, level, and diagram used across the Mission Planning Environment sandbox. Each entry covers definition, purpose, design-engineer view, MBSE-architect view, a worked example, and common pitfalls.
Find a term
L0 — Mission / Stakeholder Need
The 'why' — capability gap stated in operator language.
L1 — System Requirement
What the system must do as a black box.
L2 — Subsystem Requirement
What each subsystem must do to collectively satisfy L1.
L3 — Component / Software Requirement
What each component or software unit must do.
L4 — Unit / Verification-Level Requirement
Lowest atomic statement, verified by a single test or proof.
TFC — Test / Feature / Capability item
A verifiable feature slice that ties requirements to tests.
DID — Data Item Dictionary
Canonical names, types, and units for every data item.
ICD — Interface Control Document
Contract between two subsystems or with an external actor.
Defect — Anomaly / Problem Report
A recorded gap between specified and observed behavior.
Capability — Operational Outcome
An outcome the enterprise must be able to produce.
Review / SCCB — System Change Control Board
Governance forum that approves changes against a baseline.
V-Model — Verification & Validation Lifecycle
Left side decomposes; right side verifies at the same level.
BDD — Block Definition Diagram
Static structure: what blocks exist and how they relate.
IBD — Internal Block Diagram
How the parts inside one block are wired together.
Activity Diagram — Behavior as Flow
Step-by-step behavior with inputs, outputs, and decisions.
State Machine — Behavior as Modes
Discrete modes and the events that move between them.
Parametric Diagram — Constraints & Math
Equations binding value properties across blocks.
OV-1 — High-Level Operational Concept
Single picture of the operational concept.
SV-1 — Systems Interface Description
Which systems exist and how they are connected.
Mission Brief — Tasking → Plan → Brief
The output package crews use to execute the mission.
CV-1 — Capability Vision
The capabilities the enterprise intends to deliver.
CV-2 — Capability Taxonomy
Hierarchical breakdown of capabilities into sub-capabilities.
CV-3 — Capability Phasing
When each capability is planned to be delivered.
CV-6 — Capability-to-Operational Activities Mapping
Which capabilities deliver which operational activities.
SV-2 — Systems Resource Flow Description
Resource flows (data, materiel, energy) between systems.
SV-4 — Systems Functionality Description
Functions each system performs and how they interact.
SV-5 — Operational Activity to Systems Function Traceability
Matrix mapping operational activities to system functions.
SV-10 — Systems Rules, State Transitions, Event-Trace
Behavioral rules, state machines, and event sequences for systems.
Use-Case Diagram — Actors & Goals
Actors, the goals they pursue, and how use-cases relate.
IV&V — Independent Verification & Validation
An independent team verifies the developer's V&V.
MOE — Measure of Effectiveness
Mission-level measure of how well the operational outcome is achieved.
MOP — Measure of Performance
System-level measure of how well the system performs a function.
KPP — Key Performance Parameter
The few performance parameters whose failure is a program failure.
Risk Register — Identified Risks & Mitigations
Living list of risks with likelihood, impact, owner, and mitigation.