IEEE 16326-2009 en Systems and software engineering Life cycle processes Project management《软件工程与系统 生命周期过程 项目管理》.pdf

《IEEE 16326-2009 en Systems and software engineering Life cycle processes Project management《软件工程与系统 生命周期过程 项目管理》.pdf》由会员分享，可在线阅读，更多相关《IEEE 16326-2009 en Systems and software engineering Life cycle processes Project management《软件工程与系统 生命周期过程 项目管理》.pdf（40页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference numberISO/IEC/IEEE 16326:2009(E)ISO/IEC 2009IEEE 2009INTERNATIONAL STANDARD ISO/IEC/IEEE16326First edition2009-12-15Systems and software engineering Life cycle processes Project management Ingnierie du logiciel Processus de cycle de vie Gestion de projetISO/IEC/IEEE 16326:2009(E) PDF disc

2、laimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties

3、accept therein the responsibility of not infringing Adobes licensing policy. Neither the ISO Central Secretariat nor IEEE accepts any liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General

4、Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies and IEEE members. In the unlikely event that a problem relating to it is found, please inform the ISO Central Secretariat or

5、IEEE at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2009 IEEE 2009 All 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 photocopying and microfilm, without permiss

6、ion in writing from either ISO or IEEE at the respective address below. ISO copyright office Institute of Electrical and Electronics Engineers, Inc. Case postale 56 CH-1211 Geneva 20 3 Park Avenue, New York NY 10016-5997, USA Tel. + 41 22 749 01 11 E-mail stds.iprieee.org Fax + 41 22 749 09 47 Web w

7、ww.ieee.org E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2009 All rights reserved IEEE 2009 All rights reservedISO/IEC FDIS 16326:2009 (E) IEEE P16326/CD2 19 February 2009 ISO/IEC 2009 All rights reserved IEEE 2009 All rights reserved iiiContents PageForeword .vIntrodu

8、ctionvi1 Scope11.1 Purpose 11.2 Field of application11.3 Limitations .12 Conformance .22.1 Conformance to normative documentation content22.2 Conformance to processes 22.3 Full conformance.23 Symbols and abbreviations24 Application of this International Standard35 Elements of the project management

9、plan.45.1 Project overview (Clause 1 of the PMP)55.1.1 Project summary (Subclause 1.1 of the PMP) 55.1.2 Evolution of the plan (Subclause 1.2 of the PMP)65.2 References (Clause 2 of the PMP) .65.3 Definitions (Clause 3 of the PMP) 65.4 Project context (Clause 4 of the PMP).65.4.1 Process model (Clau

10、se 4.1 of the PMP)65.4.2 Process improvement plan (Clause 4.2 of the PMP) .75.4.3 Infrastructure plan (Clause 4.3 of the PMP)75.4.4 Methods, tools and techniques (Clause 4.4 of the PMP).75.4.5 Product acceptance plan (Clause 4.5 of the PMP).75.4.6 Project organization (Clause 4.6 of the PMP).75.5 Pr

11、oject planning (Clause 5 of the PMP) 85.5.1 Project initiation (Subclause 5.1 of the PMP) .85.5.2 Project work plans (Subclause 5.2 of the PMP) .95.6 Project assessment and control (Clause 6 of the PMP)105.6.1 Requirements management plan (Subclause 6.1 of the PMP)105.6.2 Scope change control plan (

12、Subclause 6.2 of the PMP) .105.6.3 Schedule control plan (Subclause 6.3 of the PMP)105.6.4 Budget control plan (Subclause 6.4 of the PMP) .105.6.5 Quality assurance plan (Subclause 6.5 of the PMP)115.6.6 Subcontractor management plans (Subclause 6.6 of the PMP).115.6.7 Project closeout plan (Subclau

13、se 6.7 of the PMP).115.7 Product delivery (Clause 7 of the PMP) 115.8 Supporting process plans (Clause 8 of the PMP) 115.8.1 Project supervision and work environment (Subclause 8.1 of the PMP) 115.8.2 Decision management (Subclause 8.2 of the PMP) .125.8.3 Risk management (Subclause 8.3 of the PMP)

14、125.8.4 Configuration management (Subclause 8.4 of the PMP) 125.8.5 Information management (Subclause 8.5 of the PMP) 125.8.6 Quality assurance (Subclause 8.6 of the PMP) 135.8.7 Measurement (Subclause 8.7 of the PMP) 135.8.8 Reviews and audits (Subclause 8.8 of the PMP)135.8.9 Verification and vali

15、dation (Subclause 8.9 of the PMP) 145.9 Additional plans (Clause 9 of the PMP).14ISO/IEC/IEEE 16326:2009(E)ISO/IEC FDIS 16326:2009 (E) IEEE P16326/CD2 19 February 2009 iv ISO/IEC 2009 All rights reserved IEEE 2009 All rights reserved5.10 End matter 146 Project processes156.1 Project planning process

16、166.2 Project assessment and control process .206.3 Decision management process236.4 Risk management process .256.5 Configuration management process .276.6 Information management process.296.7 Measurement process.31Bibliography32List of Figures PageFigure 1 Format of a project management plan .4ISO/

17、IEC/IEEE 16326:2009(E)ISO/IEC FDIS 16326:2009 (E) IEEE P16326/CD2 19 February 2009 ISO/IEC 2009 All rights reserved IEEE 2009 All rights reserved vISO/IEC/IEEE 16326:2009(E)Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form

18、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 particular fields of technical activity. ISO and IEC tec

19、hnical committees collaborate in fields of mutual interest. 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.

20、IEEE Standards documents are developed within the IEEE 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, whic

21、h 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 to promote fairness in the consensus developmen

22、t process, the 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. The main task of ISO/IEC JTC 1 is to prepare International

23、 Standards. Draft International Standards adopted by the 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 implementati

24、on of this standard 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 cl

25、aims for which a 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 For

26、m, if any, or in any licensing agreements are reasonable 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

27、 from ISO or the IEEE Standards Association. ISO/IEC/IEEE 16326 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Software and Systems Engineering Standards Committee of the IEEE, under the Pa

28、rtner Standards Development Organization cooperation agreement between ISO and IEEE. This first edition of ISO/IEC/IEEE 16326 cancels and replaces ISO/IEC TR 16326, which has been technically revised and merged with content from IEEE Std 1058-1998. ISO/IEC FDIS 16326:2009 (E) IEEE P16326/CD2 19 Febr

29、uary 2009 vi ISO/IEC 2009 All rights reserved IEEE 2009 All rights reservedIntroductionThis International Standard provides normative content specifications for project management planscovering software projects, and software-intensive system projects.This International Standard also provides detail

30、ed discussion and advice on applying a set of projectprocesses that are common to both the software and system life cycle as covered by ISO/IEC12207:2008 (IEEE Std 12207-2008), Systems and software engineering Software life cycle processes15, and ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and

31、 software engineering System life cycle processes 16, respectively. The discussion and advice are intended to aid in the preparation of the normative content of project management plans.This International Standard is the result of the harmonization of ISO/IEC TR 16326:1999 and IEEE Std1058-1998.ISO/

32、IEC/IEEE 16326:2009(E)FINAL DRAFT INTERNATIONAL STANDARD ISO/IEC FDIS 16326:2009 (E) IEEE P16326/CD2/FDIS ISO/IEC 2009 All rights reserved IEEE 2009 All rights reserved 1Systems and software engineering Life cycle processes Project management 1 Scope 1.1 PurposeThis International Standard is intende

33、d to aid project managers in managing to successful conclusion those projects concerned with software-intensive systems and software products. This International Standard specifies the required content of the project management plan (PMP). This International Standard also quotes the extracted purpos

34、e and outcome statements from the project processes of ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and adds detailed guidance for managing projects that use these processes for software products and software-intensive systems. 1.2 Field of application This

35、International Standard is written for those who use or plan to use ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) on projects dealing with software-intensive systems and software products, regardless of project scope, product, methodology, size or complexity. T

36、he field of application of this International Standard spans the whole software or system life cycle, and addresses everybody who plays a role in project management project managers and others, specifically: g120 those responsible for establishing and continuously improving ISO/IEC 12207:2008 (IEEE

37、Std 12207-2008) software life cycle processes and ISO/IEC 15288:2008 (IEEE Std 15288-2008) system life cycleprocesses;g120 those responsible for executing any ISO/IEC 12207:2008 (IEEE Std 12207-2008) software life cycle process or ISO/IEC 15288:2008 (IEEE Std 15288-2008) system life cycle process at

38、 a project level;g120 organizations or individuals subcontracting a project management effort. In many organizations, the various responsibilities of project management are assigned to more than one person. Where the term “project manager“ is used in this International Standard, the guidance, advice

39、 or normative requirement applies to the applicable role within the organization. This International Standard is intended to provide guidance for two-party situations and may be equally applied where the two parties are from the same organization. This International Standard can also be usedby a sin

40、gle party as self-imposed tasks. This International Standard can also serve as guidance in multi-party situations, where high risks are inherent in the supply and integration of complex software-based systems, and procurement can involve severalvendors, organizations or contracting parties. 1.3 Limi

41、tationsThe normative content specifications for project management plans and the guidance for management of the project processes are limited to projects dealing with software-intensive systems and software products. INTERNATIONAL STANDARD ISO/IEC/IEEE 16326:2009(E)ISO/IEC FDIS 16326:2009 (E) IEEE P

42、16326/CD2 19 February 2009 2 ISO/IEC 2009 All rights reserved IEEE 2009 All rights reserved2 Conformance This International Standard provides normative definition of the content of the project management plan (PMP), and provides guidance for the execution of the project processes of ISO/IEC 15288:20

43、08 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008). Users of this International Standard can claim conformance to the normative documentation content, to the process provisions, or both. 2.1 Conformance to normative documentation content A claim of conformance to the documentation

44、 provisions of this International Standard means that the user demonstrates that the content of a PMP conforms to the content requirements specified in clause 5 of this International Standard. 2.2 Conformance to processes A claim of conformance to the process provisions of this International Standar

45、d is equivalent to claiming conformance to the project processes from ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) cited in clause 6 of this International Standard. 2.3 Full conformance A claim of full conformance to this International Standard is equivalent

46、to claiming conformance to the PMP content requirements cited in clause 5 and the project processes of ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) cited in clause 6 of this International Standard.3 Symbols and abbreviations The following symbols and abbrevia

47、tions are used in this International Standard: ANSI American National Standards Institute CCB Configuration/Change Control Board CDRL Contract Data Requirements List GATES Stage-Gate methodology IBM International Business Machines ICWG Interface Control Working Group IEC International Electrotechnic

48、al Commission IEEE Institute of Electrical and Electronics Engineers ISO International Organization for Standardization OGC Office of Government Commerce (UK) PERT Program Evaluation Review Technique PM Project Management (or Project Manager) PMBOK Project Management Body of Knowledge ISO/IEC/IEEE 1

49、6326:2009(E)ISO/IEC FDIS 16326:2009 (E) IEEE P16326/CD2 19 February 2009 ISO/IEC 2009 All rights reserved IEEE 2009 All rights reserved 3PMI Project Management Institute PMP Project Management Plan PPL Product Parts List PRINCE2 Projects In Controlled Environments (version 2) RUP Rational Unified Process (registered trademark of IBM) SDP Software Development Plan SE Software Engineering SEE Software Engineering Environment SEMP Systems Engineering Management Plan SWEBOK Software Engineering Body of