Chapter 6: Software Configuration Management - Revision history

Daniel Robbins: /* Software Configuration Management Tools */

2015-08-26T11:10:50Z

‎Software Configuration Management Tools

Daniel Robbins: /* Software Configuration Management Tools */

2015-08-26T10:56:57Z

‎Software Configuration Management Tools

Daniel Robbins: /* Software Release Management and Delivery */

2015-08-26T10:55:47Z

‎Software Release Management and Delivery

Daniel Robbins: /* Software Configuration Auditing */

2015-08-26T10:53:11Z

‎Software Configuration Auditing

Daniel Robbins: /* Software Configuration Status Accounting */

2015-08-26T10:51:36Z

‎Software Configuration Status Accounting

Daniel Robbins: /* Software Configuration Control */

2015-08-26T10:48:34Z

‎Software Configuration Control

Daniel Robbins: /* Software Configuration Identification */

2015-08-26T10:39:47Z

‎Software Configuration Identification

Daniel Robbins: /* In-Process Audits of SCM */

2015-08-26T10:31:01Z

‎In-Process Audits of SCM

Daniel Robbins: /* SCM Measures and Measurement */

2015-08-26T10:28:11Z

‎SCM Measures and Measurement

Daniel Robbins: /* Surveillance of Software Configuration Management */

2015-08-26T10:27:54Z

‎Surveillance of Software Configuration Management

← Older revision		Revision as of 11:10, 26 August 2015
Line 851:		Line 851:
	suggests configuration management activities.		suggests configuration management activities.
	}}		}}
		+	{{EndSection\|title=References\|body=
		+	{{reference
		+	\|number=1
		+	\|author=
		+	\|article=
		+	\|publication=ISO/IEC/IEEE 24765:2010 Systems and Software Engineering—Vocabulary
		+	\|edition=
		+	\|publisher=ISO/IEC/IEEE
		+	\|issue=
		+	\|date=2010
		+	\|part=
		+	\|link=
		+	}}{{reference
		+	\|number=2
		+	\|author=
		+	\|article=
		+	\|publication=IEEE Std. 828-2012, Standard forConfiguration Management in Systems and Software Engineering
		+	\|edition=
		+	\|publisher=IEEE
		+	\|issue=
		+	\|date=2012
		+	\|part=
		+	\|link=
		+	}}{{reference
		+	\|number=3
		+	\|author=A.M.J Hass
		+	\|article=
		+	\|publication=Configuration Management
		+	Principles and Practices
		+	\|edition=1st ed.
		+	\|publisher=Addison Wesley
		+	\|issue=
		+	\|date=2003
		+	\|part=
		+	\|link=
		+	}}
		+	{{reference
		+	\|number=4
		+	\|author=I. Sommerville
		+	\|article=
		+	\|publication=Software Engineering, 9th ed.
		+	\|edition=9th ed.
		+	\|publisher=Addison Wesley
		+	\|issue=
		+	\|date=2011
		+	\|part=
		+	\|link=
		+	}}
		+	{{reference
		+	\|number=5
		+	\|author=J.W. Moore
		+	\|article=
		+	\|publication=The Road Map to Software
		+	Engineering: A Standards-Based Guide
		+	\|edition=
		+	\|publisher=Wiley-IEEE Computer Society Press
		+	\|issue=
		+	\|date=2006
		+	\|part=
		+	\|link=
		+	}}{{reference
		+	\|number=6
		+	\|author=S.P. Berczuk and B. Appleton
		+	\|article=
		+	\|publication=Software Configuration Management Patterns: Effective Teamwork, Practical Integration
		+	\|edition=
		+	\|publisher=Addison Wesley Professional
		+	\|issue=
		+	\|date=2003
		+	\|part=
		+	\|link=
		+	}}{{reference
		+	\|number=7
		+	\|author=CMMI Product Team
		+	\|article=CMMI for Development, Version 1.3
		+	\|publication=
		+	\|edition=
		+	\|publisher=Software Engineering Institute
		+	\|issue=
		+	\|date=2010
		+	\|part=
		+	\|link=http://resources.sei.cmu.edu/library/asset-view.cfm?assetID=9661
		+	}}{{ReferenceList}}}}

@@ Line 795: / Line 795: @@
 ==Software Configuration Management Tools==
+{{RightSection|{{referenceLink|number=3|parts=c26s1}} {{referenceLink|number=4|parts=c8s2}}}}
 When discussing software configuration management
 tools, it is helpful to classify them. SCM

@@ Line 700: / Line 700: @@
 ==Software Release Management and Delivery==
+{{RightSection|{{referenceLink|number=2|parts=c14}} {{referenceLink|number=3|parts=c8s2}}}}
 In this context, release refers to the distribution
 of a software configuration item outside the development activity; this includes internal
@@ Line 713: / Line 713: @@
 ===Software Building===
+{{RightSection|{{referenceLink|number=4|parts=c29s4}}}}
 Software building is the activity of combining the
 correct versions of software configuration items,
@@ Line 754: / Line 754: @@
 ===Software Release Management===
+{{RightSection|{{referenceLink|number=4|parts=c29s3.2}}}}
 Software release management encompasses the
 identification, packaging, and delivery of the

@@ Line 648: / Line 648: @@
 ==Software Configuration Auditing==
+{{RightSection|{{referenceLink|number=2|parts=c11}}}}
 A software audit is an independent examination
 of a work product or set of work products to
@@ Line 673: / Line 673: @@
 ===Software Functional Configuration Audit===
+{{RightSection|{{referenceLink|number=2|parts=c11s2.1}}}}
 The purpose of the software FCA is to ensure that
 the audited software item is consistent with its
@@ Line 682: / Line 682: @@
 ===Software Physical Configuration Audit===
+{{RightSection|{{referenceLink|number=2|parts=c11s2.2}}}}
 The purpose of the software physical configuration
 audit (PCA) is to ensure that the design and
@@ Line 689: / Line 689: @@
 ===In-Process Audits of a Software Baseline===
+{{RightSection|{{referenceLink|number=2|parts=c11s2.3}}}}
 As mentioned above, audits can be carried out
 during the development process to investigate

@@ Line 601: / Line 601: @@
 ==Software Configuration Status Accounting==
+{{RightSection|{{referenceLink|number=2|parts=c10}}}}
 Software configuration status accounting (SCSA)
 is an element of configuration management consisting
@@ Line 608: / Line 608: @@
 ===Software Configuration Status Information===
+{{RightSection|{{referenceLink|number=2|parts=c10s2.1}}}}
 The SCSA activity designs and operates a system
 for the capture and reporting of necessary
@@ Line 629: / Line 629: @@
 ===Software Configuration Status Reporting===
+{{RightSection|{{referenceLink|number=2|parts=c10s2.4}} {{referenceLink|number=3|parts=c1s5, c9s1, c17}}}}
 Reported information can be used by various
 organizational and project elements—including

@@ Line 457: / Line 457: @@
 ==Software Configuration Control==
+{{RightSection|{{referenceLink|number=2|parts=c9}} {{referenceLink|number=4|parts=c29s2}}}}
 Software configuration control is concerned
 with managing changes during the software
@@ Line 469: / Line 469: @@
 ===Requesting, Evaluating, and Approving Software Changes===
+{{RightSection|{{referenceLink|number=2|parts=c9s2.4}} {{referenceLink|number=4|parts=c29s2}}}}
 The first step in managing changes to controlled
 items is determining what changes to make. The
@@ Line 509: / Line 509: @@
 ====Software Configuration Control Board====
+{{RightSection|{{referenceLink|number=2|parts=c9s2.2}} {{referenceLink|number=3|parts=c11s1}} {{referenceLink|number=4|parts=c29s2}}}}
 The authority for accepting or rejecting proposed
 changes rests with an entity typically known as a
@@ Line 532: / Line 532: @@
 ====Software Change Request Process====
+{{RightSection|{{referenceLink|number=3|parts=c1s4, c8s4}}}}
 An effective software change request (SCR) process
 requires the use of supporting tools and procedures
@@ Line 542: / Line 542: @@
 ===Implementing Software Changes===
+{{RightSection|{{referenceLink|number=4|parts=c29}}}}
 Approved SCRs are implemented using the
 defined software procedures in accordance with
@@ Line 581: / Line 581: @@
 ===Deviations and Waivers===
+{{RightSection|{{referenceLink|number=1|parts=c3}}}}
 The constraints imposed on a software engineering
 effort or the specifications produced during the

@@ Line 298: / Line 298: @@
 ==Software Configuration Identification==
+{{RightSection|{{referenceLink|number=2|parts=c8}} {{referenceLink|number=4|parts=c29s1.1}}}}
 Software configuration identification identifies
@@ Line 309: / Line 309: @@
 ===Identifying Items to Be Controlled===
+{{RightSection|{{referenceLink|number=2|parts=c8s2.2}} {{referenceLink|number=4|parts=c29s1.1}}}}
 One of the first steps in controlling change is
 identifying the software items to be controlled.
@@ Line 321: / Line 321: @@
 ====Software Configuration====
+{{RightSection|{{referenceLink|number=1|parts=c3}}}}
 Software configuration is the functional and physical
 characteristics of hardware or software as set
@@ Line 329: / Line 329: @@
 ====Software Configuration Item====
+{{RightSection|{{referenceLink|number=4|parts=c29s1.1}}}}
 A configuration item (CI) is an item or aggregation
 of hardware or software or both that is
@@ Line 350: / Line 350: @@
 ====Software Configuration Item Relationships====
+{{RightSection|{{referenceLink|number=3|parts=c7s4}}}}
 Structural relationships among the selected
 SCIs, and their constituent parts, affect other
@@ Line 363: / Line 363: @@
 ====Software Version====
+{{RightSection|{{referenceLink|number=1|parts=c3}} {{referenceLink|number=4|parts=c29s3}}}}
 Software items evolve as a software project proceeds.
 A version of a software item is an identified
@@ Line 372: / Line 372: @@
 ====Baseline====
+{{RightSection|{{referenceLink|number=1|parts=c3}}}}
 A software baseline is a formally approved version
 of a configuration item (regardless of media)
@@ Line 403: / Line 403: @@
 ====Acquiring Software Configuration Items====
+{{RightSection|{{referenceLink|number=3|parts=c18}}}}
 Software configuration items are placed under
 SCM control at different times; that is, they are
@@ Line 426: / Line 426: @@
 ===Software Library===
+{{RightSection|{{referenceLink|number=3|parts=c1s3}} {{referenceLink|number=4|parts=c29s1.2}}}}
 A software library is a controlled collection of
 software and related documentation designed to

@@ Line 286: / Line 286: @@
 ====In-Process Audits of SCM====
-{{RightSection|{{referenceLink|number=3|parts=c1s1}}
+{{RightSection|{{referenceLink|number=3|parts=c1s1}}}}
 Audits can be carried out during the software
 engineering process to investigate the current status

@@ Line 253: / Line 253: @@
 ====SCM Measures and Measurement====
-{{RightSection|{{referenceLink|number=3|parts=c9s2, c25s2–s3}}
+{{RightSection|{{referenceLink|number=3|parts=c9s2, c25s2–s3}}}}
 SCM measures can be designed to provide specific
 information on the evolving product or to

@@ Line 228: / Line 228: @@
 ===Surveillance of Software Configuration Management===
-{{RightSection|{{referenceLink|number=3|parts=c11s3}}
+{{RightSection|{{referenceLink|number=3|parts=c11s3}}}}
 After the SCM process has been implemented,
 some degree of surveillance may be necessary