REQUIREMENTS L0–L6

Requirements Decomposition — Enterprise to Class

The F-35 MPE requirements stack from joint capability need (L0) down to value-type constraints in the Data Item Dictionary (L6). Each tier identifies its stage, owning role, controlling artifact, gate review, and worked examples with derive / satisfy / verify traceability.

◤ TOC

Levels at a glance

L0 · Enterprise L1 · System-of-Systems L2 · System Requirements (MPE)L3 · Segment L4 · Component L5 · Unit L6 · Class DID Template ▸Role Coverage ▸

◤ Editor

Interactive Requirements Editor (L0–L6)

Create, edit, and delete requirements at any tier. Stage / artifact / owner / gate auto-fill from the selected level and can be overridden. Stored locally in your browser.

No requirements match. Add one with “+ New Requirement”.

◤ Decomposition

L0 → L6 derive/verify fabric

⟦ SysML Snippet — Top-down derive (capability → constraint); bottom-up verify (constraint → capability) ⟧

◤ Stage Gates

Where each level is baselined

Gate	Meaning
MDD	Materiel Development Decision — accept L0 capability need
MS-A	Milestone A — L1 stakeholder reqs baselined, enter TMRR
SRR	System Requirements Review — L2 SyRS baselined
MS-B	Milestone B — enter EMD with baselined SyRS
SFR	System Functional Review — functional decomposition to L3 complete
PDR	Preliminary Design Review — L3 SRS/IRS allocated to design blocks
CDR	Critical Design Review — L4 component reqs + SSDD baselined
TRR	Test Readiness Review — verification suite covers L2–L5
FCA	Functional Configuration Audit — every L2–L4 req has Verify evidence
PCA	Physical Configuration Audit — baselined model + code + DID align
MS-C	Milestone C — production / fielding decision

◤ L0 · Enterprise / Mission Need

Stage

Concept Exploration (Pre-MDD → MDD)

Artifact

Initial Capabilities Document (ICD), Mission Needs Statement

Owner

JROC / Service Sponsor / PEO

Gate

Materiel Development Decision (MDD)

Capability-level intent. Frames the MPE inside the joint warfighting enterprise. No solution form yet — only outcomes and measures of effectiveness.

Example Requirements

ENT-0001
The Joint Force shall plan and execute 5th-gen strike, ISR, EW, and SEAD/DEAD missions with coalition partners across all theaters.
ENT-0007
Mission planning shall be executable inside the 24-hour ATO cycle for all fielded F-35 variants and partner nations.

◤ L1 · System-of-Systems / Stakeholder Requirements

Stage

Materiel Solution Analysis (MSA)

Artifact

Capability Development Document (CDD), Stakeholder Requirements Spec (StRS)

Owner

Program Office / Lead Systems Integrator

Gate

Milestone A — Tech Maturation & Risk Reduction entry

Stakeholder needs across the SoS: MPE ↔ Air Vehicle, ALIS/ODIN, TR-SIM, Ground Security, Reprogramming Labs. Allocates capability among peer systems.

Example Requirements

STK-0014· derive ← ENT-0001
The MPE shall produce a complete Mission Data Load (MDL) for the F-35 Block configuration in use, releasable to the requesting partner nation.
STK-0022· derive ← ENT-0007
The MPE shall exchange sustainment data with ALIS/ODIN bidirectionally within one mission turn.

◤ L2 · System Requirements (MPE)

Stage

Technology Maturation & Risk Reduction (TMRR)

Artifact

System Requirements Specification (SyRS)

Owner

MPE Systems Engineering / Lead Architect

Gate

Milestone B — Engineering & Manufacturing Development entry

MPE as a single system: top-level functional, performance, interface, and security requirements. Bounded by SoS allocations from L1.

Example Requirements

SyRS-MPE-0031· derive ← STK-0014; satisfy → TFCS
The MPE shall ingest, validate, classify, and label all trusted files per the Trusted File Classification Specification (TFCS).
SyRS-MPE-0044· derive ← STK-0014
The MPE shall plan MADL, Link-16, and SATCOM participation for a 4-ship to 8-ship package with deterministic time-slot allocation.
SyRS-MPE-0058· derive ← STK-0014
The MPE shall apply NIST SP 800-53 moderate baseline controls; classified handling shall apply CNSSI 1253 overlays.

◤ L3 · Segment / Subsystem Requirements

Stage

EMD — Preliminary Design (SFR → PDR)

Artifact

Software / Subsystem Requirements Spec (SRS), Interface Requirements Spec (IRS)

Owner

Segment Lead (UPC, MDF Pipeline, Crypto Planner, Output Builder, Debrief)

Gate

Preliminary Design Review (PDR)

Decomposes each MPE segment. Pairs each SRS with the IRS that governs its external interfaces. First level where requirements bind to design blocks (L3 BDD).

Example Requirements

SRS-EW-0214· derive ← SyRS-MPE-0031; satisfy → ThreatLibraryService
The MDF Compiler shall ingest emitter records conforming to the ThreatRecord schema and produce a signed MDL within 30 minutes for a full theater library.
SRS-DC-0044· derive ← SyRS-MPE-0044
The Datalink Planner shall allocate MADL time slots for up to 8 participants without collision across a 60-minute mission window.
IRS-MDF-0031· satisfy → InterfaceBlock ICD_ThreatLib_v3
The MDF Pipeline shall expose a signed-package interface (manifest + SHA-256 + signer DN) to the Distribution Adapter.

◤ L4 · Component / CSCI Requirements

Stage

EMD — Detailed Design (PDR → CDR)

Artifact

Software Subsystem Design Document (SSDD), Component SRS

Owner

Software Lead per CSCI

Gate

Critical Design Review (CDR)

Allocates L3 requirements onto specific CSCIs / services / libraries. Adds component-internal performance, error-handling, and resource budgets.

Example Requirements

SRS-EW-0214.1· derive ← SRS-EW-0214
The Threat Library Service shall accept ThreatRecord deltas via gRPC and reject any record failing schema validation, returning a structured error.
SRS-EW-0214.2· derive ← SRS-EW-0214
The Signing Service shall sign MDL manifests using FIPS-validated SHA-256 + RSA-3072 within 2 seconds per manifest.
SRS-DC-0044.1· derive ← SRS-DC-0044
The Time-Slot Allocator shall produce a deconfliction proof when scheduling more than 4 participants.

◤ L5 · Unit / Module Requirements

Stage

EMD — Code & Unit Test

Artifact

Unit Design Notes, Code Comments-as-Spec, Unit Test Plan

Owner

Developer / Module Owner

Gate

Unit Test Complete (code review + CI green)

Module-level behavior. Each unit requirement is verified by ≥1 unit test. This is the lowest tier still tracked in the requirements tool; below this is code.

Example Requirements

SRS-EW-0214.1.a· derive ← SRS-EW-0214.1; verify → TC-EW-0098-u14
ThreatRecordValidator.validate(record) shall return ValidationResult{ok=false, code='POLARIZATION_MISSING'} when polarization is null on a radar emitter.
SRS-EW-0214.2.a· derive ← SRS-EW-0214.2
Signer.sign(manifest) shall fail-closed if KMI key handle is not Active.
SRS-DC-0044.1.a· derive ← SRS-DC-0044.1
SlotAllocator.deconflict(plan) shall be deterministic given identical inputs (no wall-clock or RNG dependence).

◤ L6 · Class / Data-Item Constraints

Stage

EMD — Implementation

Artifact

DID entries, ValueType constraints, Enum invariants

Owner

Data Steward / Module Owner

Gate

Validation rules pass (model + code)

Implementation-level constraints on classes, value types, and enumerations — the contract enforced by both the SysML model (12_Library) and the code. Lives in the Data Item Dictionary.

Example Requirements

DID-0142.c1· derive ← SRS-EW-0214.1.a; satisfy → DID-0142
ThreatRecord.frequencyMHz ∈ [30, 40000]; values outside the range shall be rejected at parse time.
DID-0098.c1· satisfy → DID-0098
CryptoKeyMaterial.length ∈ {128, 192, 256, 384, 512, 1024, 2048, 3072, 4096} bytes; any other length is invalid.
DID-0203.c1· satisfy → DID-0203
MADLTimeSlot.value ∈ [0, 127] and shall be unique within a participant group.

◤ Rules

Traceability invariants every requirement must hold

▸Every L1–L5 requirement has ≥1 derive link to its parent tier.
▸Every L2–L5 requirement has ≥1 verify link (test case or analysis).
▸Every L3+ requirement has ≥1 satisfy link to a design block (BDD/IBD).
▸L6 constraints are owned by the DID and enforced by both model validation and code.
▸No orphan requirements — Cameo validation rejects any node missing required links.
▸Baseline tags are taken at each gate (SRR, PDR, CDR, FCA, PCA) on Teamwork Cloud.