Verifying and validating software requirements and design specifications
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.
Requirements engineering (RE) is perceived as an area of growing importance. the agreement dimension Looking at the RE research using this framework, the different approaches can be classified and therefore their interrelationships become much clearer.
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.
The purpose of this paper is to identify the main goals to be reached during the requirements engineering process in order to develop a framework for RE. This work was supported by ESPRIT Basic Research Action 6353 (NATURE) which is concerned with Novel Approaches to Theories Underlying Requirements Engineering and by the state Nordrhein-Westfalen, Germany.
1 Introduction There is general agreement among softwa...
These ideas have been implemented in REM, an experimental requirements management tool that is also described in this paper.