Measuring quality is the key to developing high-quality software. The author describes two approaches that help to identify the body of knowledge software engineers need to achieve this goal. The first approach derives knowledge requirements from a set of issues identified during two standards efforts: the IEEE Std. 1061-1998 for a Software Quality Metrics Methodology and the American National Standard Recommended Practice for Software Reliability (ANSI/AIAA R-013-1992). The second approach ties these knowledge requirements to phases in the software development life cycle. Together, these approaches define a body of knowledge that shows software engineers why and when to measure quality. Focusing on the entire software development life cycle, rather than just the coding phase, gives software engineers the comprehensive knowledge they need to enhance software quality and supports early detection and resolution of quality problems. The integration of product and process measurements lets engineers assess the interactions between them throughout the life cycle. Software engineers can apply this body of knowledge as a guideline for incorporating quality measurement in their projects. Professional licensing and training programs will also find it useful.
[1]
Pierre-Alain Muller,et al.
Instant Uml
,
1997
.
[2]
Norman F. Schneidewind,et al.
Reliability Modeling for Safety Critical Software
,
1997,
Ada-Europe.
[3]
Norman F. Schneidewind.
Measuring and Evaluating Maintenance Process Using Reliability, Risk, and Test Metrics
,
1999,
IEEE Trans. Software Eng..
[4]
Norman F. Schneidewind.
Software metrics model for integrating quality control and prediction
,
1997,
Proceedings The Eighth International Symposium on Software Reliability Engineering.
[5]
C. Billings,et al.
Journey to a Mature Software Process
,
1994,
IBM Syst. J..
[6]
Horst Zuse,et al.
A Framework of Software Measurement
,
1998
.