Up ] [ Link Farm ]
Reload ] [ Top ]
  quality assurance  
IEEE Standard 12207 defines QA this way:
The quality assurance process is a process for
  1. providing adequate assurance that
  2. the software products and processes
  3. in the product life cycle
  4. conform to their specific requirements
  5. and adhere to their established plans.
-- ACM article

Too Darn Big to Test - (local PDF)

Absence of evidence is not evidence of absence.

Other Logical reasoning fallacies: -- after: Good Design, Good Static Checking, and Good Unit Testing, Keith Stobie

Quality Assurance: Much More than Testing
From the article:
What goes into QA? Testing, of course, is a key activity. There is, however, an adage that ?you can?t test quality into a product.? A solid test plan should catch errors and give a measure of quality. A good QA plan ensures that the design is appropriate, the implementation is careful, and the product meets all requirements before release. An excellent QA plan in an advanced organization includes analysis of defects and continuous improvement. (This feedback loop is characteristic of mature organizations.)
- - Stuart Feldman (make, fortran77, Unix development)

Valid HTML 4.0!
  Site search:  
 Modified: Mon, 14 Mar 2005 09:16:50 -0500
Copyright © 2019 R P Herrold