What is a risk-based approach to software quality?
A risk-based approach to software quality utilizes risk as the determinant for priority of testing activities. Risk analysis involves evaluating the Impact of failure and determining the Likelihood that failure will occur. The process involves segmenting the application into logical pieces, such as function, modules, or business events. Each of these pieces is then analyzed to determine the types of errors that could occur, the impact of these errors on the business, and the likelihood that the errors will occur. The errors with the most impact and/or highest likelihood would, of course, be tested first. Depending on the nature of the application, potential failures with high impact, but low likelihood, may be candidates for thorough testing; an example would be miscalculation of drug dosage from a pharmaceutical system it might not ever happen, but if it did the effects could be disastrous. Conversely, errors with low impact, but high likelihood, could be candidates for thorough testi
Related Questions
- Is Quality Circle Time a cost effective, value for money approach in terms of the amount of staff time expended on it?
- Is Quality Circle Time a cost effective, value for money approach in terms of the amount of staff time expended on it?
- Can Quality Associates help me to understand how to take a process-based approach?
- Can Quality Associates help me to understand how to take a process-based approach?
- What is a risk-based approach to software quality?
- Is TQM Effective for Software Quality?
