Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!uwm.edu!bionet!agate!usenet.ins.cwru.edu!abvax!iccgcc!kambic
From: kambic@iccgcc.decnet.ab.com (George X. Kambic, Allen-Bradley Inc.)
Newsgroups: comp.software-eng
Subject: <None>
Message-ID: <4375.2817f371@iccgcc.decnet.ab.com>
Date: 26 Apr 91 14:31:29 GMT
References: <RICHARD.91Mar12184440@dompap.iesd.auc.dk> <36650004@hpopd.pwd.hp.com> <601@tivoli.UUCP>
Lines: 19

In article <601@tivoli.UUCP>, alan@tivoli.UUCP (Alan R. Weiss) writes:
> In article <36650004@hpopd.pwd.hp.com> daves@hpopd.pwd.hp.com (Dave Straker) writes:
>>On measuring complexity...
>>
>>Before you measure anything, you should ask: Why am I doing this?
>>What am I going to do with the information? What questions will
>>it help answer? What decisions will it help me make?

Note also that the answers you get may not be what you expect because the
actual metrics may be answering other questions.  Metrics aren't orthogonal.
They are subject to improvement processes just like the software process 
itself.  In other words, ask some questions, get some data, do some analysis,
learn, and then repeat, repeat, repeat.  

Improve the process, and the metrics, and .......(wheels within
wheels within wheels.....).

GXKambic
standard disclaimer.