1、Systems and software engineering Software life cycle processesIngnierie des systmes et du logiciel Processus du cycle de vie du logicielINTERNATIONAL STANDARDISO/IEC/IEEE12207Reference numberISO/IEC/IEEE 12207:2017(E)First edition2017-11 ISO/IEC 2017 IEEE 2017 ISO/IEC 2017 All rights reservedii IEEE
2、 2017 All rights reservedISO/IEC/IEEE 12207: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 in any form or by any means, electronic or mechanical, including
3、photocopying and microfilm, without permission in writing from ISO, IEC or IEEE at the respective address below.ISO copyright office Institute of Electrical and Electronics Engineers, IncCh. de Blandonnet 8 CP 401 3 Park Avenue, New YorkCH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USATel. +41
4、 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org stds.iprieee.orgwww.iso.org www.ieee.orgISO/IEC/IEEE 12207:2017(E) iii ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Contents Page Foreword . vi Introduction . vii 1 Scope 1 1.1 Overview . 1 1.2 Purpose . 1 1.3 Field of application
5、 1 1.4 Limitations . 2 2 Normative references . 2 3 Terms, definitions, and abbreviated terms . 2 3.1 Terms and definitions 2 3.2 Abbreviated terms 11 4 Conformance . 11 4.1 Intended usage . 11 4.2 Full conformance . 12 4.2.1 Full conformance to outcomes 12 4.2.2 Full conformance to tasks 12 4.3 Tai
6、lored conformance . 12 5 Key concepts and application 13 5.1 Introduction 13 5.2 Software system concepts 13 5.2.1 Software systems . 13 5.2.2 Software system structure . 13 5.2.3 Enabling systems . 15 5.2.4 Life cycle processes for the software system . 16 5.3 Organization and project concepts 16 5
7、.3.1 Organizations . 16 5.3.2 Organization and project-level adoption 17 5.4 Life cycle concepts 17 5.4.1 Software life cycle stages 17 5.4.2 Life cycle model for the software system 17 5.5 Process concepts . 19 5.5.1 Criteria for processes . 19 5.5.2 Description of processes . 19 5.5.3 General char
8、acteristics of processes 19 5.5.4 Tailoring . 19 5.6 Process groups . 19 5.6.1 Introduction 19 5.6.2 Agreement processes . 21 5.6.3 Organizational project-enabling processes 22 5.6.4 Technical Management processes . 22 5.6.5 Technical processes . 22 5.7 Process application 22 5.8 Process reference m
9、odel 23 6 Software life cycle processes . 24 6.1 Agreement processes . 24 6.1.1 Acquisition process 24 6.1.2 Supply process . 27 6.2 Organizational Project-Enabling processes . 28 6.2.1 Life cycle model management process . 29 6.2.2 Infrastructure Management process 30 6.2.3 Portfolio Management pro
10、cess . 31 6.2.4 Human Resource Management process . 33 ISO/IEC/IEEE 12207:2017(E) iv ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved 6.2.5 Quality Management process . 34 6.2.6 Knowledge Management process . 36 6.3 Technical Management processes 37 6.3.1 Project Planning process . 38
11、6.3.2 Project assessment and control process 40 6.3.3 Decision Management process 43 6.3.4 Risk Management process 44 6.3.5 Configuration Management process 46 6.3.6 Information Management process . 50 6.3.7 Measurement process 52 6.3.8 Quality Assurance process 53 6.4 Technical processes 55 6.4.1 B
12、usiness or Mission Analysis process . 56 6.4.2 Stakeholder Needs and Requirements Definition process 59 6.4.3 System/Software requirements definition process . 63 6.4.4 Architecture Definition process 66 6.4.5 Design Definition process . 71 6.4.6 System Analysis process 74 6.4.7 Implementation proce
13、ss . 75 6.4.8 Integration process . 79 6.4.9 Verification process 82 6.4.10 Transition process. 85 6.4.11 Validation process . 89 6.4.12 Operation process . 92 6.4.13 Maintenance process 95 6.4.14 Disposal process 99 Annex A (normative) Tailoring process . 102 A.1 Introduction . 102 A.2 Tailoring pr
14、ocess 102 A.2.1 Purpose 102 A.2.2 Outcomes . 102 A.2.3 Activities and tasks 102 Annex B (informative) Examples of process information items . 104 Annex C (informative) Process Reference Model for assessment purposes . 107 C.1 Introduction . 107 C.2 Conformance with ISO/IEC 33004 . 107 C.2.1 General
15、. 107 C.2.2 Requirements for process reference models 107 C.2.3 Process descriptions 108 C.3 The process reference model . 108 Annex D (informative) Process integration and process constructs 109 D.1 Introduction . 109 D.2 Process constructs and their usage 109 Annex E (informative) Process views 11
16、1 E.1 Introduction . 111 E.2 The process view concept 111 E.3 Process viewpoint 111 E.4 Process view for specialty engineering . 112 E.5 Process view for interface management . 114 E.6 Process view for software assurance (Information security) 116 Annex F (informative) Software system architecture m
17、odelling 120 F.1 Introduction . 120 F.2 Views, models and model kinds used in software system architecture . 120 F.2.1 Functional model 120 F.2.2 Static model 121 F.2.3 Data model 121 F.2.4 Behavioral model 121 F.2.5 Temporal model 121 F.2.6 Structural model . 121 ISO/IEC/IEEE 12207:2017(E) v ISO/IE
18、C 2017 All rights reserved IEEE 2017 All rights reserved F.2.7 Network model 121 F.3 Other model considerations 121 Annex G (informative) Application of software life cycle processes to a system of systems . 123 G.1 Introduction 123 G.2 SoS characteristics and types 123 G.3 SE processes applied to s
19、ystems of systems . 124 G.3.1 General . 124 G.3.2 Agreement processes . 124 G.3.3 Organizational project enabling processes 124 G.3.4 Technical management processes . 125 G.3.5 Technical processes . 125 Annex H (informative) Application of Agile . 127 Annex I (informative) Process Mapping from ISO/I
20、EC/IEEE 12207:2008 . 129 Bibliography . 143 List of Illustrations Figure 1 Software system and software system element relationship . 14 Figure 2 Example of software system-of-interest structure . 14 Figure 3 Software system-of-interest, its operational environment and enabling systems 15 Figure 4 S
21、oftware life cycle processes . 21 Table B.1 Sample information items by process . 104 Figure D.1 ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015 process constructs . 110 Table G.1 System of Systems types 123 Table I.1 Comparison of processes in ISO/IEC/IEEE 12207:2017 and the previous edition 12
22、9 Table I.2 Comparison of process outcomes in ISO/IEC/IEEE 12207:2017 and software-related outcomes in the previous edition 131 ISO/IEC/IEEE 12207:2017(E) vi ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Foreword ISO (the International Organization for Standardization) and IEC (the
23、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 particul
24、ar fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and nongovernmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have establish
25、ed 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) Standards Board. The IEEE develops its standards through a consensus development process, approved by t
26、he 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 t
27、o 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. The procedures used to develop this document and those intended for its further maintenance are described in the ISO/I
28、EC Directives, Part 1. In particular, the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is drawn to the possibility tha
29、t some of the elements of this document may be the subject of patent rights. ISO, IEC, and IEEE 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 li
30、st of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as we
31、ll as information about ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL www.iso.org/iso/foreword.html. This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Syst
32、ems and software engineering, in cooperation with the IEEE Computer Society Systems and Software Engineering Standards Committee, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE. This first edition of ISO/IEC/IEEE 12207 cancels and replaces ISO/IEC 122
33、07:2008 (second edition), which has been technically revised. Changes in this revision of ISO/IEC/IEEE 12207 were developed in conjunction with a corresponding revision of ISO/IEC/IEEE 15288:2015, Systems and software engineering System life cycle processes. The purpose of these revisions is to acco
34、mplish the harmonization of the structures and contents of the two documents, while supporting the requirements of the engineering and assessment communities. This document was developed with the following goals: provide a common terminology between the revision of ISO/IEC/IEEE 15288 and ISO/IEC/IEE
35、E 12207; where applicable, provide common process names and process structure between the revision of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207; and enable the user community to evolve towards fully harmonized standards, while allowing backward compatibility. This revision is intended to achieve a f
36、ully harmonized view of the system and software life cycle processes. ISO/IEC/IEEE 12207:2017(E) vii ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Introduction The complexity of software systems has increased to an unprecedented level. This has led to new opportunities, but also to
37、increased challenges for the organizations that create and utilize systems. These challenges exist throughout the life cycle of a system and at all levels of architectural detail. This document provides a common process framework for describing the life cycle of systems created by humans, adopting a
38、 Software Engineering approach. Software Engineering is an interdisciplinary approach and means to enable the realization of successful software systems. It focuses on defining stakeholder needs and required functionality early in the development cycle, documenting requirements, and performing desig
39、n synthesis and system validation while considering the complete problem. It integrates all the disciplines and specialty groups into a team effort forming a structured development process that proceeds from concept to production to operation and maintenance. It considers both the business and the t
40、echnical needs of all stakeholders with the goal of providing a quality product that meets the needs of users and other applicable stakeholders. This life cycle spans the conception of ideas through to the retirement of a system. It provides the processes for acquiring and supplying systems. It help
41、s to improve communication and cooperation among the parties that create, utilize and manage modern software systems in order that they can work in an integrated, coherent fashion. In addition, this framework provides for the assessment and improvement of the life cycle processes. The processes in t
42、his document form a comprehensive set from which an organization can construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more
43、of the following modes: a) By an organization to help establish an environment of desire d processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools and trained personnel. The organization may then employ this environment to perform and manage its pro
44、jects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project to help select, structure and employ the element s of an established environment to provide product
45、s and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment. c) By an acquirer and a supplier to help develop an agreement co ncerning processes and activities. Via the agreement, the processes and activities in this
46、 document are selected, negotiated, agreed to and performed. In this mode, this document is used for guidance in developing the agreement. d) By process assessors to serve as a process reference model fo r use in the performance of process assessments that may be used to support organizational proce
47、ss improvement. INTERNATIONAL STANDARD ISO/IEC/IEEE 12207:2017(E) 1 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Systems and software engineering Software life cycle processes 1 Scope 1.1 Overview This document establishes a common framework for software life cycle processes, with
48、welldefined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are applicable during the acquisition, supply, development, operation, maintenance or disposal of software systems, products, and services. These life cycle processes are accom
49、plished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. This document applies to the acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of software systems, products and services, and the software portion of any system, Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for softwar
