Software Verification and Validation Plan (SVVP) Template Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is ud where you might inrt wording about your project.
This document is an annotated outline for a Software Verification and Validation Plan, adapted from the IEEE Standard for Software Verification and Validation Plans (Standard 1012), and the IEEE Guide for Software Verification and Validation Plans (Guide 1059).
Tailor as appropriate. Where you decide to omit a ction, you might keep the header, but inrt a comment saying why you omit the element (e.g., “This ction is not applicable to the plan.”)
(Agency)
primary
(Project)
Software Verification and Validation Plan Version: (n)Date: (mm/dd/yyyy)
T ABLE OF C ONTENTS
1. P URPOSE3
2. R EFERENCED D OCUMENTS4
3. D EFINITIONS5
4. V ERIFICATION AND V ALIDATION O VERVIEW5
4.1 Organization 5donut
4.2 Master Schedule6
4.3 Resource Summary6
4.4 Responsibilities7
heritage
4.5 Tools, Techniques, and Methodologies7
5. L IFECYCLE V ERIFICATION AND V ALIDATION7
5.1 Management of V&V7
acceptability5.2 Concept Pha8
动感英语2
天津人力资源管理师培训
5.3 Requirements Pha9
5.4 Design Pha9
5.5 Implementation Pha10
5.6 Test Pha11
5.7 Installation and Checkout Pha11
5.8 Operation and Maintenance Pha12
6. Reporting12
T ABLE OF C ONTENTS (CONTINUED)
7. Administrative Procedures13
7.1 Anomaly Reporting and Resolution13
7.2 Task Iteration Policy13
7.3 Deviation Policy13
7.4 Control Procedures14
ninja7.5 Standards, Practices, and Conventions14
8.Plan Approvals14
1. P URPOSE
(N OTE 1: T HE S OFTWARE V ERIFICATION AND V ALIDATION P LAN GUIDELINES WERE
DERIVED AND DEVELOPED FROM IEEE S TANDARD FOR S OFTWARE V ERIFICATION AND V ALIDATION (S TANDARD 1012) AND THE IEEE G UIDE FOR S OFTWARE V ERIFICATION AND V ALIDATION P LANS (G UIDE 1059)).
(Note 2: The ordering of Software Verification and Validation Plan (SVVP) elements is not meant to imply that the ctions or subctions must be developed or
prented in that order. The order of prentation is intended for ea of u, not as a guide to prep
aring the various elements of the Software Verification and Validation Plan. If some or all of the content of a ction is in another document, then a
reference to that material may be listed in place of the corresponding content.)
schengen(The Purpo ction of the Software Verification and Validation Plan defines the purpo, scope, and goals of the plan. The software project must be identified and the specific
关爱留守儿童讲话
software product items, covered by the plan, must be identified. The specific goals of the verification and validation effort must be specified.
The SVVP purpo ction provides the highest level description of verification and
validation efforts. The following topics must be addresd:
•Project identification,
•Plan goals,
•Summary of verification and validation efforts,
•Responsibilities conveyed with the plan,
•Software to be verified and validated,
•Identification of waivers and changes to organization standards, and
大雁塔 英文
SVVP assumptions.)
Software verification and validation (V&V) is a disciplined approach to asssing software products throughout the software development life cycle. Verification and validation strives to ensure that quality is built into the software and that the software satisfies business functional requirements.
Software verification and validation employs review, analysis, and testing techniques to determine whether a software product and its intermediate deliverables comply with requirements. The requirements include both business functional capabilities and quality attributes.
