Writing a Hardware Requirements Specification Engineers Can Use
A hardware requirements specification is the contract between the people who want a product and the people who build it. When it is vague, design decisions are made by default and the arguments happen at the end. When it is precise, the design has a target and the test plan almost writes itself. This article explains how to write requirements that are clear, measurable and complete enough to design against.
At a glance
- Shall
- The conventional word for a mandatory requirement; “should” marks a goal.
- Measurable
- Each requirement states a value, a condition and a tolerance that a test can check.
- Unique ID
- A permanent identifier, so each requirement can be traced to design and test.
- Rationale
- A short note on why the requirement exists, which helps when trade-offs arise.
The problem
Phrases such as “long battery life”, “rugged” or “low cost” feel like requirements but cannot be designed or tested. Each engineer fills the gap with an assumption, and the assumptions rarely agree.
The other common gap is missing conditions. A current limit means little without the supply voltage and temperature, and an accuracy figure is incomplete without the range over which it applies.
If a requirement cannot be tested, it is a hope, and hopes are expensive to discover at the end of a project.
Anatomy of a good requirement
A usable requirement states one thing, uses “shall”, gives a number with units and tolerance, and names the conditions: supply range, temperature, load or operating mode. “The device shall operate from 9 to 36 V DC across -20 to +60 °C ambient” can be designed and tested; “wide input range” cannot.
Separate what the product must do from how it does it. “Shall communicate with a phone within 10 m” leaves room for engineering; “shall use chip X” closes it, and belongs only where there is a real reason, recorded as the rationale.
What good looks like
Collect requirements by category: function, electrical, environmental, mechanical, regulatory, cost and lifetime. Gaps show up as empty categories.
Rewrite each one as a single measurable statement with conditions, an identifier and a rationale.
Review the specification with design and test engineers, and add a verification method to each requirement before design starts.
| Vague | Testable | |
|---|---|---|
| Battery life | Long battery life | At least 12 months at one report per hour |
| Environment | Works outdoors | -20 to +60 °C, IP65 enclosure |
| Power input | Wide input range | 9 to 36 V DC, reverse polarity protected |
| Connectivity | Wireless | Bluetooth LE to a phone at 10 m line of sight |
| Category | Examples | Often forgotten |
|---|---|---|
| Functional | Inputs, outputs, modes, interfaces | Behaviour on fault or power loss |
| Electrical | Supply range, current, accuracy | Start-up, brown-out and transients |
| Environmental | Temperature, humidity, ingress, vibration | Storage and transport conditions |
| Mechanical | Size, mass, connectors, mounting | Service access and cable routing |
| Regulatory | Safety, EMC, radio, markets | Labelling and documentation |
| Commercial | Unit cost, volume, product lifetime | Component availability over the lifetime |
What it changes
Clear Targets
Engineers design to stated numbers instead of private assumptions.
Testable Results
Each requirement maps to a test that shows it was met.
Controlled Change
Identified requirements make the impact of a change visible.
Fewer Disputes
Everyone agrees at the start what finished means.
Where to go next
Keep the specification under revision control and record every change with a reason. It is a living document until the design is frozen.
Include the regulatory markets early. Standards for safety, emissions and radio bring their own requirements that shape the design.
Problems this prevents
- Requirements that no test can check
- Limits stated without operating conditions
- Solutions specified in place of needs
- Missing categories found late in the project
Discuss your project
Email support@aavico.com or use Get in Touch when the website finishes loading.