IEEE Std 1012-2012 Front Cover
Title Page
Notice to users
Laws and regulations
Copyrights
Updating of IEEE documents
Errata
Patents
Participants
Introduction
Contents
Important notice
1. Overview
1.1 Scope
1.2 Purpose
1.3 Field of application
1.4 V&V objectives
1.5 Organization of the standard
1.6 Audience
1.7 Conformance
1.8 Disclaimer
2. Normative references
3. Definitions, abbreviations, and acronyms
3.1 Definitions
3.2 Abbreviations and acronyms
4. Relationships between V&V and life cycle processes
5. Integrity levels
6. V&V processes overview
6.1 General
6.2 V&V testing
7. Common V&V activities
7.1 Activity: V&V Management
7.2 Activity: Acquisition Support V&V
7.3 Activity: Supply Planning V&V
7.4 Activity: Project Planning V&V
7.5 Activity: Configuration Management V&V
8. System V&V activities
8.1 Activity: Stakeholder Requirements Definition V&V
The purpose of the Stakeholder Requirements Definition Process is to define the requirements for a system that can provide the services needed by users and other stakeholders in a defined environment. It identifies stakeholders, or stakeholder classes...
The V&V effort shall perform, as specified in Table 2b for the selected integrity level, the following Stakeholder Requirements Definition V&V tasks described in Table 1b:
8.2 Activity: Requirements Analysis V&V
8.3 Activity: Architectural Design V&V
8.4 Activity: Implementation V&V
8.5 Activity: Integration V&V
8.6 Activity: Transition V&V
8.7 Activity: Operation V&V
8.8 Activity: Maintenance V&V
8.9 Activity: Disposal V&V
9. Software V&V activities
9.1 Activity: Software Concept V&V
9.2 Activity: Software Requirements V&V
9.3 Activity: Software Design V&V
9.4 Activity: Software Construction V&V
9.5 Activity: Software Integration Test V&V
9.6 Activity: Software Qualification Test V&V
9.7 Activity: Software Acceptance Test V&V
9.8 Activity: Software Installation and Checkout V&V
9.9 Activity: Software Operation V&V
9.10 Activity: Software Maintenance V&V
9.11 Activity: Software Disposal V&V
10. Hardware V&V activities
10.1 Activity: Hardware Concept V&V
10.2 Activity: Hardware Requirements V&V
10.3 Activity: Hardware Design V&V
10.4 Activity: Hardware Fabrication V&V
10.5 Activity: Hardware Integration Test V&V
10.6 Activity: Hardware Qualification Test V&V
10.7 Activity: Hardware Acceptance Test V&V
10.8 Activity: Hardware Transition V&V
10.9 Activity: Hardware Operation V&V
10.10 Activity: Hardware Maintenance V&V
10.11 Activity: Hardware Disposal V&V
11. V&V reporting, administrative, and documentation requirements
11.1 V&V reporting requirements
11.2 V&V administrative requirements
11.3 V&V documentation requirements
12. V&V plan outline
12.1 Overview
12.2 VVP Section 1: Purpose
12.3 VVP Section 2: Referenced documents
12.4 VVP Section 3: Definitions
12.5 VVP Section 4: V&V overview
12.5.1 VVP Section 4.1: Organization
12.5.2 VVP Section 4.2: Master schedule
12.5.3 VVP Section 4.3: Integrity level scheme
12.5.4 VVP Section 4.4: Resources summary
12.5.5 VVP Section 4.5: Responsibilities
12.5.6 VVP Section 4.6: Tools, techniques, and methods
12.6 VVP Section 5: V&V processes
12.6.1 VVP Section 5.1: Common V&V Processes, Activities, and Tasks
12.6.2 VVP Section 5.2: System V&V Processes, Activities, and Tasks
12.6.3 VVP Section 5.3: Software V&V Processes, Activities, and Tasks
12.6.4 VVP Section 5.4: Hardware V&V Processes, Activities, and Tasks
12.7 VVP Section 6: V&V reporting requirements
12.8 VVP Section 7: V&V administrative requirements
12.8.1 General
12.8.2 VVP Section 7.1: Anomaly resolution and reporting
12.8.3 VVP Section 7.2: Task iteration policy
12.8.4 VVP Section 7.3: Deviation policy
12.8.5 VVP Section 7.4: Control procedures
12.8.6 VVP Section 7.5: Standards, practices, and conventions
12.9 VVP Section 8: V&V test documentation requirements
Annex A (informative) Mapping of IEEE 1012 V&V activities and tasks
A.1 Mapping of ISO/IEC 15288 V&V requirements to IEEE 1012 V&V activities and tasks
A.2 Mapping of IEEE 1012 V&V activities to ISO/IEC 15288 system life cycle processes and activities
A.3 Mapping of ISO/IEC 12207 V&V requirements to IEEE 1012 V&V activities and tasks
A.4 Mapping of IEEE 1012 V&V activities to IEEE 12207 software life cycle processes and activities
Annex B (informative) A risk-based, integrity-level scheme
Annex C (informative) Definition of independent V&V (IV&V)
C.1 Technical independence
C.2 Managerial independence
C.3 Financial independence
C.4 Forms of independence
C.4.1 Classical IV&V
C.4.2 Modified IV&V
C.4.3 Integrated IV&V
C.4.4 Internal IV&V
C.4.5 Embedded V&V
Annex D (informative) V&V of reuse software
D.1 Purpose
D.2 V&V of software developed in a reuse process
D.2.1 V&V of assets in development
D.2.2 V&V of reused assets
D.3 V&V of software developed and reused outside of a reuse process
Annex E (informative) V&V measures
E.1 Introduction
E.2 Measures for evaluating anomaly density
E.3 Measures for evaluating V&V effectiveness
E.4 Measures for evaluating V&V efficiency
Annex F (informative) Example of V&V relationships to other project responsibilities
Annex G (informative) Optional V&V tasks
Annex H (informative) Environmental factors considerations
H.1 Introduction
H.2 In the agreement processes
H.3 In the organizational project-enabling processes
H.4 In the project processes
H.5 In the technical processes
Annex I (informative) V&V of system, software, and hardware integration
I.1 Introduction
I.2 Examples of system failures caused by integration issues
I.2.1 Year 2000 System Integration Issue
I.2.2 System architecture integration issues
I.3 System, software, and hardware interaction issues
Annex J (informative) Hazard, security, and risk analyses
J.1 Hazard analysis
Annex K (informative) Example of assigning and changing the system integrity level of “supporting system functions”
Annex L (informative) Mapping of ISO/IEC/IEEE 15288 and IEEE 12207 process outcomes to V&V tasks
Annex M (informative) Bibliography