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

[vlad@world2u.com (vlad)]

Paul_Gover@uk.ibm.com wrote:

>However, I disagree when it comes to design; this might be a
>difference in our view of where to separate design from coding.  My view is that design
>includes implementation detail such as inheritance.  I most certainly consider that
>"OO development methods" should address it.

Design of what? Design of a class or design of a system. In the design of a
system you  don't need to bother with inheritance. What about objects, that are
not defined by classes or what about objects, which can change it's class at
run-time.
In the design of a system the most important thing is a object interface and how
it coopeates with other objects. 

If you design a class, then you will find inheritance usefull. Of course the
"inheritance" can be replace by delegating and then we even don't need classes.
So inheritance is a implementation detail, that is not important in design of
your application. It is my view and I may be wrong. 



>I think from your statement about converting to equivalent programs indicates you
>consider implementation to be outside the scope of the design (since you describe two
>different implementations for the same design); in that case, do you think that
>questions of inheritance and so forth are not part of the development method?
>I think this is dangerous; in your example, the coverted program has large amounts of
>duplicated code, so making changes is harder because the programmer has to find all
>occurrences of the duplicated code, and we have lost one of the benefits of OO.

>Paul Gover
>IBM Warwick Development Group
>Mumbling for myself, not IBM

 Vlastimil Adamovsky
 ** C++ and Smalltalk consultant **
 * http://www.stepweb.com *