Benefit of written requirements

Like every management, requirements management generates an overhead. In order to remain on the „good side of the value-to-cost ratio“, the following chapter highlights the main benefits. Chapter 3. “Traps and cost driver“ shows the possibility to reduce costs. Okay, what's the benefit of systematic management of requirements?

Overview of the system

Documented requirements facilitate the overview of a system. This makes easier

• to check the completeness and
• to structure the system.

Knowledge transfer

As soon as systems have proved their right to exist for more than the first draft, it's important to reconsider the transfer of the acquired knowledge. Defining a common language and providing a concise overview, written requirements are the ideal starting point for new project staff to orientate.

Reminder

Also in a cooperative periphery, contracts have an added value as a reminder. In this regard, written requirements are very similar to a contract, as they fix the agreements. Consequently, some discussion will be brought to a more objective level and frustration will be avoided. A second important aspect is that you can make notes

• who requested this topic (and whom you have to talk to in case of a change)
• why the team has decided x-y (to avoid repeating discussions).

  Anchor point for acceptance tests

  As a supporter of TestFirst I am always looking for anchor points for acceptance tests. In this context, acceptance tests help to substantiate important requirements prior to the very first realization.

The demand for acceptance tests as an integral component help

• that the responsible person rethinks the requirements again,
• that the requirements get validated for a first time and
• that the consequences of a requirement are described again concretely.

Last but not least, acceptance tests are important as regression testing regarding the total span of life of the system

Explain to reflect

When I am faced with the task to explain my insights to another person, I often experience that these insights are not as clear as they seemed to be for me in advance. In such situations the picture in my mind changes regularly. According to my observation, there is a similar effect when writing down requirements. The aversion to write down requirements may be motivated in this mental work – and simultaneously emphasizes how necessary it is.