National foreword

This British Standard is the UK implementation of ISO/IEC/IEEE 12207‑2:2020.

The UK participation in its preparation was entrusted to Technical Committee IST/15/-/3, Life cycle management.

A list of organizations represented on this committee can be obtained on request to its committee manager.

This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application.

Compliance with a British Standard cannot confer immunity from legal obligations.

This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 October 2020.

Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work.

The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the rules given in the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its standards.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC list of patent declarations received (see https://patents.iec.c).

Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISO's adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www.iso.org/iso/foreword.html.

This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and Software Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE.

A list of all parts in the ISO/IEC/IEEE 12207 series can be found on the ISO website.

Any feedback or questions on this document should be directed to the user’s national standards body. A complete listing of these bodies can be found at www.iso.org/members.html.

Introduction

The processes in ISO/IEC/IEEE 12207:2017 form a comprehensive set from which an organization can construct software system life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfil that purpose.

However, ISO/IEC/IEEE 12207:2017 does not include "software-specific processes" as a specialization of system processes, as identified in ISO/IEC 12207:2008, Clause 7. Those processes are partially represented as activities, tasks and NOTEs in processes defined in ISO/IEC/IEEE 12207:2017. This document supports software engineering users of ISO/IEC 12207:2008 in applying their current processes, activities and tasks based on the previous edition to perform effectively and efficiently processes, activities and tasks in ISO/IEC/IEEE 12207:2017. This document also intends to help system engineers using ISO/IEC/IEEE 12207:2017 (or ISO/IEC/IEEE 15288:2015) collaborate with software engineers who have used ISO/IEC 12207:2008.

This document can be used in one or more of the following modes in conjunction with ISO/IEC/IEEE 12207:

By an organization — to help use the current organizational software processes and assets derived from ISO/IEC 12207:2008 in establishing an environment of desired processes of ISO/IEC/IEEE 12207:2017.
By a project — to help use the current project’s software processes and assets derived from ISO/IEC 12207:2008 and extend these to processes of ISO/IEC/IEEE 12207:2017 to provide software systems as products and services.
By an acquirer and a supplier — to help use the current agreement concerning processes and activities derived from ISO/IEC 12207:2008 in establishing an environment of desired processes of ISO/IEC/IEEE 12207:2017.
By process assessors — to serve as an aid to mapping tasks and activities of the previous edition of ISO/IEC 12207:2008 to the process reference model in ISO/IEC/IEEE 12207:2017, Annex C for process assessments that may be used to support organizational process improvement.

1 Scope

This document provides the mapping expressing corresponding relations between software life cycle processes in ISO/IEC/IEEE 12207:2017 and the processes in ISO/IEC 12207:2008.

These relations are demonstrated by means of mapping tables that show relationships between activities and tasks, and process outcomes.

This mapping assists users of ISO/IEC 12207:2008 to transition to using ISO/IEC/IEEE 12207:2017.

This document will help users understand the differences between the reference processes and requirements of the two editions of ISO/IEC/IEEE 12207, and any potential gaps or process enhancements that can be needed in seeking conformance to and/or using ISO/IEC/IEEE 12207:2017. Also, this document provides to such users the mapping which helps to identify corresponding process outcomes, activities and tasks of processes for software systems in ISO/IEC/IEEE 12207:2017.

The mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008 in this document can be used as a basis to continuously conduct, improve and extend current process assets including software specific process assets based on ISO/IEC 12207:2008 for effective implementation of ISO/IEC/IEEE 12207:2017. These process activities and tasks can be applied iteratively.

2 Normative references

3 Terms and definitions

4 Purpose

5 Overview of the mappings

5.1 General

5.2 Compound and singular requirements

6 Outcome mappings

6.1 Outcome mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC 12207:2008

6.2 Outcome mapping from ISO/IEC 12207:2008 to ISO/IEC/IEEE 12207:2017

7 Activity and task-level mappings

7.1 Activity and task-level mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC 12207:2008 edition

7.2 Activity and task-level mapping from ISO/IEC 12207:2008 to ISO/IEC/IEEE 12207:2017

Bibliography

BS ISO/IEC/IEEE 12207-2:2020

Systems and software engineering. Software life cycle processes - Relation and mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008

Current, Under Review

Published:

31 Oct 2020