MDA for the Enterprise

Transcription

1 MDA for the Enterprise Enterprise Collaboration Architecture Applying Model Driven Architecture to enterprise requirements using the OMG Enterprise Collaboration Architecture

2 Introductions Cory Casanave Primary author of CCA in EDOC

3 What does MDA mean to the Enterprise? What is Enterprise-MDA going to do for me today? How can MDA achieve integration and collaboration between people, departments, systems and companies? How does Enterprise-MDA fit into my I.T. strategy and development life-cycle? How do we use UML for Enterprise-MDA?

4 MDA Enables the Agile Enterprise T he M D A m essage is mea ni n gful to the entire enterprise; Fro m the CEO to the Developer The Agile Enterprise has a competitive advantage in its capability to embrace collaboration and change

5 Typical Problems Integration Nightmare Infrastructure, Version & Vendor lock-in Complex, divergent and manual development and deployment processes Solutions typically require buy-in (Lock-in) to proprietary tools & infrastructure - your solution must be open

6 The dynamic reality The information system must facilitate; Rapid realization of business goals Integration of independent processes and systems Multiple and Changing business requirements business processes products and technologies standards enterprise boundaries business partners

7 Technology Stew Web services.net C XML EAI Active Web pages EJB Java Beans Java Corba MQ-Series C++ SQL Cobol IMS CICS... Technology is transient, but we must embrace and adapt to it to provide meet current requirements

8 Goals A scalable and robust enterprise architecture Loosely coupled enterprise components Enable rapid provisioning of solutions Simple, reproducible processes supporting reuse Technology & vendor independence Enable the integration and collaboration of multiple; Agencies Business units (internal and external) Suppliers Systems Technologies

9 The OMG-Enterprise Collaboration Architecture ECA is a profile of UML, a way to use UML for a specific purpose - it is an OMG standard That purpose is modeling enterprise systems. You can also think of this as a modeling framework for enterprise computing ECA is part of the Model Driven Architecture (MDA) initiative of the OMG Using precise modeling techniques as part of the development lifecycle to speed development and provide technology independence ECA has been adopted by the OMG as part of the EDOC RFP.

10 Automated Model Driven Architecture Meta-Model Model UML Profile (E.G. ECA) Infrastructure Mapping (E.G. ebxml) Domain Focused Model (UML) Domain Architecture Mapping is tuned to the infrastructure Tools Produce & Integrate Enterprise Components C Framework & Infrastructure (E.G. ebxml) Minimize and structure manual implementation

11 Solution Triad Web Services Corba Service Based Architecture Components J2EE.NET Model Driven Development OMG ECA Development Process Tooling & Infrastructure Standards

12 Loose Coupling Loose coupling is the ability for independent parts of systems to be built and evolve independently Tightly coupled systems Prevent change (the next legacy system) Cause lock-in Become unmanageable Prevent reuse Quality architecture is essential for loose coupling

13 Enterprise Components Enterprise Components must be independent While being able to interoperate with each other Making the information system a lattice of cooperating components Open Standards Open Standards Open Standards

14 Enterprise Architecture Supply Chain Web Browser EAI Applications & B2B E-Commerce Client Applications XML Corba EJB DCOM MQ Enterprise Components SQL DBMS, Client/Server & Legacy Applications HTTP Web Server Applications User interface and application logic go here Standard Middleware connects applications to components & components to components Business and data rules go here The data goes here

15 Collaboration is Key Collaboration is a key differentiation and key cost center (Healthcare Example) Customer Collaboration Claim processing Disputes Physician Collaboration Payer Collaboration Hospital Collaboration Broker Collaboration Government Collaboration Employee Collaboration Others... The system integrates multiple collaborations

16 The Connected Enterprise Content and Communication Police Dispatcher Role Digital Map Census Data Police Records House Drawings Aerial Photos

17 Multiple roles in a collaboration

18 Travel Expense Example Ruth (President) Adam (Chief Accountant) Joe (Paymaster) 4: authorizedexpensereport Eve Douglas (Software Manager) 1: travelpermissionrequest (Marketing manager) 2: travelpermission Elsie Joyce (Programmer) 3: expensereport (Sales clerk) Bill (Bookkeeper) John (Cashier) Peter (Technical author) 5: paymentrequest Kim (Methodologist) Bill (Dispatcher) Ann (Customer consultant)

19 Diagram Travel Expense Model Ruth (President) Adam (Chief Accountant) Joe (Paymaster) / Paymaster Eve (Software Manager) / Authorizer Elsie (Programmer) Douglas (Marketing manager) Joyce (Sales clerk) Bill (Bookkeeper) Peter (Technical author) / BookKeeper / Traveler Bill (Dispatcher) John (Cashier) Kim (Methodologist) Ann (Customer consultant) Objects --> ClassifierRoles

20 Collaboration Diagram Traveler Authorizer Book Keeper Paymaster

21 Roles to Systems Framework, Middleware & Container Role Collaboration Component in Role Interaction Path Interaction (With Information) Implementation Operating System Net Hardware

22 Standards for Global Internet Computing XML J2EE EDOC-ECA ECA.NET BPML XLANG WSDL SOAP XML-Schema

23 ECA as the normal form MDA Mappings Web Services (WSDL) ebxml (BPSS) EDOC-ECA J2EE (Java RMI) The standard way to model and tool for multiple technologies.net MOM (MQ-Series)

24 An ECA Methodology A simple methodology for creating collaborative bueiness processes

25 Basic Steps Identify roles and organize roles into collaborations Define collaboration documents Create basic business transactions Organize into protocols and events Use protocols to define ports on roles Drill-down into role detail Implement roles Configure implementations for deployment with technology specifics Deploy

26 Identifying roles and collaborations

27 Identify Documents

28 Distinguish protocols and events

29 Create Business Transactions

30 Organize into protocols

31 Add ports to complete community process

32 Drill-down

33 Add implementation As component compositions In a programming language By using an external service By Wrapping legacy systems

34 Add technology specifics for deployment

35 Sample Information Model «Key» CompanyKey +CompanyId : String «EntityData» Company +Name : String -CompanyId : String «Key» AccountKey +AccountNo : String «EntityData» Account +Name : String +Balance : Decimal = 0 +AccountNo : long +Cust 1 +Adr 1..* «EntityData» Addtress +Street : String +City : String +State : String +Zip : String «Key» PartKey +PartId : String -. * «Key» InvoiceKey +InvNum : Integer * -Act -Invoices «EntityData» Invoice +InvNum : Integer +Total : Decimal -Env 1 -Items * «EntityData» LineItem +Quantity : float -Price : Currency -Part -Items 1 * -. 1 «EntityData» Part +PartId : String +Description : String +QtyInStock : float(idl)

36 Adding Entities <<Entity>> CompanyManager Entities are added to manage entity data Entity Roles are managers that provides a view of the same identity in another context «Key» CompanyKey +CompanyId : String 1 -. Manage Manages «EntityData» Company +Name : String -CompanyId : String The Entities have ports for managing and accessing the entities Non-entities which are owned by (aggregate into) an entity are managed by the entity «Key» AccountKey +AccountNo : String «EntityData» Account +Name : String +Balance : Decimal = 0 +AccountNo : long 1 1 -Manages -. <<EntityRole>> AccountManager +Cust +Adr 1 1..* «EntityData» Addtress +Street : String +City : String +State : String +Zip : String Manage

37 Event Based Business Processes Business Rules Business Rules Business Process Event Notification Business Process Business Actions Business Events Business Events Business Actions Business Entity Business Entity

38 Event Tied to Information

39 Mappings to technology Import external specifications Mappings (to and from) Web Services Standards in-progress (WSEC) Distributed Objects (Corba, EJB, DCOM) DBMS Implementation languages (Java, C++, Cobol) Client interface Legacy interfaces Automation of >80% of an application

40 Complete process Middleware artifacts are generated Implemented roles are deployed Completing the process

41 Iterative Development Business Model Design Automation Build Build Build Build Build Release Build Deploy Infrastructure Development

42 High level tooling & infrastructure MUST BE SIMPLE! We must be able to create better applications faster We must separate the technology and business concerns, enable the user Tooling + Infrastructure Executable models are source code Tooling must be technology aware Infrastructure must support tooling, not manual techniques Model based component architectures

43 High level tooling & infrastructure MUST BE SIMPLE! We must be able to create better applications faster We must separate the technology and business concerns, enable the user Executable Models Tooling + Infrastructure Executable models are source code atooling must be technology aware Infrastructure must support tooling Model based component architectures

44 MDA Solution Factory Put together the Best practices Expertise Enterprise Architecture Infrastructure Automated tooling To produce and integrate robust business collaborations quickly & reliably

45 Net effect Using these open standards and automated techniques we can; 80% Reduction in complexity (Conservative) Achieve the strategic advantage of an open and flexible enterprise Produce and/or integrate these systems FASTER and CHEAPER than could be done with legacy techniques Provide a lasting software asset that will outlive the technology of the day

46 Contact Cory Casanave Data Access Technologies (305)