Risk

Management
Software Engineering

Group Members:
Sidra Faisal (1345)
Ayesha Akbar (1336)
Sonia Kanwal (1347)
Nimra Almas (1228)
Iqra Zafar (1344)
 End user will resist the system
Risk Information Sheet
Risk ID: BU-3 Date: 18/3/21 Prob: 40% Impact: high
Description: At various points in the checklist, End user will resist system is identified as a
potential risk. There might be many reasons behind this risk. Its impact factor is high for this
risk. The problem may be on the service providing side or on the end user side.

Refinement/context:
Subcondition1: Teams design the system in such a way that user interface is not too much
friendly that’s why user resists that system.
Subcondition2: Users are not much familiar with the system that’s why they are resisting the
system.
Subcondition3: system has been designed with too much complications thats why end user is
resisting the system.
Mitigation/Monitoring: In order to prevent this from happening, the software will be developed
with the end user in mind. The user-interface will be designed in a way to make use of the
program convenient and pleasurable. The software will be developed with the end user in mind.
The development team will ask the opinion of various outside sources throughout the
development phases. Specifically the user-interface developer will be sure to get a thorough
Opinion from others.
Management/ contingency Plan/Trigger: Should the program be resisted by the end user, the
program will be thoroughly examined to find the reasons that this is so. Specifically the user
interface will be investigated and if necessary, revamped into a solution.

Current status: Mitigation step has been initiated.

Originator: Kashif Awan Assigned: Bilal Abbas

2
 Customer Will Change the Requirements
Risk Information Sheet
Risk ID:PS-2 Date: 18/3/21 Prob: 80% Impact: Critical

Description: The addition of new requirements and changes to the existing requirements can occur at all
stages of the system development process. The changes occur due to many reasons such as customer
needs. This risk factor has high impact on project development.
Refinement/context:
Sub condition 1: Technology Changes.
Sub condition 2: Changes in Business Environment.
Sub condition 3: Poorly defined requirements.

Mitigation/Monitoring: In order to prevent this, meetings will be held with customer on a routine basis
and beware of technology changes. This insures that the project we are developing and requirements of
customer are equivalent.
The meetings with customer should ensure that customer and our project team understand each other.
Management/ contingency Plan/Trigger: Should Do the eliciting meeting with customer to gather the
actual requirements then if developing team idea is different from customer, should take the necessary
steps to rectify this problem.
Current Status: Mitigation step has been initiated.

3
 Technology will not meet the requirements
Risk Information Sheet
Risk ID: Date: 19/3/21 Prob: 30% Impact: Catastrophic
Description: Technology is not fulfilling the needs may result in many problems. First of
all, it would be a loss of budget, time, and lack of quality. There could be multiple
reasons for this like it's not user friendly, it's not solving the exact problem, or not
compatible with the system.
Refinement/context:
Subcondition1: The system is not fulfilling the requirements; it’s not solving the problem
for which it’s made.
Subcondition2: There could be a problem in requirement gathering process or else it may
not be user friendly.
Subcondition3: It’s not compatible with the hardware being used.
Mitigation/Monitoring: For avoiding such kind of technical issues, you need to keep
your requirement team very vigilant. Your team should be efficient enough to understand
the problem and then communicate those issues with developers effectively to avoid
inconvenience. Secondly, it has to be user friendly because users are not technical experts
and they want ease. You should identify what kind of users would be using this software,
and then design it accordingly. Also, system compatibility and software performance
should be taken into consideration.
Management/ contingency Plan/Trigger: Should the program be solving a problem the
end user, the program will be thoroughly examined to find the reasons that this is so.
Specifically the software quality and problem solving attribute will be investigated and if
necessary, revamped into a solution.
Current status: Mitigation step has been initiated.
Originator: Assigned: