IT DEPARTMENT

SIES GST

SE LAB

Experiment No: 5 Risk Analysis and Management Aim: To perform risk analysis and management. Theory: This document deals with the listing of possible complications, threats and risks that may be faced during the development of this system. The complexities specified herewith have been speculated and calculated to be approached by pro-active measures. Risk Identification- Its a systematic attempt to specify threat to project.

Following are types of risks involved in a software project: 1.Technology Risk In our project, the technology used is conventional, ie SQL database server and php ,xampp. The functionality provided is conventional as well.The UI will be basic. The hardware requirements for the system to run are minimal. A chance of the computer crashing still exists.The server may go down. 2.People Risks The risks under this context is low as the team working on the system is bonded under the project contract. The probability of delay of schedule due to unforeseen events still prevails. 3.Tools Risks The tool used may be of old version and may not support the technology being used. 4.Requirement Risks

IT DEPARTMENT

SIES GST

SE LAB

The requirements for our project are unreliable as the market demands are likely to change on regular basis,so the database need to be updated which becomes more complex. 5.Estimation Risks The projected duration for the development is under-90 days Risk projection: Risk projection is an attempt to estimate the probability of risks, the risk table provides the project manager with a simple technique for risk. The risk projection table for our project: Probability Risks Size estimated may be low 50% 2 While planning allocate more time and resources. Increase scalability Accommodate requirements as much as possible Increase parallel work schedules for staff Impact RMMM

More no. of users than planned Requirements change

70%

70%

Low staff strength

10%

IT DEPARTMENT

SIES GST

SE LAB

RMMM: Risk Mitigation, Monitoring and Management Impact values: 1.catastrophic 2.critical 3.marginal 4.negligible Risk assessment: Find accuracy of risk projection using Risk Exposure calculation Risk Exposure R.E=P*C Where, P is probability of occurrence of a risk C is cost of the project

Risk exposure is calculated for the above risks using the table above: Size Estimation: P = 0.5 C = 4700 RE = P * C = 0.5*4700 RE = 2350 Number of Users: P = 0.7 C = 1000 RE = P * C = 0.7*1000 RE = 700 Requirements Change: P = 0.3 C = 6500 RE = P * C = 0.5*6500 RE = 3250 Low Staff Strength: P = 0.1 C =9000 RE = P * C = 0.1*9000 RE = 900 Therefore, total amount needed for contingency is 7200

IT DEPARTMENT

SIES GST

SE LAB

RMMM Sheet Risk information table:

Risk Information Sheet

Risk ID: 101

Date: 27 Feb. 13 Probability:50 Impact: 2 %

Description: There is a possibility that the size of the project in terms in the lines of code was underestimated at the time of planning. Refinement/context: The time required for the completion and the size of software will increase significantly. Mitigation/monitoring: Proper estimation of the size should be conducted and safeguards against inefficient codes should be implemented. Management/contingency plan/trigger: Ensure that the code is efficient and also give the customer an intimation of the possibility if an increase in size of the software.

Current status: The size of the project is current inside bounds.

IT DEPARTMENT

SIES GST

SE LAB

Originator: Kaksha

Assigned: Monali

RMMM Sheet Risk Information Sheet Risk ID: 102 Description: The number of users will increase and might cause problems in the functioning of the system. Refinement/context: The increased traffic on the network will render the services unavailable or even render the system to crash frequently. Mitigation/monitoring: Monitoring of this risk is only possible after the project is online. Management/contingency plan/trigger: Ensure that the system is scalable and can be upgraded to handle increased traffic. Date: 27 Feb. 13 Probability: 70% Impact: 2

IT DEPARTMENT

SIES GST

SE LAB

Current status: The software is in developmental stage therefore status unavailable. Originator:Rasika Assigned:Monali

RMMM Sheet Risk Information Sheet Risk ID: 103 Date: 27 Feb. 13 Probability:30 % Impact: 3

Description: The requirements and demands of the customers, preferences and types of services anticipated, the digital specifications required changes and the project is affected. Refinement/context: The increased functionality of the required system might not be implemented in the given frame of resources allotted to the

IT DEPARTMENT

SIES GST

SE LAB

current project. Mitigation/monitoring: Continuous requirement gathering and anticipating changes. Management/contingency plan/trigger: Design the project to be modular. Current status: The software is being implemented in phases in order to accommodate the requirement changes as per the customer. Originator: Sandhya Assigned: Monali

RMMM Sheet

Risk Information Sheet Risk ID: 104 Description: The project might take longer time due to low staff strengths Date: 27 Feb. 13 Probability:10% Impact: 3

IT DEPARTMENT

SIES GST

SE LAB

Refinement/context: Initial investment on staff and work force is low due to the nature of the project. Mitigation/monitoring: Continuous evaluation of the staff should be carried out. Management/contingency plan/trigger: Assign the responsibility of staff performance audit to the project manager. Current status: Project manager is undertaking the responsibility of managing the staff need and welfare. Originator: Monali Assigned:Monal i

Conclusion: Thus Risk Management and Analysis is successfully performed.