1 / 18

Measuring the Economic Impacts of an Inadequate Infrastructure for Software Testing

Measuring the Economic Impacts of an Inadequate Infrastructure for Software Testing. By: David Hoang Martin Hoffman. Improved infrastructure can…. Remove more bugs Detect bugs earlier Locate bugs faster. The longer it takes the more is costs…. What does this mean for the User?.

donkor
Download Presentation

Measuring the Economic Impacts of an Inadequate Infrastructure for Software Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Measuring the Economic Impacts of an Inadequate Infrastructure for Software Testing By: David Hoang Martin Hoffman

  2. Improved infrastructure can… • Remove more bugs • Detect bugs earlier • Locate bugs faster

  3. The longer it takes the more is costs…

  4. What does this mean for the User? • Fewer bugs in software operations stage • Lower maintenance costs • Change in avoidance activities

  5. Custom vs. Commercial Software Products • Custom Products: • no formal release • more resources needed for implementation (developer) • post-purchase service (developer) • 3rd party integrators

  6. Estimating Software Developer Costs • Data collected: • Company’s total pre-release testing and post-release service costs. • Surveyed developers. • Additional resources required due to an Inadequate infrastructure for software testing: • Labor costs • Software costs • Hardware costs • After-sales service cost • Delay costs • Reputation costs

  7. Estimating Software User Costs • Software purchase decision • Evaluation of products • Lack of information on the quality of products • Unable to compare across products based on price and quality • uncertainty of bugs and interoperability increases • Installation and Integration • Higher for custom products • Business operations • System failures

  8. Software User Cost Categories • labor costs • failure costs • performance cost • redundant systems • delayed profits • sales forfeited

  9. Estimating Software Bug Costs Cost of bugs still remaining with improved sw testing infrastructure. Estimate the total cost of bugs to the user Determine linearly related costs and nonlinearly related costs User inputs: total costs associated with bugs general change in total costs in a 75% reduction in bugs Cost of product failure or installation is linear with the number of bugs Redundant system costs is not linear. Difference in cost reduction is industry dependant.

  10. Estimating Software Bug Costs

  11. Industry-specific User Costs • Industries encounter different types of costs • Two industries were selected: • Financial services – FEDI/clearinghouse software users • Transportation equipment manufacturing • Quality Categories: • Functionality • Reliability • Usability • Efficiency • Maintainability • Portability

  12. Questions?

More Related