ISO 12207, 15288 and 15289
Systems and software engineering
© 2016 The European Organisation for the Safety of Air Navigation (EUROCONTROL) – All rights reserved.
High level structure
ISO 12207:2017
ISO 24748-3:2020
• Systems and software engineering -- Software life cycle
processes
• Guide to the application of
ISO 12207
ISO 15289:2019
• Systems and software engineering -- Content of lifecycle information items (documentation)
ISO 15288:2023
ISO 24748-2:2018
• Systems and software engineering -- System life cycle
processes
• Guide to the application of
ISO 15288
ISO 24748-1:2018
• Guide for life cycle management
System versus Software
• From ISO 24748-3
• In EC 2017/373
− People
− Procedure
− Equipment
o Hardware
o Software
ISO 15288:2023 System life cycle
processes
• “This document establishes a common framework of
process descriptions for describing the life cycle of
systems created by humans, defining a set of
processes and associated terminology from an
engineering viewpoint. ”
Example Configuration Management
6.3.5 Configuration Management Process
6.3.5.1 Purpose
The purpose of Configuration Management (CM) is to manage and
control system elements and configurations over the life cycle.
CM also manages consistency between a product and its associated
configuration definition.
6.3.5.2 Outcomes
As a result of the successful implementation of the Configuration
Management Process:
a) Items requiring configuration management are identified and
managed.
b) Configuration baselines are established.
…
Example Configuration Management
6.3.5.3 Activities and tasks
The project shall implement the following activities and tasks in
accordance with applicable organization policies and procedures
with respect to the Configuration Management process.
a) Plan Configuration management. This activity consists of the
following tasks:
1) Define a configuration management strategy.
2) Define the archive and retrieval approach for configuration items,
configuration management artifacts and data.
ISO 12207:2017 Software life cycle
processes
• “This document establishes a common
framework for software life cycle
processes, with well‐defined
terminology, that can be referenced by
the software industry. It contains
processes, activities, and tasks that are
applicable during the acquisition,
supply, development, operation,
maintenance or disposal of software
systems, products, and services. These
life cycle processes are accomplished
through the involvement of
stakeholders, with the ultimate goal of
achieving customer satisfaction.”
Example Configuration Management
6.3.5 Configuration Management Process
6.3.5.1 Purpose
The purpose of Configuration Management is to manage and control
system elements and configurations over the life cycle. Configuration
Management (CM) also manages consistency between a product and
its associated
configuration definition.
6.3.5.2 Outcomes
As a result of the successful implementation of the Configuration
Management process:
a) Items requiring configuration management are identified and
managed.
b) Configuration baselines are established.
…
Example Configuration Management
6.3.5.3 Activities and tasks
The project shall implement the following activities and tasks in
accordance with applicable organization policies
and procedures with respect to the Configuration Management
process.
a) Plan configuration management. This activity consists of the
following tasks:
1) Define a configuration management strategy, including
approaches for the following:
i)…
2) Define the storage, archive and retrieval procedures for
configuration items, CM artifacts, and records.
ISO 15289:2019 Content of life-cycle
information items (documentation)
Refers to ISO 15288:2015
• “This International Standard specifies the purpose and
content of all identified systems and software life-cycle
and service management information items
(documentation). The information item contents are
defined according to generic document types, and the
specific purpose of the document.”
Example 7 Generic types of information
items
a) Description
7.2 Description – generic
content
b) Plan
a) Date of issue and status
c) Policy
b) Scope
d) Procedure
c) Issuing organization
e) Report
d) References
f) Request
e) Context
g) Specification
f) Notation for description
7.1 General
g) Body
h) Summary
i)Glossary
j) Change history
Extract 10 Specific information item
contents
10.2 Acceptance plan
The references are ISO/IEC/IEEE 12207:2017, 6.3.1.3 b) 6) and
ISO/IEC/IEEE 15288:2015, 6.3.1.3 b) 6).
The generic type is plan.
The acceptance plan should prepare for acceptance based on the
defined acceptance strategy and criteria. It specifies objective
criteria for determining acceptability of the deliverable work
products, and any technical processes, methods, or tools required
for product acceptance. Methods such as testing, demonstration,
analysis, and inspection should be specified. It indicates the extent
of supplier involvement. If acceptance is based on tests, it may
reference or provide an overall test plan.
See also software integration test plan.
Extract Table 1 & 2 mapping to processes
ISO 24748-1:2018
Refers to ISO 15288:2015
• “This document provides guidelines
for the life cycle management of
systems and software,
complementing the processes
described in ISO/IEC/IEEE 15288 and
ISO/IEC/IEEE 12207.”
ISO 24748-2:2018
Refers to ISO 15288:2015
• “This document is a guideline for the application of
ISO/IEC/IEEE 15288:2015. It addresses system, life cycle,
organizational, project, and process, concept application,
principally through reference to ISO/IEC/IEEE 24748-1 and
ISO/IEC/IEEE 15288:2015. It gives guidance on applying
ISO/IEC/IEEE 15288:2015 from the aspects of strategy,
planning, application in organizations, and application on
projects.”
High level TOC
Refers to ISO 15288:2015
ISO 24748-3:2020
“The purpose of this document is to provide guidance on the
application of the software life cycle processes standard,
ISO/IEC/IEEE 12207:2017. Taken together, the parts of the
ISO/IEC/IEEE 24748 series are intended to facilitate the joint
usage of the process content of the two high-level life cycle
process standards (ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE
15288:2015), which in turn may be used together with various
more specialized lower-level process standards.”
High level TOC
Questions?