Industries
Requirements for a small hardware team, before a standard asks for them
A small hardware team can keep its requirements, the reasons for them and the tests that prove them in OpenV from the first prototype. The hosted service is free for one person and one collaborator, and self-hosting is free for any number. OpenV does not import Excel, so a spreadsheet of requirements comes in as JSON or ReqIF or is entered again.
Updated by Desktop Machine Shop, the makers of OpenV.
What these teams keep
A start-up’s requirements usually begin as a spreadsheet and a slide. That works until a customer asks which requirements changed since the last build, an investor asks what is tested, or a certification body asks for traceability. Rebuilding the record at that point is slower than keeping it from the start.
Where it goes in OpenV
- Each requirement has a reference that never changes and a history of every version.
- User needs say why each requirement exists, and a need no requirement answers is on the gap list.
- Test cases and test runs show what has been tested and what passed.
- A baseline at each prototype build, and a comparison between two builds.
- A share link gives a customer or an investor a read-only view with no account.
- When a contract manufacturer or a design partner joins, they get a project of their own.
A first project
Enter the requirements of the next prototype only, with the test for each. Take a baseline when the build is frozen. At the next build, compare the two: that list of changes is what you would otherwise reconstruct from email.
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 Excel import: JSON and ReqIF only.
- No bill of materials, cost roll-up or supplier management.
- When a standard does apply to your product, read that sector’s page for what OpenV leaves to other tools.
- 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.
