soft_engg_lecture12 - Software Engineering Asim Banerjee...

Info icon This preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Software Engineering Asim Banerjee 23 rd February 2010 [email protected]
Image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 2 Lecture Seating Plan (Sample) #1 #2 #3 #4 #5 #6 #7 #8 #9 Stage #10 #11 #12 #13 #20 #21 #24 #23 #22
Image of page 2
IT314 - Software Engineering 3 Risk Analysis & Management (1/2) Risk: Any unfavorable event or circumstance that can occur during the project life cycle NOTE: If risk becomes true, it can hamper successful and timely completion of project Risk Analysis aims at: Anticipating and Identifying project risks Access its probability of occurrence Estimate its impact So that a contingency plan can be prepared to contain their effects
Image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 4 Risk Analysis & Management (2/2) Risk Management aims at: Dealing with all risks that might affect a project Risk management consists of: Risk identification Risk assessment Risk containment (contingency plans, mitigation plans)
Image of page 4
IT314 - Software Engineering 5 Good Risk Analysis & Management The risks that are identified, analyzed and managed should be derived from a thorough study of the people, the product, the process and the project. The Risk Monitoring, Management and Mitigation (RMMM) plan should be revisited as the project proceeds to ensure that risks are kept up to date. Contingency plans for risk management should be realistic.
Image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 6 Reactive Risk Management Reactive risk strategies imply never worrying about problems until they happen. A reactive risk strategy monitors the project for likely risks, and resources are set aside to deal with them should they become actual problems Usually, the software team does nothing about risks until something goes wrong. This is often called a fire fighting mode . When this fails, Crisis management takes over.
Image of page 6
IT314 - Software Engineering 7 Software Risks Risk always involves two characteristics Uncertainty – the risk may or may not happen. NOTE : There are no 100 % probable risk Loss – if the risk becomes a reality, unwanted consequences or losses will occur. NOTE : When the risks are analyzed, it is important to quantify the level of uncertainty and the degree of loss associated with each risk. Different categories of risks are: Project Risks Technical Risks Business Risks
Image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 8 Risk Identification (1/2) One can use the risk item checklist to identify risks Product size – the overall size of the software to be built or modified Business impact – constraints imposed by management or the marketplace Customer characteristics – the interactions with the customer Process definition – the degree to which the process has been defined and being followed in the organization
Image of page 8
IT314 - Software Engineering 9 Risk Identification (2/2) One can use the risk item checklist to identify risks (continued) Development environment – the availability and quality of the tools to be used in the project Technology to be built – the complexity of the
Image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern