faa-req-handbook
FAA Requirements Engineering Management Handbook (DOT/FAA/AR-08/32)
Source: DOT/FAA (US Government work, public domain) | Chapters: 8
When to use
Use this skill when you must turn a fuzzy idea of an embedded control system into a complete, testable, change-tolerant requirements specification — and especially when system-level requirements have to hand off cleanly to software requirements. It is the avionics/medical-control complement to general requirements-writing craft: where domain-neutral guidance asks for "complete, consistent, clear" requirements, this Handbook shows the concrete machinery — typed monitored/controlled variables, validity status on every input, explicit latency and tolerance budgets, fail-safe modes, and rationale on every value. Pair it with the requirements-writing pack (sentence-level craft) and the safety packs (faa-system-safety, mil-std-882).
Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime.
How to Use This Skill
- Without arguments — load the core frameworks below: the eleven recommended practices, the monitored/controlled boundary, the functional architecture, the requirement structure (ideal value + tolerance + latency), and the four-variable model.
- With a topic — ask about a practice (e.g. "operational concepts", "environmental assumptions", "subsystem allocation"), a concept (e.g. "latency rationale", "mode confusion", "UNSPECIFIED", "four-variable model"), or one of the worked examples (Isolette, FCS/FGS/Autopilot).
- With a chapter —
ch02(boundary),ch03(operational concepts/assumptions),ch04(architecture),ch05(modes/detailed requirements),ch06(software/allocation),ch07(rationale),ch08(worked examples).
Supporting files: glossary.md, patterns.md, cheatsheet.md.
One criterion, eleven practices. The Handbook's quality bar is the Parnas criterion — specify everything needed for the correct system and nothing more — which reduces to "say what, not how." The eleven recommended practices are eleven ways to hit that bar for real-time embedded systems. It is a synthesis of prior work (SCR, the four-variable model, CoRE, RSML/RSML-e/SpecTRM, textual use cases), not a brand-new method, and it expects to be tailored.