Software Verication and Validation Plan

Revision : 2.0
433-440 Advanced Software Engineering Project

The Centaur Project

Here are the Authors of the SVVP

March 31, 2008

Abstract
This document details the Quality Assurance checks, tasks traceability techniques to be performed in each life cycle phase of the project.

CONTENTS

1 Purpose 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Deviations from IEEE Std 1012-1986 . . . . . . . . . . . . . . . . . . 2 Referenced Documents 3 Denitions 4 Verication and Validation Overview 4.1 Organisation . . . . . . . . . . . . . 4.1.1 Project Management . . . . . 4.2 Master Schedule . . . . . . . . . . . 4.3 Tools . . . . . . . . . . . . . . . . . .

4 4 4 6 7 8 8 8 8 9 10 10 11 12 13 13 14 15 15 15 16 16 17 17 17 18 18 19 19 20 20 21 21 21

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

5 Life-cycle Verication and Validation Plan 5.1 Management of V&V . . . . . . . . . . . . . . . . . . . . . . . 5.2 Concept Phase V&V . . . . . . . . . . . . . . . . . . . . . . . 5.3 Requirements Phase V&V . . . . . . . . . . . . . . . . . . . . 5.4 Use Cases Generation Phase V&V . . . . . . . . . . . . . . . 5.5 Architectural Design Phase V&V . . . . . . . . . . . . . . . . 5.6 Test Plan Generation Phase . . . . . . . . . . . . . . . . . . . 5.7 Development Phase V&V . . . . . . . . . . . . . . . . . . . . 5.7.1 Increment 1 Phase . . . . . . . . . . . . . . . . . . . . 5.7.1.1 Detailed Design . . . . . . . . . . . . . . . . 5.7.1.2 Implementation . . . . . . . . . . . . . . . . 5.7.1.3 Test Plan Execution . . . . . . . . . . . . . . 5.7.1.4 Product Release . . . . . . . . . . . . . . . . 5.7.2 Increment 2 Phase . . . . . . . . . . . . . . . . . . . . 5.7.2.1 Detailed Design . . . . . . . . . . . . . . . . 5.7.2.2 Implementation . . . . . . . . . . . . . . . . 5.7.2.3 Test Plan Execution . . . . . . . . . . . . . . 5.7.2.4 Product Release . . . . . . . . . . . . . . . . 5.8 Installation and User Documentation Generation Phase V&V 6 Software Verication and Validation Reporting 6.1 Task Reporting . . . . . . . . . . . . . . . . . . . 6.2 Phase Summary Report . . . . . . . . . . . . . . 6.2.1 Phase Tasks . . . . . . . . . . . . . . . . . 6.2.2 Phase Summary . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

6.3

Final Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21 22 22 22 22 22 23

7 Verication and Validation Admin Procedures 7.1 Anomaly Reporting . . . . . . . . . . . . . . . . . . . 7.2 Task Iteration Policy . . . . . . . . . . . . . . . . . . . 7.3 Control Procedures . . . . . . . . . . . . . . . . . . . . 7.4 Standards, Practices & Conventions . . . . . . . . . . 7.4.1 Procedure for Verication of a Life Cycle Phase

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

LIST OF TABLES

1.1 6.1

Deviations from IEEE Std 1012-1986 . . . . . . . . . . . . . . . . . . Summary of results for all V&V tasks for this phase . . . . . . . . .

5 21

CHAPTER

ONE

Purpose
1.1 Overview
This SVVP (Software Verication and Validation Plan) has been written for the 433440 Advanced Software Engineering Project and more specically for the Centaur Project. The main goals of this plan and the V&V (Verication and Validation) eort are: To ensure completeness in the implementation of requirements in each phase of the project (i.e. to ensure traceability from requirements). To maintain and improve the QA (Quality Assurance) of the project. To provide an independent method of checking for completeness of QA Tasks for each phase of the project. V&V will be the responsibility of the SQA TG (Software Quality Assurance Task Group) and it is this TG that develop and execute the SVVP. Most of the V&V eort will be verifying that all the QA tasks have been completed for each phase of the project. It should be noted this plans audience is primarily the SQA TG and it should be read in with this in mind. All phases of the project will be required to pass the QA checks detailed in this plan. The execution of this plan results in the production of the SVVR (Software Verication and Validation Report). This report states the results of all the QA tasks and provides recommendations that can be fed back into SQA for the project.

1.2 Deviations from IEEE Std 1012-1986

The table below states the deviations from the IEEE standard for SVVPs (IEEE Std 1012-1986) and the reasons for the deviations from those standards.

IEEE Section 4.3 4.4 -

Our Section 5.4

Deviation This section has been summarised in the parent section because of its simplicity in this project. This section has been summarised in the parent section because of its simplicity in this project. Due to the incremental model adopted and the importance of Architectural Design in the Centaur Project, this phase has been extracted from the design section. This section has been omitted because the nature of 440 projects does not really lend them to any operation or maintenance tasks. There are no optional reports. IEEE section 6.2 has been removed and IEEE section 6.1 has simply become our section 6. We have not included this section as anomalies will be reported in the task or summary reports. This section has not been included as its content will be handled on a case by case basis by the SQA Team.

5.8

6.1.3 7.3

Table 1.1: Deviations from IEEE Std 1012-1986

CHAPTER

TWO

Referenced Documents
This chapter lists all the documents referenced in the SVVP. IEEE Std 1012-1986 - This is the IEEE Standard for Software Verication and Validation Plans. SQAP - The Software Quality Assurance Plan for Team Centaur is located in CVS module: docs/sqap SCMP - The Software Conguration Management Plan for Team Centaur is located in CVS module: docs/scmp

CHAPTER

THREE

Denitions
This chapter contains denitions for any specic terminology or acronyms used in this plan. BoM - Board of Management PM - Project Manager QA - Quality Assurance SVVP - Software Verication and Validation Plan SVVR - Software Verication and Validation Report TG - Task Group V&V - Verication and Validation V&V task - A QA check that is performed on any part of the project. A success or failure in this check indicates that the part of the project did not meet QA standards.

CHAPTER

FOUR

Verication and Validation Overview

This chapter details the organisation of the V&V eort, the schedule for V&V tasks and the tools, techniques and methodologies employed.

4.1 Organisation
The SQA TG (led by the QA Manager) is responsible for the V&V eort for Team Centaur. All the decisions and communication for the V&V eort will be conducted in the weekly meetings of the SQA TG. There are several organisational entities that V&V eort needs to interact with.

4.1.1 Project Management

The QA Manager is responsible for informing the SQA TG of decisions from the BoM (Board of Management) and also for reporting to the BoM about the results of the V&V eort.

4.2 Master Schedule

The schedule for V&V tasks (for each phase of the project) is heavily dependent on the Team Project Plan. Therefore, the V&V tasks for a phase will be executed when that phase of the project is deemed complete by the PM (Project Manager). To avoid any incorrect specication of dates for phases, all dates must be referenced in the Team Project Plan. It is the QA Managers responsibility to ensure that the V&V tasks are executed on the dates specied in the Team Project Plan. See chapter 5 for a listing of all the phases for which V&V tasks must be conducted.

4.3 Tools
There are several Tools that will be used during the production and execution of the SVVP.
A L TEX - This will be used to write the SVVP and the SVVR.

CHAPTER

FIVE

Life-cycle Verication and Validation Plan

This chapter contains the checklists for all the V&V tasks which are to be executed for each life-cycle phase. These V&V tasks must be completed before the commencement of the next phase.

5.1 Management of V&V

The management of V&V is planned and being executed by the SQA TG. The SVVP will be generated and maintained by the SQA TG. The SVVP was supposed to be generated during the Concept Phase so that it can cover all life-cycle phases. Unfortunately, the generation had been delayed until the Architectural Design Phase. Anyhow, the V&V tasks for the Concept and Requirements Phases had been carried out. The appropriate V&V tasks for the management of V&V are as follows:

10

V&V Tasks Generation of SVVP

Required Inputs Project management and schedules Proposed changes

Required Outputs SVVP

Baseline change assessment for SVVP Internal SVVP External SVVP review(s) of

Updated SVVP

Internal review dures, SVVP External review dures, SVVP

proce-

Internal review report(s), Updated SVVP External review report(s), Updated SVVP Functional audit report(s)

review(s)

of

proce-

Functional audit(s)

Audit procedures, SRS, Test cases for System Testing Audit procedures, SRS, SADD, Detailed Designs, Development Group directories (including source les) SVVP

In-process audit(s)

In-process audit report(s)

Software V&V Reporting for each life-cycle phase Final Software V&V Report for the whole project

Task reports and Phase Summary Report SVVR

SVVP, Task reports and Phase Summary Reports

5.2 Concept Phase V&V

During this phase, all the initial managerial documents that governed the operation of the team were written. These were the SQAP, SCMP and SPMP. They were developed by SQAP TG, SCMP TG, and SPMP TG. They were required to satisfy the V&V criteria which were set for this phase. The appropriate V&V tasks for this phase are as follows:

11

V&V Tasks Internal review(s) SQAP, SCMP, SPMP of

Required Inputs Internal review procedures, SQAP, SCMP and SPMP External review procedures, SQAP, SCMP and SPMP Proposed changes

Required Outputs Internal review report(s), Updated SQAP, SCMP and SPMP External review report(s), Updated SQAP, SCMP and SPMP Updated SQAP, SCMP and SPMP

External review(s) SQAP, SCMP, SPMP

of

Baseline change assessment of SQAP, SCMP and SPMP Managerial audit

Audit procedures, Project schedules, Group directory, SQAP, SCMP and SPMP

Managerial audit report, Updated project schedules, Updated group directory

5.3 Requirements Phase V&V

In this phase, software requirements were gathered and analysed for the production of the SRS by the SRS TG. The research team, the ModSquad TG, was doing the prototyping to evaluate dierent software packages so that the suitable ones can be used in the implementation of the product. Research reports were written by the ModSquad TG. Hence, the SRS and the research reports were required to meet the specic V&V criteria before the commencement of Architectural Design Phase. The appropriate V&V tasks for this phase are as follows:

12

V&V Tasks Internal review(s) of SRS

Required Inputs Internal review dures, SRS External review dures, SRS SRS proce-

Required Outputs Internal review report(s), Updated SRS External review report(s), Updated SRS Client review report(s), Updated SRS Updated SRS

External review(s) of SRS

proce-

Client review(s) of SRS

Baseline change assessment of SRS Generation of Requirements Traceability Table Maintenance for Requirements Traceability Table Conformity check research reports

Proposed changes

SRS

Requirements ity Table

Traceabil-

Updated SRS, Requirements Traceability Table SQAP, research reports

Updated Requirements Traceability Table Research reports that conform to the specied report format in SQAP

5.4 Use Cases Generation Phase V&V

In this phase, use cases are developed and written out as the Use Cases Document by the Use Cases TG. The Use Cases Document is required to full the appropriate V&V criteria. The appropriate V&V tasks for this phase are as follows: V&V Tasks Internal review(s) of Use Cases External review(s) of Use Cases Baseline change assessment for Use Cases Required Inputs Internal review procedures, SRS, Use Cases External review procedures, SRS, Use Cases Proposed changes which are related to the changes in the SRS Required Outputs Internal review report(s), Updated Use Cases External review report(s), Updated Use Cases Update Use Cases

5.5 Architectural Design Phase V&V

In this phase, the SADD will be developed by the Architectural Design TG. This document is required to satisfy a certain level of V&V criteria. All the V&V tasks which are specic to this phase have to be accomplished before the commencement of the Detailed Design Phase for Increment 1 and Increment 2.

13

The appropriate V&V tasks for this phase are as follows: V&V Tasks Architectural Evaluation Design Required Inputs SRS, SADD Required Outputs Updated SADD

Traceability of Architectural Design Internal SADD review(s) of

SRS, SADD, Requirements Traceability Table Internal review procedures, Requirements Traceability Table, SADD

Updated Requirements Traceability Table Internal review report(s), Updated SADD, Updated Requirements Traceability Table External review report(s), Updated SADD, Updated Requirements Traceability Table Updated SADD, Updated Requirements Traceability Table

External SADD

review(s)

of

Internal review procedures, Requirements Traceability Table, SADD

Baseline change assessment of SADD

Proposed changes

5.6 Test Plan Generation Phase

During this phase, the Top-Level TP was to be developed by the TP TG. Test cases for System Testing are to be written concurrently with the development of the Top-Level TP. Each DG is required to develop its own TP. Hence, including the Top-Level TP, there are 5 TPs. All are required to fullled the following V&V tasks. The appropriate V&V tasks for this phase are as follows:

14

V&V Tasks Internal review(s) of 5 TPs

Required Inputs Internal review procedures, SRS, SADD and Detailed Design, TPs External review procedures, SRS, SADD and Detailed Design, TPs Internal review procedures, SRS, SADD and Detailed Design (for unit and integration testings) Proposed changes which are related to the changes in the SRS and SADD and Detailed Design TPs, SRS, SADD and Detailed Design, Requirements Traceability Table

Required Outputs Internal review report(s), Updated TPs

External review(s) of 5 TPs

External review report(s), Updated TPs

Internal review(s) of all types of test cases

Internal review report(s), Updated test cases

Baseline change assessment of the 5 TPs

Updated TPs, Updated test cases

Test Cases Traceability

Updated Requirements Traceability Table

5.7 Development Phase V&V

The Development Phase consists of 2 increments. There are 3 stages in each increment, namely Detailed Design, Implementation, and Test Plan Execution. All the V&V tasks which are to be conducted in each increment are listed in the corresponding stages for each increment.

5.7.1 Increment 1 Phase

The architectural design of core/essential requirements will be expanded into detailed design for implementation and testing in Increment 1 Phase. Hence, the deliverables of this phase are the Detailed Design for Increment 1, source code, source code documentation, executable code, and testing reports. They all are required to full the V&V criteria that are set for this phase.

5.7.1.1

Detailed Design

During this stage, the Detailed Design for Increment 1 will be developed by the DGs. The Detailed Design for Increment 1 is required to meet a certain level of V&V criteria before the implementation can be started. The appropriate V&V tasks are as follows:

15

V&V Tasks Internal review(s) on the Detailed Design for Increment 1

Required Inputs Internal review procedures, SRS, SADD, Requirements Traceability Table External review procedures, SRS, SADD, Requirements Traceability Table SRS, SADD, the Detailed Design for Increment 1, Requirements Traceability Table

Required Outputs Internal review report(s), Updated the Detailed Design for Increment 1

External review(s) on the Detailed Design for Increment 1

External review report(s), Updated the Detailed Design for Increment 1

Traceability of Detailed Design for Increment 1

Updated Detailed Design for Increment 1, Updated Requirements Traceability Table

5.7.1.2

Implementation

During this stage, the Detailed Design for Increment 1 will be translated into source code with appropriate documentation. The executable code is then produced by compiling the source code. The source code and source code documentation are required to meet the specic V&V criteria for conformity and ease in maintenance. The executable code depends on the source code. Therefore, if the source code and its documentation full the V&V criteria, the executable code is considered as the veried and validated version. The appropriate V&V tasks are as follows: V&V Tasks Source code review(s) Required Inputs Review Source code procedures, Required Outputs Updated source code and the corresponding executable code Updated Source code documentation

Source code documentation review(s)

Source code review procedures, Source code documentation Detailed Designs, Source code, Requirements Traceability Table

Modules traceability

Updated Requirements Traceability Table

5.7.1.3

Test Plan Execution

Only the test cases which are written for testing the implementation of the Detailed Design for Increment 1 are executed in this phase. Testing results are reported for traceability. The output of this phase is required to meet the specic V&V criteria for this phase. The appropriate V&V tasks are as follows:

16

V&V Tasks Internal review of all types of unit test cases Unit Test Cases Traceability

Required Inputs Unit test cases stored in Testing Database TP, SRS, SADD, Detailed Designs for Increment 1, Requirements Traceability Table

Required Outputs The after-review opinions

Updated TP, Updated Requirements Traceability Table

5.7.1.4

Product Release

There is only one V&V task that product release needs to carry out. The V&V task for product release: V&V Tasks Baseline change assessment of product release Required Inputs All source packages that compiled to the nal product Required Outputs The change of revision number, that is 2

5.7.2 Increment 2 Phase

In the evaluation of the Increment 1, the project plan will be updated accordingly for the Increment 2. This plan shall address: a re-evaluation of the specication and delivery plan for Increment 2 specication. the delivery of secondary features and functionality during the Increment 2. Once these are addressed, the Increment 2 Phase will be started. The V&V tasks for the Increment 2 Phase are similar to the planned V&V tasks for the Increment 1 Phase.

5.7.2.1

Detailed Design

During this stage, the Detailed Design for Increment 2 will be developed by the DGs. The Detailed Design for Increment 2 is required to meet a certain level of V&V criteria before the implementation can be started. The appropriate V&V tasks are as follows:

17

V&V Tasks Internal review(s) of the Detailed Design for Increment 2

Required Inputs Internal review procedures, SRS, SADD, Requirements Traceability Table External review procedures, SRS, SADD, Requirements Traceability Table SRS, SADD, the Detailed Design for Increment 2, Requirements Traceability Table

Required Outputs Internal review report(s), Updated Detailed Design for Increment 2

External review(s) of the Detailed Design for Increment 2

External review report(s), Updated Detailed Design for Increment 2

Traceability of Detailed Design for Increment 2

Updated Detailed Design for Increment 2, Updated Requirements Traceability Table

5.7.2.2

Implementation

The Implementation stage for Increment 2 will complete all the coding for the supplementary requirement. During this stage, the Detailed Design for Increment 2 will be translated into source code with appropriate documentation. The executable code is then produced by compiling the source code. The source code and source code documentation are required to meet the specic V&V criteria for conformity and ease in maintenance. The executable code depends on the source code. Therefore, if the source code and its documentation full the V&V criteria, the executable code is considered as the veried and validated version. The appropriate V&V tasks are as follows: V&V Tasks Source code review(s) Required Inputs Review Source code procedures, Required Outputs Updated source code and the corresponding executable code Updated Source code documentation

Source code documentation review(s)

Source code review procedures, Source code documentation The Detailed Design for Increment 2, Source code, Requirements Traceability Table

Modules traceability

Updated Requirements Traceability Table

5.7.2.3

Test Plan Execution

Only the test cases which are written for testing the implementation of the Detailed Design for Increment 2 are executed in this phase. Testing results are reported for traceability. The output of this phase is required to meet the specic V&V criteria for this phase.

18

The appropriate V&V tasks are as follows: V&V Tasks Internal review of all types of unit test cases Unit Test Cases Traceability Required Inputs Unit test cases stored in Testing Database TP, SRS, SADD, Detailed Designs for Increment 2, Requirements Traceability Table Required Outputs The after-review opinions

Updated TP, Updated Requirements Traceability Table

5.7.2.4

Product Release

There is only one V&V task that product release needs to carry out. The V&V task for product release: V&V Tasks Baseline change assessment of product release Required Inputs All source packages that compiled to the nal product Required Outputs The change of revision number, that is 3.

5.8 Installation and User Documentation Generation Phase V&V

The Installation package and the user documentation will be produced as described in the SRS by the Installation TG and UD TG. Both the installation package and the user documentation are required to meet some specic V&V criteria. The appropriate V&V tasks for this phase are as follows: V&V Tasks Internal review(s) on user documentation Required Inputs Internal review procedures, User documentation External review procedures, User documentation Installation package Required Outputs Internal review report(s), Updated user documentation External review report(s), Updated user documentation Installation port(s) testing re-

External review(s) on user documentation

Testing on installation

19

CHAPTER

SIX

Software Verication and Validation Reporting

This chapter describes how the results of the SVVP will be documented, detailing the content, format and timing of all V&V reports. The V&V reports produced will together comprise the SVVR document.
A The general structure of the SVVR will be a L TEX document split up into a section for each phase (see chapter 5 for the phases). Each phase section will contain all of the V&V task reports (see section 6.1) for that phase, and at the end of each phase section there will be a Phase Summary Report (see section 6.2). In addition, at the end of the SVVR will be a Final Report (see section 6.3).

6.1 Task Reporting

This section describes how task reports will be written and inserted into the SVVR. When a V&V task is completed, a task report will be written and inserted into the SVVR under the relevant phase section. The list of V&V tasks to be performed for each phase of the project can be found in chapter 5. Each task report shall describe for a particular V&V task the following items in the format specied: Task Name: The V&V tasks name Description: A brief description of the task Outcome: Whether it was successful Evidence: The location of evidence of the task being performed Date(s): The date(s) when the task was performed Team members: The team members involved in performing the task Where a task does not succeed in the rst task report, subsequent task reports will be made for the repeated V&V task until it succeeds.

20

6.2 Phase Summary Report

This section describes when and how Phase Summary Reports will be written and inserted into the SVVR. When a phase is completed a Phase Summary Report will be written and inserted into the SVVR under the relevant phase section, after the individual task reports.

6.2.1 Phase Tasks

The Phase Summary Report will summarise the V&V tasks performed during the relevant phase containing the following information for each task. For each V&V task, the Task Name and Outcome elds shall be obtained from the individual task reports as described in section 6.1. The format for this information will be in a table which species the Outcome (marked S or F for Success or Failure) for each Task Name: Task Name Success

Table 6.1: Summary of results for all V&V tasks for this phase

6.2.2 Phase Summary

After the table summarising the outcome of V&V tasks performed during the phase, a brief statement will be written by the QA Manager summing up the V&V tasks performed, outlining any major problems or successes and any possible lessons learned that could be applied to other subsequent phases.

6.3 Final Report

This section describes how the Final Report will be written and inserted into the SVVR. When the nal V&V phase is completed at the end of the whole project, a Final Report shall be made and inserted into a section at the end of the SVVR. The Final Report will be a summary written by the QA Manager, summarising all of the phases of the project and how the V&V process aected the quality and progress of the project. Rather than delving into particular details of phases, it will provide an overview of the V&V eorts as part of the project.

21

CHAPTER

SEVEN

Verication and Validation Admin Procedures

The chapter species the procedures to be conducted as part of the V&V eort for Team Centaur.

7.1 Anomaly Reporting

All anomaly reporting will be executed using the problem reporting procedures dened in section 5 of the SQAP.

7.2 Task Iteration Policy

Each V&V task has specied inputs and outputs. A V&V task will need to be re-performed if all the following conditions are met: The inputs to a V&V task change. The QA Manager deems the task necessary to be re-performed.

7.3 Control Procedures

The SVVP and SVVR will be stored as formal conguration items in the Teams CVS Repository. Thus SCMP procedures apply to both these documents and they will be stored, congured and protected according to the SCMP.

7.4 Standards, Practices & Conventions

The following Standards, Practices & Conventions will apply to the V&V eort for Team Centaur. 22

7.4.1 Procedure for Verication of a Life Cycle Phase

The following procedure will apply when a phase of the life cycle (see chapter 5) has been deemed complete by the BoM. 1. After notication from the BoM, in the next scheduled SQA TG meeting, the QA Manager will assign the dened V&V tasks to the members of the SQA TG. 2. Each member will complete the assigned tasks and add their task reports to the SVVR according to the procedures detailed in chapter 6. 3. If any of a members V&V tasks failed, they will report the failure to party responsible. If a member is in any doubt as to who the responsible party is they should consult the QA Manager. 4. If a task failed, the member who found the deciency will verify that the problem is resolved and upon xing, update the SVVR. 5. Once all tasks have succeeded the QA Manager will write a phase summary according to the procedures in chapter 6.

23