Requirements Gathering Reading
How do you read documents looking for Business Requirements?

Relevant material will probably be comprised of a combination of hard copy and soft copy documents and will include such items as procedures, contracts, guidelines, RFPs (requests for proposal), and SOWs (statements of work).

We have already discussed the proper method for writing Good Business Requirements. However, you will find that the documentation used does not always follow the prescribed method. You need to read documentation with an analytical eye. Requirements Gathering Reading is an active process that often requires the reader to look beyond the obvious messages and read "between the lines."

Consider the following statement:

In Business Requirements language, the need would be defined as follows:

As you can see, Business Requirements are often hidden within problems but may still be recognized and redefined.

Requirements Gathering Reading also requires other levels of analysis. As with any part of the Requirements Gathering process, you have to able to differentiate between functional and non-functional requirements.

Further, you must determine whether the requirements apply to current and future needs.

Finally, while it may seem obvious, remember to record your findings as you read. Even if you highlight relevant passages, keep a master list that refers to the location of each passage. You can always "flesh out" the list after all your reading is complete.

ClearlyPUT's Requirementing process uses requirements gathering reading to discover requirements.

Summary

Gather all the necessary documentation before you begin Requirements Gathering Reading. Relevant material will probably be comprised of a combination of hard copy and soft copy documents. Good Business Requirements will likely be hidden inside the language of problems rather than solutions. Check the uncovered requirements for current and future relevance. Remember to record your findings as you read.

Requirementing Steps