Achieving High Software Reliability.ppt

Achieving High Software Reliability Taghi M. Khoshgoftaar (taghi@cse.fau.edu) Empirical Software Engineering Laboratory Florida Atlantic University Boca Raton, Florida USA Overview SMART: The Software Measurement Analysis and Reliability Toolkit Module-Order Modeling Investigating the impact of underlying prediction models on module-order models Empirical case studies Summary SMART Case-Based Reasoning quantitative software quality prediction models: predicting faults, code churn, etc. qualitative software classification (risk-based) models: two-group and three-group models Module-Order Models priority-based ranking of modules with respect to their software quality SMART (GUI) SMART (GUI) Module-Order Models Why module-order models? Classification models are not suitable from the business improved cost-effective view points same quality improvement resources applied to all modules predicted as high-risk or fault-prone A priority-based software quality improvement is more suited for a cost-effective usage of available resources inspecting the most fault-prone modules first MOMs ... Answers practical questions posed by project management, such as which how many modules to target for VV? what’s the best usage of available resources? Different underlying quantitative software quality prediction models available what is their impact on the performance of module-order models? MOMs ... Components of a module-order model underlying software quality prediction model ranking of modules according to the predicted quality factor, and procedure for evaluating accuracy and effectiveness of predicted ranking Alberg diagrams: faults accounted-for by rankings Performance diagrams: measuring accuracy of the predicted ranking with respect to actual (perfect) ranking MOMs ... Based on schedule resources allocated for testing and VV, determine a range of cutoff percentages that includes the management’s options for covering the last module (as per the ranking) to be inspected Choose