IEEE 828-2012 en Configuration Management in Systems and Software Engineering (IEEE Computer Society)《软件工程和系统配置管理》.pdf

《IEEE 828-2012 en Configuration Management in Systems and Software Engineering (IEEE Computer Society)《软件工程和系统配置管理》.pdf》由会员分享，可在线阅读，更多相关《IEEE 828-2012 en Configuration Management in Systems and Software Engineering (IEEE Computer Society)《软件工程和系统配置管理》.pdf（71页珍藏版）》请在麦多课文档分享上搜索。

1、 IEEE Standard for Configuration Management in Systems and Software Engineering Sponsored by the Software +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. Copyright 2012 IEEE. All r

2、ights reserved. ivNotice to users Laws and regulations Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not imply compliance to any applicable regulatory requirements. Implementers of the standard

3、 are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. Copyrights This document is copyright

4、ed by the IEEE. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making this document available for u

5、se and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this document. Updating of IEEE documents Users of IEEE Standards documents should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended

6、 from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In order to determine whether a given document is the curre

7、nt edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE-SA Website at http:/standards.ieee.org/index.html or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards

8、 development process, visit the IEEE-SA Website at http:/standards.ieee.org/index.html. Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata periodically. P

9、atents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the existence or validity of any patent rights in connection therewith. If

10、a patent holder or patent applicant has filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website http:/standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicate whether the Submitter is willing or unwilling to

11、grant licenses under patent rights without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applicants desiring to obtain such licenses. Copyright 2012 IEEE. All rights reserved. vEssential Patent Claims may exist

12、 for which a Letter of Assurance has not been received. The IEEE is not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or conditions provi

13、ded in connection with submission of a Letter of Assurance, 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 thei

14、r own responsibility. Further information may be obtained from the IEEE Standards Association. Copyright 2012 IEEE. All rights reserved. viParticipants At the time this IEEE standard was completed, the Configuration Management Working Group had the following membership: Chuck Walrad, Chair Mike Smit

15、h, Vice Chair Diego Pamio, Secretary Ranata Johnson, Editor Bob Aiello Adonica Geiger Darrel Strom Christopher Ward Ben Weatherall Bernhard Westfechtel M. Karen Woolf The following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapprova

16、l, or abstention. Ed Addario Johann Amsenga Chris Bagge Bakul Banerjee Charles Barest Juris Borzovs Pieter Botman Lyle Bullock Lawrence Catchpole Keith Chow Paul Croll Geoffrey Darnton Thomas Dineen Jennifer Doman Sourav Dutta Harriet Feldman Andrew Fieldsend Eva Freund David Friscia David Fuschi Ge

17、orge Gianacakes Gregg Giesler Lewis Gray Ron Greenthaler Randall Groves John Harauz Werner Hoelzl Robert Holibaugh Bernard Homes Peter Hung Atsushi Ito Mark Jaeger Cheryl Jones Hirofumi Kamibayashiyama Piotr Karocki Stanley Klein Dwayne Knirk Thomas Kurihara George Kyle Susan Land Kenneth Lang David

18、 Leciston Vincent Lipsio Greg Luri Wayne W. Manges Edward McCall Avygdor Moise James Moore Adi Mulawarman Michael S. Newman Chris Osterloh Mark Paulk Robert Peterson William Petit Annette Reilly Robert Robinson Fernando Lucas Rodriguez Garry Roedler Randall Safier Helmut Sandmayr Bartien Sayogo Robe

19、rt Schaaf David Schultz Stephen Schwarm Gil Shultz Carl Singer David Singleton Michael Smith Kapil Sood Friedrich Stallinger Thomas Starai Darrel Strom Walter Struppler Gerald Stueve March Stutzman K. Subrahmanyam Richard Thayer Thomas Tullia John Vergis Charlene Walrad M. Karen Woolf Jian Yu Oren Y

20、uen Janusz Zalewski Shuhui ZhangCopyright 2012 IEEE. All rights reserved. viiWhen the IEEE-SA Standards Board approved this standard on 6 February 2012, it had the following membership: Richard H. Hulett, Chair John Kulick, Vice Chair Robert M. Grow, Past President Judith Gorman, Secretary Masayuki

21、Ariyoshi William Bartley Ted Burse Clint Chaplin Wael Diab Jean-Philippe Faure Alexander Gelman Paul Houz Jim Hughes Joseph L. Koepfinger* David J. Law Thomas Lee Hung Ling Oleg Logvinov Ted Olsen Gary Robinson Jon Walter Rosdahl Sam Sciacca Mike Seavey Curtis Siller Phil Winston Howard L. Wolfman D

22、on Wright *Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Richard DeBlasio, DOE Representative Michael Janezic, NIST Representative Satish Aggarwal, NRC Representative Julie Alessi IEEE Standards Program Manager, Document Development Malia Zaman IEEE Stan

23、dards Program Manager, Technical Program Development Copyright 2012 IEEE. All rights reserved. viiiIntroduction This introduction is not part of IEEE Std 828-2012, IEEE Standard for Configuration Management in Systems and Software Engineering. This revision to IEEE Std 828TM-2005 replaces the earlie

24、r focus on the contents of a Software Configuration Management Plan (SCMP) with a focus on the processes that comprise System and Software Configuration Management. The standard for the SCMP is now included as a normative Annex. Configuration Management in Systems and Software Engineering is a speci

25、alty discipline within the larger discipline of Configuration Management (CM). The purpose of Configuration Management is to: a) Identify and document the functional and physical characteristics of any product, component, result, or service b) Control any changes to such characteristics c) Record an

26、d report each change and its implementation status d) Support the audit of the products, results, services, or components to verify conformance to requirements Configuration Management is essential to Systems Engineering and to Software Engineering. CM establishes and protects the integrity of a pro

27、duct or product component throughout its lifespan, from determination of the intended users needs and definition of product requirements through the processes of development, testing, and delivery of the product, as well as during its installation, operation, maintenance, and eventual retirement. In

28、 so doing, CM processes interface with all other processes involved in the products life. Annex A provides a condensed view of the purposes and outcomes of the lower level CM processes described in this standard. Copyright 2012 IEEE. All rights reserved. ixContents 1. Overview 1 1.1 Scope . 1 1.2 Pu

29、rpose 1 2. Definitions, acronyms, and abbreviations 2 2.1 Definitions . 2 2.2 Acronyms and abbreviations . 4 3. Tailoring . 5 4. Audience. 5 5. The configuration management process . 5 6. CM planning lower-level process. 7 6.1 Purpose 7 6.2 Activities and tasks 8 7. CM management lower-level process

30、 9 7.1 Purpose 9 7.2 Activities and tasks 9 8. Configuration identification lower-level process . 10 8.1 Purpose 10 8.2 Activities and tasks 11 9. Configuration change control lower-level process . 14 9.1 Purpose 14 9.2 Activities and Tasks. 14 10. Configuration status accounting lower-level process

31、 . 17 10.1 Purpose 17 10.2 Activities and tasks 17 11. CM configuration auditing lower-level process . 18 11.1 Purpose 18 11.2 Activities and Tasks. 19 12. Interface control lower-level process 20 12.1 Purpose 20 12.2 Activities and Tasks. 21 13. Supplier configuration item control lower-level proce

32、ss 21 13.1 Purpose 21 13.2 Activities and Tasks. 21 14. Release management lower-level process 22 14.1 Purpose 22 14.2 Activities and tasks 22 Annex A (informative) CM lower-level process models 25 Copyright 2012 IEEE. All rights reserved. xA.1 General 25 A.2 Related processes 28 A.3 Statement of co

33、nformity to ISO/IEC 15504-2 30 Annex B (informative) Mapping IEEE Std 828 to ISO/IEC/IEEE 12207:2008. 32 Annex C (informative) Mapping IEEE Std 828 to ISO/IEC/IEEE 15288:2008. 35 Annex D (normative) The configuration management plan (CMP). 37 D.1 Introduction to the plan. 37 D.2 Criteria for identif

34、ication of the configuration items (CIs) to which CM will be applied 37 D.3 Limitations and assumptions affecting the plan 38 D.4 CM responsibilities and authorities 38 D.5 Project organization 38 D.6 CM responsibilities. 38 D.7 Applicable policies, directives, and procedures 39 D.8 Planned activiti

35、es, schedule and resources . 39 D.9 CMP maintenance. 39 Annex E (informative) Examples of how CM planning and management are applied 40 E.1 Requirements. 40 E.2 Design . 40 E.3 Construction and integration . 40 E.4 Qualification testing 40 E.5 Installation and acceptance 40 E.6 Operation. 41 E.7 Mai

36、ntenance 41 E.8 Disposal. 41 Annex F (informative) Examples of how configuration identification (CI) is applied. 42 F.1 Requirements. 42 F.2 Design 42 F.3 Construction and integration . 43 F.4 Qualification testing 44 F.5 Installation and acceptance 44 F.6 Operation. 45 F.7 Maintenance 45 F.8 Dispos

37、al. 45 Annex G (informative) Examples of implementing change control in a software development environment46 G.1 Item-level change control . 46 G.2 Product-level change control and baselines 46 Annex H (informative) Examples of how configuration control is applied 47 H.1 Requirements 47 H.2 Design.

38、47 H.3 Construction and integration. 47 H.4 Testing 48 H.5 Acceptance 48 Annex I (informative) Examples of how configuration status accounting is applied. 49 I.1 Requirements 49 I.2 Design 49 I.3 Construction and testing. 49 I.4 Acceptance . 50 Copyright 2012 IEEE. All rights reserved. xiI.5 Mainten

39、ance . 50 I.6 Operations 50 Annex J (informative) Examples of how configuration auditing is applied . 52 J.1 Requirements . 52 J.2 Design 52 J.3 Construction and integration 53 J.4 Qualification testing. 53 J.5 Installation and acceptance 54 J.6 Maintenance. 54 Annex K (informative) Software build n

40、aming schemes . 55 Annex L (informative) Mapping IEEE Std 828 to ISO 10007:2003 56 Annex M (informative) Bibliography. 58 Copyright 2012 IEEE. All rights reserved. 1IEEE Standard for Configuration Management in Systems and Software Engineering IMPORTANT NOTICE: IEEE Standards documents are not inten

41、ded to ensure safety, health, or environmental protection, or ensure against interference with or from other devices or networks. Implementers of IEEE Standards documents are responsible for determining and complying with all appropriate safety, security, environmental, health, and interference prot

42、ection practices and all applicable laws and regulations. This IEEE document is made available for use subject to important notices and legal disclaimers. These notices and disclaimers appear in all publications containing this document and may be found under the heading “Important Notice” or “Impor

43、tant Notices and Disclaimers Concerning IEEE Documents.” They can also be obtained on request from IEEE or viewed at http:/standards.ieee.org/IPR/disclaimers.html. 1. Overview 1.1 Scope This standard establishes the minimum requirements for Configuration Management (CM) in Systems and Software Engin

44、eering, without restriction to any form, class, or type. 1.2 Purpose This standard describes CM processes to be established, how they are to be accomplished, who is responsible for doing specific activities, when they are to happen, and what specific resources are required. It addresses CM activitie

45、s over a products life cycle. This standard is consistent with IEEEs Software Engineering Body of Knowledge (SWEBOK), ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008. IEEE Std 828-2012 IEEE Standard for Configuration Management in Systems and Software Engineering Copyright 2012 IEEE. All rights

46、reserved. 22. Definitions, acronyms, and abbreviations For the purposes of this document, the following terms and definitions apply. ISO/IEC/IEEE 247651and the IEEE Standards Dictionary: Glossary of Terms and Definitions2should be consulted for terms not defined in this clause. 2.1 Definitions basel

47、ine: (1) specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures (2) formally approved version of a configuration item, regardless of media, formally d

48、esignated and fixed at a specific time during the configuration items life cycle. (ISO/IEC 24765:2009) NOTEA software baseline is a set (one or more) of software configuration items formally designated and fixed at a specific time during the software life cycle. A baseline, together with all approve

49、d changes to the baseline, represents the current approved configuration. The term is thus used to refer to a particular version of a software configuration item that has been agreed on, e.g., as a stable base for further development or to mark a specific project milestone. In either case, any new baseline is agreed through the projects agreed change control procedures.3build: (n) an operational version of a system or component that incorporates a specified subset of the capabilities that the final product will provide (ISO/IEC 24765:2009); (v) to perform the s