Each requirement you write represents a single market need, that you either satisfy or fail to satisfy. A well written requirement is independently deliverable and represents an incremental increase in the value of your software. That is the definition of an atomic requirement. Read on to see why atomic requirements are important.
As part of the ongoing series, Writing Good Requirements – The Big Ten Rules, I wrote about the importance of atomic requirements first in 2006. That article touched on only one aspect of atomic requirements – being able to ask “is it done?”
Writing atomic requirements is important from two perspectives – delivering value to your customers, and operating efficiently. You get benefits both operationally,...read more