Information Technology Reference
In-Depth Information
TABLE 1.3
ANSI/IEEE Std 730-1984 and 983-1986 Software Quality Assurance Plans
I. Purpose of the plan
II. References
III. Management
a. Organization
b. Tasks
c. Responsibilities
IV. Documentation
a. Purpose
b. Required software engineering documents
c. Other documents
V. Standards, practices, and conventions
a. Purpose
b. Conventions
VI. Reviews and audits
a. Purpose
b. Review requirements
i. Software requirements review
ii. Design reviews
iii. Software verification and validation reviews
iv. Functional audit
v. Physical audit
vi. In-process audit
vii. Management reviews
VII. Test
VIII. Problem reporting and corrective action
IX. Tools, techniques, and methodologies
X. Code control
XI. Media control
XII. Supplier control
XIII. Records collection, maintenance, and retention
XIV. Training
XV. Risk management
relationship with cost in that deciding to meet high-quality standards at the beginning
of the project/operation ultimately may reduce maintenance and troubleshooting costs
in the long term. This a Design for Six Sigma theme: Avoid design-code-test cycles.
Joseph Juran, one of the world's leading quality theorists, has been advocating
the analysis of quality-related costs since 1951, when he published the first edition of
his Quality Control Handbook (Juran & Gryna, 1988). Feigenbaum (1991) made it
one of the core ideas underlying the TQM movement. It is a tremendously powerful
tool for product quality, including software quality.
 
Search WWH ::




Custom Search