Request a firmware review
Menu
Founders and first firmware hires scoping a device's firmware

Write firmware requirements you can test

Each row is one requirement, how you will prove it and who owns it. Edit the example rows, add your own and download a CSV for your team.

Key characteristics

Columns
ID, requirement, type, priority, how we verify it, owner
Output
Editable table, CSV download, print
Default example
Six fictional rows for the LW-1 soil probe
Runs
In your browser with nothing sent

Worksheet: Write firmware requirements you can test

The rows are a fictional example. Edit any cell, add or remove rows, then download a CSV for your team. Nothing leaves your browser.

IDRequirementTypePriorityHow we verify itOwnerRemove

A firmware requirement is only useful if someone can check it. “Long battery life” starts arguments. “Runs 3 years on two AA lithium cells, verified by measured average current on 5 boards” ends them. This worksheet keeps each requirement in one row with its type, its priority, the test that proves it and the person who owns it. It is the table we ask for at the start of a firmware review, and the one that keeps growing through the build.

How to use it

  1. Replace the example rows with your own, or add rows below them.
  2. Write each requirement as something the firmware does, with a number wherever one applies.
  3. Fill in how you will verify it before you call the row done. If you cannot think of a test, the requirement needs rewriting.
  4. Download the CSV and keep it with the project, or print it for a review meeting.

What each column means

Column What to write
ID A stable label such as FW-001. Never reuse an ID, so test reports and tickets can point to it
Requirement One behavior with a number and a condition: what, how much, how often, in what environment
Type Function, Power, Update, Security, Connectivity, Manufacturing or Regulatory, so gaps show at a glance
Priority Must, Should or Could. Must means the product does not ship without it
How we verify it The test, the sample size and the pass condition
Owner The team or person who answers for it, not necessarily whoever writes the code

Reading the default example

Example (fictional). Loamwick’s first six requirements for the LW-1 soil probe. Four are Musts owned by firmware. FW-001: read soil moisture and temperature every 5 minutes, verified by a bench test against a reference probe for 72 hours. FW-002: run 3 years on two AA lithium cells, verified by measured average current on 5 boards and the battery life calculator. FW-003: accept signed updates from the gateway and roll back on a failed self-test, verified by an interrupted-update test that pulls power at 10 points in the transfer. FW-004: refuse images not signed with the production key, verified by trying an image signed with a test key, which the device must refuse. Two are Shoulds. FW-005: reconnect to the gateway within 10 minutes after it restarts, verified by restarting the gateway 20 times and logging reconnect times (owner: firmware). FW-006: finish the factory test in under 60 seconds per probe, verified by timing 50 boards on the test fixture (owner: operations).

What the example does well: every row has a number, and every test has a sample size. FW-002 ties a power target to a measurement and a calculation, so the battery life calculator becomes a way to track the budget, not a one-off guess. FW-003 and FW-004 make the update path a requirement from the first week, which is the only time it is cheap. FW-006 belongs to operations, because a slow factory test is a cost problem before it is a firmware problem.

What it leaves for later: there is no Regulatory row yet. Before the trial turns into a product, Loamwick would add rows for the radio test modes a certification lab needs and for any security baseline its markets require. NIST IR 8259 Rev. 1, published in April 2026, describes cybersecurity activities manufacturers should consider before their IoT products are sold, and is a useful source of Security rows.

How the worksheet works

There is no calculation. Each row is a set of text fields and two drop-down lists. You can add and remove rows, and Download CSV saves exactly what is on screen, so the file opens in a spreadsheet or imports into an issue tracker. Nothing is stored after you leave the page.

Limits

  • A list, not a specification. Large products need traceability from requirement to design to test that a spreadsheet will not hold for long. For a first product, a well-kept sheet is usually enough to start.
  • Too many Musts. If most rows are Musts, the priority column has stopped helping you decide anything.
  • Regulated products need more. Medical devices and some other markets expect formal requirements and verification records. This sheet can be a starting point, not the record itself.
  • Requirements change. Date the file each time you download it, and keep the old copies.

What to do next

Requirements feed the decisions that follow. The RTOS selection worksheet uses them to weight criteria, and the update policy worksheet turns the update rows into rules with owners. Our firmware development work starts from a sheet like this, and the engagements page lists what you provide at the start. More in the firmware architecture section of Field Update.

Send us your board and your plan.

A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.