Let's put this to rest

Responding to Bob Martin...

In another thread you said:

"Sigh. HS, what you call OOA/D is not what most people call OOA/D.
What you call OOA/D has more to do with the particular religion of
translation (or should we say MDA)."

You haven't responded to my challenge in that thread, but I'm not going to let you off that easily. You have made similar assertions several times over the years and I am getting really tired of it because there is no basis in fact for the assertion. So I want to settle this once for all.

I want some demonstration of why the OOA/D that MDA-based translationists practice is not the OOA/D that "most people" practice. (Aside from the obvious use of translation automation for OOD/P.) We could start a quote war by pulling quotes out of various OOA/D authors' books but that is subject to interpretation, context, and other factors. Fortunately there is a more objective way to resolve the dispute.

If there is some fundamental difference between the MDA/translation view and "most people's", then that difference should be manifested in the OOA models we produce. That is, for some problem the model that we would produce would /always/ be different from the model that "most people" would produce and that difference would be directly traceable to some fundamental difference in design approaches.

The book "Executable UML" by Mellor and Balcer defines an MDA profile for translation OOA modeling that is essentially the one I use. The book has dozens of examples of real problem solutions. Similarly, Leon Starr's "Executable UML: How to Build Class Models" has hundreds of examples of Class Diagrams.

Here's my challenge: Find an example in one of those books where you can demonstrate that a non-MDA/translation developer would always produce a different OOA model because that developer has a fundamentally different approach to OO software design.


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl@xxxxxxxxxxxxxxxxx
Pathfinder Solutions -- Put MDA to Work
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
Pathfinder is hiring: http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH




.

Relevant Pages

  • Re: OOD beginner (i already did a searc of the archives of comp.object)
    ... directory alphabetically lists all names and their phone numbers and ... i struggled for months with Python (i was just beginning programming at ... The first diagram is the OOA/D view where all one needs to know is that the collection is ordered somehow. ... followin boks (listing only those books which are available in INDIA) ...
    (comp.object)
  • Re: OO, I just dont get it.
    ... > advanced/professional topics. ... To do OO development properly you need to understand OOA/D. ... The OOPLs, ... shelves-full of books in any major retailer on one Amazon to see that OO ...
    (comp.object)
  • Re: OOP/OOD Philosophy
    ... OOA/D methodology despite having OOA/D-like features nearly a decade before Smalltalk. ... It is true that Smalltalk preceded OOA/D but by the time Objective-C and C++ got on the scene there were already full OOA/D methodologies around. ... books and papers written about it, ...
    (comp.object)