IEEE Std 1059-1993 IEEE Guide for Software Verification and Validation Plans -Description

Abstract: Guidance in preparing Software Verification and Validation Plans (SVVPs) that comply with IEEE Std 1012-1986 are provided. IEEE Std 1012-1986 specifies the required content for an SVVP. This guide recommends approaches to Verification and Validation (VampV) planning. This guide does not present requirements beyond those stated in IEEE Std 1012-1986.

Keywords: baseline change assessment, life cycle phases, master schedule, VampV tasks

Content

• 1. Overview
• • 1.1 Scope
• 1. References
• 3. Conventions, definitions, and acronyms and abbreviations
• • 3.1 Conventions
  • 3.2 Definitions
  • 3.3 Acronyms and abbreviations
• 4. Software verification and validation
• • 4.1 Software VampV planning guidance
  • 4.2 Integrating and continuing VampV tasks
  • • 4.2.1 Traceability analysis
    • 4.2.2 Evaluation
    • 4.2.3 Interface analysis
    • 4.2.4 Testing
• 5. SVVP guidance
• • 5.1 Purpose
  • 5.2 Referenced documents
  • 5.3 Definitions
  • 5.4 Verification and validation overview
  • • 5.4.1 Organization
    • 5.4.2 Master schedule
    • 5.4.3 Resource summary
    • 5.4.4 Responsibilities
    • 5.4.5 Tools, techniques, and methodologies
  • 5.5 Life cycle verification and validation
  • • 5.5.1 Management of VampV
    • 5.5.2 Concept phase VampV
    • 5.5.3 Requirements phase VampV
    • 5.5.4 Design phase VampV
    • 5.5.5 Implementation phase VampV
    • 5.5.6 Test phase VampV
    • 5.5.7 Installation and checkout phase VampV
    • 5.5.8 Operation and maintenance VampV
  • 5.6 Reporting
  • • 5.6.1 Required reports
    • 5.6.2 Optional reports
  • 5.7 Verification and validation administrative procedures
  • • 5.7.1 Anomaly reporting and resolution
    • 5.7.2 Task iteration policy
    • 5.7.3 Deviation policy
    • 5.7.4 Control procedures
    • 5.7.5 Standards, practices, and conventions
  • A.1 Overview
  • A.2 Elevator system reference material
  • A.3 Extracts from a sample SVVP
  • • A.3.1 Example for Purpose
    • A.3.2 Example for Organization
    • A.3.3 Example for Responsibilities
    • A.3.4 Example for SVVP generation
    • A.3.5 Example for Management review of VampV
    • A.3.6 Example for Software requirements traceability analysis
    • A.3.7 Example for Software requirements evaluation
    • A.3.8 Example for Software requirements interface analysis
    • A.3.9 Example for System test plan generation
    • A.3.10 Example for Acceptance test plan generation
    • A.3.11 Example for Software design traceability analysis
    • A.3.12 Example for Software design evaluation
    • A.3.13 Example for Software design interface analysis
    • A.3.14 Example for Component test plan generation
    • A.3.15 Example for Integration test plan generation
    • A.3.16 Example for Test design generation - Component testing
    • A.3.17 Example for Test design generation - integration testing
    • A.3.18 Example for Test design generation - System testing
    • A.3.19 Example for Test design generation - Acceptance testing
    • A.3.20 Example for Source Code traceability analysis
    • A.3.21 Example for Source code evaluation
    • A.3.22 Example for Source code interface analysis
    • A.3.23 Example for Source code documentation evaluation
    • A.3.24 Example for Test case generation - Component testing
    • A.3.25 Example for Test case generation - integration testing
    • A.3.26 Example for Test case generation - System testing
    • A.3.27 Example for Test case generation - Acceptance testing
    • A.3.28 Example for Test procedure generation - Component testing
    • A.3.29 Example for Test procedure generation - integration testing
    • A.3.30 Example for Test procedure generation - System testing
    • A.3.31 Example for Component test execution
    • A.3.32 Example for Acceptance test procedure generation
    • A.3.33 Example for Integration test execution
    • A.3.34 Example for System test execution
    • A.3.35 Example for Acceptance test execution
  • C.1 VampV Tasks
  • C.2 Methods and criteria
  • C.3 Inputs and outputs
  • C.4 Schedule
  • C.5 Resources
  • C.6 Risks and assumptions
  • C.7 Roles and responsibilities

links: [Standard Status] - [Purchase] - [PDF^*] - [Software Engineering Collection - Description]

available for Standards Online Software Engineering Collection subscribers only