Over the years, I’ve read, written, reviewed, and otherwise made use of a large variety of Requirements documents. Many were exercises in typing, some were a bare minimum to meet a checkbox, and others were useful tools. The latter ones are invaluable, and the others should be so, but aren’t due to process-heavy development cycles or teams just trying to “deliver the mail”.
Regardless of the type of Requirements document provided, it is important to not only understand the requirements, but to know how they might impact each other. Some of this requires experience, the rest just requires a little time.
I present three, out of many, situations that could have been avoided if a little attention had been applied to understanding the requirements.