Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!hobbes.physics.uiowa.edu!news.iastate.edu!sharkey!fmsrl7!slee01!hugh
From: hugh@slee01.srl.ford.com (Hugh Fader)
Newsgroups: comp.lang.c++
Subject: Analysis/Design Methods for OOP
Message-ID: <44056@fmsrl7.UUCP>
Date: 20 Jun 91 16:39:56 GMT
Sender: root@fmsrl7.UUCP
Lines: 17

It seems as though every reference I read encourages a bottom-up (or
maybe more appropriately middle-down, middle-up) type of design
approach for object oriented programming -- i.e. do your program
design by developing objects, then use the objects to develop the
system.

This approach may be OK for small one or two programmer projects but
seems inadequate for larger ones. Are Yourdon/DeMarco/Page-Jones
structured analysis and design techniques now obsolete? If not, how
have people modified them to work with OOP? If these techniques are
obsolete, what are people using in their place?

I am also interested in references anyone may have for analysis and
design of object oriented systems.
--
Hugh Fader
hugh@slee01.srl.ford.com