Software verification and validation

In software project management, software testing, and software engineering, verification and validation (V&V) is the process of checking that a software system meets specifications and that it fulfills its intended purpose. It may also be referred to as software quality control. It is normally the responsibility of software testers as part of the software development lifecycle. In simple terms, software verification is: 'Assuming we should build X, does our software achieve its goals without any bugs or gaps?' On the other hand, software validation is: 'Was X what we should have built? Does X meet the high level requirements?'ISVV PlanningRequirements VerificationDesign VerificationCode VerificationValidation In software project management, software testing, and software engineering, verification and validation (V&V) is the process of checking that a software system meets specifications and that it fulfills its intended purpose. It may also be referred to as software quality control. It is normally the responsibility of software testers as part of the software development lifecycle. In simple terms, software verification is: 'Assuming we should build X, does our software achieve its goals without any bugs or gaps?' On the other hand, software validation is: 'Was X what we should have built? Does X meet the high level requirements?' Verification and validation are not the same things, although they are often confused. Boehm succinctly expressed the difference as 'Building the product right' checks that the specifications are correctly implemented by the system while 'building the right product' refers back to the user's needs. In some contexts, it is required to have written requirements for both as well as formal procedures or protocols for determining compliance.

[ "Software construction" ]
Parent Topic
Child Topic
    No Parent Topic