Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!cmcl2!lanl!beta!drich
From: drich@klaatu.lanl.gov (David O. Rich)
Newsgroups: comp.object
Subject: Object-Oriented Metrics (Summary of Responses)
Message-ID: <DRICH.91Feb28084312@klaatu.lanl.gov>
Date: 28 Feb 91 15:43:12 GMT
Sender: news@lanl.gov
Distribution: comp
Organization: Los Alamos National Laboratory (LANL)
Lines: 55


My initial posting asked for references and pointers to
object-oriented metrics.

The responses sent directly to me were few; I've included excerpts
from a couple of the more interesting ones below.  I was disappointed
not to hear more on the Demeter System and specifically the Law of
Demeter (but, maybe that says it all).  In any case, the "Emperor
Strikes Back" series is far more interesting ;-).

--------------------------------------------------------------------
From: root@nextserver.cs.stthomas.edu (Max Tardiveau)

Luiz A. Laranjeira
Software Size Estimation of Object-Oriented Systems
IEEE Transactions on Software Engineering, May 1990, pp. 510-522


--------------------------------------------------------------------
From: Craig Hubley <craig@utcs.utoronto.ca>

Measures that we and our clients have used include:
	- absolute detail size of the interface
		(i.e. # of functions + # of arguments + # of returns to each)
		(smaller is better)
		(applies to a single type, group of types, app., or domain)
	- absolute detail size of the type
		(as above PLUS number of internal functions/arguments/datums)
		(following principle that variables inhibit reusability)
	- absolute code size per unit of specification (i.e. function, type)
		(smaller is better)
	- relative scope restriction of the interface (in re-engineering)
		(i.e. 1 point per fn or data item removed from 1 scope level)
		(obviously this only works if a structured version exists)
	- relative cohesion (in re-engineering)
		(i.e. 1 point per fn/datum or fn/fn interaction moved within
		 a type, which was formerly exposed to a wider scope)
		(this is a form of scope restriction)
	- absolute coupling between two types (measured in absolute details)
		(e.g. type calls fn in other with 2 arguments = 3 points)
		(again, smaller is better, following weak coupling principle)
	- relative coupling
		(i.e. how much is dependence increased/decreased by change)
	- standard empirical SW quality control metrics


--
=============================================================
David Rich            | Military Systems Analysis Group (A-5)
Email: dor@lanl.gov   | Mail Stop F602
Phone: (505) 665-0726 | Los Alamos National Laboratory
FAX  : (505) 665-2017 | Los Alamos, NM 87545
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
"...in the abundance of water, the fool is thirsty..."
=============================================================