You are on page 1of 5

Qtn: You work for a small organization that just set up an IT organization in Order to develop a

new database system in-house. You have been appointed a project manager;

a) Write a memorandum to the managing director for: 1 Change Control and 2


Configuration Management, highlight at least 2 benefits and one disadvantage of
each. 12 marks

Let our Organisation in this case be MINISTRY OF GENDER LABOR AND SOCIAL
DEVELOPMENT. Note that all information in the document is assumptive AND fiction:
The Memorandum find attachment.
Advantages upon control change:

Quick access time into the system

Reduced ambiguity while using the system

Disadvantage

Time lag after releasing the new interface as users have to relearn the system

Advantages upon configuration Management

Shortened query sequences

Time saving as some access rights have been passed on to other staff

Disadvantage

Relearning the system

b) List six different people (group of people) who would be involved in handling and
implementing a request for change within the proposed control procedure. Identify
clearly for each, their specific responsibilities relating to the request for change.

i. Review of changes is normally undertaken by a nominated Change Review Board


(CRB). This has the authority to accept or reject the change, however, its
responsibilities are wider than reviewing individual changes in isolation. It takes a
broader and longer term view of a system and assess the need for such suggested
changes
ii. All stakeholders have an opportunity to participate in the control of any subsequent
changes
iii. All recipients are made aware of any changes that occur and
iv. There is also an Audit trail team which connects a change to a configuration item to
the reason for its change, and which records the participation and authorisation of those
people concerned with the change.
v. System Testing team
vi. System validation team

c) Name and describe briefly the three major elements of a configuration management
system. (3 marks)

Configuration Management (CM) is the discipline that ensures that the state of the software
at any given time is known and reconstructable and these are the major elements it involves:

i. Configuration Identification (CID)


CID provides a method for specifically and uniquely identifying each instance (e.g.,
release, version) of a given software product or set of products. By using a standard naming
convention that allows for the identification of every instance of the product, each new
draft of a document, each new compilation of a unit, or each new build can be specifically
identified.
ii. Configuration Control (CC)
CC is the element that ensures that each change to an instance of the product is known,
authorized, and documented. CC includes the activities of the change control board (CCB),
which reviews and authorizes changes to the documents and code as increasingly formal
control is placed on the developing software system. The software library may also be
included as a function of CC.
iii. Configuration Accounting (CA)
CA serves to keep track of the status of each instance of the product. This becomes
increasingly important as units and modules are integrated into subsystems and systems. It
is obvious that the specific parts of a given system must be known so the system itself can
be known. CA also assigns and tracks the status of each baseline of the requirements, test,
design, code, and so on, as the software effort proceeds. Another growing requirement for
CA is the case of a basic product that is adapted for use in multiple installations, each with
slight variations in the total requirements set.
d) List and discuss briefly at least four items of information contained within a
configuration item description.

The following are the characteristic of a CI:

1. A classification, or type, this indicates what kind of item it is.


2. Attributes, these vary by classification and describe the characteristics of the
individual CI.
3. A status value, this is the unit that represents the CI's state in the lifecycle used for CIs
of this classification.
4. Relationships, theses indicate how the CI is related to other Cis and or the owner or
the person who is responsible for the CI.

e) What is the purpose of a business case?

A business case is the reasoning for initiating a project or task, it is the information needed for
authorisation of a project. The purpose of the business case is to document the justification for
the undertaking of a project usually based on the estimated cost of development and
implementation against the risks and the anticipated business benefits and savings to be gained.

f) What are the main headings in a business case document?

Most organisations will have a standard approach to composing a business case. However, key
elements usually include for;

1. Reasons (Why the project should be run)


2. Options (a brief description of the different options considered and option
recommended)
3. Benefits expected (expressed in measurable terms against today’s situation
4. Risks (summary of the key risks of the project)
5. Cost (extracted from the project plan)
6. Timescales (summary of the project plan)
7. Investment appraisal

OR IN ANOTHER VERSION

1. identify reason for change


2. investigate impact – configuration items to be changed, costs, timescales, risks
3. review change – accept or reject
4. make changes as agreed, and update configuration status
5. Release changes..

g. Identify four events which might lead to an updating of a business case document.

1. Changes can also occur because of problems in development or operation.


2. Handling proposed alterations to items that have been previously designated as fixed.
3. Need for system and or module redesigning.
4. If a signed-off item is changed then there is need for updating a business case document

OR FOR SOFTWARE

 operations error;
 user documentation does not conform to code;
 code does not conform to design;
 design does not conform to requirements;

new or changed requirements


References:

1. https://www.ibm.com/support/knowledgecenter/SSANHD_7.6.0.2/com.ibm.sccd.doc/con
fig/c_config_item.html
2. https://www.spec-india.com/blog/basic-elements-of-configuration-management/
3. http://2020projectmanagement.com/resources/project-documentation/the-business-case
4.

You might also like