The following graph is why I think the cost of additional design reviews and additional testing during implementation (e.g, unit testing and code reviews) is justified, because it is still far cheaper than fixing the issues later during testing or after product release (maintenance).
Source data from IBM Research.
2 Trackbacks/Pingbacks
[...] testing is that it costs more time than it would to not write the tests; this is simply not true as this chart highlights. Writing tests for TDD may take longer to do than implementing the same solution [...]
[...] the design been peer reviewed, remember its cheapest to fix bugs at the requirements and design [...]
Post a Comment