Software Development Templates

Software Verification and Validation Plan Version 0.0 Description of Project

DOCUMENT NO: VERSION: CONTACT: EMAIL:

Ivan Walsh

DATE:

4/13/2004

Distribution is subject to copyright.

Software Verification and Validation Plan Created by Ivan Walsh

Disclaimers The information contained in this document is the proprietary and exclusive property of XXX except as otherwise indicated. No part of this document, in whole or in part, may be reproduced, stored, transmitted, or used for design purposes without the prior written permission of XXX. The information contained in this document is subject to change without notice. The information in this document is provided for informational purposes only. XXX specifically disclaims all warranties, express or limited, including, but not limited, to the implied warranties of merchantability and fitness for a particular purpose, except as provided for in a separate software license agreement.

Privacy Information This document may contain information of a sensitive nature. This information should not be given to persons other than those who are involved in the Project Name project or who will become involved during the lifecycle

Trademarks [Trademarks are added here]

Version History REVISION CHART Version

Preface

Author(s)

Description of Version

Date Completed

i

Software Verification and Validation Plan Created by Ivan Walsh

Document Owner The primary contact for questions regarding this document is: Author: Project Name Phone: Email:

Document Approval Document Name: Publication Date: Contract Number: Project Number: Prepared by:

Approval:

__________________________

Name and Organization

Concurrence:

_________________________

Name and Organization

ii

Preface

Software Verification and Validation Plan Created by Ivan Walsh

Table of Contents

1

Introduction Background Objectives Document Overview Identification Relationship to Other Plans Scope Key Stakeholders References Policies, Directives and Procedures

5 5 5 5 6 6 6 6 6 6

Lifecycle Verification and Validation 2.1 Management 2.2 Concept Phase 2.3 Requirements Phase 2.4 Design Phase 2.5 Implementation Phase 2.6 Test Phase 2.7 Installation and Checkout Phase 2.8 Operation and Maintenance Phase

7 7 7 8 8 8 9 9 9

1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 2

3

Reporting

10

4

Administrative Procedures 4.1 Anomaly Reporting and Resolution 4.2 Task Iteration Policy 4.3 Deviation Policy 4.4 Control Procedures 4.5 Standards, Practices, and Conventions

11 11 11 11 12 12

5

Project Management 5.1 Priorities 5.2 Schedule 5.3 Tasks 5.4 Risk Assessment 5.5 Constraints 5.6 Issues

13 13 13 13 14 14 14

Preface

iii

Software Verification and Validation Plan Created by Ivan Walsh

5.7 5.8 5.9 6

15 15 15

Project Team Organization Resource Summary Roles and Responsibilities Sign-Off Criteria Training

16 16 16 16 17 17

Appendices 7.1 Glossary of Terms 7.2 Acronyms and Abbreviations

18 18 18

6.1 6.2 6.3 6.4 6.5 7

Assumptions Dependencies Tools, Techniques, and Methodology

Index of Tables Table 1 — Schedule Table 2 — Risks Table 3 — Constraints Table 4 — Issues Table 5 — Assumptions Table 6 — Dependencies Table 7— Roles and Responsibilities Table 8 — Sign-off Criteria Table 9 — Glossary of Terms Table 10 — Acronyms and Abbreviations

iv

13 14 14 14 15 15 16 17 18 18

Preface

1 Introduction

1.1 Background Describe the purpose of the Software Verification and Validation Plan, including the details of the following areas: •

Goals and objectives

•

Project identification

•

Project Management

•

Roles and Responsibilities

•

Software to be verified and validated

•

Summary of verification and validation efforts

This plan is used to assess software products throughout the software development lifecycle, and ensure that the software satisfies business functional requirements.

1.2 Objectives Describe the main business (and technical) objectives that this plan intends to achieve, e.g.: •

Comply with previous life cycle phase requirements

•

Establish the proper basis for initiating the next life cycle phase.

•

Satisfy standards, policies, practices, procedures, and conventions.

The role of the validation process is to ensure that the completed end product complies with established software and system requirements.

1.3 Document Overview Outline the main sections in this document, e.g.: •

Chapter 1 – Describe the contents of this chapter.

•

Chapter 2 – Describe the contents of this chapter.

•

Chapter 3 – Describe the contents of this chapter.

Software Verification and Validation Plan

© Copyright 2004

5

1.4 Identification Provide full details of the system to which this document applies, including, identification number(s), title(s), abbreviation(s), version number(s), release number(s) etc.

1.5 Relationship to Other Plans Describe this document relation to other plans, such as: •

Program Management Plan

•

Configuration Management Plan

•

Software Quality Assurance Plan

1.6 Scope Identify the scope (i.e. parameters) for the plan(s) and any areas specifically excluded from the plan(s).

1.7 Key Stakeholders Outline the project’s key stakeholders, for example: •

John Q Public, the client’s representative

•

Jane Q Public, Head of IT Dept.

•

James Q Public, Head of QA Dept.

1.8 References Identify any documents referenced in the plan, and any supporting documents required to implement the plan. Include the version and date reference.

1.9 Policies, Directives and Procedures Outline the policies and procedures that apply to this document. Identify any external constraints or requirements placed on this document by policies, directives, or procedures.

Project Name

© Copyright XXX

6

2 Lifecycle Verification and Validation

Describe the main verification and validation tasks to be achieved throughout the project lifecycle.

2.1 Management Provide details of the following management tasks: •

Baseline Change Assessment

•

Management Review

•

Review Support.

•

Software Verification and Validation Plan Generation

The Software Verification and Validation Plan begins during the concept phase of the project. Other areas to observe include: •

Correlating V&V task results to project management reviews.

•

Evaluating proposed changes for effects on previously completed V&V tasks.

•

Identifying key review support milestones.

•

Reviewing other Verification and Validation efforts, technical accomplishments, resource utilization, future planning, and risk management.

2.2 Concept Phase Evaluate the concept documentation to determine if the proposed concept satisfies the user needs and objectives. Identify the main constraints posed by interfacing systems. This phase establishes the basis for the proposed system. Therefore, at this point you need to confirm that the system objectives match the user needs.

Software Verification and Validation Plan

© Copyright 2004

7

2.3 Requirements Phase Define the functional and technical capabilities of the software product. The product from the requirements specification phase identifies what the software is intended to do. Ensure that the requirements can be traced to the user’s needs. In addition, discuss the following areas: •

Software requirements traceability analysis. Ensure that the requirements completely satisfy the capabilities specified in the concept document.

•

Software requirements evaluation. Assess the technical merits of the SRS requirements.

•

Software requirements interface analysis. Ensure that all external interfaces to the software and internal interfaces between software functions are identified.

2.4 Design Phase For this phase, perform the following tasks: •

Software design traceability analysis. Analyze relationships for correctness, consistency, completeness, and accuracy.

•

Software design evaluation. Evaluate the technical merits of the requirements and compliance to company standards.

•

Software design interface analysis. Ensure that the data elements at each interface includes: •

Test design generation

•

Component test plan

•

Integration test plan

2.5 Implementation Phase For the implementation phase, perform the following tasks:

Project Name

•

Evaluate draft code-related documents with source code

•

Evaluate source code for correctness, consistency, completeness, accuracy, and testability.

•

Evaluate source code with hardware, user, and design documentation.

•

Trace source code to design specification.

•

Provide test cases for: © Copyright XXX

8

•

Component testing

•

Integration testing

•

System testing

•

Acceptance testing

2.6 Test Phase Describe the following tasks: •

Acceptance test

•

Acceptance test procedure

•

Integration test

•

System test

•

Test execution

2.7 Installation and Checkout Phase Describe the tasks that must be accomplished for this phase, e.g.: •

Determine that all software products are correctly installed.

•

Provide a Final Report on all activities/results (including anomalies.)

2.8 Operation and Maintenance Phase At this phase, perform the following tasks: •

Change assessment

•

Evaluate anomalies

•

Phase task iteration

•

V&V plan revision

This "phase" can be interpreted as a sequence of subsets of the software development life cycle.

Software Verification and Validation Plan

© Copyright 2004

9

6 Project Team

Identify the team members by functional job description. State the approximate percentage of each team member's time that will be required to be devoted to the project(s).

6.1 Organization Describe how the V&V plan relates to other company-wide efforts, e.g. quality assurance or IT strategy. Identify the lines of communication and the authority(s) for resolving issues and approving verification and validation deliverables.

6.2 Resource Summary Describe the resources required to perform V&V tasks, such as staffing, facilities, and finances.

6.3 Roles and Responsibilities Identify the organization/business units responsible for each task. Describe each person(s) responsibility for ensuring the activities are performed.

Name

Role

Responsibility

% Committed

Table 7— Roles and Responsibilities

Project Name

© Copyright XXX

16

6.4 Sign-Off Criteria Identify individuals authorized to sign off the V&V Plan. Name

Role

Signature

Date

Table 8 — Sign-off Criteria

6.5 Training Describe any training requirements for customers, user groups and the project team. Outline the content and scheduling of training courses for personnel.

Software Verification and Validation Plan

© Copyright 2004

17

7 Appendices

Attach any addition information that supplements the V&V plan.

7.1 Glossary of Terms List and define all terms that establish meaning within the context of the V&V plan.

Term

Meaning

SVVP

Software Verification and Validation Plan

Validation

The process of evaluating software at the end of the software development process to ensure compliance to software requirements

Verification

The process of determining whether or not products of a given phase of the software development process fulfill the requirements established during the previous phase

V&V

Verification and validation

Table 9 — Glossary of Terms

7.2 Acronyms and Abbreviations Provide a list of acronyms and abbreviations used in this document and the meaning of each.

Acronym

Meaning

Table 10 — Acronyms and Abbreviations

Project Name

© Copyright XXX

18