2. Page 2 2008-01-11 Agenda Agile process and its variations Object-Oriented paradigm its meaning is complexity management 3-layer architecture and code generation Abstract Domain Driven Development
9. Page 9 2008-01-11 Why collaboration is simpler Functional decomposition Object collaboration A D Trick A1 Trick A2 Trick D1 Trick D2 B C Trick B1 Trick B2 Trick C1 Trick C2 A D B C Two layer encapsulated and collaborative complexity Flat layer connection complexity
10. Page 10 2008-01-11 Combining ER- and process models OO-model Two separate model higly difficult to combine ER - model Process model
11. Page 11 2008-01-11 The overall viewpoint is dominative in nature OO viewpoin leads to collaborative agent solution Functional decomposition lead to timebase functiona decomposition and 2- layer soultions Paradigm principle of Object Orientation These approaches are mutually exclusive and can not be combined by their very paradigm nature
13. Page 13 2008-01-11 Abrstract model – intersection of business dimensions
14. Page 14 2008-01-11 Close (almost one-to-one) correlation with reality (simulation model) => easy to understand and verify Multy layer encapsulation bring order to chaos=> object encapsulation collapses complexity Inheritance expands possibilities=>representation several abstraction levels in one model The net result: the overall complexity of the model drops to square root or cubic root of the original Priorities of Object-Oriented principles
16. Page 16 2008-01-11 Explotion of complexity definition design implementation Domain implemenstation Application additions Abstract domain modeling Comparison between agile and waterfall project principal Waterfall implementation definition design Tradition agile Agile model driven developmet
17. small big semantic content abstraction level high low amount of semantics The paradox of abstraction
18. Agility with model reality Development process Abstract core model 5 -15 dyas Design Implementations
19. GUI Application Objects Business Objects Persistent Objects Business objective 1 Abstract domain model Business processes Workflows 3 Use cases Implementation 2 4 Implementation Development process
20. GUI Application Objects Business Objects Persistent Objects Generate 100% 10% 80 % Development process
21. Business logic Application logic Business Objects Application Objects Screens Persistence Asymmetrically tightly coupled Structure of 3-tier architecture
22. Page 22 2008-01-11 Into the hard core of things Understanding Of Object paradigm 1 Controled abstraction and 3-tier architecture 2 Agility 3 Code generation 4
