- "Software Quality is the fitness for use of the software product" [1]
- Kitchenham states quality is "Hard to define, impossible to measure, easy to recognize" [2].
- Gilles states, "Quality is generally transparent when present, but easily recognized in its absence" [3].
- Project Managers and Software Developers need to understand what "Software Quality Assurance" is and how their project can benefit by its application.
- Software Quality Assurance implementation is a balancing activity that must be tailored as project appropriate.
- Software Quality Assurance must evaluate the process as well as the products.
- There must be a Software Assurance Plan.
- Software Quality Assurance must span the entire Software Development Life Cycle.
- Requirements, the birthplace of successful projects.
- Software Quality Assurance does NOT Equal Testing.
- Metrics are a necessity.
- Safety and Reliability are critical aspects of SQA.
- Independent Verification and Validation (IV&V) is an important tool within SQA.
- Hardware Does NOT Equal Software!
- Risk Management is NOT Optional.
References
[1] Schulmeyer, G. Gordon and McManus, James I., Handbook of Software Quality Assurance, 3rd Edition, Prentice Hall PRT, 1998
[2] Kitchenham, Barbara, Pfleeger, Shari Lawrence, "Software Quality: The Elusive Target", IEEE Software, Vol 13, No 1 (January 1996) 12-21
[3] Gillies, Alan C., Software Quality, Theory and Management, International Thomson Computer Press, 1997