http://www.elilopian.com/2009/05/26/big-steps-to-code-integrity/ Creating better software Mon, 02 Jan 2012 09:09:26 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://www.elilopian.com/2009/05/26/big-steps-to-code-integrity/comment-page-1/#comment-38226 Andy Tue, 26 May 2009 15:32:44 +0000 http://www.elilopian.com/2009/05/26/big-steps-to-code-integrity/#comment-38226 A wise Quality Assurance Manager once told me that if you look carefully at what "QA" stands for: it's to "assure" the quality of the product, not to build in quality. It all comes back to the developer to build in quality, security, scalability, etc. etc. QA's job is to verify that it is meeting the requirements. At http://www.codeintegritysolutions.com, we see a number of organizations who are working hard to build quality into the software development process, not after the fact. Better design tools, static analysis and building of test frameworks are a great way for developers to build in quality. It's good engineering and better/cheaper/faster in the long run. A wise Quality Assurance Manager once told me that if you look carefully at what “QA” stands for: it’s to “assure” the quality of the product, not to build in quality. It all comes back to the developer to build in quality, security, scalability, etc. etc. QA’s job is to verify that it is meeting the requirements. At http://www.codeintegritysolutions.com, we see a number of organizations who are working hard to build quality into the software development process, not after the fact. Better design tools, static analysis and building of test frameworks are a great way for developers to build in quality. It’s good engineering and better/cheaper/faster in the long run.

]]>