Page 139 -

110 PART TWO MANAGING SOFTWARE PROJECTS

Number of user inputs: 12
Number of user outputs: 60
Number of user inquiries: 9
Number of external interfaces: 3
Transformations: 36
Transitions: 24
Assume that the complexity of these counts is evenly divided between low, average,
and high.
4.13. The software used to control a photocopier requires 32,000 of C and 4,200
lines of Smalltalk. Estimate the number of function points for the software inside the
photocopier.

4.14. McCall and Cavano (Section 4.5.1) define a "framework" for software quality.
Using information contained in this and other books, expand each of the three major
"points of view" into a set of quality factors and metrics.

4.15. Develop your own metrics (do not use those presented in this chapter) for cor-
rectness, maintainability, integrity, and usability. Be sure that they can be translated
into quantitative values.
4.16. Is it possible for spoilage to increase while at the same time defects/KLOC
decrease? Explain.

4.17. Does the LOC measure make any sense when fourth generation techniques
are used? Explain.

4.18. A software organization has DRE data for 15 projects over the past two years.
The values collected are 0.81, 0.71, 0.87, 0.54, 0.63, 0.71, 0.90, 0.82, 0.61, 0.84, 0.73,
0.88, 0.74, 0.86, 0.83. Create mR and individual control charts to determine whether
these data can be used to assess trends.

FURTHER READINGS AND INFORMATION SOURCES

Software process improvement (SPI) has received a significant amount of attention
over the past decade. Since measurement and software metrics are key to success-
fully improving the software process, many books on SPI also discuss metrics. Worth-
while additions to the literature include:

Burr, A. and M. Owen, Statistical Methods for Software Quality, International Thomson Pub-
lishing, 1996.
El Emam, K. and N. Madhavji (eds.), Elements of Software Process Assessment and Improve-
ment, IEEE Computer Society, 1999.
Florac, W.A. and A.D. Carleton, Measuring the Software Process: Statistical Process Control for
Software Process Improvement, Addison-Wesley, 1999.