Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!fernwood!dumbcat!marc
From: marc@dumbcat.sf.ca.us (Marco S Hyman)
Newsgroups: comp.object
Subject: Re: OOA/D
Message-ID: <224@dumbcat.sf.ca.us>
Date: 8 Nov 90 03:26:04 GMT
References: <3697@vela.acs.oakland.edu>
Organization: MH Software, Hayward, Ca.
Lines: 20

In article <3697@vela.acs.oakland.edu> rdthomps@vela.acs.oakland.edu (Robert D. Thompson) writes:
    **My own** opinion is
    that neither book provides a discrete method for deriving class-specs 
    by a step-by-step process.
	
One of the questions I hear often, especially from newcomers into things OO,
is "how do I determine what should be an object/class?"  This is not far
from rdthomps quest for a step-by-step process to derive class
sepcifications.  Perhaps the advice I give to that question is appropriate
here -- read Robert Pirsig's "Zen and the Art of Motorcycle Maintenance,"
especially the chautauquas on QUALITY.  Most know a quality design (or class
specification) when they see it.  The steps when you don't see it is to
change it.  Iteration is probably the key.

This is not the answer most want to hear.  It's the best I can give.

// marc
-- 
// marc@dumbcat.sf.ca.us
// {ames,decwrl,sun}!pacbell!dumbcat!marc