Xref: utzoo comp.sw.components:301 comp.software-eng:2094
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!gatech!hubcap!billwolf%hazel.cs.clemson.edu
From: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu (William Thomas Wolfe, 2847 )
Newsgroups: comp.sw.components,comp.software-eng
Subject: Re: Schedule and budget are secondary
Message-ID: <6693@hubcap.clemson.edu>
Date: 6 Oct 89 15:33:40 GMT
References: <16168@vail.ICO.ISC.COM>
Reply-To: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu
Lines: 16

From article <16168@vail.ICO.ISC.COM>, by rcd@ico.ISC.COM (Dick Dunn):
>>    ...But engineers don't play; this is left 
>>    for hackers.  We're here to engineer products on time, under budget,
>>    and with as much quality as we can get within those two constraints.
> 
> why not "ahead of time, on budget" or even getting both right and being 
> "on time, on budget"?  But that's another digression...)  It's particularly
> sad to see "quality" a poor third to the other two.

   If the product does not meet the minimal standards of acceptability,
   then it is not complete.  "On time", etc., refers to the product
   being completed in accordance with the relevant quality requirements.


   Bill Wolfe, wtwolfe@hubcap.clemson.edu