1、Systems and software engineering Life cycle management Part 5: Software development planningIngnierie des systmes et du logiciel Gestion du cycle de vie Partie 5: Planification de dveloppement de logicielINTERNATIONAL STANDARDISO/IEC/IEEE24748-5Reference numberISO/IEC/IEEE 24748-5:2017(E)First editi
2、on2017-06 ISO/IEC 2017 IEEE 2017ii ISO/IEC 2017 All rights reserved IEEE 2017 All rights reservedISO/IEC/IEEE 24748-5: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
3、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 ISOs member body in the country of the requester.
4、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 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org stds.iprieee.orgwww.iso.org www.ieee.orgISO/IEC/IEEE 24748-5
5、:2017(E) iii ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Contents 1 Scope 1 2 Normative references . 1 3 Terms, definitions and abbreviated terms 1 4 Abbreviations 5 5 Conformance 5 5.1 General 5 5.2 Intended usage 6 5.3 Conformance to processes 6 5.4 Conformance to information it
6、em content 6 5.5 Full conformance 6 5.6 Tailored conformance 7 6 Concepts 7 6.1 General 7 6.2 System concepts . 7 6.3 Life cycle concepts . 7 6.4 Process concepts 8 6.5 Project concepts . 8 6.6 Information item concepts 8 6.6.1 General 8 6.6.2 Concept of Plans 9 6.6.3 Software development plans 9 6.
7、7 Management concepts . 10 6.7.1 General . 10 6.7.2 Project management 10 6.7.3 Technical management . 10 6.8 Software development model concepts . 10 6.8.1 General . 10 6.8.2 Once-Through software development model 11 6.8.3 Evolutionary software development model . 11 6.8.4 Incremental software dev
8、elopment model 11 7 Software life cycle processes and software development planning . 12 7.1 General . 12 7.2 Agreement processes . 12 7.3 Organizational project-enabling processes 12 7.4 Technical management processes . 13 7.5 Technical processes . 13 8 Software development planning 13 9 Process Ex
9、ecution . 14 9.1 Overview 14 9.2 Project planning process 14 9.2.1 General . 14 9.2.2 Responsibility for planning . 14 9.2.3 Project scope . 15 9.2.4 Work Breakdown Structure 16 ISO/IEC/IEEE 24748-5:2017(E) iv ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved 9.2.5 Project estimation .
10、16 9.2.6 Relationship management 18 9.2.7 Risk Management 19 9.2.8 Configuration management 19 9.2.9 Information management . 19 9.2.10 Quality Assurance 19 9.3 Project and software measurement 19 9.3.1 Measurement overview . 19 9.3.2 Project measures . 20 9.3.3 Software measures 20 9.4 Project asse
11、ssment and control 21 9.4.1 Overview . 21 9.4.2 General guidance . 21 9.4.3 Project assessment and control process 23 9.5 Decision management 25 10 Information items: Technical plans . 26 10.1 Software Development Plan related to other plans . 26 10.2 Content of the Software Development Plan 27 10.2
12、.1 Content Overview 27 10.2.2 Detailed content of the SDP 27 Annex A (informative) Generic content for a plan 30 Annex B (informative) Sample Software Development Plan outline 31 Annex C (informative) Application of related standards 35 Bibliography . 37 ISO/IEC/IEEE 24748-5:2017(E) v ISO/IEC 2017 A
13、ll rights reserved IEEE 2017 All rights reserved Foreword Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specializ
14、ed 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 commit
15、tees 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 established a joint technical committee, ISO/IEC JTC 1. IEEE Standards
16、 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 the American National Standards Institute, which brings togeth
17、er 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
18、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 standa
19、rd may require the use of subject matter 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
20、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
21、any licensing agreements are reasonable or nondiscriminatory. 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 I
22、EEE Standards Association. Use of IEEE Standards documents is wholly voluntary. IEEE documents are made available for use subject to important notices and legal disclaimers (see http:/standards.ieee.org/IPR/disclaimers.html for more information). This document was prepared by Joint Technical Committ
23、ee ISO/IEC JTC 1, Information Technology, Subcommittee SC 7, Systems and software engineering, in cooperation with IEEE Computer Society Systems and Software Engineering Standards Committee, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE. A list of al
24、l parts in the ISO/IEC/IEEE 24748 series can be found on the ISO website. ISO/IEC/IEEE 24748-5:2017(E) vi ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Introduction ISO/IEC/IEEE 24748 provides unified and consolidated guidance on the life cycle management of systems and software. Th
25、is document draws on key aspects of the former IEEE JStd016 Standard for information technology software Software life cycle processes Software development Acquirer-supplier agreement. The IEEE has identified the need for a nonmilitary standard to guide managers of software systems in software devel
26、opment planning. Taken together, the parts of ISO/IEC/IEEE 24748 are intended to facilitate the joint usage of the process content of ISO/IEC/IEEE FDIS 12207 Systems and software engineering Software life cycle processes and ISO/IEC/IEEE 15288, Systems and software engineering System life cycle proc
27、esses, which in turn may be used together with related standards, such as for Information Technology (IT) service management and various lowerlevel process standards. The acquisition or supply of a software system is usually done within a project. A project prepares and implements the technical plan
28、s 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 plans for the technical management of activities as necessary for the software development effort. This document
29、 unifies technical and management requirements and guidance from several sources to specify the requirements for software engineering planning, including software development plans or software engineering plans. This document also identifies the processes as defined in ISO/IEC/IEEE FDIS 12207 to per
30、form the necessary project planning activities to accomplish the projects technical effort and to develop the software projects technical management and development plans. This document focuses on the processes required for successful planning and management of the projects software development effo
31、rt and for development of the software development plan (SDP) as a vehicle for representing a projects application of software life cycle processes. The SDP is a top level technical planning document for a project which addresses technical management processes established by three principal sources
32、(the projects agreement, applicable organizational and technical management processes, and the software development project team) as necessary to successfully accomplish the software development related tasks of the project. ISO/IEC/IEEE FDIS 24748-5 1 ISO/IEC 2017 All rights reserved IEEE 2017 All
33、rights reserved Systems and software engineering Life cycle management Part 5: Software development planning 1 Scope This document provides a common framework for planning and controlling the technical processes and activities to produce and sustain software products. The complete life cycle is cove
34、red by this document, from idea conception to the retirement of a software product. The framework described by this document provides for best practices in communication and cooperation among parties that plan for, develop, utilize, and manage modern software. This document: specifies the required i
35、nforma tion items to be produced through the implementation of the required planning and control processes; specifies the required content of the required information items; gives guidelines for the format and content of the required a nd related information items; and details the processes necessar
36、y to develop and implement a software plan. This document is intended to provide guidance for parties involved in the planning of software engineering at all stages of the software life cycle. It is intended to provide a common framework for twoparty and multiparty collaborations and can be applied
37、where the parties are from the same organization. This document can also be used by a single party. This document is applicable to: those who use ISO/IEC/IEEE FDIS 12207 on projects dealing with software products and services related to those products; those who are responsible for the technical man
38、agement of the development of software systems; organizations and individuals performing software development activities; and organizations and individuals developing information items du ring the development of software. 2 Normative references The following documents are referred to in the text in
39、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/IEEE FDIS 12207:20171, Systems and software
40、engineering Software life cycle processes 3 Terms, definitions and abbreviated terms For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE FDIS 12207, ISO/IEC TS 247481:2016, and the following apply. For additional terms and definitions, consult ISO/IEC/IEEE 24765, avail
41、able at puter.org/sevocab. ISO, IEC and IEEE maintain terminological databases for use in standardization at the following addresses: 1Under preparation. (Stage at time of publication ISO/IEC/IEEE FDIS 12207) ISO/IEC/IEEE 24748-5:2017(E) 2 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserv
42、ed IEC Electropedia: available at http:/www.electropedia.org/ ISO Online browsing platform: available at http:/www.iso.org/obp IEEE Standards Dictiona ry Online: available at http:/dictionary.ieee.org 3.1 acceptance action by an authorized representative of the acquirer by which the acquirer assumes
43、 ownership of products as partial or complete performance of an agreement 3.2 audit independent examination of a work product or set of work products to assess compliance with specifications, standards, contractual agreements, or other criteria Note 1 to entry: Independent assessment of software pro
44、ducts and processes conducted by an authorized person in order to assess compliance with requirements. SOURCE: ISO/IEC/IEEE 15288:2015, 4.1.10 3.3 configuration item item or aggregation of hardware, software, or both, that is designated for configuration management and treated as a single entity in
45、the configuration management process SOURCE: ISO/IEC/IEEE 15288:2015, 4.1.13 3.4 document uniquely identified unit of information for human use, such as a report, specification, manual or book, in printed or electronic form SOURCE: ISO/IEC/IEEE 15289:2015, 5.10 3.5 estimation process of developing a
46、 quantitative assessment of the likely amount or outcome 3.6 evaluation systematic determination of the extent to which an entity meets its specified criteria Note 1 to entry: The entity can be an item or activity. SOURCE: ISO/IEC 25001:2014, 4.1 3.7 information item separately identifiable body of
47、information that is produced, stored, and delivered for human use SOURCE: ISO/IEC/IEEE 15289:2015, 5.13 ISO/IEC/IEEE 24748-5:2017(E) 3 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved 3.8 plan information item that presents a systematic course of action for achieving a declared purpose
48、, including when, where, how, and by whom specific activities are to be performed Note 1 to entry: The plan can also state artifacts that are to be created. Note 2 to entry: Annex A provides contents of a generic plan. SOURCE: ISO/IEC/IEEE 15289:2011, 5.16 3.9 planning activities concerned with the
49、specification of a plan 3.10 project manager stakeholder with overall responsibility for the planning, execution, and closure of a project Note 1 to entry: According to ISO/IEC/IEEE FDIS 12207, the project closure is performed in the Portfolio Management process. 3.11 project management plan information item that describes how the project will be executed, monitored, and controlled Note 1 to entry : The plan typically describes the work to
