Software Engineering

Dr. Satyanarayana. Mummana

Professor, Dept. of CSE, LIET
UNIT - 5

Risk Management:
 Risk types
 Strategies
 Estimation and Planning
 Software Quality –McCall Quality factors
 Six Sigma for Software Quality
 Quality Assurance and its techniques.
5.1. Introduction to Risk
A risk is an undesired event or circumstance that occurs while
a project is underway the project manager must anticipate and
identify different risks that a project may be susceptible to
Risk Management. It aims to reduce the impact of all kinds of
risks that may affect the project by identifying, analyzing, and
managing them
It involves 2 characteristics
Uncertainty: Risk may or may not happen
Loss: If risk is a reality unwanted loss or consequences will
occur
Risk Management
A software project can be concerned with a large variety of
risks. To be adept at systematically identifying the significant
risks that might affect a software project, it is essential to
classify risks into different classes. The project manager can
then check which risks from each class are relevant to the
project.
Three main classifications of risks can affect a software
project:
[Link] risks
[Link] risks
[Link] risks
5.2. Types of Risks
1)Project Risk
2)Technical Risk
3)Business Risk
4)Known Risk
5)Unpredictable Risk
6) Predictable risk
 Project risk: Threaten the project plan and affect the
schedule and resultant cost
Technical risk: Threaten the quality and timeliness of
software to be produced
Business risk: Threaten the viability of software to be built
Known risk: These risks can be recovered from careful
evaluation
Predictable risk: Risks are identified by past project
experience
Unpredictable risk: Risks that occur and may be difficult to
identify
Risk Management Process
 Risk Identification: Identify the project,
product and business risks.
 Risk Analysis: Assess the likelihood and
consequences of these risks.
 Risk Planning: Draw up plans to avoid or to
minimize the effects of the risks.
 Risk Monitoring: Constantly monitor the risks
and plan for risk mitigation.
Risk Management Process
1. Risk Identification:
Risk identification involves brainstorming activities.
It also involves the preparation of a risk list.
Brainstorming is a group discussion technique where
all the stakeholders meet together. This technique
produces new ideas and promotes creative thinking.
Preparation of a risk list involves the identification of
risks that are occurring continuously in previous
software projects.
1. Risk Identification
It concerned with identification of risk
Step1: Identify all possible risks
Step2: Create item check list
Step3: Categorize into risk components-Performance risk,
cost risk, support risk and schedule risk
Step4: Divide the risk into one of 4 categories
Negligible-0
Marginal-1
Critical-2
2. Risk Analysis and Prioritization:
It is a process that consists of the following steps:
• Identifying the problems causing risk in projects
• Identifying the probability of occurrence of the problem
• Identifying the impact of the problem
• Assigning values to step 2 and step 3 in the range of 1 to 10
• Calculate the risk exposure factor which is the product of
values of Step 2 and Step 3
• Prepare a table consisting of all the values and order risk
based on risk exposure factor
3. Risk Avoidance and Mitigation:
The purpose of this technique is to eliminate the
occurrence of risks. so the method to avoid risks is
to reduce the scope of projects by removing non-
essential requirements.
4. Risk Monitoring:
In this technique, the risk is monitored continuously by
reevaluating the risks, the impact of risk, and the probability
of occurrence of the risk.
This ensures that:
 Risk has been reduced
 New risks are discovered
 The impact and magnitude of risk are measured
Risk Control
It is the process of managing risks to achieve desired
outcomes. After all, the identified risks of a plan are
determined; the project must be made to include the most
harmful and the most likely risks. Different risks need
different containment methods. In fact, most risks need
ingenuity on the part of the project manager in tackling the
risk.
There are three main methods to plan for risk management:

1. Avoid the risk: This may take several ways such as

discussing with the client to change the requirements to
decrease the scope of the work, giving incentives to the
engineers to avoid the risk of human resources turnover,
etc.

2. Transfer the risk: This method involves getting the risky

element developed by a third party, buying insurance cover,
etc.

3. Risk reduction: This means planning method to include

the loss due to risk. For instance, if there is a risk that some
key personnel might leave, new recruitment can be planned.
Risk Leverage: To choose between the various methods of
handling risk, the project plan must consider the amount of
controlling the risk and the corresponding reduction of risk.
For this, the risk leverage of the various risks can be estimated.

Risk leverage is the variation in risk exposure divided by the

amount of reducing the risk.

Risk leverage = (risk exposure before reduction - risk exposure

after reduction) / (cost of reduction)
1. Risk planning: The risk planning method considers each of
the key risks that have been identified and develop ways to
maintain these risks.
For each of the risks, you have to think of the behavior that you
may take to minimize the disruption to the plan if the issue
identified in the risk occurs.
You also should think about data that you might need to collect
while monitoring the plan so that issues can be anticipated.
Again, there is no easy process that can be followed for
contingency planning. It rely on the judgment and experience
of the project manager.
2. Risk Monitoring: Risk monitoring is the method king that
your assumption about the product, process, and business risks
has not changed.
RMMM Plan :
A risk management technique is usually seen in the software
Project plan. This can be divided into Risk Mitigation,
Monitoring, and Management Plan (RMMM). In this plan, all
works are done as part of risk analysis. As part of the overall
project plan project manager generally uses this RMMM plan.
In some software teams, risk is documented with the help of a
Risk Information Sheet (RIS). This RIS is controlled by using a
database system for easier management of information i.e
creation, priority ordering, searching, and other analysis. After
documentation of RMMM and start of a project, risk mitigation
and monitoring steps will start.
Risk Mitigation :
It is an activity used to avoid problems (Risk Avoidance).
Steps for mitigating the risks as follows.
[Link] out the risk.
[Link] causes that are the reason for risk creation.
[Link] the corresponding documents from time to time.
[Link] timely reviews to speed up the work.
Risk Monitoring :
It is an activity used for project tracking.
It has the following primary objectives as follows.
[Link] check if predicted risks occur or not.
[Link] ensure proper application of risk aversion steps
defined for risk.
[Link] collect data for future risk analysis.
[Link] allocate what problems are caused by which risks
throughout the project.
Risk Management and planning :
It assumes that the mitigation activity failed and the risk is a
reality. This task is done by Project manager when risk becomes
reality and causes severe problems. If the project manager
effectively uses project mitigation to remove risks successfully
then it is easier to manage the risks. This shows that the response
that will be taken for each risk by a manager. The main objective
of the risk management plan is the risk register. This risk register
describes and focuses on the predicted threats to a software
project.
Drawbacks of RMMM:
•It incurs additional project costs.
•It takes additional time.
•For larger projects, implementing an RMMM may itself
turn out to be another tedious project.
•RMMM does not guarantee a risk-free project, infact,
risks may also come up after the project is delivered.
 Open Source Database
A robust, highly scalable, and powerful way
of storing data in comparison to traditional
High Performance database model

MongoDB offers incredible

features like on-demand Easy to Use
scaling, real-time resources etc,
To guarantee high
performance of the
applications Highly Flexible
Flexible Schema
Flexible scheme design
that allows you to meet
the ever-changing Always you to store and
conditions Characteristics work on different data types
of Big Data applications in one document

Reliable Indexing Advanced Security

Powerful Query Language