Information Technology Reference
In-Depth Information
makes and good and bad metric, and how to establish uniform measures. We have
discussed how metrics can play a key role in estimating project scheduling, size,
effort required and cost via baseline measurements from past projects. Once began,
we have seen how metrics can allow us to measure the quality of the design and
architecture of a project, and, more specifically, for the object-oriented approach.
And once complete, this chapter explained how project metrics help define process
metrics for organizations in order to improve the software engineering process so
higher quality software can be produced. Lastly, post release metrics were defined
for maintaining software and testing maturity.
12.9 Exercises
1. Briefly describe the properties of a good metric.
2. Not all metrics are available for every member of an organization or even
development team to see. Describe the difference between public and private
metrics and explain why a metric might be private.
3. Explain and diagram how complexity can be increased/decreased by the fan-in
and fan-out of components within a system.
4. Why might a Software Maturity Index approaching 1 be an indication that the
software release is becoming more stable?
References
Basili V, Phillips T-Y (1981) Evaluating and comparing software metrics in the software
engineering laboratory. ACM.
http://portal.acm.org/citation.cfm?id=807913
. Accessed 24
July 2009
Card D, Glass R (1990) Measuring software design quality. Prentice Hall
Conte SD, Dunsmore H E, Shen V Y (1986) Software engineering metrics and models.
Benjamin-Cummings Publishing Co., Inc.
McCabe T (1976) A complexity measure. IEEE Computer Press Society
McCall J, Cavano J (1978) A framework for the measurement of software quality. ACM
Sigmetrics Performance Evaluation Review
Pressman R (2005) Software engineering: a practitioner's approach, 6th edn. McGraw-Hill
Pressman R (2010) Software engineering: a practitioner's approach, 7th edn. McGraw-Hill
Schach SR (2007) Object-oriented and classical software engineering, 7th edn. McGraw-Hill
Sommerville I (2004) Software engineering, 7th edn. Peason Education, Ltd., Boston
Zuse (1997) A framework of software measurement. Hubert and Co.
