1. Initiative for a public method  dominique.vauquier@praxeme.orgdominique.vauquier@praxeme.org  +33 (0) 6 77 62 31 75  http://www.praxeme.org http://www.praxeme.org ?http://dvau.praxeme.orghttp://dvau.praxeme.org Reference Version Protection Enterprise Architecture: a Method 2008-11-20SLB-25 How a comprehensive approach of the enterprise can really change our systems « Theory without practice is useless; practice without theory is blind. » Immanuel Kant

2. “Enterprise Architecture: a Method” www.praxeme.org /12 SLB-252 Presentation objective  Objective  Topics  Architecture  EA, TOGAF  Modeling MDA  Methodology, training, transition Provide insight into the state of the art and advanced practices Document protection

3. “Enterprise Architecture: a Method” www.praxeme.org /12 Dictum 1.Separation of concerns  An ancient principle, in place since the beginning of software engineering 2.Continuity of the transformation chain  Strategy, EA, organization, logical architecture, software, physical architecture…  EA & SOA 3.Isolation of the sources of variations  Time binding: adapt the enterprise to a changing environment  Facilitate sustainable transformation  Space binding: reconfigure the Enterprise System  Ensure convergence and interoperability SLB-253

4. “Enterprise Architecture: a Method” www.praxeme.org /12 Novelties SLB-254

5. “Enterprise Architecture: a Method” www.praxeme.org /12 How to do 1.Need for a methodological framework  What are the different kinds of models?  How to organize the skills? 2.“Productive” models  If we are to produce different models, we want them to link together  Partial automation to obtain new modeling elements or to generate the code SLB-255

6. “Enterprise Architecture: a Method” www.praxeme.org /12 Which framework?  Zachman’s framework  Cross questions and scopes  Enterprise Architecture  Four levels of representation  Poorly articulated  Merise  Levels of abstraction  Crossed with data/function separation SLB-256 Technology Architecture Data Architecture Application Architecture Business Architecture

7. “Enterprise Architecture: a Method” www.praxeme.org /12 SLB-237 Pragmatic aspect Business: the “good” description  Approach by activities  Classical approach  Flawed with local variation  Functional & hierarchical breakdown structure  Semantic modelling  Additional approach  Move to genericity  New solution to cope with complexity Actors & organisational entities Process & use-cases Business objects, real objects (Information+Transformation+Action) Semantic aspect Refers to

8. “Enterprise Architecture: a Method” www.praxeme.org /12  Determine the software structure from the business description  Applying MDA standard  Independence from technical choices  Technical Target free  Long term SLB-238 Software: the “good” structure Pragmatic aspect Semantic aspect Logical aspect Derives Logical services & aggregates (logical machines…) Core StratumOrganization StratumInteraction Stratum

9. “Enterprise Architecture: a Method” www.praxeme.org /12 SLB-239 FD Caricature of an architecture based upon functional approach Logical blocks take in charge functional domains Which structure the pragmatic model It stems from that important dependencies or redundancies since same business objects are used inside many functional domains BO FD OD Outlined logical architecture according to Praxeme method Several logical blocks match with the objects domains from semantic model. Dependencies obey topological constraints Between strata (“Business Core”, “Organization”, “Interaction”) Coupling reducing, No dependency between FD, unless special cases, etc. Logical architecture: a new approach FD: functional domain BO: business object OD: objects domain

10. “Enterprise Architecture: a Method” www.praxeme.org /12 LogiqueSémantiquePragmatiqueGéographiqueMatérielTechnique Logiciel Physique Logical aspect Semantic aspect Pragmatic aspect Geographic aspect Hardware Technical aspect Software Physical aspect Scoping The Enterprise System Topology

11. “Enterprise Architecture: a Method” www.praxeme.org /12 The method in a nutshell  Architectural decisions  Define the objects domains  Semantic aspect  Define the functional domains  Pragmatic aspect  Establish the logical architecture graph  Logical aspect  Choose style and express rules  Topological rules, derivation rules…  Approach  First step using functional approach  Then, correct by introducing semantic and endeavoring to simplify the structure SLB-2511

12. “Enterprise Architecture: a Method” www.praxeme.org /12 Conclusion  For further information  The site of the association “Praxeme Institute”  http://www.praxeme.org http://www.praxeme.org  The site of the “Sustainable IT Architecture” community  http://www.sustainableitarchitecture.com/ http://www.sustainableitarchitecture.com/  Next events  Workshop around Christophe Roche, “Praxeme and ontologies”  Symposium 2008, free conference  Register to keep in touch  http://groups.google.com/group/Praxeme-Annonces http://groups.google.com/group/Praxeme-Annonces SLB-2312 Help us to help you: please join us in our efforts!

13. “Enterprise Architecture: a Method” www.praxeme.org /12 SLB-2313 /38 The Zachman framework

14. “Enterprise Architecture: a Method” www.praxeme.org /12 SLB-2314 The three chapters of methodology WHAT HOW (collective)(individual)

15. “Enterprise Architecture: a Method” www.praxeme.org /12 SLB-2315 Position of current assets WHAT HOW (collective)(individual) Start: the kinds of architecture… Detailed how-to-do ?