I gave a talk in Febuary 2005 at the local java group called
COBOL oriented J2EE
The point to the talk is not to say that "COBOL orieinted J2EE " (COJ) is good.
COJ makes development and maintenance harder and more expensive.
However, "COBOL oriented J2EE" (COJ) is the dominant paradigm.
And if we want to make our jobs easier, we need to
understand:
(1) why does COJ exist?
(2) what is Domain Design?
(3) who benefits from COJ?
(4) How can those same people benefit more from OO Domain design?
(5) What small easy steps can we take to more toward OO Domain Design? or How to escape being just a "COJ on the wheel" (couldn't resist :-)
That's a pretty long list to cover in one short presentation.
But I tryed to give some jumping off points for people who
want to go deeper in a particular area.
