Case Study on Risk Analysis

3469 Words Oct 23rd, 2010 14 Pages
A Case Study in Successful Risk-Based Testing at CA Introduction This article presents a case study of a risk-based testing pilot project at CA, the world 's leading independent IT management software company. The development team chosen for this pilot is responsible for a widely-used mainframe software product called CA SYSVIEW® Performance Management, an intuitive tool for proactive management and real-time monitoring of z/OS environments. By analyzing a vast array of performance metrics, CA SYSVIEW can help organizations identify and resolve problems quickly. Companies are highly dependent on the reliability of their mainframe systems. If the mainframe doesn’t run, the company stops. Mainframe workloads also are growing considerably as …show more content…
Which have passed? Which have failed? Which defects have not yet been fixed or retested? How do the tests and defects relate back to the risks? In other words, with risk-based testing, risk management is an ongoing event. The above three responses to risk occur throughout the project lifecycle. Quality risks are mitigated by running tests, and project risks are mitigated by controls. Risks and risk levels are periodically re-evaluated based on new information, and, if necessary, priorities, allocation of effort, and project controls are modified. Why Adopt Risk-Based Testing? All testing faces two serious challenges. First, the set of possible test cases is infinite. So, if test coverage is measured by dividing the number of tests run by the number that could have been run, test coverage is always zero percent (n/∞ = 0). In fact, testers always select a relatively small subset of tests from the set of tests that they could possibly run – so they have to be very smart about that selection. Selection based on risk makes the most sense both in terms of product quality and project success. Second, because projects cannot take an infinite amount of time, all testing is “timeboxed” but the time-box is not a fixed size. Changes in upstream task durations for the project often compress the time-box for subsequent testing. The risk-based prioritization of tests directly addresses this challenge. By prioritizing tests according both to likelihood and impact, testers give themselves
Open Document