ISO/IEC/ IEEE Systems and software engineering Content of life-cycle information items (documentation)

Transcription

1 INTERNATIONAL STANDARD This is a preview - click here to buy the full publication ISO/IEC/ IEEE Third edition Systems and software engineering Content of life-cycle information items (documentation) Ingénierie des systèmes et du logiciel Contenu des articles d information du cycle de vie (documentation) Reference number ISO/IEC/IEEE 15289:2017(E) ISO/IEC 2017 IEEE 2017

2 ISO/IEC/IEEE 15289:2017(E) This is a preview - click here to buy the full publication COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland IEEE 2017 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO or IEEE at the address below or ISO s member body in the country of the requester. ISO copyright office Institute of Electrical and Electronics Engineers, Inc Ch. de Blandonnet 8 CP Park Avenue, New York CH-1214 Vernier, Geneva, Switzerland NY , USA Tel Fax copyright@iso.org stds.ipr@ieee.org ii ISO/IEC/IEEE 2017 All rights reserved

3 This is a preview - click here to buy the full publication ISO/IEC/IEEE 15289:2017(E) Contents Page Foreword... vi Introduction... vii 1 Scope Normative references Terms, definitions, and abbreviated terms Terms and definitions Abbreviated terms Applicability Purpose Intended users of this document Applicability to work efforts Applicability to information item audiences Conformance Definition of conformance Conformance situations Type of conformance Life-cycle data and information items Life-cycle data characteristics Records compared to information items (documents) Management of life-cycle data (records) Management of information items (documents) Developing the documentation plan Managing and controlling information items Generic types of information items General Description generic content Plan generic content Policy generic content Procedure generic content Report generic content Request generic content Specification generic content Mapping of information items to the life cycle and service management processes Mapping of information items to the system life cycle Mapping of information items to the software life cycle Mapping of information items to the service management processes Records Record generic content Specific record contents Specific information item (document) contents General Acceptance plan Acceptance report Acquisition plan Asset management plan Audit acknowledgement report Audit plan iii

4 ISO/IEC/IEEE 15289:2017(E) This is a preview - click here to buy the full publication 10.8 Audit procedure Audit report Capacity plan Capacity management procedure Change request Communication procedure Complaint procedure Concept of operations Configuration management plan and policy Configuration management procedure Configuration status report Contract Customer satisfaction survey Database design description Development plan Disposal plan Documentation plan Documentation procedure Domain engineering plan Evaluation report Implementation procedure Improvement plan Improvement procedure Incident management procedure Incident report Information management plan Information management procedure Information security plan Information security policy Information security procedure Installation plan Installation report Integration and test report Integration plan Interface description Life-cycle policy and procedure Maintenance plan Maintenance procedure Measurement plan Measurement procedure Monitoring and control report Operational test procedure Problem management procedure Problem report Process assessment procedure Process improvement report Product need assessment Progress report Project management plan Proposal Qualification test procedure Qualification test report Quality management plan Quality management policy and procedure Release plan (and policy) Request for proposal (RFP) Resource request Reuse plan Review minutes Risk action request iv

5 This is a preview - click here to buy the full publication ISO/IEC/IEEE 15289:2017(E) Risk management policy and plan Service catalog Service continuity and availability plan Service level agreement (SLA) Service management plan (and policy) Service plan Service report Software architecture description Software design description Software requirements specification Software unit description Software unit test procedure Software unit test report Supplier management procedure Supplier selection procedure System architecture description System element description System requirements specification Training documentation Training plan User documentation User notification Validation plan Validation procedure (validation test specification) Validation report Verification plan Verification procedure Verification report Annex A (informative) Procedure for identifying information items and their contents Annex B (informative) Information items and records by source Bibliography List of Tables Table 1 Mapping of ISO/IEC/IEEE 15288:2015, clauses to information items for each system lifecycle process Table 2 Mapping of ISO/IEC 12207:2008 (IEEE Std ) clauses to information items for each software life-cycle process Table 3 Mapping of ISO/IEC :2011 (IEEE Std :2013) and ISO/IEC :2012 (IEEE Std :2013) clauses to information items for each service management process Table 4 Record references and contents Table B.1 Information items by source Table B.2 Records by source v

6 ISO/IEC/IEEE 15289:2017(E) This is a preview - click here to buy the full publication 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. Attention is called to the possibility that implementation of this document may require the use of subject matter covered by patent rights. By publication of this document, no position is taken with respect to the existence or validity of any patent rights in connection therewith. ISO/IEC and IEEE are 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 document 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. This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Systems and software 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 third edition cancels and replaces the second edition (ISO/IEC/IEEE 15289:2015), of which it constitutes a minor revision. This third edition reflects ISO/IEC/IEEE 15288:2015, Systems and software engineering System life cycle processes, which replaced ISO/IEC 15288:2008 (IEEE Std 15288:2008). vi

7 This is a preview - click here to buy the full publication ISO/IEC/IEEE 15289:2017(E) Introduction The purpose of this document 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 document 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 are combined or subdivided as needed for project or organizational purposes. This document is based on the life cycle processes specified in ISO/IEC 12207:2008 (IEEE Std ), Systems and software engineering Software life cycle processes; ISO/IEC/IEEE 15288:2015, Systems and software engineering System life cycle processes; and the service management processes specified in ISO/IEC :2011 (IEEE Std :2013), Information technology Service management Part 1: Service Management System Requirements; and ISO/IEC :2012 (IEEE Std :2013), Information technology Service management Part 2: Guidance on the application of service management systems. ISO/IEC 12207:2008 (IEEE Std ) and ISO/IEC/IEEE 15288:2015 define a set of processes for managing and performing the stages of a system life cycle. They define an Information Management process, but they do not detail information items in terms of name, format, explicit content, and recording media. ISO/IEC/IEEE 15288:2015, and ISO/IEC 12207:2008 (IEEE Std ) establish a common framework for systems and software life cycle processes and identify or require a number of documentation items. Their 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 12207:2008 (IEEE Std ) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC :2011 (IEEE Std :2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC :2012 (IEEE Std :2013), Information technology Service management Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. IEEE contributed IEEE , 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 the first edition of this document. vii

8 This is a preview - click here to buy the full publicationiso/iec/ieee 15289:2017(E) Systems and software engineering Content of life-cycle information items (documentation) 1 Scope This document 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 document assumes an organization is performing life cycle processes, or practicing service management, using one or more of the following: ISO/IEC 12207:2008 (IEEE Std ), Systems and software engineering Software life cycle processes; ISO/IEC/IEEE 15288:2015, Systems and software engineering System life cycle processes; ISO/IEC :2011 (IEEE Std :2013), Information technology Service management Part 1: Service management system requirements; and ISO/IEC (IEEE Std :2013), Information technology Service management Part 2: Guidance on the application of service management systems. This document provides a mapping of processes from the above standards to a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. This document does not establish a service management system. ISO/IEC 12207:2008 (IEEE Std ) and ISO/IEC/IEEE 15288:2015 define a set of processes for managing and performing the stages of a software or system life cycle. They define an Information Management process, but do not detail information items in terms of name, format, explicit content, and recording media. ISO/IEC/IEEE 15288:2015 and ISO/IEC 12207:2008 (IEEE Std ) establish a common framework for system and software life cycle processes. They identify or require a number of documentation items. Their process reference model does not represent a particular process implementation approach, nor prescribe a system/software life cycle model, methodology or technique. ISO/IEC :2011 (IEEE Std :2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC :2012 (IEEE Std :2013), provides guidance on the use of ISO/IEC :2011 (IEEE Std :2013). The generic document types defined in this document are used to identify the information necessary to support the following: the ISO/IEC/IEEE 15288:2015 agreement; organizational project enabling; technical management and processes; the ISO/IEC 12207:2008 (IEEE Std ) primary, supporting, and organizational life cycle processes; and 1

9 ISO/IEC/IEEE 15289:2017(E) This is a preview - click here to buy the full publication the ISO/IEC :2011 (IEEE Std :2013) service management system (SMS), service delivery, relationship, resolution, and control processes. The generic document types (which can be referred to as information item types) are used to identify the information necessary to support the ISO/IEC/IEEE 15288:2015 agreement, organizational project enabling, technical management, and technical processes; the ISO/IEC 12207:2008 (IEEE Std ) primary, supporting, and organizational life cycle processes; or the ISO/IEC :2011 (IEEE Std :2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 15288:2015 or ISO/IEC 12207:2008 (IEEE Std ). As ISO/IEC/IEEE 15288:2015 points out (1.4), The users of this document are responsible for selecting a life cycle model for the project and mapping the processes, activities, and tasks in this document into that model. The parties are also responsible for selecting and applying appropriate methodologies, methods, models and techniques suitable for the project. Thus, information items are combined or subdivided consistent with the life cycle model, as needed for project or organizational purposes, as further defined in Clause 4, Applicability, and Clause 5, Conformance. The scope of this document does not include the following: a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items; b) instructions on combining or subdividing information items and information item contents of a similar nature; c) guidance on selecting an appropriate presentation format, delivery media, and maintenance technology for systems or software life cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories; NOTE 1 ISO/IEC 12207:2008 (IEEE Std ) does not always specify when software information items are to be prepared, nor does it identify information item contents. NOTE 2 ISO/IEC/IEEE 26531, System and software engineering Content management for product life cycle, user, and service management documentation, provides requirements for content management and component content management systems. d) detailed content for information items related to general business, contractual, organizational, and financial management that is not specific to systems and software engineering and information technology service management, such as business strategies, contract change notices, human resources and investment policies, personnel selection criteria, financial budgeting and accounting policies and procedures, cost reports, or payroll data; e) information items showing only approval of an ISO/IEC 12207:2008 (IEEE Std ) subclause, such as ISO/IEC 12207:2008 (IEEE Std ), ; f) any ISO/IEC/IEEE 15288:2015 or ISO/IEC 12207:2008 (IEEE Std ) subclause not explicitly or implicitly identifying the recording of information about a process, activity or task, for example, ISO/IEC 12207:2008 (IEEE Std ), 6.4.4; g) work products, models, software, and other artifacts of life cycle products and services that are not information items or records used in information items. NOTE 3 ISO/IEC 26514:2008, Systems and software engineering Requirements for designers and developers of user documentation, provides guidance on formats for user documentation. 2

10 This is a preview - click here to buy the full publication ISO/IEC/IEEE 15289:2017(E) 2 Normative references The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 12207:2008 (IEEE Std ), Systems and software engineering Software life cycle processes ISO/IEC/IEEE 15288:2015, Systems and software engineering System life cycle processes ISO/IEC :2011 (IEEE Std :2013), Information technology Service management Part 1: Service management system requirements 3