Industries
Requirements, flow-down and verification evidence for aerospace and defence programmes
An aerospace programme can keep each level of its requirements in its own OpenV project, with each requirement tracing up to the one it refines and down to the test that verifies it. Suppliers work in their own project and see only what they are given. OpenV is not qualified as a tool under DO-330 and does not trace to source code or structural coverage, so it holds the requirements and verification record and leaves those to other tools.
Updated by Desktop Machine Shop, the makers of OpenV.
What these teams keep
Teams working to ARP4754A, DO-178C and DO-254 keep requirements at several levels, from the aircraft or system down to software and hardware items, with traceability in both directions between the levels and from each requirement to its verification. They show that every requirement is verified, that nothing is implemented without a requirement, and that the configuration reviewed is the configuration delivered.
Where it goes in OpenV
- One project per level or per item, filed under its parent. A requirement in a child project refines one in the parent, and the link is visible from both.
- A supplier is a member of its own project with read access to the parent, and nothing else of the programme.
- Each requirement carries a verification method: test, analysis, inspection or demonstration. Test runs record results against test cases, with evidence files attached.
- A parent requirement shows the verification of the requirements that refine it, so coverage rolls up from the items to the system.
- Baselines freeze the project at a review. Two baselines compare to a list of what changed.
- The plan holds the reviews as milestones, and a milestone can wait for requirements to be approved or verified.
- ReqIF import and export for exchange with a customer or supplier.
A first project
Take one item and its parent system. Put the system requirements in one project and the item requirements in a child, link them, add the test cases, and record one test run. Then open the gap list in both projects and download the parent as a PDF from a baseline. That is the record a review would see.
What OpenV does not do
- No certification, no tool qualification kit and no claim of compliance with any standard named on this page. OpenV holds the record; your process and your assessor decide whether it is enough.
- No traceability to source code, object code or structural coverage results. Low-level requirements can be recorded; the code they trace to cannot.
- No enforced independence between the author and the reviewer of an artifact.
- ReqIF has been tested between OpenV instances only, not yet against DOORS or Polarion.
- No electronic signatures, and no separate approver role: any project editor can approve, including their own change.
- OpenV is in alpha: screens still change between releases, though data, exports and the API stay compatible across stable releases.
