Start Methods for validating requirements

Methods for validating requirements

), I’ve developed some much more nimble requirements validation practices. And while sign-off is often thought of as the tried-and-true way to validate requirements, the reality is that every question you ask to ensure the completeness of your requirements and their link back to the business need is part of requirements validation.

is the verification of a product or system using models, calculations and testing equipment.

Analysis allows someone to make predictive statements about the typical performance of a product or system based on the confirmed test results of a sample set or by combining the outcome of individual tests to conclude something new about the product or system.

Many BAs, myself included, conflate requirements verification and validation.

(Here’s a challenge: Read the comments on the Requirements Verification post and see if you can find evidence of validation instead. We’re all learning here.) It wasn’t until I was deep in my preparation for the CBAP exam that the difference finally sunk in.

In my early days as a business analyst, my requirements verification and validation activities happened together, in a big room or an over-crowded small room with business and technical stakeholders walking through a draft of the requirements specification… In the detailed meetings with the entire stakeholder team, I was ensuring alignment of solution requirements and business requirements.

But since those early days, most of which involved big thick requirements documents and (yes, and) detailed use case specifications (oh, my, the documentation to validate and verify!

I will provide a description of each with two brief examples of how each could be used to verify the requirements for a car and a software application.

is the nondestructive examination of a product or system using one or more of the five senses (visual, auditory, olfactory, tactile, taste).

Other objectives of the requirements document are listed below.

Requirements validation is similar to requirements analysis as both processes review the gathered requirements.

Hence, it is desirable to detect errors in the requirements before the design and development of the software begins.