Standard for Software Verification and Validation Plans
|Publication Date:||1 January 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 SVVPs
(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.
For critical software, this standard requires that minimum V&V tasks and their inputs and outputs be included in all SVVPs. For noncritical software, this standard does not specify minimum required V&V tasks; however, all other requirements of this standard shall be satisfied. This standard does recommend that the minimum V&V tasks for critical software also be employed for noncritical software. This standard defines optional V&V tasks that permit V&V planners to tailor an SVVP for a V&V effort. For critical software, the minimum tasks may be supplemented with tasks selected from the optional tasks. For noncritical software, tasks may be selected from the minimum and optional tasks.
Additional tasks identified by the user of this standard may be included in the SVVP for critical and noncritical software. The life cycle used in this standard serves as a model and consists of the following life-cycle phases:
(6) Installation and checkout
(7) Operation and maintenance Compliance with this standard does not require use of the life-cycle model presented here. If a different model is used, the SVVP shall include cross-references to this standard's life cycle and to the V&V tasks, inputs, and outputs specified here for each life-cycle phase.
This standard requires that the following be
(1) Verification and validation tasks
(2) Methods and criteria
(3) Inputs and outputs
(6) Risks and assumptions
(7) Roles and responsibilities
This standard requires a management effort that encompasses all life-cycle phases. The management section of the SVVP defines information necessary to manage and perform the V&V effort, and to coordinate V&V with other aspects of the project. The standard requires the SVVP to specify how the V&V results shall be documented in the Software Verification and Validation Report (SVVR).
When this standard is invoked for existing software, the SVVP shall describe how V&V will be performed when required inputs do not exist. The standard does not prohibit the incorporation of additional content into an SVVP. The SVVP standard derives its scope from ANSI/IEEE Std 730-1984 .l The SVVP standard may be applied in conjunction with, or independent of, other IEEE software engineering standards. This standard uses the definitions of ANSI/IEEE Std 729-1983 [i]. This SVVP standard contains V&V configuration analysis tasks that, in part or in whole, are reflected in ANSI! IEEE Std 828-1983 . Test documentation is compatible with that in ANSI/IEEE Std 829- 1983