Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!spool.mu.edu!sol.ctr.columbia.edu!src.honeywell.com!skyler.mavd.honeywell.com!djbailey From: djbailey@skyler.mavd.honeywell.com Newsgroups: comp.software-eng Subject: Re: Software Quality Message-ID: <1991Mar15.095125.44@skyler.mavd.honeywell.com> Date: 15 Mar 91 15:51:24 GMT References: Distribution: comp.software-eng Lines: 28 In article , jgautier@vangogh.ads.com (Jorge Gautier) writes: > [...] "We can't apply metrics that we don't understand." First, let me recommend a couple of my favorite books: SOFTWARE SYSTEM TESTING AND QUALITY ASSURANCE by Boris Beizer published in 1984 by Van Nostrand Reinhold, ISBN 0-442-21306-9 and WICKED PROBLEMS, RIGHTEOUS SOLUTIONS by Peter DeGrace and Leslie Hulet Stahl published in 1990 by Yourdon Press. Peter DeGrace has some excellant comments on software development, software engineering, and science. He compares the present state of the art of software development with the level of understanding of architecture by the builders of the great medieval cathedrals of europe. We have a lot of practical knowledge but we don't understand the underlying science very well. I think that is true. The general difficulty in estimating jobs and meeting schedules supports this view. Software development takes place in our heads. It is difficult to observe and measure what happens. Now, back to the quote. The problem is that we attach too much significance to metrics without understanding them. If you want to investigate software development scientifically, you have to measure something. You also have to evaluate your measurement techniques. Developing good measurement techniques is extremely important. You can't develop a science without measurements. -- Don Bailey