IEEE 1012

IEEE 1012
Title	IEEE 1012
Status	Active
Version	2016 (Revision of IEEE Std 1012-2012)
Organization	Institute of Electrical and Electronics Engineers
Committee	IEEE Computer Society / Software & Systems Engineering Standards Committee
Related standards	ISO/IEC/IEEE 12207, ISO/IEC/IEEE 15288, IEEE 829, IEEE 1028
Domain	Software engineering, systems engineering

IEEE 1012. It is a foundational standard within software engineering and systems engineering, formally titled "IEEE Standard for System, Software, and Hardware Verification and Validation." The standard provides a comprehensive framework for planning, executing, and documenting verification and validation processes throughout the system lifecycle. Its primary goal is to ensure that products conform to specified requirements and are fit for their intended use in operational environments.

Overview

The standard is developed and maintained by the Institute of Electrical and Electronics Engineers, specifically through the IEEE Computer Society and its Software & Systems Engineering Standards Committee. It defines a rigorous, integrated process for conducting verification and validation across software, hardware, and entire system of systems. A key aspect of its philosophy is the concept of independence, often recommending that verification and validation activities be performed by personnel not directly involved in the development work to reduce bias. The current version, IEEE Std 1012-2016, is harmonized with other major lifecycle standards like ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288.

Scope and Purpose

The scope of the standard encompasses all software integrity levels and system integrity levels, which it defines based on the potential consequences of failure. It applies to the entire system lifecycle, from initial concept of operations through to disposal. The purpose is to provide a disciplined engineering approach to build quality into products, reduce risk, and provide objective evidence that requirements are met. It is particularly critical in safety-critical systems domains such as avionics, medical devices, nuclear power plants, and automotive systems, where failures can have severe consequences.

Key Concepts and Processes

Central to the standard are the defined software integrity levels and system integrity levels, which range from low to high and determine the rigor of the required verification and validation effort. It mandates the creation of a Verification and Validation Plan early in the project, which is a living document guiding all subsequent activities. The standard details four fundamental verification and validation processes: concept V&V, requirements V&V, design V&V, and implementation V&V. Each process includes specific tasks and defines the required inputs, such as design documentation, and outputs, like anomaly reports.

Verification and Validation Activities

The standard prescribes a wide array of specific activities, including but not limited to traceability analysis, criticality analysis, interface analysis, and hazard analysis. It covers both static techniques, like document review and static code analysis, and dynamic techniques, such as unit testing, integration testing, and system testing. For each software integrity level, it specifies minimum tasks and evaluation criteria. The outputs of these activities feed into formal verification and validation reports and support the overall quality assurance process managed under standards like ISO 9001.

Relationship to Other Standards

IEEE 1012 is designed to be used in conjunction with a family of related IEEE standards. It aligns closely with the process frameworks of ISO/IEC/IEEE 12207 for software and ISO/IEC/IEEE 15288 for systems. It directly references and complements testing documentation standards like IEEE 829 and review process standards like IEEE 1028. In regulated industries, it supports compliance with domain-specific standards such as DO-178C for avionics, IEC 61508 for functional safety, and ISO 26262 for road vehicles.

Applications and Industry Use

The standard is extensively applied in government and commercial projects where reliability and safety are paramount. It is mandated or strongly recommended in contracts for the United States Department of Defense, NASA, and the Federal Aviation Administration. Major corporations in the aerospace sector, such as Boeing and Lockheed Martin, and in the medical device industry, like Medtronic, utilize its processes. Its structured approach to verification and validation is also adopted in the development of complex financial systems and telecommunications infrastructure to ensure robustness and compliance.

Category:IEEE standards Category:Software engineering Category:Systems engineering