IEEE 1012-1986

This standard has a threefold purpose: 1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs) 2) To define, for critical software, specific minimum verification and validation (V&V) tasks and their required inputs and outputs that shall be included in SVVPsi 3) To suggest optional V&V tasks to be used to tailor SVVPs as appropriate for the particular V&V effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses. This SVVP shall include V&V tasks to: 1) Verify that the products of each software life-cycle phase: a) Comply with previous life-cycle phase requirements and products (for example, for correctness, completeness, consistency, accuracy) b) Satisfy the standards, practices, and conventions of the phase c) Establish the proper basis for initiating the next life-cycle phase activities 2) Validate that the completed end product complies with established software and system requirements.



New IEEE Standard - Superseded. Uniform and minimum requirements for the format and content of software verification and validation (V&V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&V tasks to be used to tailor SVVPs as appropriate for the particular V&V effort are suggested. An overview of V&V is given, and life-cycle V&V, software V&V reporting, and V&V administrative procedures are covered.