What's The Plan?

To create a Quality Assurance function, you first have to define what quality means to you. It's an ambiguous term.  In common use, it implies "best quality" or "highest quality".

In software development, the quality process can be viewed as two distinct processes: Quality Assurance (QA, prevention of errors via standards and procedures), and Quality Control (QC, detection of errors during the development process).

If you are an experienced software professional, you know that QA (prevention) can be a tough sale due to the amount of upfront effort and planning required.

QC (software testing) makes up the bulk of what most organizations identify as their quality assurance process.  Software testing is easy to understand and explain - you find bugs and fix them.  There is an immediate and tangible return.  Consequently, expenditures for QC efforts (test planning, manual and automated testing, etc.) are readily accepted by decision makers as necessary expenses.

The benefits of QA (the prevention of bugs) are not so readily apparent.  QA initiatives require an upfront commitment, investment, and long-term view.

The purpose of this site is to assist you in creating a balanced quality assurance strategy (QA+QC) that supports your efforts to deliver superior software applications to your customers.

I hope the information you find here supports your mission to further the cause of quality in your work and your life.

Tony Vizza


click a link below for more information

quality-assurance-defined

software-quality-assurance

continuous-improvement

the-numbers-trap

prevention

cost-of-software-bugs

black-box-testing