How to write good requirments | Atomic Spin

Requirements are pretty ubiquitous in the embedded world. They are used to define tasks, help coordinate large development efforts, and to communicate the behavior of the desired end product between the developers and the customer. When done right, requirements can be very useful. Unfortunately, if you spend much time working in the embedded world you quickly discover that there are a lot of bad requirements. And then when you try to go fix them, you quickly discover that writing good requirements is hard. Here are some tips that will hopefully make the process more clear:

At a high level, the purpose of requirements is to provide a useful description of the desired behavior of a blackbox system that is detailed enough that:

  • An engineer can make an implementation of said system.
  • A tester could verify that a given device satisfies the requirements (without talking to the engineer)
  • The resulting system satisfies the desires of the end user.

this is a great article.

check the tips How to write good requirments | Atomic Spin.