1、Systems and software engineering Life cycle management Part 1: Guidelines for life cycle management PD ISO/IEC TS 24748-1:2016 BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06National foreword This Published Document is the UK implementation of ISO/IEC TS 24748-1:20
2、16. It supersedes PD ISO/IEC TR 24748-1:2010 which is withdrawn. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained on request to its secretary. This publication
3、does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 93536 7 ICS 35.080 Compliance with a British Standard cannot confer immunity from
4、legal obligations. This Published Document was published under the authority of the Standards Policy and Strategy Committee on 31 May 2016. Amendments/corrigenda issued since publication Date Text affected PUBLISHED DOCUMENT PD ISO/IEC TS 24748-1:2016Systems and software engineering Life cycle manag
5、ement Part 1: Guidelines for life cycle management Ingnierie des systmes et du logiciel Gestion du cycle de vie Partie 1: Lignes directrices pour la gestion du cycle de vie ISO/IEC TS 24748-1 First edition 2016-05-01 Reference number ISO/IEC TS 24748-1:2016(E) TECHNICAL SPECIFICATION ISO/IEC 2016 PD
6、 ISO/IEC TS 24748-1:2016 ii ISO/IEC 2016 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2016, Published in Switzerland 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,
7、 including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzer
8、land Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC TS 24748-1:2016(E) PD ISO/IEC TS 24748-1:2016 ISO/IEC TS 24748-1:2016(E)Foreword v Introduction vi 1 Scope . 1 2 T erms and definitions . 1 3 Life cycle-related concepts 10 3.1 System concepts 10 3.1.1 General.10 3.
9、1.2 Systems .10 3.1.3 System structure .12 3.1.4 Structure in systems and projects13 3.1.5 Enabling systems 14 3.2 Life cycle concepts 15 3.2.1 System life cycle model15 3.2.2 System life cycle stages . .16 3.2.3 Stages in a system-of-interest and its enabling systems 17 3.3 Process concepts 18 3.3.
10、1 Life cycle processes 18 3.3.2 Process responsibility 21 3.4 Process application 22 3.5 Processes under key views 24 4 Life cycle stages .26 4.1 General 26 4.2 Concept Stage 27 4.2.1 Overview 27 4.2.2 Purpose .28 4.2.3 Outcomes .28 4.3 Development Stage .28 4.3.1 Overview 28 4.3.2 Purpose .29 4.3.3
11、 Outcomes .29 4.4 Production Stage 30 4.4.1 Overview 30 4.4.2 Purpose .30 4.4.3 Outcomes .30 4.5 Utilization Stage 31 4.5.1 Overview 31 4.5.2 Purpose .31 4.5.3 Outcomes .31 4.6 Support Stage 31 4.6.1 Overview 31 4.6.2 Purpose .32 4.6.3 Outcomes .32 4.7 Retirement Stage 32 4.7.1 Overview 32 4.7.2 Pur
12、pose .33 4.7.3 Outcomes .33 5 Life cycle adaptation 33 5.1 General 33 5.2 Adaptation sequence 34 5.2.1 General.34 5.2.2 Identify the project environment and characteristics 35 5.2.3 Solicit inputs .35 ISO/IEC 2016 All rights reserved iii Contents Page PD ISO/IEC TS 24748-1:2016 ISO/IEC TS 24748-1:20
13、16(E)5.2.4 Select the appropriate standards .35 5.2.5 Select life cycle model .36 5.2.6 Select stages and processes .36 5.2.7 Document the adaptation decisions and rationale .36 5.3 Adaptation guidance .37 5.4 Scope adaptation 38 5.5 Stage adaptation .39 5.6 Process adaptation .39 5.7 Life cycle mod
14、el adaptation for domains, disciplines and specialties 39 5.7.1 Adaptation for domains 39 5.7.2 Adaptation for disciplines .41 5.7.3 Adaptation for specialties .41 5.8 Adapting evaluation-related activities 43 6 Relationship with detailed process standards .44 Annex A (informative) Process views .46
15、 Annex B (informative) Guidance on development strategies and build planning .56 Annex C (informative) Candidate joint management reviews 59 Annex D (informative) Problem reporting capability .62 Bibliography .64 iv ISO/IEC 2016 All rights reserved PD ISO/IEC TS 24748-1:2016 ISO/IEC TS 24748-1:2016(
16、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 tec
17、hnical 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 p
18、art in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different a
19、pproval 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 that some of the elements of this document may be the su
20、bject of patent rights. ISO and IEC 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 list of patent declarations received (see www.iso.org/patents)
21、. 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 well as information about ISOs adherence to the WTO principles
22、 in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 7, Software and systems engineering. This first edition of ISO/IEC/TS 24748-1 cancels and replaces ISO/IEC/TR
23、 24748-1, which has been technically revised. ISO/IEC 24748 consists of the following parts, under the general title Systems and software engineering Life cycle management: Part 1: Guidelines for life cycle management Technical Specification Part 2: Guide to the application of ISO/IEC 15288 (System
24、life cycle processes) Part 3: Guide to the application of ISO/IEC 12207 (Software life cycle processes) Part 4: Systems engineering planning ISO/IEC/IEEE Part 5: Software development planning ISO/IEC/IEEE The following parts are under preparation: Part 6: Guide to system integration engineering ISO/
25、IEC 2016 All rights reserved v PD ISO/IEC TS 24748-1:2016 ISO/IEC TS 24748-1:2016(E) Introduction The purpose of this Technical Specification is to facilitate the joint usage of the process content of the latest revisions of ISO/IEC/IEEE 15288 and ISO/IEC 12207, by providing unified and consolidated
26、 guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combinat
27、ion. That will in turn help a project team design a life cycle model for managing the progress of their project. This Technical Specification will also aid in identifying and planning use of life cycle processes described in ISO/IEC/IEEE 15288 and ISO/IEC 12207 that will enable the project to be com
28、pleted successfully, meeting its objectives/requirements for each stage and for the overall project. Besides the above, there is also increasing recognition of the importance of ensuring that all life cycle stages and all aspects within each stage are supported with thorough guidance to enable align
29、ment with any process documents that might subsequently be created that focus on areas besides systems and software, including hardware, humans, data, processes (e.g. review process), procedures (e.g. operator instructions), facilities and naturally occurring entities (e.g. water, organisms, mineral
30、s). By addressing these needs specifically in this Technical Specification, the users of the process- focused ISO/IEC 12207 and ISO/IEC/IEEE 15288 will not only benefit from having one document complementarily addressing the aspect of product or service life cycle: they will also benefit from a fram
31、ework that links life cycle management aspects to more than just the systems or software aspects of products or services. ISO/IEC/IEEE 15288 and ISO/IEC 12207 also have published guidelines (ISO/IEC/TR 24748-2 and ISO/IEC/TR 24748-3), respectively, to support use of the two revised International Sta
32、ndards individually.vi ISO/IEC 2016 All rights reserved PD ISO/IEC TS 24748-1:2016 Systems and software engineering Life cycle management Part 1: Guidelines for life cycle management 1 Scope This Technical Specification provides guidelines for the life cycle management of systems and software, compl
33、ementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC 12207. This Technical Specification: addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines; establishe
34、s a common framework for describing life cycles, including their individual stages, for the management of projects to provide, or acquire either products or services; defines the concept and terminology of a life cycle; supports the use of the life cycle processes within an organization or a project
35、. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services; provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle; describes the relationship between life cycles and their u
36、se in applying the processes in ISO/IEC/ IEEE 15288 (systems aspects) and ISO/IEC 12207 (software aspects); shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects; and describes how its concepts
37、 relate to detailed process standards, for example, in the areas of measurement, project management and risk management. 2 T erms a nd definiti ons For the purposes of this document, the following terms and definitions apply. 2.1 acquirer stakeholder that acquires or procures a product or service fr
38、om a supplier Note 1 to entry: Other terms commonly used for an acquirer are buyer, customer, owner, purchaser, or internal/organizational sponsor. SOURCE: ISO/IEC/IEEE 15288:2015 2.2 acquisition process of obtaining a system, product or service SOURCE: ISO/IEC/IEEE 15288:2015 TECHNICAL SPECIFICATIO
39、N ISO/IEC TS 24748-1:2016(E) ISO/IEC 2016 All rights reserved 1 PD ISO/IEC TS 24748-1:2016 ISO/IEC TS 24748-1:2016(E) 2.3 activity set of cohesive tasks of a process SOURCE: ISO/IEC/IEEE 15288:2015 2.4 agile development software development approach based on iterative development, frequent inspectio
40、n and adaptation, and incremental deliveries, in which requirements and solutions evolve through collaboration in cross- functional teams and through continual stakeholder feedback SOURCE: ISO/IEC/IEEE 26515:2011 2.5 agreement mutual acknowledgement of terms and conditions under which a working rela
41、tionship is conducted EXAMPLE Contract, memorandum of agreement. SOURCE: ISO/IEC/IEEE 15288:2015 2.6 architecturefundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution Note 1 to entry: ISO/IEC 12207
42、 and ISO/IEC/IEEE 15288 use the word “elements” instead of “components” and this Technical Specification follows that usage. SOURCE: ISO/IEC/IEEE 42010:2011 2.7 architecture framework conventions, principles and practices for the description of architectures established within a specific domain of a
43、pplication and/or community of stakeholders EXAMPLE 1 Generalized Enterprise Reference Architecture and Methodologies (GERAM) (ISO 15704) is an architecture framework. EXAMPLE 2 Reference Model of Open Distributed Processing (RM-ODP) (ISO/IEC 10746) is an architecture framework. SOURCE: ISO/IEC/IEEE
44、 42010:2011 2.8 architecture view work product expressing the architecture of a system from the perspective of specific system concerns SOURCE: ISO/IEC/IEEE 42010:2011 2.9 architecture viewpoint work product establishing the conventions for the construction, interpretation and use of architecture vi
45、ews to frame specific system concerns SOURCE: ISO/IEC/IEEE 42010:20112 ISO/IEC 2016 All rights reserved PD ISO/IEC TS 24748-1:2016 ISO/IEC TS 24748-1:2016(E) 2.10 audit independent examination of a work product or set of work products to assess compliance with specifications, standards, contractual
46、agreements, or other criteria SOURCE: ISO/IEC/IEEE 24765:2010 2.11 baseline approved version of a configuration item, regardless of media, formally designated and fixed at a specific time during the configuration items life cycle SOURCE: IEEE 828:2012 2.12 concept of operations verbal and/or graphic
47、 statement, in broad outline, of an organizations assumptions or intent in regard to an operation or series of operations Note 1 to entry: The concept of operations frequently is embodied in long-range strategic plans and annual operational plans. In the latter case, the concept of operations in the
48、 plan covers a series of connected operations to be carried out simultaneously or in succession. The concept is designed to give an overall picture of the organization operations. See also operational concept (2.25). Note 2 to entry: It provides the basis for bounding the operating space, system cap
49、abilities, interfaces and operating environment. SOURCE: ANSI/AIAA G-043A-2012e 2.13 concerninterest in a system relevant to one or more of its stakeholders Note 1 to entry: A concern pertains to any influence on a system in its environment, including developmental, technological, business, operational, organizational, political, economic, legal, regulatory, ecological and social influences. SOURCE: ISO/IEC/IEEE 42010:2011 2.14 c on f i g u r at ion i t e m item or aggrega
