Docstoc

Project Management Validation Plan

Document Sample
Project Management Validation Plan Powered By Docstoc
					 Software Verification 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                                                                                                                 4
  1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                                          4
  1.2 Deviations from IEEE Std 1012-1986 . . . . . . . . . . . . . . . . . .                                              4

2 Referenced Documents                                                                                                    6

3 Definitions                                                                                                              7

4 Verification and Validation Overview                                                                                     8
  4.1 Organisation . . . . . . . . . . . . .      .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   8
      4.1.1 Project Management . . . . .          .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   8
  4.2 Master Schedule . . . . . . . . . . .       .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   8
  4.3 Tools . . . . . . . . . . . . . . . . . .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   9

5 Life-cycle Verification and Validation Plan                                                                              10
  5.1 Management of V&V . . . . . . . . . . . . . . . . . . . . . . .                                     .   .   .   .   10
  5.2 Concept Phase V&V . . . . . . . . . . . . . . . . . . . . . . .                                     .   .   .   .   11
  5.3 Requirements Phase V&V . . . . . . . . . . . . . . . . . . . .                                      .   .   .   .   12
  5.4 Use Cases Generation Phase V&V . . . . . . . . . . . . . . .                                        .   .   .   .   13
  5.5 Architectural Design Phase V&V . . . . . . . . . . . . . . . .                                      .   .   .   .   13
  5.6 Test Plan Generation Phase . . . . . . . . . . . . . . . . . . .                                    .   .   .   .   14
  5.7 Development Phase V&V . . . . . . . . . . . . . . . . . . . .                                       .   .   .   .   15
       5.7.1 Increment 1 Phase . . . . . . . . . . . . . . . . . . . .                                    .   .   .   .   15
              5.7.1.1 Detailed Design . . . . . . . . . . . . . . . .                                     .   .   .   .   15
              5.7.1.2 Implementation . . . . . . . . . . . . . . . .                                      .   .   .   .   16
              5.7.1.3 Test Plan Execution . . . . . . . . . . . . . .                                     .   .   .   .   16
              5.7.1.4 Product Release . . . . . . . . . . . . . . . .                                     .   .   .   .   17
       5.7.2 Increment 2 Phase . . . . . . . . . . . . . . . . . . . .                                    .   .   .   .   17
              5.7.2.1 Detailed Design . . . . . . . . . . . . . . . .                                     .   .   .   .   17
              5.7.2.2 Implementation . . . . . . . . . . . . . . . .                                      .   .   .   .   18
              5.7.2.3 Test Plan Execution . . . . . . . . . . . . . .                                     .   .   .   .   18
              5.7.2.4 Product Release . . . . . . . . . . . . . . . .                                     .   .   .   .   19
  5.8 Installation and User Documentation Generation Phase V&V                                            .   .   .   .   19

6 Software Verification and Validation Reporting                                                                           20
  6.1 Task Reporting . . . . . . . . . . . . . . . . . . .                    .   .   .   .   .   .   .   .   .   .   .   20
  6.2 Phase Summary Report . . . . . . . . . . . . . .                        .   .   .   .   .   .   .   .   .   .   .   21
      6.2.1 Phase Tasks . . . . . . . . . . . . . . . . .                     .   .   .   .   .   .   .   .   .   .   .   21
      6.2.2 Phase Summary . . . . . . . . . . . . . .                         .   .   .   .   .   .   .   .   .   .   .   21


                                                                                                                           1
   6.3   Final Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .                 21

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




                                                                                                     2
                                       LIST OF TABLES



1.1   Deviations from IEEE Std 1012-1986 . . . . . . . . . . . . . . . . . .    5

6.1   Summary of results for all V&V tasks for this phase . . . . . . . . .    21




                                                                                3
                                                                        CHAPTER

                                                                           ONE




                                                             Purpose

1.1 Overview

This SVVP (Software Verification and Validation Plan) has been written for the 433-
440 Advanced Software Engineering Project and more specifically for the Centaur
Project.

The main goals of this plan and the V&V (Verification and Validation) effort 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
effort will be verifying that all the QA tasks have been completed for each phase of
the project. It should be noted this plan’s 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
Verification 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 SVVP’s (IEEE
Std 1012-1986) and the reasons for the deviations from those standards.




                                                                                 4
IEEE      Our        Deviation
Section   Section
4.3       -          This section has been summarised in the parent section
                     because of its simplicity in this project.
4.4       -          This section has been summarised in the parent section
                     because of its simplicity in this project.
-         5.4        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.
5.8       -          This section has been omitted because the nature of 440
                     projects does not really lend them to any operation or
                     maintenance tasks.
6         6          There are no optional reports. IEEE section 6.2 has been
                     removed and IEEE section 6.1 has simply become our sec-
                     tion 6.
6.1.3     -          We have not included this section as anomalies will be
                     reported in the task or summary reports.
7.3       -          This section has not been included as its content will be
                     handled on a case by case basis by the SQA Team.

                Table 1.1: Deviations from IEEE Std 1012-1986




                                                                                  5
                                                                  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 Verification
     and Validation Plans.

   • SQAP - The Software Quality Assurance Plan for Team Centaur is located
     in CVS module: docs/sqap

   • SCMP - The Software Configuration Management Plan for Team Centaur is
     located in CVS module: docs/scmp




                                                                          6
                                                                       CHAPTER

                                                                      THREE




                                                      Definitions

This chapter contains definitions for any specific terminology or acronyms used in
this plan.


 BoM - Board of Management

 PM - Project Manager

 QA - Quality Assurance

 SVVP - Software Verification and Validation Plan

 SVVR - Software Verification and Validation Report

 TG - Task Group

 V&V - Verification 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.




                                                                                7
                                                                          CHAPTER

                                                                           FOUR




             Verification and Validation
                              Overview

This chapter details the organisation of the V&V effort, 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 effort for Team
Centaur. All the decisions and communication for the V&V effort will be conducted
in the weekly meetings of the SQA TG.

There are several organisational entities that V&V effort 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 effort.



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 specification of dates for phases, all dates must be referenced
in the Team Project Plan. It is the QA Manager’s responsibility to ensure that the
V&V tasks are executed on the dates specified in the Team Project Plan.

See chapter 5 for a listing of all the phases for which V&V tasks must be conducted.




                                                                                   8
4.3 Tools

There are several Tools that will be used during the production and execution of
the SVVP.


   • L TEX - This will be used to write the SVVP and the SVVR.
     A




                                                                              9
                                                                       CHAPTER

                                                                          FIVE




              Life-cycle Verification and
                         Validation Plan

This chapter contains the checklists for all the V&V tasks which are to be exe-
cuted 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 sup-
posed 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 De-
sign 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                    Required Inputs               Required Outputs

 Generation of SVVP           Project management and        SVVP
                              schedules

 Baseline change assess-      Proposed changes              Updated SVVP
 ment for SVVP

 Internal   review(s)    of   Internal review     proce-    Internal review report(s),
 SVVP                         dures, SVVP                   Updated SVVP

 External    review(s)   of   External review     proce-    External review report(s),
 SVVP                         dures, SVVP                   Updated SVVP

 Functional audit(s)          Audit procedures, SRS,        Functional audit report(s)
                              Test cases for System
                              Testing

 In-process audit(s)          Audit procedures, SRS,        In-process audit report(s)
                              SADD, Detailed Designs,
                              Development Group di-
                              rectories (including source
                              files)

 Software V&V Reporting       SVVP                          Task reports and Phase
 for each life-cycle phase                                  Summary Report

 Final Software V&V Re-       SVVP, Task reports and        SVVR
 port for the whole project   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                    Required Inputs              Required Outputs

 Internal review(s)      of   Internal review proce-       Internal review report(s),
 SQAP, SCMP, SPMP             dures, SQAP, SCMP and        Updated SQAP, SCMP
                              SPMP                         and SPMP

 External review(s)      of   External review proce-       External review report(s),
 SQAP, SCMP, SPMP             dures, SQAP, SCMP and        Updated SQAP, SCMP
                              SPMP                         and SPMP

 Baseline change assess-      Proposed changes             Updated SQAP, SCMP
 ment of SQAP, SCMP and                                    and SPMP
 SPMP

 Managerial audit             Audit procedures, Project    Managerial audit report,
                              schedules, Group direc-      Updated project sched-
                              tory, SQAP, SCMP and         ules, Updated group direc-
                              SPMP                         tory


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 different 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
specific 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                   Required Inputs               Required Outputs

 Internal review(s) of SRS   Internal review     proce-    Internal review report(s),
                             dures, SRS                    Updated SRS

 External review(s) of SRS   External review     proce-    External review report(s),
                             dures, SRS                    Updated SRS

 Client review(s) of SRS     SRS                           Client review report(s),
                                                           Updated SRS

 Baseline change assess-     Proposed changes              Updated SRS
 ment of SRS

 Generation of Require-      SRS                           Requirements    Traceabil-
 ments Traceability Table                                  ity Table

 Maintenance for Require-    Updated SRS, Require-         Updated      Requirements
 ments Traceability Table    ments Traceability Table      Traceability Table

 Conformity check research   SQAP, research reports        Research reports that con-
 reports                                                   form to the specified re-
                                                           port 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 fulfil the appropriate
V&V criteria.

The appropriate V&V tasks for this phase are as follows:

 V&V Tasks                   Required Inputs               Required Outputs

 Internal review(s) of Use   Internal review proce-        Internal review report(s),
 Cases                       dures, SRS, Use Cases         Updated Use Cases

 External review(s) of Use   External review proce-        External review report(s),
 Cases                       dures, SRS, Use Cases         Updated Use Cases

 Baseline change assess-     Proposed changes which        Update Use Cases
 ment for Use Cases          are related to the changes
                             in the SRS


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 specific 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                    Required Inputs              Required Outputs

 Architectural      Design    SRS, SADD                    Updated SADD
 Evaluation

 Traceability of Architec-    SRS, SADD, Require-          Updated      Requirements
 tural Design                 ments Traceability Table     Traceability Table

 Internal   review(s)    of   Internal review proce-       Internal review report(s),
 SADD                         dures,       Requirements    Updated SADD, Updated
                              Traceability Table, SADD     Requirements Traceabil-
                                                           ity Table

 External    review(s)   of   Internal review proce-       External review report(s),
 SADD                         dures,       Requirements    Updated SADD, Updated
                              Traceability Table, SADD     Requirements Traceabil-
                                                           ity Table

 Baseline change assess-      Proposed changes             Updated SADD, Updated
 ment of SADD                                              Requirements Traceabil-
                                                           ity Table


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 fulfilled the following V&V
tasks.

The appropriate V&V tasks for this phase are as follows:




                                                                                14
 V&V Tasks                   Required Inputs              Required Outputs

 Internal review(s) of 5     Internal review proce-       Internal review report(s),
 TPs                         dures, SRS, SADD and         Updated TPs
                             Detailed Design, TPs

 External review(s) of 5     External review proce-       External review report(s),
 TPs                         dures, SRS, SADD and         Updated TPs
                             Detailed Design, TPs

 Internal review(s) of all   Internal review proce-       Internal review report(s),
 types of test cases         dures, SRS, SADD and         Updated test cases
                             Detailed Design (for unit
                             and integration testings)

 Baseline change assess-     Proposed changes which       Updated TPs, Updated
 ment of the 5 TPs           are related to the changes   test cases
                             in the SRS and SADD and
                             Detailed Design

 Test Cases Traceability     TPs, SRS, SADD and           Updated      Requirements
                             Detailed Design, Require-    Traceability Table
                             ments Traceability Table


5.7 Development Phase V&V

The Development Phase consists of 2 increments. There are 3 stages in each in-
crement, 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 cor-
responding stages for each increment.


5.7.1 Increment 1 Phase

The architectural design of core/essential requirements will be expanded into de-
tailed 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 fulfil 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                      Required Inputs             Required Outputs

 Internal review(s) on the      Internal  review  pro-      Internal review report(s),
 Detailed Design for Incre-     cedures, SRS, SADD,         Updated the Detailed De-
 ment 1                         Requirements Traceabil-     sign for Increment 1
                                ity Table

 External review(s) on the      External  review  pro-      External review report(s),
 Detailed Design for Incre-     cedures, SRS, SADD,         Updated the Detailed De-
 ment 1                         Requirements Traceabil-     sign for Increment 1
                                ity Table

 Traceability of Detailed       SRS, SADD, the Detailed     Updated Detailed Design
 Design for Increment 1         Design for Increment 1,     for Increment 1, Updated
                                Requirements Traceabil-     Requirements Traceabil-
                                ity Table                   ity 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 specific 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 fulfil the V&V criteria, the executable code is considered as the
verified and validated version.

The appropriate V&V tasks are as follows:

 V&V Tasks                      Required Inputs             Required Outputs

 Source code review(s)          Review        procedures,   Updated source code
                                Source code                 and the corresponding
                                                            executable code

 Source code documenta-         Source code review proce-   Updated Source code doc-
 tion review(s)                 dures, Source code docu-    umentation
                                mentation

 Modules traceability           Detailed Designs, Source    Updated      Requirements
                                code,        Requirements   Traceability Table
                                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 specific V&V criteria
for this phase.

The appropriate V&V tasks are as follows:



                                                                                  16
 V&V Tasks                      Required Inputs              Required Outputs

 Internal review of all types   Unit test cases stored in    The after-review opinions
 of unit test cases             Testing Database

 Unit Test Cases Traceabil-     TP, SRS, SADD, Detailed      Updated TP, Updated
 ity                            Designs for Increment 1,     Requirements Traceabil-
                                Requirements Traceabil-      ity Table
                                ity 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                      Required Inputs              Required Outputs

 Baseline change assess-        All source packages that     The change of revision
 ment of product release        compiled to the final prod-   number, that is 2
                                uct


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 specification and delivery plan for Increment 2 specifi-
     cation.

   • 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                      Required Inputs             Required Outputs

 Internal review(s) of the      Internal  review  pro-      Internal review report(s),
 Detailed Design for Incre-     cedures, SRS, SADD,         Updated Detailed Design
 ment 2                         Requirements Traceabil-     for Increment 2
                                ity Table

 External review(s) of the      External  review  pro-      External review report(s),
 Detailed Design for Incre-     cedures, SRS, SADD,         Updated Detailed Design
 ment 2                         Requirements Traceabil-     for Increment 2
                                ity Table

 Traceability of Detailed       SRS, SADD, the Detailed     Updated Detailed Design
 Design for Increment 2         Design for Increment 2,     for Increment 2, Updated
                                Requirements Traceabil-     Requirements Traceabil-
                                ity Table                   ity 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 specific V&V criteria for conformity
and ease in maintenance. The executable code depends on the source code. There-
fore, if the source code and its documentation fulfil the V&V criteria, the executable
code is considered as the verified and validated version.

The appropriate V&V tasks are as follows:

 V&V Tasks                      Required Inputs             Required Outputs

 Source code review(s)          Review        procedures,   Updated source code
                                Source code                 and the corresponding
                                                            executable code

 Source code documenta-         Source code review proce-   Updated Source code doc-
 tion review(s)                 dures, Source code docu-    umentation
                                mentation

 Modules traceability           The Detailed Design for     Updated      Requirements
                                Increment 2, Source code,   Traceability Table
                                Requirements Traceabil-
                                ity 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 specific V&V criteria
for this phase.



                                                                                  18
The appropriate V&V tasks are as follows:

 V&V Tasks                      Required Inputs              Required Outputs

 Internal review of all types   Unit test cases stored in    The after-review opinions
 of unit test cases             Testing Database

 Unit Test Cases Traceabil-     TP, SRS, SADD, Detailed      Updated TP, Updated
 ity                            Designs for Increment 2,     Requirements Traceabil-
                                Requirements Traceabil-      ity Table
                                ity 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                      Required Inputs              Required Outputs

 Baseline change assess-        All source packages that     The change of revision
 ment of product release        compiled to the final prod-   number, that is 3.
                                uct


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 specific V&V criteria.

The appropriate V&V tasks for this phase are as follows:

 V&V Tasks                      Required Inputs              Required Outputs

 Internal review(s) on user     Internal review proce-       Internal review report(s),
 documentation                  dures, User documenta-       Updated user documenta-
                                tion                         tion

 External review(s) on user     External review proce-       External review report(s),
 documentation                  dures, User documenta-       Updated user documenta-
                                tion                         tion

 Testing on installation        Installation package         Installation   testing    re-
                                                             port(s)




                                                                                      19
                                                                          CHAPTER

                                                                               SIX




                 Software Verification 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.

The general structure of the SVVR will be a L TEX document split up into a section
                                              A

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 specified:
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 first 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 fields 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 specifies 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 final 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 affected the quality and
progress of the project. Rather than delving into particular details of phases, it will
provide an overview of the V&V efforts as part of the project.




                                                                                    21
                                                                     CHAPTER

                                                                     SEVEN




            Verification and Validation
                    Admin Procedures

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



7.1 Anomaly Reporting

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



7.2 Task Iteration Policy

Each V&V task has specified 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 configuration items in the Team’s
CVS Repository. Thus SCMP procedures apply to both these documents and they
will be stored, configured and protected according to the SCMP.



7.4 Standards, Practices & Conventions

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


                                                                             22
7.4.1 Procedure for Verification 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 notification from the BoM, in the next scheduled SQA TG meeting, the
     QA Manager will assign the defined 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 member’s 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 deficiency will verify that the
     problem is resolved and upon fixing, 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

				
DOCUMENT INFO
Description: Project Management Validation Plan document sample