Ground Systems Requirement Owner
Requirement Owner Perspective
Holds long-term ownership of each decomposed Ground Systems requirement throughout its lifecycle in JAMA, including updates, verification linkage, and change control.
- Own the requirement in JAMA over its lifecycle
- Maintain quality, traceability, and verification linkage
- Approve changes and re-baselines
Primary responsibilities
- Take long-term ownership of decomposed requirements after JAMA entry.
- Ensure each requirement remains accurate as architecture, interfaces, and Product Support context evolve.
- Coordinate with verification owners to confirm the requirement is testable and traced to verification artifacts.
- Approve or reject change requests to the requirement text or allocation.
Day-to-day work activities
- Monitor JAMA notifications for changes to owned requirements, parents, or children.1
- Review change requests against scope, ownership, and ARB-approved naming/behavior.2
- Coordinate with the Verification owner to keep verification links current.3
- Refresh rationale when architecture or SME context shifts.4
- Participate in re-baseline events triggered by ARB or program review outcomes.5
Lifecycle stages owned
| Stage | Owner action | Approvers |
|---|---|---|
| Baseline entry | Accept handoff from author | Architect + Project Engineer |
| Steady state | Monitor and maintain | Owner |
| Change request | Evaluate and disposition | Architect (allocation) + SME (intent) |
| Re-baseline | Apply ARB-approved changes | ARB / CCB |
| Verification close-out | Confirm linkage and evidence | Verification owner |
Government approvals touched
- ARB approval for any scope, naming, or behavior change.
- Customer concurrence for changes affecting program-visible requirements.
- Verification closure evidence for audits and program reviews.
Deliverables
- Up-to-date JAMA records with correct parents, children, and rationale.
- Change history aligned with ARB decisions and SME confirmations.
- Verification linkage that closes the requirement loop.
Ownership checklist
- Requirement is in the correct JAMA location and baseline.
- Parent-child traceability is intact after any change.
- Rationale still reflects current architecture and SME context.
- Verification approach is identified.
- All change requests are reviewed against scope and ownership rules.