cinjug,
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) who benefits from it?
(3) what is Domain Design?
(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 presentation.
But I'll try to give some jumping off points for people who
want to go deeper in a particular area.
Hope that is a little clearer
-Mark.
> All,
>
> We will be having a meeting this Monday. Mark
> Windholtz will speaking on:
>
> Domain Design and Patterns, Avoiding the common
> approach of COBOL oriented J2EE
>
> Most current J2EE applications separate Data and
> Processing just like the COBOL programs. This is the
> opposite of Object Oriented design.
> * Why does this happen?
> * When is this the right approach?
> * How do you recognize it quickly?
> * Tips on how to move to real OO driven J2EE
> applications.
>
> Be there or be square.
>
> --Chris
|