ISO IEC IEEE 15289-2017 en Systems and software engineering - Content of life-cycle information items (documentation)《系统和软件工程 生命周期信息项目(文件)的内容》.pdf

《ISO IEC IEEE 15289-2017 en Systems and software engineering - Content of life-cycle information items (documentation)《系统和软件工程 生命周期信息项目(文件)的内容》.pdf》由会员分享，可在线阅读，更多相关《ISO IEC IEEE 15289-2017 en Systems and software engineering - Content of life-cycle information items (documentation)《系统和软件工程 生命周期信息项目(文件)的内容》.pdf（97页珍藏版）》请在麦多课文档分享上搜索。

1、Systems and software engineering Content of life-cycle information items (documentation)Ingnierie des systmes et du logiciel Contenu des articles dinformation du cycle de vie (documentation)INTERNATIONAL STANDARDISO/IEC/IEEE15289Reference numberISO/IEC/IEEE 15289:2017(E)Third edition2017-05 ISO/IEC

2、2017 IEEE 2017ii ISO/IEC/IEEE 2017 All rights reservedISO/IEC/IEEE 15289:2017(E)COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland IEEE 2017All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any mean

3、s, 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 ISOs member body in the country of the requester.ISO copyright office Institute of Electrical

4、and Electronics Engineers, IncCh. de Blandonnet 8 CP 401 3 Park Avenue, New YorkCH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USATel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org stds.iprieee.orgwww.iso.org www.ieee.orgISO/IEC/IEEE 15289:2017(E) iii ISO/IEC 2017 All rights reserved I

5、EEE 2017 All rights reserved Contents Page Foreword . vi Introduction . vii 1 Scope 1 2 Normative references . 3 3 Terms, definitions, and abbreviated terms . 3 3.1 Terms and definitions 3 3.2 Abbreviated terms . 6 4 Applicability 6 4.1 Purpose . 6 4.2 Intended users of this document . 6 4.3 Applica

6、bility to work efforts . 7 4.4 Applicability to information item audiences . 7 5 Conformance . 7 5.1 Definition of conformance . 7 5.2 Conformance situations . 8 5.3 Type of conformance . 9 6 Life-cycle data and information items . 9 6.1 Life-cycle data characteristics 9 6.2 Records compared to info

7、rmation items (documents) 9 6.3 Management of life-cycle data (records) . 10 6.4 Management of information items (documents) . 10 6.4.1 Developing the documentation plan 10 6.4.2 Managing and controlling information items 11 7 Generic types of information items . 11 7.1 General . 11 7.2 Description

8、generic content 11 7.3 Plan generic content 12 7.4 Policy generic content . 14 7.5 Procedure generic content 15 7.6 Report generic content . 16 7.7 Request generic content . 18 7.8 Specification generic content . 18 8 Mapping of information items to the life cycle and service management processes .

9、19 8.1 Mapping of information items to the system life cycle 20 8.2 Mapping of information items to the software life cycle . 25 8.3 Mapping of information items to the service management processes . 32 9 Records . 37 9.1 Record generic content . 37 9.2 Specific record contents 38 10 Specific inform

10、ation item (document) contents 41 10.1 General . 41 10.2 Acceptance plan . 41 10.3 Acceptance report . 41 10.4 Acquisition plan . 42 10.5 Asset management plan 42 10.6 Audit acknowledgement report 42 10.7 Audit plan 43 ISO/IEC/IEEE 15289:2017(E) iv ISO/IEC 2017 All rights reserved IEEE 2017 All righ

11、ts reserved 10.8 Audit procedure . 43 10.9 Audit report . 43 10.10 Capacity plan . 43 10.11 Capacity management procedure . 44 10.12 Change request . 44 10.13 Communication procedure . 44 10.14 Complaint procedure . 44 10.15 Concept of operations 45 10.16 Configuration management plan and policy . 4

12、5 10.17 Configuration management procedure 46 10.18 Configuration status report 47 10.19 Contract 47 10.20 Customer satisfaction survey . 48 10.21 Database design description 48 10.22 Development plan . 49 10.23 Disposal plan . 49 10.24 Documentation plan . 50 10.25 Documentation procedure . 50 10.2

13、6 Domain engineering plan 50 10.27 Evaluation report 50 10.28 Implementation procedure 51 10.29 Improvement plan. 51 10.30 Improvement procedure . 51 10.31 Incident management procedure . 52 10.32 Incident report . 52 10.33 Information management plan . 53 10.34 Information management procedure 53 1

14、0.35 Information security plan . 53 10.36 Information security policy 54 10.37 Information security procedure . 54 10.38 Installation plan . 55 10.39 Installation report . 55 10.40 Integration and test report . 55 10.41 Integration plan . 55 10.42 Interface description 56 10.43 Life-cycle policy and

15、 procedure 56 10.44 Maintenance plan 56 10.45 Maintenance procedure 57 10.46 Measurement plan 57 10.47 Measurement procedure . 57 10.48 Monitoring and control report 57 10.49 Operational test procedure 58 10.50 Problem management procedure 58 10.51 Problem report 58 10.52 Process assessment procedur

16、e . 59 10.53 Process improvement report . 59 10.54 Product need assessment 59 10.55 Progress report 60 10.56 Project management plan . 60 10.57 Proposal . 61 10.58 Qualification test procedure 61 10.59 Qualification test report 62 10.60 Quality management plan . 62 10.61 Quality management policy an

17、d procedure 62 10.62 Release plan (and policy) . 63 10.63 Request for proposal (RFP) 64 10.64 Resource request . 64 10.65 Reuse plan . 64 10.66 Review minutes 65 10.67 Risk action request . 65 ISO/IEC/IEEE 15289:2017(E) v ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved 10.68 Risk mana

18、gement policy and plan . 65 10.69 Service catalog 65 10.70 Service continuity and availability plan . 65 10.71 Service level agreement (SLA) . 66 10.72 Service management plan (and policy) 67 10.73 Service plan . 67 10.74 Service report . 68 10.75 Software architecture description . 68 10.76 Softwar

19、e design description 69 10.77 Software requirements specification 70 10.78 Software unit description . 71 10.79 Software unit test procedure . 71 10.80 Software unit test report . 71 10.81 Supplier management procedure 71 10.82 Supplier selection procedure 72 10.83 System architecture description .

20、72 10.84 System element description . 73 10.85 System requirements specification . 73 10.86 Training documentation . 74 10.87 Training plan 74 10.88 User documentation . 74 10.89 User notification 75 10.90 Validation plan . 75 10.91 Validation procedure (validation test specification) 75 10.92 Valid

21、ation report . 75 10.93 Verification plan 75 10.94 Verification procedure 77 10.95 Verification report 77 Annex A (informative) Procedure for identifying information items and their contents 78 Annex B (informative) Information items and records by source 80 Bibliography 84 List of Tables Table 1 Ma

22、pping of ISO/IEC/IEEE 15288:2015, clauses to information items for each system life-cycle process . 21 Table 2 Mapping of ISO/IEC 12207:2008 (IEEE Std 12207-2008) clauses to information items for each software life-cycle process . 26 Table 3 Mapping of ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) an

23、d ISO/IEC 20000-2:2012 (IEEE Std 20000-2:2013) clauses to information items for each service management process . 33 Table 4 Record references and contents . 38 Table B.1 Information items by source 80 Table B.2 Records by source 83 ISO/IEC/IEEE 15289:2017(E) vi ISO/IEC 2017 All rights reserved IEEE

24、 2017 All rights reserved 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 Internationa

25、l 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 nongovernmental, in liaison with IS

26、O 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 (IEEESA

27、) 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

28、 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

29、 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

30、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

31、 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 nondiscriminatory. Users of this document are expressly advised that determination

32、 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

33、, Subcommittee SC 7, Systems and software engineering, in cooperation with the Software ISO/IEC/IEEE 15288:2015, Systems and software engineering System life cycle processes; and the service management processes specified in ISO/IEC 200001:2011 (IEEE Std 200001:2013), Information technology Service

34、management Part 1: Service Management System Requirements; and ISO/IEC 200002:2012 (IEEE Std 200002:2013), Information technology Service management Part 2: Guidance on the application of service management systems. ISO/IEC 12207:2008 (IEEE Std 122072008) and ISO/IEC/IEEE 15288:2015 define a set of

35、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 122072008) est

36、ablish a common framework for systems and software lifecycle 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 lifecycle model, methodology, or tech

37、nique. ISO/IEC 12207:2008 (IEEE Std 122072008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 200001:2011 (IEEE Std 200001:2013) establishes comprehensive requirements for documents and records, with some specific r

38、equirements. ISO/IEC 200002:2012 (IEEE Std 200002:2013), Information technology Service management Pa rt 2: Guidance on the application of service management systems provides guidance on the use of Part 1. IEEE contributed IEEE 12207.11997, Industry Implementation of International Standard ISO/IEC 1

39、2207: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. 1 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Systems and software engineering Content of life-cycle information items

40、(documentation) 1 Scope This document specifies the purpose and content of all identified systems and software lifecycle 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

41、 purpose of the document (Clause 10). This document assumes an organization is performing lifecycle processes, or practicing service management, using one or more of the following: ISO/IEC 12207:2008 (IEEE Std 122072008), Systems and software engineering Software life cycle processes; ISO/IEC/IEEE 1

42、5288:2015, Systems and software engineering Sys tem life cycle processes; ISO/IEC 200001:2011 (IEEE Std 200001:2013), Information technology Service management Part 1: Service management system requirements; and ISO/IEC 200002 (IEEE Std 200002:2013), Information technology Service management Part 2:

43、 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 ser

44、vice management. This document does not establish a service management system. ISO/IEC 12207:2008 (IEEE Std 122072008) 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 d

45、o 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 122072008) establish a common framework for system and software lifecycle processes. They identify or require a number of documentation items. Th

46、eir process reference model does not represent a particular process implementation approach, nor prescribe a system/software lifecycle model, methodology or technique. ISO/IEC 200001:2011 (IEEE Std 200001:2013) establishes comprehensive requirements for documents and records, with some specific requ

47、irements. ISO/IEC 200002:2012 (IEEE Std 200002:2013), provides guidance on the use of ISO/IEC 200001:2011 (IEEE Std 200001: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; organi

48、zational projectenabling; technical management and processes; the ISO/IEC 12207:2008 (IEEE Std 122072008) primary, supporting, and organizational lifecycle processes; and ISO/IEC/IEEE 15289:2017(E) 2 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved the ISO/IEC 200001:2011 (IEEE Std 200

49、001: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 projectenabling, technical management, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 122072008) pr