Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!uunet!pdn!locke
From: locke@paradyne.com (Richard Locke)
Newsgroups: comp.software-eng
Subject: Re: Info wanted on Guidelines for Metrics
Keywords: in-process metrics, creating a metrics program
Message-ID: <1991Feb21.185654.27911@pdn.paradyne.com>
Date: 21 Feb 91 18:56:54 GMT
References: <7574@drutx.ATT.COM> <1991Feb20.180831.28131@e2big.mko.dec.com>
Sender: news@pdn.paradyne.com (News Subsystem)
Distribution: comp
Organization: AT&T Paradyne, Largo, Florida
Lines: 29
Nntp-Posting-Host: nike

In article <1991Feb20.180831.28131@e2big.mko.dec.com> fjs@bonz.enet.dec.com (Jay Shields) writes:

>   DeMarco also has a project-level metrics tool called Checkpoint. 
>I know it runs on DOS, but am not sure if any other OS's are
>supported.

It's not DeMarco, but Capers Jones who's behind Checkpoint.

Checkpoint just helps you keep track of some metric & milestone
information (as opposed helping you decide what metrics to track, which
is very different).  Its substantial price tag is justified more
(in my opinion) in its predictive abilities than its date storage
abilities...  Of course, I'm a developer with no direct need to give
upper management nice impressive graphs, etc ;-)

Addressing the original issue:  "Software Metrics: Establishing
a Company-Wide Program" by Grady & Caswell has some practical
stuff in it, though it obviously is focused less on the project
level than the company level.  I think you'll find it useful
nonetheless.

By the way, I've been working to evaluate project estimation tools
lately which is why I'm familiar with Checkpoint.  I'd be interested
in comparing notes with others who've done work in this area recently.


-dick

{uunet,peora}!pdn!locke			Phone: (813) 530-8241


Brought to you by Super Global Mega Corp .com