BS ISO IEC IEEE 24748-4-2016 Systems and software engineering Life cycle management Systems engineering planning《系统和软件工程 生命周期管理 系统工程规划》.pdf

1、BS ISO/IEC/IEEE 24748-4:2016 Systems and software engineering Life cycle management Part 4: Systems engineering planning BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO/IEC/IEEE 24748-4:2016 BRITISH STANDARD National foreword This British Standard is the UK i

2、mplementation of ISO/IEC/IEEE 24748-4:2016. It supersedes BS ISO/IEC 26702:2007 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

3、to its secretary. This publication 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 80611 7 ICS 35.080 Compliance with a British St

4、andard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 May 2016. Amendments/corrigenda issued since publication Date T e x t a f f e c t e dBS ISO/IEC/IEEE 24748-4:2016 ISO /IEC 2016 IEEE 2016

5、 Systems and software engineering Life cycle management P art 4: Systems engineering planning Ingnierie des systmes Gestion du cycle de vie Partie 4: Ingnierie des systmes IN T E R NA T I O NA L S TA N DA R D ISO/IEC/ IEEE 24748-4 First edition 2016-05- 15 R ef erence number ISO 24748-4:2016(E)BS IS

6、O/IEC/IEEE 24748-4:2016ISO/IEC/IEEE 24748-4:2016(E) ii COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2016 IEEE 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 mechanic

7、al, 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 Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 1

8、1 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York NY 10016-5997, USA E-mail stds.iprieee.org Web www.ieee.org IEC Central Office 3, rue de Varemb CH-1211 Geneva 20 Switzerland E-mail inmailiec.ch Web www.ie

9、c.ch ISO/IEC 2016 - All rights reserved IEEE 2016 - All rights reservedBS ISO/IEC/IEEE 24748-4:2016ISO/IEC/IEEE 24748-4:2016(E) ISO/IEC 2016 All rights reserved IEEE 2016 All rights reserved iii Contents Page Foreword . v Introduction ix 1 Scope 1 2 Conformance . 2 2.1 Intended usage 2 2.2 Conforman

10、ce to processes 2 2.3 Conformance to information item content 2 2.4 Full conformance . 2 2.5 Tailored conformance . 3 3 Normative references 3 4 Terms and definitions . 3 5 Concepts 5 5.1 Introduction 5 5.2 System concepts . 6 5.3 Life cycle concepts . 6 5.4 Process concepts 6 5.5 Organizational con

11、cepts . 7 5.6 Project concepts 7 5.7 Information items concepts 7 5.8 SEMP development concepts 8 6 Technical management processes for systems engineering planning . 9 6.1 General . 9 6.2 Project planning process 10 6.3 Project assessment and control process . 14 6.4 Decision management process . 16

12、 6.5 Risk management process . 18 6.6 Configuration management process . 19 6.7 Information management process . 20 6.8 Measurement process . 21 6.9 Quality assurance process . 22 7 Information items 23 8 Guidelines for information items . 23 8.1 Introduction 23 8.2 Adaptation of ISO/IEC/IEEE 15288

13、. 24 8.3 Elements of the SEMP . 26 9 Information item content 27 9.1 General . 27 9.2 Front matter . 28 9.3 Technical Project Summary . 28 9.3.1 General . 28 9.3.2 Purpose, scope and objectives 28 9.3.3 Assumptions and constraints 29 9.3.4 System description . 29 9.3.5 Schedule and budget summary .

14、29 9.4 References . 29 9.5 Definitions 29BS ISO/IEC/IEEE 24748-4:2016 ISO/IEC/IEEE 24748-4:2016(E) iv ISO/IEC 2016 All rights reserved IEEE 2016 All rights reserved 9.6 Technical project organization 29 9.7 Planning for technical definition . 30 9.7.1 General . 30 9.7.2 Process definition . 30 9.7.3

15、 Infrastructure planning 31 9.7.4 Technical project planning 31 9.8 Technical project execution and control 33 9.8.1 Performance assessment and control . 33 9.8.2 Measurement . 34 9.8.3 Quality assurance . 34 9.8.4 Reviews and audits. 34 9.8.5 Subcontractor management 35 9.8.6 Project management con

16、trols . 35 9.8.7 Technical project closeout 35 9.8.8 Technical baseline management . 36 9.9 Supporting process plans . 38 9.9.1 General . 38 9.9.2 Decision management 38 9.9.3 Risk management . 39 9.9.4 Communications . 39 9.9.5 Verification and validation . 39 9.10 Specialty engineering activities

17、and plans 40 Annex A (informative) Project Management Plan (PMP) elements . 42 Relationship of ISO/IEC/IEEE 24748-4 SEMP content to ISO/IEC 16326 PMP content . 42 Annex B (informative) SEMP considerations for system life cycle stages 49 B.1 Introduction . 49 B.2 Concept stage . 52 B.3 Development st

18、age . 53 B.4 Production stage. 54 B.5 Utilization stage 55 B.6 Support stage 56 B.7 Retirement stage . 57 Annex C (normative) Tailoring policies . 59 C.1 Introduction . 59 C.2 Information item tailoring process 59 C.2.1 Purpose 59 C.2.2 Outcomes 59 C.2.3 Activities and tasks 59 Bibliography . 61BS I

19、SO/IEC/IEEE 24748-4:2016ISO/IEC/IEEE 24748-4:2016(E) ISO/IEC 2016 All rights reserved IEEE 2016 All rights reserved v Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. N

20、ational 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 inter

21、est. 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

22、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 viewpo

23、ints 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, te

24、st, 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 th

25、e 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 matt

26、er 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 conductin

27、g 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 reasonabl

28、e 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/IE

29、EE 24748-4 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Systems and software engineering, in cooperation with the IEEE Computer Society Systems and Software Engineering Standards Committee, under the Partner Standards Development Organization co

30、operation agreement between ISO and IEEE. This edition cancels and replaces the first edition of ISO/IEC 26702:2007 IEEE Std 1220-2005, which has been technically revised. ISO/IEC 24748 consists of the following parts, under the general title Systems and software engineering Life cycle management: P

31、art 1: Guide for life cycle management Part 2: Guide to the application of ISO/IEC 15288 (System life cycle processes) Part 3: Guide to the application of ISO/IEC 12207 (Software life cycle processes)BS ISO/IEC/IEEE 24748-4:2016 ISO/IEC/IEEE 24748-4:2016(E) vi ISO/IEC 2016 All rights reserved IEEE 2

32、016 All rights reserved Part 4: Systems engineering planning Part 5: Software development planningBS ISO/IEC/IEEE 24748-4:2016ISO/IEC/IEEE 24748-4:2016(E) ISO/IEC 2016 All rights reserved IEEE 2016 All rights reserved ix Introduction ISO/IEC/IEEE 15288, Systems and software engineering System life c

33、ycle processes, provides a common process framework covering the life cycle of man-made systems. This life cycle spans the conception of ideas through to the retirement of a system. It provides the processes for acquiring and supplying systems. In addition, this framework provides for the assessment

34、 and improvement of the life cycle processes. This common framework improves communication and cooperation among the parties that create, utilize, and manage modern systems in order that they can work in an integrated, coherent fashion. The acquisition or supply of a system is usually done within a

35、project. A project prepares and implements the technical plans and schedules necessary to guide the project toward accomplishment of its objectives and proper conclusion. Given the projects authorization and objectives, the project should establish a Systems Engineering Management Plan (SEMP). This

36、part of ISO/IEC/IEEE 24748 replaces the former ISO/IEC 26702:2007 (IEEE Std 1220-2005), Systems engineering Application and management of the systems engineering process. In preparation for harmonization, ISO/IEC 26702 provided explanations regarding key differences between IEEE Std 1220 and ISO/IEC

37、/IEEE 15288 in areas such as terminology and structure. The evolution of the harmonized set of ISO/IEC/IEEE 15288-12207 related standards and technical reports that are discussed in this part of ISO/IEC/IEEE 24748 provides detailed requirements and guidance on the application of system life cycle pr

38、ocesses. This part of ISO/IEC/IEEE 24748 unifies technical and management requirements and guidance from several of these sources to specify the requirements for the content of a SEMP and to provide a common SEMP format. This part of ISO/IEC/IEEE 24748 also identifies the processes as defined in ISO

39、/IEC/IEEE 15288 to perform the necessary project planning activities to accomplish the projects technical effort and to develop the projects SEMP. Due to close alignment with the content of ISO/IEC 24748, ISO/IEC 26702 is now Part 4 of the multi-part International Standard, ISO/IEC 24748 (Systems an

40、d software engineering Life cycle management). Taken together, the parts of ISO/IEC 24748 are intended to facilitate the joint usage of the process content of ISO/IEC/IEEE 15288 and ISO/IEC 12207, Systems and software engineering Software life cycle processes, which in turn may be used together with

41、 related standards such as for service management, and various other lower-level process standards. In this way, ISO/IEC 24748 provides unified and consolidated guidance on the life cycle management of systems and software. Its purpose is to help ensure consistency in system concepts and life cycle

42、concepts, models, stages, processes, process application, key points of view, adaptation, and use in various domains as the two International Standards (and others) are used in combination. It should help a project to design a life cycle model for managing progress on a project. The five parts of IS

43、O/IEC 24748 are: ISO/IEC TR 24748-1: Systems and software engineering Life cycle management Part 1: Guide for life cycle management ISO/IEC TR 24748-2: Systems and software engineering Life cycle management Part 2: Guide for the application of ISO/IEC 15288 (System life cycle processes) ISO/IEC TR 2

44、4748-3: Systems and software engineering Life cycle management Part 3: Guide for the application of ISO/IEC 12207 (Software life cycle processes) ISO/IEC/IEEE 24748-4: Systems and software engineering Life cycle management Part 4: Systems engineering planningBS ISO/IEC/IEEE 24748-4:2016 ISO/IEC/IEEE

45、 24748-4:2016(E) x ISO/IEC 2016 All rights reserved IEEE 2016 All rights reserved ISO/IEC/IEEE 24748-5: Systems and software engineering Life cycle management Part 5: Software development planning Whereas Part 1 addresses in generic terms the purpose stated above of guidance for the life cycle manag

46、ement of systems and software, Part 2 focuses on and expands the coverage of those aspects for systems. Part 2 will also, in conjunction with Part 1, aid in identifying and planning the use of the life cycle processes described in ISO/IEC/IEEE 15288. The proper use of these processes will contribute

47、 to a project being completed successfully, meeting its objectives and requirements for each stage and for the overall project. This part of ISO/IEC/IEEE 24748 focuses on the processes required for successful planning and management of the projects systems engineering effort. It calls for developmen

48、t of a SEMP as the key vehicle for representing a projects application of systems life cycle processes. The SEMP is a top level technical planning document for a project which addresses Technical Management processes established by three principal sources (the projects contract or agreement, applica

49、ble organizational processes, and the systems engineering project team) as necessary to successfully accomplish the systems engineering-related tasks of the project. The terms technical planning and systems engineering planning are used interchangeably in this part of ISO/IEC/IEEE 24748 to emphasize or differentiate technical contributions in the processes under discussion. This part of ISO/IEC/IEEE 24748 draws on key aspects of the former ISO/IEC 26702 (I