Name: Saket Kumar Vishwakarma

Roll.No: 201610101110078
Course: B.Tech CS-83

Problem Set -5
1. Discuss the need of software configuration management (SCM). How SCM affect
the software?
Answer:
The primary reasons for Implementing Software Configuration Management System are:

There are multiple people working on software which is continually updating

It may be a case where multiple version, branches, authors are involved in a software
project, and the team is geographically distributed and works concurrently
Changes in user requirement, policy, budget, schedule need to be accommodated.
Software should able to run on various machines and Operating Systems
Helps to develop coordination among stakeholders
SCM process is also beneficial to control the costs involved in making changes to a
system

This helps with project management, asset management and audit processes, as well as
software development and debugging.
2. What are the configuration items?
Answer: The term "configuration item" can be applied to anything designated for the
application of the elements of configuration management and treated as a single entity in the
configuration-management system. Configuration items, their versions, and their changes
form the basis of any configuration audit.
Configuration Items Types:
Hardware/Devices
Software/Applications
Communications/Networks
Location
Database
Service
Documentation
People (Staff and Contractors)
Entities of Change management, Incidents and Problem management and other
processes are sometimes also considered a Configuration items.
3. Discuss the Software Project Management roles for the followings.
1. Baseline for controlling software evolution.
2. Change Request management (CRM).
3. Version Control.
Answer:
1. Baseline for controlling software evolution:
A baseline is a formally accepted version of a software configuration item. It is
designated and fixed at a specific time while conducting the SCM process. It can only
be changed through formal change control procedures.
Activities during this process:
Facilitate construction of various versions of an application
Defining and determining mechanisms for managing various versions of these work
products
The functional baseline corresponds to the reviewed system requirements
Widely used baselines include functional, developmental, and product baselines
In simple words, baseline means ready for release.

2. Change Request Management(CRM):

Change Request Management coordinates all changes in a software landscape, to
ensure that changes do not conflict with each other. It also ensures that changes are
made without disrupting the ongoing business. This results in improved quality of the
software landscape, higher availability of IT solutions, and lower total cost of
ownership. Change Request Management ensures that the performed changes remain
transparent and traceable.
Change Request Management comes with a predefined set of workflows and
processes, which are all compliant to the recommendations provided by the IT
infrastructure library (ITIL).
3. Version Control:
SCM uses archiving method or saves every change made to file. With the help of
archiving or save feature, it is possible to roll back to the previous version in case of
issues.
Version control systems are a category of software tools that help a software team
manage changes to source code over time. Version control software keeps track of
every modification to the code in a special kind of database. If a mistake is made,
developers can turn back the clo ck and compare earlier versions of the code to help fix
the mistake while minimizing disruption to all team members.

4. Discuss the Risk Management Process.

Answer:
Risk management means risk containment and mitigation. First, you’ve got to identify and
plan. Then be ready to act when a risk arises, drawing upon the experience and knowledge of
the entire team to minimize the impact to the project.
Risk management includes the following tasks:
Identify risks and their triggers
Classify and prioritize all risks
Craft a plan that links each risk to a mitigation
Monitor for risk triggers during the project
Implement the mitigating action if any risk materializes
Communicate risk status throughout project
5. Explain Risk Breakdown Structure (RBS).

Answer: :. A risk breakdown structure organizes the risks that have been identified into
categories using a chart with 3 different levels: Risk Topic / Risk Categories / Risk factors).
For example, the business category can be subdivided into different types of risks associated
with it, including Competitors, Suppliers, and Cash flow.
Example of IT Project :