F-35 MPE
Mission Planning Environment · v7.2.1
CALLSIGN
VIPER-01
ZULU
------Z
Legend MBSE CM REF NET
MBSE · DECOMPOSITION TEMPLATES

Requirements Decomposition Templates

Pick a requirement from the RTM, pick a template — use case, activity, or state machine — and get a live SysML skeleton plus a rendered diagram, ready to paste into CAMEO.

Step 1

Choose a requirement from your RTM

→ Open RTM
L0 · JROC / PEO · V&V D · Validated
Joint mission planning capability

The Joint Force shall plan, validate, and disseminate 5th-gen strike, ISR, EW, and SEAD/DEAD mission products within the 24-hour ATO cycle.

Step 2

Pick a template

Step 3

Fill in the template — Use Case Template

Preview

Live diagram (Mermaid)

⟦ SysML Snippet
Skeleton

SysML-style skeleton — paste into CAMEO

// Decomposition template: UC-TMPL
// Kind: Use Case
// Traces to: MPE-L0-001 — Joint mission planning capability

package "20_Behavior::UseCases" {
  useCase "Plan Sortie" satisfies MPE-L0-001
  actor "Mission Planner" -- "Plan Sortie"
  actor "Intel Officer" -- "Plan Sortie"
  "Plan Sortie" include "Validate Route"
  "Plan Sortie" extend  "Commit to DTC"
}
Traceability

How this links to your RTM

The generated skeleton opens with a satisfies MPE-L0-001 clause. In CAMEO, the SysML «satisfy» relationship makes the diagram appear in the requirement's derived-elements panel automatically — no manual bookkeeping. Confirm in the RTM that the requirement's status advances to Allocated once the block/behavior element is created.