Requirements management for hardware teams
Trace every requirement to the parts, tests and changes it depends on, so a changed part shows up before a build does.
100+ demos given. The first beta users are onboarded.
| ID | Requirement | Test | Status |
|---|---|---|---|
| REQ-112 | Housing holds 85 °C for 4 h | TH-04 | Verified |
| REQ-147 | Gear ratio holds at full load | LD-11 | Review |
| REQ-152 | Mounting holes match the frame | FT-02 | Verified |
| REQ-158 | Seal keeps dust out at IP54 | IP-01 | Not run |
REQ-147 needs reviewGH-3 moved from rev B to rev C. Its load test LD-11 has no result on rev C yet.
Every requirement, traced to its parts and tests
Each row is one requirement, with the part it depends on and the test that proves it. A row changes status when one of its links changes.
Requirements
1 needs review| ID | Requirement | Linked part | Linked test | Status |
|---|---|---|---|---|
| REQ-101 | Controller cuts output within 50 ms of power loss | Power module PM-220 | TST-012 Brown-out | Verified |
| REQ-112 | Housing holds 85 °C ambient for 4 h | Gearbox housing GH-3, rev B | TST-031 Thermal soak | Verified |
| REQ-147 | Gear ratio holds at full loadLinked part changed: GH-3 rev B to rev C | Gearbox housing GH-3, rev C | TST-044 Load run | Review |
| REQ-118 | Torque sensor reads within 1% from 0 to 40 Nm | Torque sensor TS-4 | TST-040 Calibration sweep | In progress |
| REQ-124 | Motor driver stops PWM on overcurrent | Motor driver MD-7 | TST-019 Overcurrent trip | Verified |
| REQ-131 | Harness passes the pre-scan on the bench | Wire harness H-2 | TST-052 Pre-scan | Open |
| REQ-152 | Status light visible from 5 m | Front panel FP-1 | TST-061 Visual check | Verified |
| REQ-160 | Boot loader rejects an unsigned image | Boot loader BL-2 | TST-070 Signature test | In progress |
| REQ-166 | Battery board holds 2 h runtime at 20 °C | Battery board BB-5 | TST-077 Runtime | Open |
A changed part flags what it breaks.
Each requirement linked to the changed part is marked for review, with the test that covers it.
Each requirement links to a part, a test and a change
Write the requirement
One statement, one owner, one status.
Link the part and the test
Parts come from the bill of materials. Tests come from the test plan.
Review when a link changes
A new part revision flags every requirement that uses it, and its test.
Book a demo with Josh
Josh, the founder, runs the demo himself. Bring a current project with a few requirements and the parts they link to.