Verifying validating software requirements design specifications
The main reason for doing this is indicated in Figure 1, (1).It shows that savings of up to 100:1 are possible by finding and fixing problems early rather than late in the life-cycle.It does not do something “how” it is supposed to do it.Classification of methods In mission-critical software systems, where flawless performance is absolutely necessary, formal methods may be used to ensure the correct operation of a system.
Failure – the manifestation of a fault during execution. The software was not efficient (it took too many resources such as CPU cycles, it used too much memory, performed too many I/O operations, etc.), it was not usable, it was not reliable, etc.This paper presents the following guideline information on verification and validation (V&V) of software requirements and design specifications: Definitions of the terms "verification " and "validation, " and an explanation of their context in the software life-cycle; A description of the basic sequence of functions performed during software requirements and design V&V An explanation, with examples: of the major software requirements and design V&V criteria: completeness, consistency, feasibility, and testability; An evaluation of the relative cost and effectiveness of the major software requirements and design V&V techniques with respect to the above criteria; An example V&V checklist for software system reliability and availability.