ISO/IEC 12207:1995/Amd 2:2004

INTERNATIONAL ISO/IEC
STANDARD 12207
First edition
1995-08-01
AMENDMENT 2
2004-11-01


Information technology — Software life
cycle processes
AMENDMENT 2
Technologies de l'information — Processus du cycle de vie du logiciel
AMENDEMENT 2




Reference number
ISO/IEC 12207:1995/Amd.2:2004(E)
©
ISO/IEC 2004

---------------------- Page: 1 ----------------------
ISO/IEC 12207:1995/Amd.2:2004(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


©  ISO/IEC 2004
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2004 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 12207:1995/Amd.2:2004(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
Amendment 2 to ISO/IEC 12207:1995 was prepared by Technical Committee ISO/IEC JTC 1, Information
technology, Subcommittee SC 7, Software and systems engineering.
ISO/IEC 12207 was published on 1 August 1995 and is the first International Standard to provide a
comprehensive set of life-cycle processes, activities and tasks for software that is part of a larger system,
stand-alone software product, and software services. It provides common software process architecture for
the acquisition, supply, development, operation and maintenance of software. It also provides the necessary
supporting and organizational processes, activities and tasks for managing and improving the processes.
Amendment 1 was published in 2002 to establish a coordinated set of software process information that can
be used for process definition and process assessment and improvement. Amendment 1 resolved the
granularity issue related to the use of ISO/IEC 12207 for process assessment and provides the process
purpose and outcomes to establish a Process Reference Model in accordance with the requirements of
ISO/IEC 15504-2. A Process Reference Model provides definitions of processes in a life cycle described in
terms of process purpose and outcomes, together with an architecture describing relationships between the
processes. A Process Reference Model provides the mechanism whereby externally defined assessment
models are related to the assessment framework defined by ISO/IEC 15504.
The use of Amendment 1 for process assessment revealed technical defects and editorial issues in certain
processes of the Process Reference Model. These technical defects and editorial issues are documented in
Defect Report N2873. The noted defects have impacted the development of the exemplar assessment model
ISO/IEC 15504-5. Amendment 2 resolves these deficiencies and provides to the users of the Process
Reference Model and to the developers of assessment models an improved basis for their work.
This amendment addresses a number of minor technical and editorial issues in Amendment 1, i.e.
ISO/IEC 12207:1995/Amd.1:2002. The amendment contains:
a) Statements of Purpose and Outcomes for several processes identified within the scope of Amendment 1;
b) Corrections to statements of Purpose and Outcomes for several processes, for technical reasons; and
c) Corrections to statements of Purpose and Outcomes for several processes, to correct editorial
deficiencies.


© ISO/IEC 2004 — All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 12207:1995/Amd.2:2004(E)
Information technology — Software life cycle processes
AMENDMENT 2
1 Changes to the Text of ISO/IEC 12207:1995/AMD 1:2002:
1.1 Clause F.1.2 is modified as follows:
F.1.2 Supply Process
Purpose:
The purpose of the Supply process is to provide a product or service to the customer that meets the agreed
requirements.
Outcomes:
As a result of successful implementation of the Supply process:
1. a response to a customer's request is produced;
2. an agreement is established between the customer and the supplier for developing, maintaining,
operating, packaging, delivering, and installing the product and/or service;
3. a product and/or service that meets the agreed requirements are developed by the supplier;
4. the product and/or service is delivered to the customer in accordance with the agreed requirements; and
5. the product is installed in accordance with the agreed requirements.
The Supply Process includes purposes and outcomes for the following sub-processes:
 Supplier tendering;
 Contract agreement;
 Product release;
 Product acceptance support.
F.1.2.1 Supplier tendering
Purpose:
The purpose of Supplier tendering is to establish an interface to respond to customer inquiries and requests
for proposal, prepare and submit proposals, and confirm assignments through the establishing of a relevant
agreement / contract.
© ISO/IEC 2004 — All rights reserved 1

---------------------- Page: 4 ----------------------
ISO/IEC 12207:1995/Amd.2:2004(E)
Outcomes:
As a result of successful implementation of Supplier tendering:
1) a communication interface is established and maintained in order to respond to customer inquiries and
requests for proposal;
2) requests for proposal are evaluated according to defined criteria to determine whether or not to submit a
proposal;
3) the need to undertake preliminary surveys or feasibility studies is determined;
4) suitable resources are identified to perform the proposed work;
5) a supplier proposal is prepared and submitted in response to the customer request; and
6) formal confirmation of agreement is obtained.
F.1.2.2 Contract agreement
Purpose:
The purpose of Contract agreement is to negotiate and approve a contract / agreement that clearly and
unambiguously specifies the expectations, responsibilities, work products / deliverables and liabilities of both
the supplier(s) and the acquirer.
Outcomes:
As a result of successful implementation of Contract agreement:
1) a contract / agreement is negotiated, reviewed, approved and awarded to the supplier(s);
2) mechanisms for monitoring the capability and performance of the supplier(s) and for mitigation of
identified risks are reviewed and considered for inclusion in the contract conditions;
3) proposers/tenderers are notified of the result of proposal /tender selection; and
4) formal confirmation of agreement is obtained.
F.1.2.3 Product release
Purpose:
The purpose of Product release is to control the availability of a product to the intended customer.
Outcomes:
As a result of the successful implementation of Product release:
1) the contents of the product release are determined;
2) the release is assembled from configured items;
3) the release documentation is defined and produced;
4) the release delivery mechanism and media is determined;
5) release approval is effected against defined criteria;
6) the product release is made available to the intended customer; and
7) confirmation of release is obtained.
2 © ISO/IEC 2004 — All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 12207:1995/Amd.2:2004(E)
F.1.2.4 Product acceptance support
Purpose:
The purpose of Product acceptance support is to assist the customer to achieve confidence that the product
meets requirements.
Outcomes:
As a result of successful implementation of the Product acceptance support:
1) the product is completed and delivered to the customer;
2) customer acceptance tests and reviews are supported;
3) the product is put into operation in the customer’s environment; and
4) problems detected during acceptance are identified and communicated to those responsible for resolution.
NOTE Incremental delivery would be in completed increments.
1.2 Clause F.2.2 is modified as follows:
F.2.2 Configuration Management Process
Purpose:
The purpose of the Configuration management process is to establish and maintain the integrity of the work
products/items of a process or project and make them available to concerned parties.
Outcomes:
As a result of successful implementation of the Configuration management process:
1) a configuration management strategy is developed;
2) work products/items generated by the process or project are identified, defined and baselined;
3) modifications and releases of the work products/items are controlled;
4) modifications and releases are made available to affected parties;
5) the status of the work products/items and modifications are recorded and reported;
6) the completeness and consistency of the work products/items is ensured; and
7) the st
...