Role-Based Perspectives
How each discipline engages with Product Support requirement decomposition — work activities, requirements, architecture interaction, government approvals, reviews, and decision rights.
Why this section exists
Requirement decomposition crosses many disciplines. The same lower-level requirement looks different to a Systems Engineer writing the text, an Architect approving allocation, a Project Engineer tracking commitments, a Product Support SME validating intent, and downstream Integration or Reliability Engineers who must implement and verify it. This section makes each viewpoint explicit so collaboration is intentional rather than implied.
Roles covered
Systems Engineer
Authors and decomposes lower-level requirements; owns text quality, traceability, and rationale completeness.
System Architect
Confirms allocation, interfaces, and architectural coherence; protects ARB-approved naming and behavior.
Project Engineer
Tracks decomposition commitments, ARB milestones, JAMA readiness, and cross-team dependencies.
Product Support / SME
Validates intent for CBM+, Integrity, Reliability, and sustainment; supplies definitions and constraints.
Requirement Owner (Ground Systems)
Holds long-term ownership of each decomposed requirement and its lifecycle in JAMA.
Integration Engineer
Consumes requirements downstream; verifies they are implementable, testable, and interface-complete.
Reliability Engineer
Reviews reliability, maintainability, and Integrity-related decomposition with Mohammed and Feras.
Configuration / Data Manager
Preserves IDs, baselines, links, and digital-thread artifacts across decomposition cycles.
Common review and approval landscape
| Review / Gate | Purpose | Typical cadence |
|---|---|---|
| SME Review | Confirm intent and definitions | Per requirement batch |
| Architecture Review Board (ARB) | Approve naming, behavior, allocation | Scheduled cycle |
| JAMA Readiness Gate | Quality gate before JAMA entry | Continuous |
| Configuration Control Board (CCB) | Approve baseline changes | On change request |
| Test Readiness Review (TRR) | Authorize verification | Per campaign |
| Customer / Program Review (SRR, PDR, CDR) | Government concurrence | Program milestones |
Open the page that matches your role before an ARB or JAMA review. Each page describes work activities, requirements work, architecture touchpoints, government approvals, deliverables, decision rights, and a focused checklist.