Change Management

Question 1

The “First Law”

Answer 1

No matter where you are in the system life cycle,
the system will change, and the desire to change
it will persist throughout the life cycle

Question 2

Baselines

Answer 2

a baseline is a milestone in the development of software

that is marked by the delivery of one or more software
configuration items

and the approval of these SCIs that is
obtained through a formal technical review

Question 3

Repository Features

Answer 3

Versioning
Dependancy tracking and change management
Requirements tracing
Config management
Audit trails

Question 4

Versioning

Answer 4

Saves all of these versions to enable effective management of product releases and to permit developers to go back to previous versions

Question 5

Dependency tracking and change management.

Answer 5

The repository manages a wide variety of relationships among the data elements stored in it

Question 6

Requirements tracing

Answer 6

Provides the ability to track all the design and construction components and deliverables that result
from a specific requirement specification.

Question 7

Configuration management.

Answer 7

Keeps track of a series of configurations representing specific project milestones or production releases. Version management provides the needed versions, and link management keeps track of interdependencies.

Question 8

Audit trails.

Answer 8

Establishes additional information about when, why, and by whom changes are made

Question 9

Version Control

Answer 9

manages diff verstions of SCIs

1- it’s a big repo

2- it stores all versions

3- it can be used to make builds

4- it can be used to track issues

Question 10

Change Prediction

Answer 10

need to know how sys works with environ

e.g. tightly coupled w environ means need to change along w environ

should know
num + complexity of interfaces
num of inherently volatile sysreqs (volatile means depends on org policies, e.g. only HR manager can view employee records)

Question 11

Change Control Boards (CCB)

Answer 11

► On moderate or large projects
► Two types:
 Project Level CCB
 Software Change Control Board (SCCB)
► Role
 Assesses impact of change and approve
change before it is implemented.
 Determines when the change will be released

Question 12

Steps of Change Control Process

Answer 12

SCI identification
make a change request
it’s
analysed
approved?
implemented
tested
integrated with prod
validated
aaaaand closed

Question 13

Change Control Process:
Controlled Implementation

Answer 13

request submitted
assign homies to work
checkout <need_to_change>
make change
audit change
checkin new versiion
baseline test
qa</need_to_change>

Question 14

Change Control Process: Controlled Build

Answer 14

collect changes for next release
rebuild new release
make change
audit changes
release