Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!udel!rochester!kodak!ispd-newsserver!ism.isc.com!ico!attc!alesha
From: alesha@attc.UUCP (Alec Sharp)
Newsgroups: comp.software-eng
Subject: reviews at the various stages in the software eng process
Message-ID: <1052@attc.UUCP>
Date: 11 Feb 91 15:52:03 GMT
Reply-To: alesha@auto-trol.UUCP (Alec Sharp)
Organization: Auto-trol Technology, Denver
Lines: 32

All the voluminous correspondence about code inspections is very
interesting, but I'm intrigued about reviews in the earlier part 
of the process.

There are various checkpoints to satisfy in the traditional process:
	Requirements spec
	Analysis
	Functional Spec
	Users Guide
	High level design
	Low level design
	Test plans
	Implementation
	Testing
(not necessarily in the order shown).

To avoid wasting time detecting and correcting errors at later 
stages in the game, we're told to review each component before going
on to the next one (a certain amount of parallelism seems to be
acceptable).  However, I've never seen a consistent description 
of the order these documents should be produced and reviewed.

Does anyone have experience with the process shown above?  If so,
which documents did you create, in what order, and when did you
review them?

Alec Sharp  alesha@auto-trol.com

-- 
--------------------------------------------------------------------
Alec Sharp                          Auto-trol Technology Corporation
alesha@auto-trol.com                12500 North Washington Street
(303) 252-2229 	                    Denver, CO 80241-2404