System Architect
System Architect Perspective
Ensures decomposed requirements fit the Ground Systems architecture, respect interface boundaries, and align with the ARB-approved direction.
- Confirm allocation and architectural fit
- Protect interface and boundary integrity
- Keep CBM+ / Integrity / Data Collection naming consistent
Primary responsibilities
- Validate that each lower-level requirement allocates to the correct Ground Systems element.
- Maintain architectural coherence across CBM+, Integrity Programs, Data Collection, Instrumentation, and Product Support functions.
- Preserve generalized naming and behavior agreed at ARB.
- Flag requirements that imply Air Vehicle ownership or analytics performed by other teams.
Day-to-day work activities
- Review the architecture description and Level 4 element list before each decomposition batch.1
- Sit with Systems Engineers during drafting to allocate each requirement to a single element.2
- Maintain the generalized naming/behavior package that goes to ARB.3
- Prepare ARB submissions: naming changes, behavior generalizations, new interfaces, removed CBM+-only language.4
- Disposition ARB comments and update architecture artifacts before requirements re-enter JAMA review.5
- Audit JAMA periodically for drift between requirement allocation and the architecture baseline.6
Architecture artifacts owned
| Artifact | Purpose | Update trigger |
|---|---|---|
| Ground Systems architecture description | Canonical names, behaviors, scope | ARB-approved change |
| Level 4 element decomposition | Allocation targets for requirements | New element or scope shift |
| Interface catalog (CJP, FDR adjacency, PSE) | Defines integration boundaries | Interface change or addition |
| Naming/behavior generalization log | Tracks CBM+ → broader-term updates | Each ARB cycle |
Government approvals and reviews
| Review | Architect role | Inputs | Outcome |
|---|---|---|---|
| ARB | Presenter / approver | Naming, behavior, allocation changes | Approved baseline used in JAMA |
| Pre-ARB technical walkthrough | Author | Draft architecture deltas | Reduces ARB rework |
| JAMA Readiness Gate | Allocation approver | Allocated requirement list | Allocation signed off |
| Customer architecture review | Co-presenter with PM | Approved architecture description | Government concurrence |
Deliverables
- Architecture allocation decisions for each decomposed requirement.
- Updated architecture descriptions (post-ARB) reflecting generalized naming and behavior.
- Interface contracts that requirement authors can cite in rationale.
- ARB submission packages and decision minutes.
Dependencies
Needs from others
- Draft requirements from Systems Engineers.
- SME confirmation of operational intent.
- ARB feedback on naming and behavior changes.
Provides to others
- Allocation and boundary guidance.
- Approved architectural descriptions for use in rationale.
- Escalation when a requirement breaks the model.
Decision rights
- Allocation of a requirement to a Ground Systems element.
- Acceptance or rejection of naming/behavior changes prior to ARB.
- Approval of interface changes affecting multiple consumers.
Architectural review checklist
- Requirement allocates to a defined Ground Systems element.
- Naming uses generalized terms aligned with the ARB update.
- No implicit Air Vehicle scope creep.
- Interfaces referenced exist or are tracked as architectural work.
- CBM+, Integrity, and Data Collection behaviors remain functionally consistent.