comment on this article

Quantifying the cost of fixing vs preventing bugs

When you think about improving software quality, your first thoughts might be the cost of new tools and engineering labour to implement them, as well as the impact of 'slowing down' the development cycle by adding new processes.

But really, you need to first think about the current cost to your organization to find and fix bugs over the product life cycle. Beyond these direct costs, have you considered the opportunity cost associated with missed release dates, or the good will that is lost from unhappy customers, or product recalls?

Author
Vector Software

Related Downloads
65147\Vector_PDF.pdf

Comment on this article


This material is protected by MA Business copyright See Terms and Conditions. One-off usage is permitted but bulk copying is not. For multiple copies contact the sales team.

What you think about this article:


Add your comments

Name
 
Email
 
Comments
 

Your comments/feedback may be edited prior to publishing. Not all entries will be published.
Please view our Terms and Conditions before leaving a comment.

Related Articles

ST buys Atollic

STMicroelectronics is acquiring the software-development tools specialist ...

Change based testing

A major cause of software bugs is inefficient and incomplete testing. This ...

KeyStone software

This whitepaper explores how Texas Instruments' KeyStone multicore SoCs offload ...

Life without GitHub?

The software development platform and code sharing repository GitHub celebrates ...

Keeping standards high

Engineers – at least those who are worth their salt – ask questions. And those ...