Re: Interesting but sensitive topic to discuss (HELP: - OOP and CASE t

["Chris" <gaijin@infonie.fr>]

OOP design is interresting for two points.

First, it may be a way to think about/to solve your problem. Just a
different approach (not better, not worse than others). You may not have
here to really think about inheritance or polymorphism.
Second, when designing your solution, you may think about reusing what you
found. Then inheritance and polymorphism are useful.

What's making OOP a better approach than other non-OOP paradigms is that
you can orient your design toward the present problem AND the futures at
the same time (could get it a little longer, thus).


-- 
Chris, drunk philosoph and bad programmer
--------------------------------------------------------------------

"The nail pulling up calls the hammer"

                                     zen proverb



> > I think implementation inheritance is overemphasized.  Many seem to
think
> > that the class hierarchy **is** the design!
> 
> > As I noted in another post: the
> > same class hiearchy may permit the specification of many different
programs,
> > each with a different architecture and design.
> 
> This is possible, but is it useful? If my implementation hierarchy
differs  
> too far from the design hierarchy, I'd expect horrible costs just to keep
 
> them in sync.
> 
> If the objects involved are design objects, I'd take a long, hard look at
 
> the classes involved. If two objects have identical behaviour, and I feel
 
> they shouldn't go in the same class, then I probably forgot to include  
> some behaviour that differs. (Or behaviour that might differ in the  
> future. In that case, the future evolution paths should be fixed by some 

> constraints on the class.)
> 
> > * When should delegation be used instead of inheritance?
> >
> > * When should the Strategy pattern be used instead of inheritance?