Use of Scenarios for Validation of Conceptual Specifications

The development of a large information system is generally regarded as one of the most complex activities undertaken by organisations. Boehm has reported that although only 6 percent of project's cost and between 9 and 12 percent of the project's duration is spent in the requirements phase, it costs between five and ten times more to repair errors during coding than during the requirements phase. Development and customer organisations could save a lot of time and money if they could detect and correct a fraction of the errors then, rather than later. This task is supported by the process of verification and validation of requirements specifications, which basic objectives are to identify and resolve software problems and highrisk issues early in the software life cycle. Verification and Validation activities produce their best results when performed as soon as possible and involve user feedback.

• https://dblp.org/pid/l/ValiLalioti.html