A requirements database that lives in your wiki. DOORS, without the DOORS.
What it does
- Requirements live as pages in your space, next to the docs that explain them.
- Typed fields, so every item carries what your standard asks for.
- Starter templates for DO-178C, DO-254, ARP4754A, ECSS and UAS SORA.
- Trace links between items, with a verification matrix derived from them.
- Change an item and every trace touching it is flagged for review.
- Baselines you can freeze and compare.
The compliance matrix
One row per requirement, the verification method it is claimed under, its safety classification, and what is missing. The matrix is derived from your items and their links, so there is nothing to keep in sync by hand.
Edit a requirement and every trace touching it is flagged as suspect, so a link nobody has re-reviewed shows up as an open issue instead of passing quietly.
Requirements beside the documents that justify them
The trade study behind a requirement, the interface it constrains and the procedure that verifies it are all documents. In a dedicated requirements tool they sit behind a different login, at a different version.
Here a trace link points at a page in the same space, and one search covers your requirements and your engineering notes together.
Start from your standard
A new collection adopts a preset and inherits its whole vocabulary: the status chain, the verification methods that standard recognizes, the safety classification scheme, and the fields that have to be filled in. Adopt the spacecraft preset and the four ECSS verification methods are the only ones the collection will accept.
Presets are copied into your collection rather than referenced, so a later change to a shipped preset cannot invalidate work you have already done.
