Aerospace Requirements Decomposition & Traceability
Decompose aerospace requirements into traceable derived specs with compliance matrices
What You Can Do
You can systematically break down complex top-level system requirements into lower-level functional, performance, interface, and constraint requirements allocated to subsystems and components. Claude generates comprehensive traceability matrices that link customer requirements to derived requirements to verification methods, while automatically identifying conflicts, ambiguities, and infeasibilities before design begins—ensuring your requirements documentation is audit-ready for certification.
Features
automatically breaks top-level requirements into functional, performance, interface, and constraint categories with inheritance tracking
generates forward and reverse traceability linking customer → derived → verification requirements with compliance status
distributes performance budgets (weight, power, thermal, cost) across subsystems with margin tracking and allocation justification
maps requirements to DO-178C/DO-254/ARP4754A evidence items and provides regulatory alignment checklists
identifies requirement contradictions, undefined acceptance criteria, and testability gaps before design reviews
generates measurable, testable acceptance criteria with verification method assignment (analysis, test, inspection, demonstration)
traces requirement changes across the hierarchy to identify affected subsystems and verification activities
produces CDR-ready requirement genealogy with allocation justification and risk mitigation strategies
Example Output
Example 1: Software Requirement Decomposition (DO-178C Level A)
Input: "System shall automatically divert aircraft from hazardous weather"
Output:
-
Derived Requirement 1.1: Weather radar shall detect convective activity within 200 nm at ±5° bearing accuracy
- Allocation: Avionics subsystem
- Verification: Hardware-in-loop test (DO-178C objective 6.3.1d)
- Traceability: Customer Req 2.4.1 → Design Spec 3.2.1 → Test Case WDR-047
-
Derived Requirement 1.2: Flight management system shall compute diversion waypoints with <2 nm lateral error
- Allocation: Software component SWC_FMS_NAV
- Verification: Software unit test + integration test (DO-178C objectives 6.4.4.2, 6.5.1)
- Acceptance Criteria: 1000 test vectors, all pass within error margin
Example 2: Traceability Matrix (Partial)
| Customer Req | Derived Req | Subsystem | Ver. Method | DO-254 Evidence | Status |
|---|---|---|---|---|---|
| 2.4.1 Weather avoidance | 1.1 Radar detection | Avionics | HW Test | TSR-082, TR-156 | Allocated |
| 2.4.1 Weather avoidance | 1.2 FMS guidance | Software | SW Test | STP-034 | In Review |
Example 3: Allocation Table (Power Budget)
| Subsystem | Requirement | Allocated Power (W) | Margin (%) | Justification |
|---|---|---|---|---|
| Avionics | Continuous radar operation | 180 | 15% | Thermal analysis ATH-042 |
| Flight control | Actuator redundancy | 120 | 20% | Load case analysis FCA-156 |
What's Included
- SKILL.md instruction file with decomposition methodology and DO-178C/DO-254/ARP4754A compliance guidance:
- Requirement Decomposition Template: hierarchical requirement tree with derived requirement categories, allocation fields, and traceability references
- Traceability Matrix Framework: bidirectional matrix linking customer → derived → verification requirements with compliance status and evidence tags
- Allocation Table Checklist: performance budget allocation (weight, power, thermal, cost) with margin tracking and justification fields
- Compliance Verification Mapping: cross-reference tables for DO-178C Level A/B objectives, DO-254 design and production controls, and ARP4754A requirement rigor assignments
- Conflict Detection Checklist: questions to identify ambiguous acceptance criteria, untestable requirements, and allocation gaps before design reviews
Who It's For
- Systems Engineers — decomposing customer requirements and building traceability for design reviews and certification
- Requirements Managers — owning requirement genealogy, managing changes, and preparing compliance evidence for audits
- Certification/Compliance Engineers — mapping requirements to DO-178C/DO-254/ARP4754A objectives and generating audit-ready documentation
- Hardware/Software Design Leads — translating allocated requirements into design specifications and test plans
- Supply Chain/RFQ Managers — generating detailed design-input requirements for supplier RFQs and subcontract SOWs
Best For
- DO-178C Level A/B software certification — requirement allocation and traceability matrix generation with objective linkage
- DO-254 hardware certification — design-input requirement decomposition and verification method assignment
- ARP4754A system safety analysis integration — linking functional requirements to safety requirements and failure condition mitigation
- Design review preparation (PDR/CDR) — requirement genealogy, conflict resolution, and allocation justification documentation
- Requirement change management — impact analysis across derived requirements and verification activities
You might also like
You can rapidly validate FEA model inputs, boundary conditions, and mesh strategies before expensive simulations run. Claude analyzes your model documentation, interprets stress concentrations and failure predictions against design criteria, maps results to certification requirements (FAA Part 23/25, DO-254, MIL-STD-1916), and identifies root causes for convergence issues or anomalous results. This compresses the 20-30% of analysis time typically spent on verification and documentation.
by a7garden
You can rapidly examine thousands of instrumentation parameters across multiple test points to isolate unexpected behaviors and their origins. Claude structures the detective work: asking conditional questions about parameter relationships, flagging impossible states, isolating anomaly emergence moments, and building logical chains connecting symptoms to root causes. The output produces defensible technical justifications suitable for FAA or military certification packages and flight test reports.
by a7garden
You can analyze static and fatigue test data from aerospace components, distinguish between real failure modes and test artifacts, establish statistical confidence in results, and generate certification-ready engineering reports. The skill helps you interpret physical behavior under load, determine root causes of structural failures, and validate finite element predictions against test evidence—enabling design review boards and certification authorities to make informed decisions.
by a7garden
You can conduct rapid fatigue life assessments, apply damage tolerance principles per AC 25.571-1D methodology, and predict residual strength of aircraft structures under cyclic loading. This skill organizes fatigue data interpretation, applies appropriate failure theories, calculates safety margins, and documents analysis assumptions for certification compliance—reducing analysis time while maintaining the rigor required for structural certification and service life determination.
by a7garden
You can master professional podcast audio editing, mixing, and mastering workflows using Audacity with Claude-guided processes that transform raw recordings into broadcast-quality episodes. Claude provides step-by-step instructions for noise reduction, multi-track mixing, dynamic range control, and mastering optimization tailored to your podcast's mic setup and distribution requirements. Automate repetitive editing tasks and achieve consistent audio quality across entire episode catalogs.
by a7garden
You can systematically diagnose avionics system failures by organizing failure symptoms into decision frameworks that consider hardware, software, and environmental factors simultaneously. The skill generates failure logic trees, maps cross-system dependencies, and produces defensible root cause analysis reports that meet FAA/EASA certification requirements. This transforms ad-hoc troubleshooting into a repeatable, auditable methodology that accelerates fault isolation and supports occurrence reporting.
by a7garden
You can rapidly review FEA stress, strain, and displacement results to spot unrealistic outputs, correlate simulation predictions with test measurements, and identify when design changes or additional testing are warranted. This skill helps you build defensible evidence packages for certification authorities (FAA/EASA/NADCAP) by documenting the correlation between analysis and physical validation, reducing certification delays and safety risks.
by a7garden
You can analyze complex avionics test failures by feeding Claude multiple data streams—oscilloscope traces, BITE logs, CAN/ARINC 429 transcripts, and environmental parameters—to build diagnostic decision trees that prioritize root causes based on failure signatures. Claude helps you cross-reference specifications against observed behavior, identify design-versus-implementation gaps, and generate testable hypotheses with step-by-step verification procedures that accelerate failure resolution across multi-LRU (Line Replaceable Unit) systems.
by a7garden