0% found this document useful (0 votes)
19 views6 pages

Software Verification & Validation Plan Guide

The SVVP Guide outlines the Software Verification and Validation Plan for a Software Engineering Project course. It details the purpose, organization, and management of verification tasks, including required reports and administrative procedures. The guide is based on IEEE Std. 1012 - 1986 and aims to adapt the standard to the course's specific process model.

Translated by

ScribdTranslations
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views6 pages

Software Verification & Validation Plan Guide

The SVVP Guide outlines the Software Verification and Validation Plan for a Software Engineering Project course. It details the purpose, organization, and management of verification tasks, including required reports and administrative procedures. The guide is based on IEEE Std. 1012 - 1986 and aims to adapt the standard to the course's specific process model.

Translated by

ScribdTranslations
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SVVP Guide

Software Verification & Validation Plan

Software Engineering Project - Course 2001


Institute of Computing - Software Engineering Project Course 2001

INDEX

IINTRODUCTION TO THEGGUIDE OFSVVP...................................................................................3


1. PPROPOSAL............................................................................................................3
2. DDOCUMENTSRREFERENCED
3. DDEFINITIONS3
4. DDESCRIPTION OF THEVVERIFICATION ANDVVALIDATION........................................................3
4.1. Organization....................................................................................................3
4.2. Main Agenda..............................................................................................3
4.3. Summary of Resources
4.4. 4
4.5. Tools, Techniques and methodologies...............................................................4
5. CCYCLE OFVDeparture from theVVERIFICATION& VVALIDATION.....................................................4
5.1. Verification Management...............................................................4
5.1.1. Tasks..........................................................................................................5
5.1.2. Methods and criteria........................................................................................5
5.1.3. Entries/Exits............................................................................................5
5.1.4. Agenda........................................................................................................5
5.1.5. Resources......................................................................................................5
5.1.6. Risks and assumed.................................................................5
5.1.7. Roles and responsibilities...............................................................................5
5.2. LT of Requirements........................................................................................5
5.3. Analysis LT...................................................................................................6
5.4. Design LT....................................................................................................6
5.5. Implementation LT.......................................................................................6
5.6. Test Level....................................................................................................6
6. RREPORTS OFVVERIFICATION ANDVVALIDATION.................................................................6
6.7. Required reports.........................................................................................6
6.8. Optional reports..........................................................................................6
7. PPROCEDURESAADMINISTRATIVE OFVVERIFICATION ANDVVALIDATION.............................6
7.1. Error reporting and resolution.
7.2. Policy for iteration on tasks.........................................................6
7.3. Deviation Policies......................................................................................6
7.4. Control Procedures.................................................................................6
7.5. Standards, practices, and conventions.................................................................6
8. RREFERENCES OF THIS GUIDE

SVVP Guide Page 2 of 6


Institute of Computing - Software Engineering Project Course 2001

Introduction to the SVVP Guide

This document provides a guide on the content of the sections determined by the
IEEE Std. 1012 - 1986 for the Verification and Validation Plan.

The purpose of this guide is to provide a basis for the adaptation of the standard to the model of
process applied in the 2001 course of the Software Engineering Project subject,
highlighting, for example, planning aspects related to the course process.

1. Purpose
The purpose and scope of the SVVP must be outlined, indicating the software project that
integrates, the products it covers and the objectives set for verification.

2. Referenced Documents
The referenced and/or complementary documents of the SVVP are indicated.

3. Definitions
the definitions of the required terms must be provided for the correct
interpretation of the SVVP.

4. Description of Verification and Validation


the topic of this section is to describe the resources needed to carry out the verification in
the project framework. Organization, agenda, resources, responsibilities, and will be specified
tools, techniques, and methodologies.

4.1. Organization
It indicates how the organization of the verification effort will be, defining the
relationships with the rest of the development areas, GP, SQA, SCM, and end user.

4.2. Main agenda


The verification tasks to be performed are identified and scheduled in time.
about the project life cycle. It should also indicate how the results of these
tasks provide feedback to the development process.

For this course, the Verification activities defined in the process model are:

Activity Associated Deliverable


Preparation of the Verification Plan Verification Plan
Development of the Prototype Test Plan Prototype Test Plan
Development of the Test Plan of the Iteration Test Plan
iteration
Verify documents Document verification reports
Definition of the Testing Model Testing Model
Check Model Traces
Design Test Cases Test Cases
Prototype test Prototype test reports
Unit test Unit test reports
Integration test Integration test reports
System Test System Test Reports
Test Evaluation Evaluation of the iteration verification

The activities of the process that are prior to the activities must be identified.
Verification, indicating the sequence of them, and the key points in the process in the
that these activities will be carried out. For example, when marking the verification of
documents for the Iteration I Development Phase (corresponding to weeks 5 and 6),
the verification of the Requirements Specification should be indicated in week 5 or in
week 6 and it must be done based on the version delivered in week 4, which corresponds to
The Initial Phase. As work continues on that document at the same time,

SVVP Guide Page 3 of 6


Institute of Computing - Software Engineering Project Course 2001

the next version should also include the observations made by the Responsible
of Verification in its verification.

4.3. Summary of Resources


The resources available to the verification area to carry out its tasks are described.
tasks, including staff, facilities, tools, among others.

For this course, there is a team made up of a Verification Officer and 3


Verification assistants (for the defined group of 12 people) that are incorporating into the
gradual verification of the principle of the Construction Phase.

4.4. Responsibilities
The responsibilities assigned for the completion of the tasks are described
verification and for each phase in the development process.

In this course, the Verification Manager is responsible for carrying out all the tasks.
planning for the area, defining in each case when, how, and what products
they will be verified, when, how and what tests will be carried out on the software in
development. It must also be involved in the Planning of the Integration of the
iteration that implementers carry out at the beginning of each iteration. When it counts
With the verification assistants, you will be able to distribute the tests in the verification group.
(including himself), but he will remain responsible for the indicated activities and
through the verification area.

4.5. Tools, Techniques, and Methodologies


It indicates whether any special software tool will be used for the execution.
of the tests, as well as techniques or methodologies, describing the purpose and use of
each one.

5. Life Cycle of Verification & Validation


A detailed plan of the verification lifecycle must be provided, indicating the tasks.
for verification by area, covering at least in each case the following points:
verification tasks: identify the verification tasks by phase, iteration, and LT.
methods and criteria: describe the methods, criteria, and procedures to perform each
task identified.
inputs/outputs: identify the required inputs to perform the tasks and the outputs
generated in each case, specifying the format of the corresponding reports.
mark the activities in time, by Phase, iteration, and week.
Resources: identify the resources that the verification area will have in each
time for the completion of the planned tasks.
risks and understandings: identify the risks and understandings associated with carrying out
the verification tasks, including agenda, resources or approach, and specify for
for each identified risk (or for the most important ones) a contingency plan of the area.
roles and responsibilities: clearly identify and assign at each moment the
responsibilities for carrying out the tasks.

In this course, the development process is iterative incremental, so the tasks of


Verification is given for each indicated Phase and iteration, regarding the Lines of Work.
defined in the process. In each case, the information related to the points will be included.
previously described. The following section provides a guide on the content of
each of these proposed points, which must be included in the rest of the sections
in the same way.

5.1. Management of Verification


it describes how verification will be managed during the project development, which
tasks will be redone, for example in document verification several will be verified
versions of the same document before it is finalized, or will be conducted
again the same tests on the software if errors were found.

SVVP Guide Page 4 of 6


Institute of Computing - Software Engineering Project Course 2001

5.1.1. Tasks
The tasks specifically related to verification management are indicated.

This section highlights the generation of the SVVP and the evaluation of the verification.
from the iteration.

5.1.2. Methods and criteria


The methods and criteria that will be applied in the performance of the tasks are indicated.
identified for verification management >

5.1.3. Inputs/outputs
The necessary inputs and the expected outputs are described, indicating the format of
the corresponding reports.

For the SVVP, the IEEE std. 1012-1986 is followed, and for the Evaluation Document of the
Verification there is a template that indicates the most important points of its content.

5.1.4. Agenda
The timing of the tasks identified for this section is indicated.

Preparation of the SVVP:


Initial Phase, Iteration I, weeks 1 and 2: a draft of the plan is made identifying in
the standard the content that must have it.
Initial Phase, Iteration II, weeks 3 and 4: the plan is completed so that it remains
clearly established the line that verification will follow during the project.
Development Phase, Construction Phase: the plan is stable, they might
make some modifications if considered necessary, for example in the agenda
anticipated.
.........

5.1.5. Resources
the resources available to carry out the tasks are identified in each
moment.

Preparation of the SVVP:


The only resource to carry out this task throughout its duration is X person.
...

5.1.6. Risks and assumed


The risks associated with the completion of the planned tasks are identified.
section.

Preparation of the SVVP:


Identified risk: not having completed the SVVP by the end of the Initial Phase.
Risk assessment: critical, affects the fulfillment of the planned tasks in the area
of verification influencing the rest of the areas and products of the project.
Contingency: the planned activities for the rest of the sections will not be postponed and
the SVVP will be finalized at the same time.

5.1.7. Roles and responsibilities


They define and assign the responsibilities for each task planned in this section.

Preparation of the SVVP:


Role: Verification Responsible.
In charge.

5.2. Requirements LT
<same as before>

SVVP Guide Page 5 of 6


Institute of Computing - Software Engineering Project Course 2001

5.3. LT of Analysis
<same as above>

5.4. Design LT
<same as above>

5.5. Implementation LT
<same as above>

5.6. Testing LT
<same as before>

6. Verification and Validation Reports


The reports that will be generated by the planned verification tasks are indicated,
attaching an example of the format and content of each.

6.1. Required Reports


The reports that must be generated as a minimum for the tasks are indicated.
foreseen verification

For the course, the deliverables are defined as: Verification report of
unit test report
system testing, iteration test plan, test cases (and
procedures), Verification evaluation document of the iteration.

6.2. Optional Reports


It indicates whether there are other documents associated with tasks not foreseen in the SVVP.

7. Administrative Procedures for Verification and Validation


The administrative procedures that will be followed to report, make
follow up and correct the errors found when performing verification tasks. It should
indicate in each case how and to whom (or whom) these errors will be reported, the (or the)
responsible for correcting them and established times for their correction.

7.1. Reporting and resolving errors


The method to follow for reporting, tracking, and resolving errors is indicated.
found in both document verification tasks and testing of
software

7.2. Iteration Policy on Tasks


It describes the criteria for repeatedly doing the same task as it changes.
your entrance.

7.3. Deviation Policies


The procedures and documents that will be used to deviate from the
SVVP, including the person responsible for the approval of deviations.

7.4. Control procedures


The procedures that will be followed to configure, protect and
store the products generated by the verification tasks, including relationships
with the areas of SQA, SCM or others.

7.5. Standards, practices, and conventions


the standards, practices, and conventions that will be followed are identified
performance of verification tasks, including internal standards, practices and
policies.

8. References of this guide


IEEE Std. 1012 – 1986 Standard for Software Verification and Validation Plans

SVVP Guide Page 6 of 6

Common questions

Powered by AI

The SVVP outlines risk management by identifying risks associated with the completion of verification tasks, including the agenda, resources, or approach. It specifies contingency plans for critical risks, such as the risk of not completing the SVVP as scheduled, and emphasizes the importance of timely completion to prevent impacts on related tasks and areas .

The document suggests that errors found during the verification process should be reported, tracked, and corrected following a specified administrative procedure. It indicates how and to whom these errors will be reported, the personnel responsible for correcting them, and the timeframe for their correction, ensuring a systematic approach to error management .

The IEEE Std. 1012-1986 significantly shapes the structure and content of the SVVP by providing standardized guidelines for verification and validation plans. It ensures that the SVVP is comprehensive and systematic, covering all necessary aspects such as inputs, outputs, methods, criteria, and reporting requirements, which enhances the plan's effectiveness and reliability in verifying software projects .

The document suggests that verification activities be tightly integrated with the overall software development process through iterative and incremental verification phases. This involves scheduled verification tasks providing feedback into the development cycle, ensuring that each iteration aligns with the project's quality objectives and facilitates continuous improvement throughout the software lifecycle .

The SVVP specifies various techniques and methodologies aimed at ensuring that the software meets its requirements and works as expected. These methodologies involve detailed planning of verification tasks, utilization of specific tools, and adherence to defined methods and criteria. The purpose is to apply a systematic approach to verify various stages of software development incrementally and iteratively, improving the software quality and ensuring compliance with project specifications .

The primary purpose of the Software Verification & Validation Plan (SVVP) is to provide a structured basis for verifying that the software project meets its specified requirements and objectives. It outlines the scope of verification, specifying the software project it integrates with, the products it covers, and the objectives set for verification. This ensures that the software development process produces a reliable and functional end product .

The recommended resources for effective implementation of the SVVP include a Verification Officer, verification assistants, tools, and facilities. These resources play various roles, such as planning and executing verification activities, managing and distributing tasks within the team, and utilizing sophisticated tools and facilities to conduct comprehensive verification tests .

The Verification Manager is responsible for planning and carrying out all verification tasks, deciding when, how, and which products will be verified, and which tests will be conducted. The manager must also collaborate in planning for the integration of iterations and can delegate tests within the verification group but retains ultimate responsibility for the success of these activities .

The process for re-verifying tasks involves conducting the same tests or verification tasks multiple times if errors are found or changes are made, ensuring that all corrections are verified. The criteria for re-verification are based on changes in input or findings of errors, and the rationale is to ensure that corrections do not introduce new issues and the software continues to meet its requirements .

Critical phases and iteration cycles for verification tasks include the Initial Phase, Iteration I, and subsequent iterations throughout the Development and Construction Phases. This structuring is significant because it allows for iterative and incremental verification, which helps uncover defects early in the software development lifecycle, thereby facilitating timely corrections and minimizing risks .

You might also like