1 / 15

Enterprise Architecture: a Method

Enterprise Architecture: a Method. «  Theory without practice is useless; practice without theory is blind. » Immanuel Kant. How a comprehensive approach of the enterprise can really change our systems. Presentation objective. Objective Topics Architecture EA, TOGAF Modeling MDA

bluma
Télécharger la présentation

Enterprise Architecture: a Method

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Architecture: a Method « Theory without practice is useless; practice without theory is blind. » Immanuel Kant How a comprehensive approach of the enterprise can really change our systems SLB-25

  2. Presentation objective • Objective • Topics • Architecture • EA, TOGAF • Modeling MDA • Methodology, training, transition Provide insight into the state of the art and advanced practices Duration: 1/2 h Document protection SLB-25

  3. Dictum • Separation of concerns • An ancient principle, in place since the beginning of software engineering • Continuity of the transformation chain • Strategy, EA, organization, logical architecture, software, physical architecture… • EA & SOA • 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-25

  4. Novelties SLB-25

  5. How to do • Need for a methodological framework • What are the different kinds of models? • How to organize the skills? • “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-25

  6. 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 Business Architecture Application Architecture Data Architecture Technology Architecture SLB-25

  7. 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 Semantic aspect Objects Business objects, real objects (Information+Transformation+Action) Refers to Pragmatic aspect Activities Actors & organisational entitiesProcess & use-cases SLB-23

  8. Software: the “good” structure Core Stratum Organization Stratum Interaction Stratum • Determine the software structure from the business description • Applying MDA standard • Independence from technical choices • Technical Target free • Long term Semantic aspect Logical aspect Objects Logical services & aggregates (logical machines…) Derives Pragmatic aspect Activities Derives SOA SLB-23

  9. Logical architecture: a new approach Caricature of an architecturebased upon functional approach Outlined logical architectureaccording to Praxeme method FD FD FD FD OD OD OD BO OD OD BO FD FD FD FD Logical blocks take in charge functional domains Which structure the pragmatic model It stems from that important dependencies orredundancies since same business objects are usedinside many functional domains • Several logical blocks match with the objects domainsfrom semantic model. • Dependencies obey topological constraints • Between strata (“Business Core”, “Organization”, “Interaction”) • Coupling reducing, • No dependency between FD, unless special cases, • etc. FD: functional domain BO: business object OD: objects domain SLB-23

  10. The Enterprise System Topology Sémantique Pragmatique Géographique Matériel Technique Logiciel Physique Logicalaspect Semanticaspect Pragmatic aspect Geographicaspect Hardware Technicalaspect Software Physicalaspect Logique Scoping

  11. 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-25

  12. Conclusion • For further information • The site of the association “Praxeme Institute” • http://www.praxeme.org • The site of the “Sustainable IT Architecture” community • 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 Help us to help you: please join us in our efforts! SLB-23

  13. The Zachman framework SLB-23

  14. The three chapters of methodology Product WHAT Process HOW Procedures & methods (collective) (individual) SLB-23

  15. Position of current assets Start: the kinds of architecture… Product Frameworks & Target architectures Detailed how-to-do ? UP, RUP, OpenUP... WHAT Governance framework & process CMMI Process HOW Procedures & methods (collective) (individual) TOGAF SLB-23

More Related