OpenV holds what your product must do, why, and the evidence that it does. Every artifact has a stable reference, a history and typed links, so you can see what changed and what the change affects.
Requirements and traceability
Write requirements, user needs, design items, hazards and test cases, each with a reference that never changes. Link them by type, and OpenV flags a link for review when either end changes. Every version is kept, and a baseline freezes the project as it stood.
Verification evidence
Record a test run, and each result counts for the requirements its test case verifies. Coverage, the gap list and the traceability matrix follow the links as you change them. The V&V status downloads as a PDF.
Agents with human review
An agent reads your project through a fixed set of tools and writes back as proposals, which you approve or reject one by one. Start a run from a card on the board, on a schedule, or when something happens in the project.
Stakeholder interviews
Send a stakeholder a link. An interviewer agent asks what they need and records each answer as a draft user need for your team to review.
Documents and hand-over
Download a specification as PDF or Word with the sections, fields and evidence you choose, from the live project or from a baseline. Exchange ReqIF with a customer’s tool. Send a share link to someone who only needs to read.
Programmes with subsystems and suppliers
Give each subsystem and each supplier a project of its own under the main one. Their requirements refine the ones above, and their test results count toward them. Each artifact names its owner, so it is clear who is responsible for what.