BAIT3153 Software Project Management

Tutorial 6: SOFTWARE CONFIGURATION MANAGEMENT (SCM)

Question 1 [April 2017, Q4a]

“Change control is important in software projects.” Give THREE (3) reasons to support the above
statement.

Any THREE (3) reasons why change control is important in software projects:
 Changes can upset schedules, costs, and resource allocation. Changes in a project can happen due
to both external and internal factors that impinge on a project. Some changes are brought about
by the marketplace and may affect the outcome of the final product.
 It is important for ensuring that only authorized changes are made to a particular configuration
object. Change control includes access control which allows which software engineers have the
authority to access and modify a particular configuration object. This prevents unauthorized
changes to the software.
 It is important for ensuring that only authorized changes are made to a particular configuration
object. Change control includes access control which governs which software engineers have the
authority to access and modify a particular configuration object. This prevents unauthorized
changes to the software.
 Change control includes synchronization control which helps to ensure that parallel changes,
performed by two different people, do not overwrite one another.

Question 2 [April 2016, Q4(a)]

The Software Configuration Management (SCM) process comprises FIVE (5) main activities: objects
identification, version control, change control, configuration auditing and change status reporting.
For each activity, briefly describe it and assess its importance to a software project.

1. Objects identification: To specify the configuration items to be controlled and managed in a project.
-This activity is important to be able to distinguish objects and also to ensure a common understanding among
the team members.

2. Version control combines procedures and tools to manage different versions of configuration objects that are
created during the software process.
-It is important so that there is no confusion among the various versions of configuration objects and also to
ensure that all modifications to objects are assimilated with integrity

3. Change control combines human procedures and automated tools to provide a mechanism for the control of
change.
-It is important for ensuring that only authorized changes are made to a particular configuration object.

4. Configuration audit tasks include formal technical review and software configuration audit.
-It is important to ensure that changes have been properly implemented.

5. Change status reporting provides information on what changes were made, who made the changes, when the
change was made and what are the other objects affected by the change.
-This is important for accountability and also to consider any side-effects of a particular change.
BAIT3153 Software Project Management
Question 3
Baseline
 A 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.
(IEEE)
 Software configuration management concept
that helps us to control change without
seriously impeding justifiable change.
 A baseline is a milestone in the development
of software that is marked by the delivery of
one or more SCIs and the approval of these
SCIs that is obtained through a formal
technical review.
 which a balance must be achieved between
Question 4 [April 2017(B), Q4c]
Differences:
Version control
Version control is concerned with managing the
different version of configuration objects that are
created during the software process.
Version control is important to distinguish the
different version of the configuration objects, to
ensure that the developers use the correct or latest
version, to enable developers to revert to an earlier
version if necessary, etc.
 Both version control and change control use a combination of human procedures and automated
tools to achieve their purpose.
SCI
 A configuration item (CI) is an item or
aggregation of hardware or software or both
that is designed to be managed as a single
entity. A software configuration item (SCI) is a
software entity that has been established as a
configuration item. The SCM typically
controls a variety of items in addition to the
code itself.
 SCIs include plans, specifications and design
documentation, testing materials, software
tools, source and executable code, code
libraries, data and data dictionaries, and
documentation for installation, maintenance,
operations, and software use.
 Selecting SCIs is an important process in
providing adequate visibility for project
control purposes and providing a manageable
number of controlled items.
Change control
Whereas change control provides a mechanism for
the control of change of software.
Change control is important because it ensures that
only authorized changes are made and that only
authorized software engineers access and modify a
particular configuration object, and ensures that
parallel changes, performed by two different
people, do not overwrite one another.