Requirement Review Checklist

Requirement quality

• Single-purpose, testable statement
• Adds value beyond the parent requirement
• No vague language ("essential", "appropriate", "as needed")

Scope correctness

• Stays within Ground Systems scope
• Does not claim analytics or maintenance decision ownership

Ownership accuracy

• Does not imply ownership of Air Vehicle systems
• References FDR/CJP only as interfaces, not owned items

Interface accuracy

• Interfaces named correctly (e.g., Common Junction Panel)
• Direction of data flow is clear

Rationale completeness

• Explains why the requirement exists
• References applicable standards, AFIs, or program docs
• Captures SME-confirmed assumptions

Parent-child traceability

• Traces to the correct parent in the RV package
• Outdated parent links broken and reconnected

SME validation

• Mission reliability claims confirmed with Reliability Engineering
• Configuration preservation language confirmed with CM / Air Vehicle SME
• PSE / O-Level language confirmed with Product Support

Spelling and terminology

• Spell check completed
• Acronyms expanded on first use
• Consistent terminology with parent and sibling requirements