Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!lgc.com!cl From: cl@lgc.com (Cameron Laird) Newsgroups: comp.software-eng Subject: Re: Code Inspections Message-ID: <1991Feb6.150845.10496@lgc.com> Date: 6 Feb 91 15:08:45 GMT References: <15469.9102041851@olympus.cs.hull.ac.uk> <1991Feb6.143922.20539@cs.uiuc.edu> Sender: news@lgc.com Organization: Landmark Graphics Corp., Houston, Tx Lines: 20 Nntp-Posting-Host: forest.lgc.com In article <1991Feb6.143922.20539@cs.uiuc.edu> marick@cs.uiuc.edu (Brian Marick) writes: . . . >Because of this, I like to write the test cases and user documentation >well before I write the code. . . . I insist on this, whenever I can. For me, the obligatory order is 1. user's manual; 2. test suite; 3. implementation. In this submission, I'll only argue by assertion: my experience is that scheduling work in this sequence contributes mightily to satisfaction, quality, timeliness, ... -- Cameron Laird USA 713-579-4613 cl@lgc.com USA 713-996-8546