Presentation is loading. Please wait.

Presentation is loading. Please wait.

CAS 747 - Software Architecture and Reverse Engineering, 2006 EAI Architecture Elements of Style by Magdin Stoica McMaster University March 28, 2006.

Published byDouglas Fox Modified over 9 years ago

Similar presentations

Presentation on theme: "CAS 747 - Software Architecture and Reverse Engineering, 2006 EAI Architecture Elements of Style by Magdin Stoica McMaster University March 28, 2006."— Presentation transcript:

1 CAS 747 - Software Architecture and Reverse Engineering, 2006 EAI Architecture Elements of Style by Magdin Stoica McMaster University March 28, 2006

2 CAS 747 - Software Architecture and Reverse Engineering, 20062 Outline What is Enterprise Application Integration (EAI)? Why do we need EAI? What are the elements of an EAI solution? What is the architecture of an EAI solution? Are there different ways to architect an EAI solution? Why do we need architecture styles? Defining an EAI architecture style How do we represent EAI architectures? How should we represent EAI architectures?

3 CAS 747 - Software Architecture and Reverse Engineering, 20063 EAI Explained Enterprise automation islands Data and the EAI journey from liability to asset  Confidence  Availability  Control  Visibility  Analytical support  Scalability Connected enterprises and business to business integration (B2Bi)

4 CAS 747 - Software Architecture and Reverse Engineering, 20064 EAI Solution – A layered approach Data Integration Business Process Automation Presentation Services Data availability Confidence Control Visibility Analytical support Scalability

5 CAS 747 - Software Architecture and Reverse Engineering, 20065 EAI Software Architectures Point-to-Point Message Bus Hub and Spoke  Database Hub  ERP Hub  Message Broker  Process Broker Hybrid Architectures: Hub & Spoke with Message Bus Service Oriented EAI architecture

6 CAS 747 - Software Architecture and Reverse Engineering, 20066 Point-to-Point Architecture Payroll CRM Accounting Inventory Management Web Portal Payroll 1 connection3 connections6 connections10 connections Inventory Management CRM

7 CAS 747 - Software Architecture and Reverse Engineering, 20067 Message Bus Architecture Payroll CRM Accounting Inventory Management Web Portal Publish & Subscribe

8 CAS 747 - Software Architecture and Reverse Engineering, 20068 Hub & Spoke Architecture Payroll CRM Accounting Inventory Management Web Portal HUB

9 CAS 747 - Software Architecture and Reverse Engineering, 20069 Hub & Spoke Architecture – Database Hub Payroll CRM Accounting Inventory Management Web Portal Database

10 CAS 747 - Software Architecture and Reverse Engineering, 200610 Hub & Spoke Architecture – ERP Hub Payroll CRM Accounting Inventory Management Web Portal ERP

11 CAS 747 - Software Architecture and Reverse Engineering, 200611 Hub & Spoke Architecture – Message Broker Payroll CRM Accounting Inventory Management Web Portal Message Broker

12 CAS 747 - Software Architecture and Reverse Engineering, 200612 Hub & Spoke Architecture – Process Broker Payroll CRM Accounting Inventory Management Web Portal Process Broker

13 CAS 747 - Software Architecture and Reverse Engineering, 200613 An Inside Look at HUB

14 CAS 747 - Software Architecture and Reverse Engineering, 200614 Hybrid Architecture – Hub with Message Bus HUB Payroll CRM Accounting Inventory Management Web Portal

15 CAS 747 - Software Architecture and Reverse Engineering, 200615 EAI Architecture Style EAI architecture styles are hierarchical Components  End Point: Database End Point, Application End Point, Web End Point  HUB: Message Broker, Process Broker, ERP, Database  Document  Transaction Monitor Connectors  Call (Push)  Poll (Pull)  Notification (Indirect Call)  Message Queue  Message Bus Constraints  End-Points can only be connected with the hub (Hub & Spoke)  End-Points can only be connected with the message bus (Message Bus)

16 CAS 747 - Software Architecture and Reverse Engineering, 200616 Documenting EAI Architecture Styles Documenting through UML  OMG standardized UML4EAI metamodel and the EAI UML profile  Regular UML tools can be used for designing EAI solutions  Does not support the notion of architecture styles  Does not support all components and connectors  Basic support for hierarchical styles  An enhanced MOF metamodel for EAI architecture styles  An enhanced UML profile for EAI architecture styles Documenting through ACME  Strong support for architecture styles and system families  Lack of tools and industry support  No specific EAI architecture styles defined  Define EAI architecture style in ACME

17 CAS 747 - Software Architecture and Reverse Engineering, 200617 Summary EAI architectures are mature and exhibit clear elements of style EAI architecture styles make for a great case in hierarchical architecture styles EAI architecture styles are not formally defined EAI architectures can be described through UML tools using UML4EAI or… …in ADLs once EAI architecture styles are defined in ACME

18 CAS 747 - Software Architecture and Reverse Engineering, 200618 REFERENCES 1. Devin Spackman, Mark Speaker, Enterprise Integration Solutions, Microsoft Press, ISBN: 0-7356- 2060-1 2. David S. Frankel, Model Driven Architecture: Applying MDA to Enterprise Computing, Wiley Publishing Inc., ISBN: 0-471-31920-1 3. S. Radhakrishnan, Integrating Enterprise Applications Backgrounder, http://www.intel.com/cd/ids /developer/asmo-na/eng/213532.htmhttp://www.intel.com/cd/ids /developer/asmo-na/eng/213532.htm 4. Paul Johannesson, Erik Perjons, Design Principles for Process Modelling in Enterprise Application Integration, Information Systems 26 (2001) 165-184, Elsevier Science Ltd. 5. Wolfgang Emmerich, Ernst Ellmer, Henry Fieglein, TIGRA – An Architectural Style for Enterprise Application Integration, Proceedings of the 23rd International Conference on Software Engineering, July 2001 6. Francisca Losavio, Dinarle Ortega, Maria Pérez: Comparison of EAI Frameworks, Journal of Object Technology, vol. 4, no. 4, May-June 2005, pp. 93-114 http://www.jot.fm/issues/ issue_2005_05/article1http://www.jot.fm/issues/ 7. Microsoft, MSDN, Patterns and Practices, Integration Topologies, http://msdn.microsoft.com/library/default.asp? url=/library /en- us/dnpag/html/implmessagebroker.asp http://msdn.microsoft.com/library/default.asp? url

19 CAS 747 - Software Architecture and Reverse Engineering, 200619 REFERENCES 8. OMG Group, UML Profile and Interchange Models for Enterprise Application Integration (EAI) Specification, March 2004, http://www.omg.org/cgi-bin/doc?formal/2004-03-26 http://www.omg.org/cgi-bin/doc?formal/2004-03-26 9. OMG Group, Flow Composition Model Specification, February 2004, http://www.omg.org/cgi- bin/doc?formal/2004-02-03 http://www.omg.org/cgi- bin/doc?formal/2004-02-03 10. David Garlan, Mary Shaw, An Introduction to Software Architecture, CMU Software Engineering Institute Technical Report CMU/SEI-94-TR-21, ESC-TR-94-21. 11. David Garlan, Robert T. Monroe, David Wile, Acme: Architectural Descriptions of Component- Based Systems, Foundations of component-based systems, 2000, Cambridge University Press, pp. 47-67

Download ppt "CAS 747 - Software Architecture and Reverse Engineering, 2006 EAI Architecture Elements of Style by Magdin Stoica McMaster University March 28, 2006."

Similar presentations

EDOC 2004 - MDSW Workshop1 An MDA-based Approach for Facilitating Adoption of Semantic Web Service Technology Dr. Gerald Gannod –

EDOC MDSW Workshop1 An MDA-based Approach for Facilitating Adoption of Semantic Web Service Technology Dr. Gerald Gannod –
Copyright © 2006 Data Access Technologies, Inc. Open Source eGovernment Reference Architecture Approach to Semantic Interoperability Cory Casanave, President.

Copyright © 2006 Data Access Technologies, Inc. Open Source eGovernment Reference Architecture Approach to Semantic Interoperability Cory Casanave, President.
M.B.A. II SEMESTER Course No. 208 Paper No. – XVI E-Business Dr.N.C.Dhande Objectives Provide analytical and technical framework to understand the emerging.

M.B.A. II SEMESTER Course No. 208 Paper No. – XVI E-Business Dr.N.C.Dhande Objectives Provide analytical and technical framework to understand the emerging.
Architecture Representation

Architecture Representation
Service Oriented Architecture Concepts March 27, 2006 Chris Armstrong

Service Oriented Architecture Concepts March 27, 2006 Chris Armstrong
Adding More Value to Your ERP System Using Service-Oriented Architecture (SOA) Copyright © 2001 iWay Software 1 Information Builders.

Adding More Value to Your ERP System Using Service-Oriented Architecture (SOA) Copyright © 2001 iWay Software 1 Information Builders.
Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.

Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.
Applying Architectural Styles and Patterns. Outline  Defining Architectural Patterns and Style The activation model Styles and Quality Attributes  Common.

Applying Architectural Styles and Patterns. Outline  Defining Architectural Patterns and Style The activation model Styles and Quality Attributes  Common.
Architecture-driven Modeling and Analysis By David Garlan and Bradley Schmerl Presented by Charita Feldman.

Architecture-driven Modeling and Analysis By David Garlan and Bradley Schmerl Presented by Charita Feldman.
Aligning Business Processes to SOA B. Ramamurthy 6/16/2015Page 1.

Aligning Business Processes to SOA B. Ramamurthy 6/16/2015Page 1.
The Five Key Elements of Enterprise Services Architecture

The Five Key Elements of Enterprise Services Architecture
Software Engineering and Middleware: a Roadmap by Wolfgang Emmerich Ebru Dincel Sahitya Gupta.

Software Engineering and Middleware: a Roadmap by Wolfgang Emmerich Ebru Dincel Sahitya Gupta.
Introduction to Software Architecture. What is Software Architecture?  It is the body of methods and techniques that help us to manage the complexities.

Introduction to Software Architecture. What is Software Architecture?  It is the body of methods and techniques that help us to manage the complexities.
1 Software Architecture: a Roadmap David Garlen Roshanak Roshandel Yulong Liu.

1 Software Architecture: a Roadmap David Garlen Roshanak Roshandel Yulong Liu.
21-February-2003cse403-14-Architecture © 2003 University of Washington1 Architecture CSE 403, Winter 2003 Software Engineering

21-February-2003cse Architecture © 2003 University of Washington1 Architecture CSE 403, Winter 2003 Software Engineering
OOHDM Hypermedia Research Work Designing Web-based applications with Object Oriented Hypermedia Design Method OOHDM.

OOHDM Hypermedia Research Work Designing Web-based applications with Object Oriented Hypermedia Design Method OOHDM.
Demystifying Architectural Styles Nikunj Mehta 3/11/02Demystifying Architectural Styles2 Architectural Styles Characterize –Structure, i.e. external.

Demystifying Architectural Styles Nikunj Mehta 3/11/02Demystifying Architectural Styles2 Architectural Styles Characterize –Structure, i.e. external.
Using the Vanderbilt Generic Modeling Environment (GME) to Address SOA QoS Sumant Tambe Graduate Intern, Applied Research, Telcordia Technologies Inc.

Using the Vanderbilt Generic Modeling Environment (GME) to Address SOA QoS Sumant Tambe Graduate Intern, Applied Research, Telcordia Technologies Inc.
System Integration (Cont.) Week 7 – Lecture 2. Approaches Information transfer –Interface –Database replication –Data federation Business process integration.

System Integration (Cont.) Week 7 – Lecture 2. Approaches Information transfer –Interface –Database replication –Data federation Business process integration.
SOA, EDA, ECM and more Discover a pragmatic architecture for an intelligent enterprise, to maximize impact on the business Patrice Bertrand Software Architect.

SOA, EDA, ECM and more Discover a pragmatic architecture for an intelligent enterprise, to maximize impact on the business Patrice Bertrand Software Architect.

Similar presentations

Ads by Google