ISO IEC IEEE 12207-2017 PDF

Full title and description

ISO/IEC/IEEE 12207:2017 — Systems and software engineering — Software life cycle processes. This international standard establishes a common framework of processes, activities and tasks for the acquisition, supply, development, operation, maintenance and disposal of software and the software portions of systems. It provides consistent terminology, process outcomes and tailoring guidance to be applied at organization or project level.

Abstract

ISO/IEC/IEEE 12207:2017 defines a comprehensive set of software life-cycle processes organized into agreement, organizational, project-enabling, technical management and technical process groups. The standard gives process purposes, outcomes, activities and tasks and is intended to be used for defining, controlling and improving software life cycle processes within an organization or project and during software acquisition. It is aligned with ISO/IEC/IEEE 15288 (system life cycle processes) and can be used in conjunction with it.

General information

• Status: Published / Active standard.
• Publication date: November 2017 (ISO/IEEE publication dates commonly listed as 15 November 2017).
• Publisher: Joint publication by ISO, IEC and IEEE (ISO/IEC/IEEE collaboration; IEEE and ISO hold copyright and distribution).
• ICS / categories: 35.080 (Software engineering / systems and software engineering).
• Edition / version: Edition 1 (2017) — ISO/IEC/IEEE 12207:2017 (supersedes ISO/IEC 12207:2008).
• Number of pages: Vendor listings vary by format — official ISO entry lists 145 pages while some distributors list 157–158 pages depending on publisher formatting; expect roughly 145–158 pages depending on the edition/format.

Scope

The standard specifies software life cycle processes applicable to software systems, software products and software services whether developed internally or by suppliers. It covers acquisition and supply, development (including requirements, architecture, design and implementation), integration, verification, validation, transition, operation, maintenance and disposal. It also provides processes for project and technical management, organizational enabling, agreement management and support activities such as configuration, quality and risk management. It is intended for use alone for software-focused work or together with ISO/IEC/IEEE 15288 for system-of-interest contexts.

Key topics and requirements

• Defined process groups: agreement processes, organizational project‑enabling processes, technical management processes and technical processes (with detailed sub-processes such as requirements, architecture, design, implementation, integration, verification, validation, operation, maintenance and disposal).
• Process purpose and outcomes model: each process is described by its purpose, outcomes and associated activities/tasks to support measurable conformance and tailoring.
• Conformance and tailoring guidance: full and tailored conformance options are described to allow application across projects, organizations and lifecycle models (including agile).
• Emphasis on stakeholder involvement, traceability, configuration and quality management across the software lifecycle.
• Alignment with ISO/IEC/IEEE 15288 to address software within broader system life cycles and ensure consistent outcomes across system/software engineering.

Typical use and users

Used by software and systems engineering organizations, acquirers and suppliers, project and program managers, process engineers, quality assurance teams, and certification bodies. Typical applications include establishing organizational process frameworks, tailoring lifecycle processes for projects, preparing acquisition and supply contracts, process assessments and improvement initiatives, and mapping organizational practices to a common international reference.

Related standards

Closely related to ISO/IEC/IEEE 15288 (Systems and software engineering — System life cycle processes) for system-level processes; it also aligns with other lifecycle and process standards such as ISO/IEC 12207:2008 (superseded), ISO/IEC/IEEE 24748 family (life cycle management guidance) and various ISO/IEC/IEEE standards for requirements, architecture, and software documentation.

Keywords

software life cycle, software processes, acquisition, supply, requirements, architecture, design, implementation, integration, verification, validation, operation, maintenance, disposal, process tailoring, conformance, configuration management, quality assurance, risk management.

FAQ

Q: What is this standard?

A: ISO/IEC/IEEE 12207:2017 is an international standard that defines a structured set of software life cycle processes, activities and tasks for acquiring, supplying, developing, operating, maintaining and disposing of software and software portions of systems.

Q: What does it cover?

A: It covers agreement, organizational and project-enabling, technical management and technical processes — including requirements, architecture, design, implementation, integration, verification, validation, transition, operation, maintenance and disposal — plus supporting activities like configuration, quality and risk management.

Q: Who typically uses it?

A: Organizations and teams involved in software acquisition, development, delivery and maintenance (acquirers, suppliers, project managers, process engineers, QA, systems engineers), and practitioners mapping internal processes to an international reference model.

Q: Is it current or superseded?

A: As published in November 2017, ISO/IEC/IEEE 12207:2017 superseded the 2008 edition and is listed as the 2017 edition. Vendor and standards bodies list it as the active/current version; ISO records note ongoing work to update standards families but the 2017 edition remains the recognized publication. Check with your national standards body or the standards publishers for the very latest status before relying on a newer revision.

Q: Is it part of a series?

A: Yes — it is part of the family of ISO/IEC/IEEE standards addressing system and software life-cycle processes and life-cycle management (notably ISO/IEC/IEEE 15288 and the ISO/IEC/IEEE 24748 series for life cycle management and planning). These documents are intended to be used together where appropriate.

Q: What are the key keywords?

A: Keywords include software life cycle, processes, acquisition, supply, requirements, architecture, design, implementation, integration, verification, validation, operation, maintenance, disposal, tailoring, conformance, configuration and quality management.