Inexpensive phase of SDLC to catch and fix bugs

Inexpensive phase of SDLC to catch and fix bugs

Is there a phase in the SDLC where fixing bugs can be done inexpensively? Also which phase of SDLC, is fixing bugs most expensive? How can I save costs and still be assured that I have a quality software product?

    Requires Free Membership to View

    Login

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Fixing the problems before they're ever introduced is the cheapest. In other words, have your developers understand the security implications of their actions and decisions and use the right tools to keep security flaws from every becoming part of the code. Arguably the most expensive time in the SLDC to fix flaws is after the code has gone into production. You not only have to find out what flaws exist (often the hard way via a breach) but you also have to go back to the drawing board so to speak and fix the issues all over again.

This was first published in September 2009