IEEE 1012 2012

$108.88

IEEE Standard for System and Software Verification and Validation

Published By	Publication Date	Number of Pages
IEEE	2012	223

Guaranteed Safe Checkout

Category: IEEE

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

Description

Revision Standard – Active. Verification and validation (V&V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&V life cycle process requirements are specified for different integrity levels. The scope of V&V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), nondevelopmental items]. The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes documentation. V&V processes include the analysis, evaluation, review, inspection, assessment, and testing of products.

PDF Catalog

PDF Pages	PDF Title
1	IEEE Std 1012-2012 Front Cover
3	Title Page
6	Notice to users Laws and regulations Copyrights Updating of IEEE documents Errata
7	Patents
8	Participants
10	Introduction
12	Contents
15	Important notice 1. Overview 1.1 Scope
16	1.2 Purpose
17	1.3 Field of application
18	1.4 V&V objectives 1.5 Organization of the standard
20	1.6 Audience
21	1.7 Conformance 1.8 Disclaimer 2. Normative references 3. Definitions, abbreviations, and acronyms 3.1 Definitions
25	3.2 Abbreviations and acronyms
26	4. Relationships between V&V and life cycle processes
29	5. Integrity levels
31	6. V&V processes overview 6.1 General
32	6.2 V&V testing
33	7. Common V&V activities 7.1 Activity: V&V Management
34	7.2 Activity: Acquisition Support V&V
35	7.3 Activity: Supply Planning V&V 7.4 Activity: Project Planning V&V 7.5 Activity: Configuration Management V&V
47	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
48	8.3 Activity: Architectural Design V&V
49	8.4 Activity: Implementation V&V 8.5 Activity: Integration V&V
50	8.6 Activity: Transition V&V 8.7 Activity: Operation V&V
51	8.8 Activity: Maintenance V&V
52	8.9 Activity: Disposal V&V
82	9. Software V&V activities 9.1 Activity: Software Concept V&V 9.2 Activity: Software Requirements V&V
83	9.3 Activity: Software Design V&V 9.4 Activity: Software Construction V&V
84	9.5 Activity: Software Integration Test V&V 9.6 Activity: Software Qualification Test V&V
85	9.7 Activity: Software Acceptance Test V&V 9.8 Activity: Software Installation and Checkout V&V
86	9.9 Activity: Software Operation V&V 9.10 Activity: Software Maintenance V&V
87	9.11 Activity: Software Disposal V&V
124	10. Hardware V&V activities 10.1 Activity: Hardware Concept V&V 10.2 Activity: Hardware Requirements V&V
125	10.3 Activity: Hardware Design V&V 10.4 Activity: Hardware Fabrication V&V
126	10.5 Activity: Hardware Integration Test V&V 10.6 Activity: Hardware Qualification Test V&V
127	10.7 Activity: Hardware Acceptance Test V&V 10.8 Activity: Hardware Transition V&V
128	10.9 Activity: Hardware Operation V&V 10.10 Activity: Hardware Maintenance V&V
129	10.11 Activity: Hardware Disposal V&V
161	11. V&V reporting, administrative, and documentation requirements 11.1 V&V reporting requirements
164	11.2 V&V administrative requirements 11.3 V&V documentation requirements
165	12. V&V plan outline 12.1 Overview
166	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
167	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
168	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
169	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
170	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
172	A.2 Mapping of IEEE 1012 V&V activities to ISO/IEC 15288 system life cycle processes and activities
173	A.3 Mapping of ISO/IEC 12207 V&V requirements to IEEE 1012 V&V activities and tasks
175	A.4 Mapping of IEEE 1012 V&V activities to IEEE 12207 software life cycle processes and activities
177	Annex B (informative) A risk-based, integrity-level scheme
179	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
180	C.4.1 Classical IV&V C.4.2 Modified IV&V C.4.3 Integrated IV&V C.4.4 Internal IV&V
181	C.4.5 Embedded V&V
182	Annex D (informative) V&V of reuse software D.1 Purpose
183	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
189	Annex E (informative) V&V measures E.1 Introduction E.2 Measures for evaluating anomaly density
190	E.3 Measures for evaluating V&V effectiveness E.4 Measures for evaluating V&V efficiency
192	Annex F (informative) Example of V&V relationships to other project responsibilities
193	Annex G (informative) Optional V&V tasks
199	Annex H (informative) Environmental factors considerations H.1 Introduction H.2 In the agreement processes H.3 In the organizational project-enabling processes
200	H.4 In the project processes H.5 In the technical processes
202	Annex I (informative) V&V of system, software, and hardware integration I.1 Introduction I.2 Examples of system failures caused by integration issues
203	I.2.1 Year 2000 System Integration Issue I.2.2 System architecture integration issues
204	I.3 System, software, and hardware interaction issues
207	Annex J (informative) Hazard, security, and risk analyses J.1 Hazard analysis
212	Annex K (informative) Example of assigning and changing the system integrity level of “supporting system functions”
214	Annex L (informative) Mapping of ISO/IEC/IEEE 15288 and IEEE 12207 process outcomes to V&V tasks
223	Annex M (informative) Bibliography