Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!elroy!devvax!jplpro!des
From: des@jplpro.JPL.NASA.GOV (David Smyth)
Newsgroups: comp.lang.c++
Subject: Re: Object Design Tools
Message-ID: <1442@devvax.JPL.NASA.GOV>
Date: 1 Mar 88 22:59:19 GMT
References: <97@cui.UUCP> <36300003@pyr1.cs.ucl.ac.uk>
Sender: news@devvax.JPL.NASA.GOV
Reply-To: des@jplpro.JPL.NASA.GOV (David Smyth)
Organization: Jet Propulsion Laboratory, Pasadena CA.
Lines: 26

In article <36300003@pyr1.cs.ucl.ac.uk> winnie@pyr1.cs.ucl.ac.uk writes:
>
>Tsichritzis has given some comments regarding proper design tools
>for object-oriented programming. However, I believe that before
>we can decide what design tools are necessary, we do need a proper design
>methodology which provides the infrastructure for the design tools.

OOD Methodology (derived from Booch, Cox, and MANY others):

1)	Understand the problem any way you want to.  Maybe throw together a 
	prototype.  I don't care - understanding the problem is beyond the
	scope of "design."

2)	Write an informal description of the problem.  This is just prose.

3)	Identify the "objects" in the informal description (nouns, and
	identifying prose).

4)	Identify the attributes of the objects (descriptive prose) and the
	methods applied to the objects (active prose).

Well, that does it for the OOD methodology.  Pretty easy isn't it?  Try it,
you'll like it - everybody else has! 

What is OOP?  Implement those attributes and methods in a programming language.
I don't care which one, use FORTRASH if you want.  However, a true "OOPL" is
alot easier, just like symbolic programming is easier in LISP than FORTRASH.