Industries
A requirements baseline and a verification matrix for space projects
A space project can keep its requirements by segment and sub-system in OpenV, with a verification method and status on each one and a baseline at every review. The plan holds the reviews as milestones and shows them for every sub-system on one chart. OpenV’s verification methods are test, analysis, inspection and demonstration, so a project using the ECSS method “review of design” records it under one of those by its own convention.
Updated by Desktop Machine Shop, the makers of OpenV.
What these teams keep
ECSS and NASA practice both ask for a requirements baseline that flows down from mission to segment to sub-system, a verification matrix that gives the method and the status of every requirement, and a set of reviews at which the baseline is agreed. Small teams and university missions need the same, with far fewer people.
Where it goes in OpenV
- A project for the mission and a child for each segment and sub-system, with requirements that refine the level above.
- The verification method is a field on every requirement, and a requirement without one is on the gap list.
- The V&V status report is the verification matrix: each requirement, its method, its test cases and their latest result.
- Milestones for the requirements, preliminary and critical design reviews, each able to wait for requirements to be approved or verified.
- A baseline at each review and a document from it for the review board.
- Self-hosting keeps the data on your own network.
A first project
Put one sub-system’s requirements in, set the method on each, and link the tests you already have. The gap list then shows what the next review would ask about. A CubeSat team can do the whole mission this way in an afternoon.
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 verification control document template in an ECSS layout; the V&V status report has OpenV’s own layout.
- No “review of design” verification method of its own.
- No mass, power or link budgets: OpenV keeps requirements and evidence, not engineering budgets.
- 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.
