Techniques for validating requirements
In this lesson we will learn about software validation and verification, an aspect of project management in which requirements and processes of new software are analyzed to verify that the product meets certain specifications and functions correctly. A county library staff currently records all library transactions on a hand-written ledger - everything from lending materials to recording fine payments.
They would like to automate these manual processes through the use of a computerized system.
It may be performed on an iterative basis on every produced engineering element during development and may begin with the validation of the expressed stakeholder requirements.
When the validation process is applied to the system when completely integrated, it is often called final validation.
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!
In particular, during the development cycle of the system, the validation process is performed in parallel with the system definition and system realization processes and applies to any activity and product resulting from this activity.
The validation process is not limited to a phase at the end of system development, but generally occurs at the end of a set of life cycle tasks or activities, and always at the end of each milestone of a development project.
My views: Requirement verification is about ensuring that they are defined clearly and precisely to the extent that they can be designed, developed and tested.
In fact, very often I’ve found that an ambiguous requirement is ambiguous because the business value is unclear. But as I reflect more deeply on my requirements validation experience, walk-throughs, while the obvious candidates, don’t make up the half of it.
We might start debating the semantics of a term and discover we’re solving the wrong problem and end up throwing out the requirement completely. Before we even had a draft specification, I was meeting with the primary business stakeholder to iterate through potential requirements, understand the business value and fit them together in a logical way. The So in those early meetings with the sponsor, I was ensuring the alignment of stakeholder requirements and business requirements.
And still, in reality, the activities of validation and verification are often done together.
We might hold a requirements review and in the process discover ambiguous requirements (verification) and unneeded ones (validation).
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.