Software Verification & Validation Plan Guide
Software Verification & Validation Plan Guide
INDEX
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.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.
For this course, the Verification activities defined in the process model are:
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,
the next version should also include the observations made by the Responsible
of Verification in its verification.
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.
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.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.
5.1.5. Resources
the resources available to carry out the tasks are identified in each
moment.
5.2. Requirements LT
<same as before>
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>
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.
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 .