Re: Good Design Strategies <Was comments on comments>

[djones@megatest.UUCP (Dave Jones)]

From article <52101@yale-celray.yale.UUCP>, by jellinghaus-robert@CS.YALE.EDU (Rob Jellinghaus):

> A good object-oriented
> system quite often will consist largely of software components that
> have been taken from older projects, which is not really a possibility
> in either the top-down or the bottom-up model.  If the map of a top-
> down system is a tree, with the principal function at the top, then
> an object-oriented system is a net, with each object providing
> services to other objects, with no clear hierarchical arrangement;
> this enables the system to be locally modified without global effects.
>



Point of semantics well taken.  Perhaps I should not be using the term
"bottom-up".  I guess if you get into the topology of it, inheritance
of structure (not reference), yields a directed acyclic graph which
may have lots of local bottoms and tops.  But if I said, "infrenum-supremum"
programming, who would know what I was talking about?




                              Dave J.