Adaptable Process Model Checklists: Assessing the SQA Process
	IMPORTANT NOTICE: The complete Adaptable Process Model (APM) is provided for informational purposes and for assessment by potential users. The APM is copyrighted material and may not be downloaded, copied, or extracted for use in actual project work. The full hypertext (html) version of the APM may be licensed for use and customization within your organization. Contact R.S. Pressman & Associates, Inc. for complete licensing information.
	Assessing the SQA Process Software Quality Assurance (SEPA, 5/e, Chapter 8) is conducted to ensure that the software process and the resulting product exhibit characteristics that will result in a successful outcome. The following checklist will help you to assess your SQA approach. The more questions that elicit a negative response, the higher the risk that SQA is inadequate for your project. Has your organization established a broad-based "total quality management" program or something similar? Do your organization develop metrics that enable you to accurately predict defect prevention costs? appraisal (inspection) costs? failure costs? external failure (failure in the field) costs? Is a template SQA Plan available for all software projects? Is it used by all software projects? Is it followed by all software projects? Does an independent SQA team serve the software organization? Is the role of the SQA team clearly defined? Is it carried out uniformly? Do members of the SQA team have software engineering experience? Do software developers and SQA meet on a regular basis? Are quality-related roles clearly identified for all software engineers? Do all project teams conduct formal technical reviews (e.g., walkthroughs, inspections)? Is there a set of written review guidelines? Are they followed? Are the results of reviews documented? Has your organization established or adopted a set of standards that apply to the software that you build? Do you collect defect measures? Do you apply statistical SQA techniques to defect measures that you collect? Do you give serious consideration to software reliability? Do you attempt to compute the reliability of the software you build? Do you give serious consideration to software safety? Do you use poka yoke techniques? Return to Checklist Table of Contents