Xref: utzoo comp.software-eng:388 comp.lang.c++:942
Path: utzoo!utgpu!water!watmath!clyde!att-cb!att-ih!pacbell!ames!oliveb!pyramid!decwrl!labrea!csli!kasper
From: kasper@csli.STANFORD.EDU (Kasper Osterbye)
Newsgroups: comp.software-eng,comp.lang.c++
Subject: Re: Object Oriented Design
Message-ID: <3221@csli.STANFORD.EDU>
Date: 31 Mar 88 20:59:10 GMT
References: <1711@devvax.JPL.NASA.GOV> <421@goofy.megatest.UUCP>
Reply-To: kasper@csli.UUCP (Kasper Osterbye)
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 29

Hi,

There was a guy that asked for design methodologies for software engeneering.
I know that a number of persons might not agree on my suggestion, but here it
goes: 
Michael Jacson, System Development. Prentice-Hall International Inc. 1983

You will not find the word object-oriented anywhere in it, but it stresses
the importance of in finding the objects and operations on these objects
in the very first part of system development. He has a number of "rules of
thump" on what kind of objects to include, what to exclude, what kind of
actions to look out for and pitfalls in general.

He do NOT give any hint on how to organize your objects into a class hierarchy.

His methodology has a number of stages, with the implementation being the
last. With the arrival of o-o architectures, this last part of the book might
not be that relavant anymore. 

check it out, said the wise student who have never done programming in the
large :-)

--Kasper.

Kasper Osterbye                                |||  ///   ///|
Internet: kasper@csli.stanford.edu             ||| ///   ///||
UUCP: {backbones..}!csli.stanford.edu!kasper   |||<<<   ///|||
AT&T: (415) 323 9604                           ||| \\\ ///=|||
USMAIL: 2420 Tasso st. #3, Palo Alto CA 94301  |||  \\X//  |||MIGA