IEEE 828-2012

$80.71

IEEE Standard for Configuration Management in Systems and Software Engineering

Published By	Publication Date	Number of Pages
IEEE	2012	71

Guaranteed Safe Checkout

Category: IEEE

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

Description

Revision Standard – Active. This standard establishes the minimum requirements for processes for Configuration Management (CM) in systems and software engineering. The application of this standard applies to any form, class, or type of software or system. This revision of the standard expands the previous version to explain CM, including identifying and acquiring configuration items, controlling changes, reporting the status of configuration items, as well as software builds and release engineering. Its predecessor defined only the contents of a software configuration management plan. This standard addresses what CM activities are to be done, when they are to happen in the life cycle, and what planning and resources are required. It also describes the content areas for a CM Plan. The standard supports ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008 and adheres to the terminology in ISO/IEC/IEEE Std 24765 and the information item requirements of IEEE Std 15939TM

PDF Catalog

PDF Pages	PDF Title
1	IEEE Std 828-2012 Front Cover
3	Title page
6	Notice to users Laws and regulations Copyrights Updating of IEEE documents Errata Patents
8	Participants
10	Introduction
11	Contents
14	Important notice 1. Overview 1.1 Scope 1.2 Purpose
15	2. Definitions, acronyms, and abbreviations 2.1 Definitions
17	2.2 Acronyms and abbreviations
18	3. Tailoring 4. Audience 5. The configuration management process
20	6. CM planning lower-level process 6.1 Purpose
21	6.2 Activities and tasks
22	7. CM management lower-level process 7.1 Purpose 7.2 Activities and tasks
23	8. Configuration identification lower-level process 8.1 Purpose
24	8.2 Activities and tasks
27	9. Configuration change control lower-level process 9.1 Purpose 9.2 Activities and Tasks
30	10. Configuration status accounting lower-level process 10.1 Purpose 10.2 Activities and tasks
31	11. CM configuration auditing lower-level process 11.1 Purpose
32	11.2 Activities and Tasks
33	12. Interface control lower-level process 12.1 Purpose
34	12.2 Activities and Tasks 13. Supplier configuration item control lower-level process 13.1 Purpose 13.2 Activities and Tasks
35	14. Release management lower-level process 14.1 Purpose 14.2 Activities and tasks
38	Annex A (informative) CM lower-level process models A.1 General
41	A.2 Related processes
43	A.3 Statement of conformity to ISO/IEC 15504-2
45	Annex B (informative) Mapping IEEE Std 828 to ISO/IEC/IEEE 12207:2008
48	Annex C (informative) Mapping IEEE Std 828 to ISO/IEC/IEEE 15288:2008
50	Annex D (normative) The configuration management plan (CMP) D.1 Introduction to the plan D.2 Criteria for identification of the configuration items (CIs) to which CM will be applied
51	D.3 Limitations and assumptions affecting the plan D.4 CM responsibilities and authorities D.5 Project organization D.6 CM responsibilities
52	D.7 Applicable policies, directives, and procedures D.8 Planned activities, schedule and resources D.9 CMP maintenance
53	Annex E (informative) Examples of how CM planning and management are applied E.1 Requirements E.2 Design E.3 Construction and integration E.4 Qualification testing E.5 Installation and acceptance
54	E.6 Operation E.7 Maintenance E.8 Disposal
55	Annex F (informative) Examples of how configuration identification (CI) is applied F.1 Requirements F.2 Design
56	F.3 Construction and integration
57	F.4 Qualification testing F.5 Installation and acceptance
58	F.6 Operation F.7 Maintenance F.8 Disposal
59	Annex G (informative) Examples of implementing change control in a software development environment G.1 Item-level change control G.2 Product-level change control and baselines
60	Annex H (informative) Examples of how configuration control is applied H.1 Requirements H.2 Design H.3 Construction and integration
61	H.4 Testing H.5 Acceptance
62	Annex I (informative) Examples of how configuration status accounting is applied I.1 Requirements I.2 Design I.3 Construction and testing
63	I.4 Acceptance I.5 Maintenance I.6 Operations
65	Annex J (informative) Examples of how configuration auditing is applied J.1 Requirements J.2 Design
66	J.3 Construction and integration J.4 Qualification testing
67	J.5 Installation and acceptance J.6 Maintenance
68	Annex K (informative) Software build naming schemes
69	Annex L (informative) Mapping IEEE Std 828 to ISO 10007:2003
71	Annex M (informative) Bibliography