Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!udel!gatech!purdue!yuma!csn!stortek!k1!alec
From: alec@k1.stortek.com (Alec Sharp)
Subject: Code Reviews
Message-ID: <D3y83H.DFL@stortek.com>
Sender: news@stortek.com
Organization: Storage Technology Corporation
X-Newsreader: TIN [version 1.2 PL2]
Date: Mon, 13 Feb 1995 17:18:53 GMT
Lines: 25

I'm looking for pointers on what reviewers should look for
when reviewing Smalltalk code.

We are about to review a project done in Smalltalk. Our
situation is:

	There is no design document since this project was
	a learning experience in OO thinking and the design
	changed quite radically between the initial ideas
	and the final implementation. Thus the review will
	really be a combination code and design review.

	We do not have Envy.

How do your reviewers do code and/or design reviews. What do
they look for? How do they proceed through classes and methods?

Thanks for any information you can give.

Alec


--
alec_sharp@stortek.com		Storage Tek, 2270 S. 88th Street
(303)-673-2955			Louisville, CO 80028-4286
