Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!abvax!iccgcc!kambic From: kambic@iccgcc.decnet.ab.com (George X. Kambic, Allen-Bradley Inc.) Newsgroups: comp.software-eng Subject: Re: bridge building and discipline Message-ID: <4708.28437219@iccgcc.decnet.ab.com> Date: 29 May 91 14:19:20 GMT References: <1259@grapevine.EBay.Sun.COM> <9105012313.AA23259@enuxha.eas.asu.edu> <1991May3.142824.208@keinstr.uucp> <1991May3.234349.14026@auto-trol.com> <4504.28267bad@iccgcc.decnet.ab.com> <1991May9.053311.800@netcom.COM> <4563.282e83ea@iccgcc.decnet.a <4639. Lines: 20 Lines: 19 In article , jgautier@vangogh.ads.com (Jorge Gautier) writes: > In article <4639.283807a0@iccgcc.decnet.ab.com> kambic@iccgcc.decnet.ab.com (George X. Kambic, Allen-Bradley Inc.) writes: [...] > > I'm not saying I don't want to know quantitative information, but I > think qualitative information is much more valuable and reliable. > Assuming you can interpret it, which requires knowledge about and > experience in software development and usage. Interesting point. What qualitative information do you collect, and how do you interpret it? Not trying to be funny here, but is it 2x, 10x or 100x more valuable than quantitative information? Better yet, what relative worth does it have to specific metrics? Guess I am trying to quantify qualitative indicators, but this would help point to where we should be spending our time in assessing sw projects. GXKambic standard disclaimer