ISO/IEC/IEEE 15289:2011

INTERNATIONAL ISO/IEC/
STANDARD IEEE
15289
First edition
2011-11-01

Systems and software engineering —
Content of life-cycle information products
(documentation)
Ingénierie des systèmes et du logiciel — Contenu des systèmes et
produits d'information du processus de cycle de vie du logiciel
(documentation)




Reference number
ISO/IEC/IEEE 15289:2011(E)

©
ISO/IEC 2011
©
IEEE 2011

---------------------- Page: 1 ----------------------
ISO/IEC/IEEE 15289:2011(E)

COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2011
©  IEEE 2011
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 ISO, IEC or IEEE at the respective
address below.
ISO copyright office IEC Central Office Institute of Electrical and Electronics Engineers, Inc.
Case postale 56 3, rue de Varembé 3 Park Avenue, New York
CH-1211 Geneva 20 CH-1211 Geneva 20 NY 10016-5997, USA
Tel. + 41 22 749 01 11 Switzerland E-mail stds.ipr@ieee.org
Fax + 41 22 749 09 47 E-mail inmail@iec.ch Web www.ieee.org
E-mail copyright@iso.org Web www.iec.ch
Web www.iso.org
Published in Switzerland

© ISO/IEC 2011 – All rights reserved
ii © IEEE 2011 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC/IEEE 15289:2011(E)
Contents Page
Foreword .vii
Introduction.viii
1 Scope.1
2 Applicability.2
2.1 Purpose.2
2.2 Intended users of this International Standard.3
2.3 Applicability to work efforts .3
2.4 Applicability to information item audiences.3
3 Conformance .4
3.1 Definition of conformance.4
3.2 Conformance situations .4
3.3 Type of conformance .5
4 Normative references.5
5 Terms and definitions .5
6 Life cycle data and information items .8
6.1 Life cycle data characteristics .8
6.2 Records compared to information items (documents) .8
6.3 Management of life cycle data (records).9
6.4 Management of information items (documents) .9
6.4.1 Developing the documentation plan .9
6.4.2 Managing and controlling information items .10
7 Generic types of information items .10
7.1 General.10
7.2 Description – generic content.10
7.3 Plan – generic content .11
7.4 Policy – generic content .13
7.5 Procedure – generic content.13
7.6 Report – generic content .14
7.7 Request – generic content.15
7.8 Specification – generic content .16
8 Mapping of information items to the life cycle and service management processes.16
8.1 Mapping of information items to the system life cycle .17
8.2 Mapping of information items to the software life cycle .22
8.3 Mapping of information items to the service management processes .33
9 Records.38
9.1 Record – generic content .38
9.2 Specific record contents.38
10 Specific information item (document) contents.42
10.1 General.42
10.2 Acceptance plan.42
10.3 Acceptance review and testing report .43
10.4 Acquisition plan.43
10.5 Asset management plan .43
10.6 Audit acknowledgement report.44
10.7 Audit plan.44
10.8 Audit procedure.44
10.9 Audit report.44
© ISO/IEC 2011 – All rights reserved
© IEEE 2011 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC/IEEE 15289:2011(E)
10.10 Capacity plan.45
10.11 Capacity management procedure.45
10.12 Change request.45
10.13 Complaint procedure.45
10.14 Concept of operations.46
10.15 Configuration management plan and policy.46
10.16 Configuration management procedure .47
10.17 Configuration status report .48
10.18 Contract.48
10.19 Customer satisfaction survey .49
10.20 Database design description.49
10.21 Development plan.50
10.22 Disposal plan.51
10.23 Documentation plan .51
10.24 Domain engineering plan.51
10.25 Evaluation report.51
10.26 Implementation procedure.52
10.27 Improvement plan.52
10.28 Improvement policy.52
10.29 Incident management procedure .53
10.30 Incident report.53
10.31 Information management plan .54
10.32 Information security plan.54
10.33 Information security policy.55
10.34 Installation plan.55
10.35 Installation report.56
10.36 Integration and test report .56
10.37 Integration plan.56
10.38 Interface description .56
10.39 Life cycle policy and procedure.57
10.40 Maintenance plan.57
10.41 Maintenance procedure.58
10.42 Measurement plan.58
10.43 Monitoring and control report .58
10.44 Operational test procedure.59
10.45 Problem management procedure.59
10.46 Problem report.59
10.47 Process assessment procedure.60
10.48 Process improvement analysis report .60
10.49 Product need assessment .61
10.50 Progress report.61
10.51 Project management plan .62
10.52 Proposal.63
10.53 Qualification test procedure .63
10.54 Qualification test report.63
10.55 Quality management plan .63
10.56 Quality management policy and procedure.64
10.57 Release plan.64
10.58 Request for proposal (RFP) .65
10.59 Resource request.65
10.60 Reuse plan.65
10.61 Review minutes.66
10.62 Risk action request.66
10.63 Risk management policy and plan.66
10.64 Service availability and continuity plan .66
10.65 Service catalog.67
10.66 Service level agreement (SLA) .67
10.67 Service management plan .68
10.68 Service report.68
10.69 Software architecture description.68
© ISO/IEC 2011 – All rights reserved
iv © IEEE 2011 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC/IEEE 15289:2011(E)
10.70 Software design description .69
10.71 Software requirements specification .70
10.72 Software unit description .71
10.73 Software unit test procedure.71
10.74 Software unit test report.72
10.75 Supplier management procedure .72
10.76 Supplier selection procedure.72
10.77 System architecture description.72
10.78 System element description.73
10.79 System requirements specification.73
10.80 Training documentation.74
10.81 Training plan.74
10.82 User documentation.74
10.83 User notification .75
10.84 Validation plan.75
10.85 Validation report.76
10.86 Validation test specification.76
10.87 Verification plan.76
10.88 Verification report.77
Annex A (informative)  Procedure for identifying information items and their contents .78
Annex B (informative)  Information Items and Records by Source .79
Bibliography.83

© ISO/IEC 2011 – All rights reserved
© IEEE 2011 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC/IEEE 15289:2011(E)
List of Tables
Table 1 — Mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), Clauses to Information Items
for Each System Life Cycle Process. 18
Table 2 — Mapping of ISO/IEC 12207:2008 (IEEE Std 12207-2008) Clauses to Information Items
for Each Software Life Cycle Process . 24
Table 3 — Mapping of ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005 Clauses to Information Items
for Each Service Management Process . 34
Table 4 — Record References and Contents. 39
Table B.1 — Information Items by Source. 79
Table B.2 — Records by Source . 81

© ISO/IEC 2011 – All rights reserved
vi © IEEE 2011 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC/IEEE 15289:2011(E)
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. In the field of information technology, ISO
and IEC have established a joint technical committee, ISO/IEC JTC 1.
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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted
by the joint technical committee are circulated to national bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is called to the possibility that implementation of this standard may require the use of subject matter
covered by patent rights. By publication of this standard, no position is taken with respect to the existence or
validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential
patents or patent claims for which a license may be required, for conducting inquiries into the legal validity or
scope of patents or patent claims or determining whether any licensing terms or conditions provided in
connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if
any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly
advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is
entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards
Association.
ISO/IEC/IEEE 15289 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Software and systems engineering, in cooperation with the Software & Systems
Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development
Organization cooperation agreement between ISO and IEEE.
This first edition of ISO/IEC/IEEE 15289 cancels and replaces ISO/IEC 15289:2006, which has been
technically revised.

© ISO/IEC 2011 – All rights reserved
© IEEE 2011 – All rights reserved vii

---------------------- Page: 7 ----------------------
ISO/IEC/IEEE 15289:2011(E)
Introduction
The purpose of this International Standard is to provide requirements for identifying and planning the specific
information items (information products) to be developed and revised during systems and software life cycles
and service processes. This International Standard specifies the purpose and content of all identified systems
and software life-cycle information items, as well as information items for information technology service
management. The information item contents are defined according to generic document types and the specific
purpose of the document. Information items may be combined or subdivided as needed for project or
organizational purposes.
This International Standard is based on the life-cycle processes specified in ISO/IEC 12207:2008
(IEEE Std 12207-2008), Systems and software engineering — Software life cycle processes;
ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering — System life cycle
processes; and the service management processes specified in ISO/IEC 20000-1:2005, Information
technology — Service management — Part 1: Specification; and ISO/IEC 20000-2:2005, Information
technology — Service management — Part 2: Code of practice.
IEEE contributed IEEE 12207.1-1997, Industry Implementation of International Standard ISO/IEC 12207:1995.
(ISO/IEC 12207) Standard for Information Technology — Software life cycle processes — Life cycle data, as a
source for this International Standard.

© ISO/IEC 2011 – All rights reserved
viii © IEEE 2011 – All rights reserved

---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO/IEC/IEEE 15289:2011(E)

Systems and software engineering — Content of life-cycle
information products (documentation)
1 Scope
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, as presented in Clause 7, and the specific purpose of the document
(Clause 10).
This International Standard assumes an organization is implementing life-cycle processes in conformance
with ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering — System life cycle
processes, or ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering — Software
life cycle processes, or practising service management in conformance with ISO/IEC 20000-1:2005,
Information technology — Service management — Part 1: Specification, and ISO/IEC 20000-2:2005,
Information technology — Service management — Part 2: Code of practice. ISO/IEC 12207:2008
(IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for
managing and performing the stages of a systems life cycle. They define an Information Management process,
but they do “not detail documentation in terms of name, format, explicit content, and recording media”
[ISO/IEC 15288:2008 (IEEE Std 15288-2008), 1.4)]. ISO/IEC 12207:2008 (IEEE Std 12207-2008) establishes
a common framework for software life-cycle processes and in passing identifies or requires a number of
documentation items. The Process Reference Model does not represent a particular process implementation
approach, nor does it prescribe a system/software life-cycle model, methodology, or technique.
ISO/IEC 20000-1:2005 establishes general requirements for documents and records (3.2).
ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to
be prepared, nor does it identify information item contents. This International Standard provides a mapping of
ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) clauses with a
set of information items.
The generic document types (which may be referred to as information item types) are to be used to identify
...