Enterprise Colaboraton Architecture
Upcoming SlideShare
Loading in...5
×
 

Enterprise Colaboraton Architecture

on

  • 492 views

 

Statistics

Views

Total Views
492
Views on SlideShare
491
Embed Views
1

Actions

Likes
0
Downloads
6
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Enterprise Colaboraton Architecture Enterprise Colaboraton Architecture Presentation Transcript

  • MDA & SOA in the Enterprise VCA MDA SOA/ESB Applying Model Driven Architecture (MDA) to Services Oriented Architecture (SOA) to enable the Executable Enterprise
  • Introductions Cory Casanave cory-c@enterprisecomponent.com Primary author of “CCA” in EDOC
  • Enterprise MDA MDA Viewpoint Model Of The Business The CIM Processes, Information, Business Model Requirements, Structure The Information System The PIM Application Components Application Component Model Serving Business Needs Technology The PSM Specifies How specific technologies Technology Model Will implement application Components Copyright © 2000-2005, Data Access Technologies, Inc.
  • Case Study U.S. General Services Administration (GSA) Customer: GSA OCIO Provider: LMI & Data Access Technologies Tooling: Component-X, Magicdraw UML, OsEra Sections reproduced with the permission of the GSA – George Thomas
  • “Sea Change” Sea of change Get-it-right (Initiative for better acquisition) Merger of FTS/FSS (Major Internal Organizations) Restructuring to provide a unified face to the customer OMB and Congressional mandates and changes of mission Integrating and modernizing financial management Reduction of redundant processes and systems Implications Massive organizational change Massive system changes Retraining staff High cost of change Risky and hard to achieve Change combined with current costs and inefficiencies of redundant stovepipe systems is not practical Copyright © 2000-2005, Data Access Technologies, Inc.
  • “Sea Change” Enablers & Cost Reduction Value Chain Analysis Analyzing and restructuring business processes based on realized customer value Model Driven Executable Architecture Executable enterprise architecture to realize business goals with systems and workflow automation Business Service Oriented Architecture / ESB An enterprise modernization strategy supporting business services, integration, reuse and common components across a system of systems integrated with SOA/ESB Combined effect of more automated processes Being able to realize your business goals – priceless! Copyright © 2000-2005, Data Access Technologies, Inc.
  • Tactical Goals Replacement of outdated systems Improve business processes Position to become a government wide service “Get to green” (OMB Requirements for architectural maturity) Copyright © 2000-2005, Data Access Technologies, Inc.
  • One-GSA Initiative Stovepipes PBS One-GSA Solutions Schedules Telecoms Buildings Supplies Auto I.T. FSS FTS Marketing Finance H.R. Un-Architected Solution Architected Solution Copyright © 2000-2005, Data Access Technologies, Inc.
  • Acquisition Model Solution Today Provider FSS Finance s Acquisition lie system pp Su Solution Customer IT Service Provider Customer s Needs Solutions FTS Finance Acquisition Sp system ace lea se Solution Provider PBS GSA GSA Finance Acquisition system Copyright © 2000-2005, Data Access Technologies, Inc.
  • To Be Acquisition Model Finance Customer Solution Contracting Solution Vendor Needs Provider Provider Solution Project Management GSA GSA Copyright © 2000-2005, Data Access Technologies, Inc.
  • System + Investment cost over 6 years Business Advantage Savings Not Included 160 140 120 100 Baseline 80 Option B 60 Option C 40 20 0 Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Note: Representative Numbers Est. NPV Break Even – About 6 Years Copyright © 2000-2005, Data Access Technologies, Inc.
  • Enterprise Service Bus to Enable Target State One-GSA Business Model Services driven from the business model Reusable Enterprise Services Project are independent & easily Management Service adapted and interconnected Services communicate with Contracting each other like humans do with Service email Information systems become a lattice of cooperating services CIO to Provide an “Enterprise Service Bus” using commercial standards s ice Industry best practice to avoid rv Se developing large monolithic Funds Management applications e Solution Service ris Provider rp Service te En Copyright © 2000-2005, Data Access Technologies, Inc.
  • Legacy “Wrapping” Wrapping allows existing programs and data to work with and work as enterprise components. Legacy systems are wrapped as a set of services. Purchasing Services Enterprise Services Advantage Adap ters Copyright © 2000-2005, Data Access Technologies, Inc.
  • Enterprise Systems Modernization Strategy Identify components that will offer greatest ROI Create target executable model ⌧OneGSA enterprise model is baseline Identify system of systems to consider for target Pick an alternative for each; • Evolve one or more current systems to support target processes, take on new capabilities and support One-GSA interfaces and/or • Harvest one or more systems to build a replacement and/or • Integrate functionality into shared services as common components and/or • Replace systems or parts of systems that are no longer suitable. Model driven SOA provides the flexibility to mix and match approaches as required. Commonality where possible – diversity where necessary. Evolving over time from integration to common components. End result – architected system of systems Copyright © 2000-2005, Data Access Technologies, Inc.
  • Systems to Role Based Service Components System System System System System System System System System System System System Copyright © 2000-2005, Data Access Technologies, Inc.
  • Transition by role, not system Still Theory System System System System Role Role Role Enterprise Role Service Role Bus Role Role Role Role System Role System System System System Copyright © 2000-2005, Data Access Technologies, Inc.
  • Consolidation into Service Components The Good Strategic reduction in operating cost – up to 50% Agile business processes Unification of the enterprise Only way to achieve enterprise transition? The Bad Investment in change – As high as 25% Legacy and packaged systems are not componentized The Ugly Change is expensive and can be disruptive Current boundaries and ownership change – may require centralized authority and budgeting Requires more “enterprise” agreement – very difficult to get consensus Copyright © 2000-2005, Data Access Technologies, Inc.
  • Strategic Migration Executable Enterprise Architecture Drives Target State Agile Systems of Systems using Interoperable Components Systems Composed of Interoperable Components Standards based integration of Monolithic Systems Ad Hoc Point to Point Integration of Monolithic Systems •Are you here? Separate and Non-Interoperable Applications Copyright © 2000-2005, Data Access Technologies, Inc.
  • MDA Enhanced Procurement Current Strategic Analyze Order & Requirements against Requirements or Create BA Service Component MDA Enterprise Reuse Library Fund/Contract Architecture Component Fund/Contract Component Generate Elaborate Fund/Contract Fund/Contract Adapt Contractor Reuse Components Construct Design Implement SC Integration Test Testing Solution Solution Copyright © 2000-2005, Data Access Technologies, Inc.
  • EA Governance Structure EA Governance Initiative OMB - 300 •Guides One GSA Target EA Specifies Acquisition •Refines •Satisfies Business Drivers Copyright © 2000-2005, Data Access Technologies, Inc.
  • “One GSA” EA Strategic Integration EA is a STRATEGIC ASSET •The “One GSA” EA aligns with: GSA Strategic Plan IT Capital IT Capital Planning and GSA Planning and Investment Control process Strategic Investment Plan Control Human Capital Planning process The “One GSA” EA Competitive Performance Management Repository Sourcing process Competitive Sourcing Governance Human Capital Performance The “One GSA” EA repository houses models Planning Management and artifacts that have been vetted and agreed to. Process Copyright © 2000-2005, Data Access Technologies, Inc.
  • Enterprise MDA An approach to realizing executable enterprise architecture with MDA and SOA
  • Enterprise MDA Architecture at the Enterprise Level Systems of systems Collaboration of organizations, systems & people Wide-scale collaborative processes ⌧roles and responsibilities Business Service Oriented Architecture Enterprise Components Componentizing functionality – not creating it Executable processes – smooth transition from model to simulation to solution Executable Enterprise Architecture Copyright © 2000-2005, Data Access Technologies, Inc.
  • 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 Profile for UML specification. Copyright © 2000-2005, Data Access Technologies, Inc.
  • Value Focused Target Architecture Business Drivers Business Drivers Business Models Business Models Workflow Workflow Current Processes Current Processes I.T. Systems Specs I.T. Systems Specs FAR FAR Collaborative Environment Collaborative Environment One GSA Target EA Current Environment Current Environment Documentation &Training Documentation &Training Projects Projects Initiatives Initiatives Time Line Time Line Trends Trends Trends Trends Critical Success Factors Critical Success Factors Copyright © 2000-2005, Data Access Technologies, Inc.
  • Simulated Model Driven Architecture Enterprise Architecture Refine/Iterate Model (CIM) Domain Live Process Simulation Architecture ECA Standard Simulator “Meta-Model” & UML Profile Copyright © 2000-2005, Data Access Technologies, Inc.
  • Automated Model Driven Architecture Enterprise Meta-Model Architecture UML Profile Model (CIM) (E.G. ECA) Domain Architecture Enterprise Infrastructure Tools Components Mapping Produce & C Integrate Minimize and structure (E.G. J2EE-WS) manual implementation Framework & Infrastructure Mapping is tuned (E.G. -J2EE-WS) to the infrastructure PSM Technical Architecture Copyright © 2000-2005, Data Access Technologies, Inc.
  • Automated Model Driven Architecture Enterprise Meta-Model Architecture Multiple and Changing UML Profile Model (CIM) Technology Support (E.G. ECA) Domain Architecture J2EE-WS Simulated Infrastructure Tools Enterprise Enterprise Infrastructure Mapping Components Components Mapping Produce & C Integrate C C (E.G. J2EE-WS) (E.G. .NET-WS) Framework & Simulation Infrastructure Infrastructure Mapping is tuned (E.G. -J2EE-WS) to the infrastructure PSM Techn Te Archite Arc Copyright © 2000-2005, Data Access Technologies, Inc.
  • Copyright © 2000-2005, Data Access Technologies, Inc.
  • The Connected Enterprise Content and Communication Digital Map Census Data Police Records House Drawings Police Aerial Dispatcher Photos Role Copyright © 2000-2005, Data Access Technologies, Inc.
  • Multiple roles in a collaboration Copyright © 2000-2005, Data Access Technologies, Inc.
  • Travel Expense Example Ruth (President) 4: authorizedExpenseReport Eve Adam Douglas (Chief Accountant) (Software Manager)travelPermissionRequest 1: (Marketing manager) Joe 2: travelPermission Elsie Joyce (Paymaster) 3: expenseReport clerk) (Programmer) (Sales Bill Peter Bill (Bookkeeper) (Technical author) (Dispatcher) 5: paymentRequest John Kim Ann (Cashier) (Methodologist) (Customer consultant) Copyright © 2000-2005, Data Access Technologies, Inc.
  • Diagram Travel Expense Model Ruth (President) Adam Eve Douglas (Chief Accountant) (Software Manager) (Marketing manager) / Authorizer Joe Elsie Joyce (Paymaster) / Paymaster (Programmer) (Sales clerk) Bill Peter Bill (Bookkeeper) (Technical author) (Dispatcher) / BookKeeper / Traveler John Kim Ann (Cashier) (Methodologist) (Customer consultant) Objects --> ClassifierRoles Copyright © 2000-2005, Data Access Technologies, Inc.
  • Collaboration Diagram Traveler Authorizer Book Keeper Paymast er Copyright © 2000-2005, Data Access Technologies, Inc.
  • The Marketplace Example Order Conformation Shipped Mechanics Are Us Process Acme Industries Buyer Complete Seller Status Ship Req Shipped Physical Delivered Delivery GetItThere Freight Shipper Copyright © 2000-2005, Data Access Technologies, Inc.
  • Where are the services? Order Web Service Conformation Web Service Shipped Mechanics Are Us Acme Industries Buyer Web Seller Service Status Web Ship Req Service Shipped Web Physical Service Delivered Delivery GetItThere Freight Shipper Copyright © 2000-2005, Data Access Technologies, Inc.
  • Inside the Seller Order Web Service Web Conformation Service Order Processing Web Service Shipped Web Service Shipping Web Service Ship Req Event Web Service Shipped Web Web Service Receivables Service Delivered Copyright © 2000-2005, Data Access Technologies, Inc.
  • Roles to Systems Component in Role Role Collaboration Interaction Path Framework, Interaction (With Information) Middleware & Container Implementation Operating System Net Hardware Copyright © 2000-2005, Data Access Technologies, Inc.
  • Model to Integrate From business needs to executing solutions
  • Enterprise MDA Process Computation Independent Model (CIM) Computation Independent Model (CIM) •Stakeholders •Business Drivers Plan and Design Develop and Deliver Provide After Care •As-Is Business Mission-Critical Value Chain Processes Business Context Value Chains Roles and Information Model Collaboration Platform Independent Model (PIM) Platform Independent Model (PIM) Business Case •As-Is Systems Service-Oriented Data Model EA Report Architecture Sequencing Plan Platform Specific Model (PSM) Platform Specific Model (PSM) •Open Source <wsdl:porttype> … eGov Reference </wsdl:porttype Architecture > Web Services Components Program Management and Risk Assessment/Mitigation Program Management and Risk Assessment/Mitigation Change Management, Configuration Management, and Communications Change Management, Configuration Management, and Communications Copyright © 2000-2005, Data Access Technologies, Inc.
  • Value Chains Develop Provide Plan and Design and Deliver After Care Mission-Critical Value Chain Development of Government-wide Policy Marketing Acquisition Support Services Value Chains Financial Management Services I.T. Services Human Capital Services Shared Services Value Chains Copyright © 2000-2005, Data Access Technologies, Inc.
  • Disciplines – Areas of Responsibility Financial Management Acquisition Solutions Property Management Policy Business Intelligence Human Resources Marketing Copyright © 2000-2005, Data Access Technologies, Inc.
  • Collaborative Process Model Enterprise Role. A major area of Enterprise Role. A major area of Work Role. A role responsible for a specific functional Work Role. A role responsible for a specific functional functional responsibility within the functional responsibility within the area within an enterprise role, such as might be assigned area within an enterprise role, such as might be assigned discipline of financial management. discipline of financial management. to a single worker or supported by an IT system. to a single worker or supported by an IT system. Activity. A specification of a business function in Activity. A specification of a business function in carried out the context of a work role. carried out the context of a work role. Subactivity. A specification a subfunction within Subactivity. A specification a subfunction within necessary to carry out an activity. necessary to carry out an activity. Protocol. A defined conversation between two Protocol. A defined conversation between two Information Flow. An individual Information Flow. An individual roles that may be extended over time. One role roles that may be extended over time. One role flow of information across a flow of information across a initiates and the other responds to the protocol, but initiates and the other responds to the protocol, but protocol or into or out of an activity. protocol or into or out of an activity. information may flow both ways across the protocol. information may flow both ways across the protocol. Copyright © 2000-2005, Data Access Technologies, Inc.
  • Receivables Management Example Related to Customer Orders Related to Receivables Copyright © 2000-2005, Data Access Technologies, Inc.
  • Information Model Example A term in the A term in the Entities may be Entities may be A relation between terms is A relation between terms is vocabulary vocabulary described as having described as having described by an described by an represents a class represents a class a unique identity. a unique identity. association between association between of things to be of things to be classes. classes. described. described. Attributes specify Attributes specify descriptive descriptive information having information having simple types. simple types. An un-shaded class is further detailed on a This means “zero or more” different diagram. A class may be A class may be specialized into specialized into sub-classifications. sub-classifications. This indicates a compositional This means “one or more” (as opposed to referential) association. This is a constraint that defines the sub-classification. Copyright © 2000-2005, Data Access Technologies, Inc.
  • Business (CIM) view - Collaborating Roles with Processes Role Role Role Conversation Protocol Role Copyright © 2000-2005, Data Access Technologies, Inc.
  • “Upper” PIM (system) View - Enterprise Component “Rotate” to look At other aspects of the component Role Role nt p one e Com rpris Ente People, organizations And/or enterprise components play roles in Business Processes. Copyright © 2000-2005, Data Access Technologies, Inc.
  • The “Enterprise Digital Assistant” Business People, Organizations Process And systems play roles Role Enterprise components help people Components frequently and organizations play roles help people play these roles by automating and monitoring The business process People, organizations and systems components work together to realize roles Role From the system perspective. Enterprise People and organizations Component become part of the implementation Components are the peoples Of the role Automated assistant Copyright © 2000-2005, Data Access Technologies, Inc.
  • People, Components & Organizations Collaborating Role Role Enterprise Enterprise Component Component Role Enterprise Component Copyright © 2000-2005, Data Access Technologies, Inc.
  • “Lower” PIM View - Enterprise Component Internals Browser UI Client Tier UI Framework UI Server Tier Enterprise Component Enterprise Business Logic Component Enterprise Enterprise Enterprise Component [Web] Service Legacy Systems [Web] Service Adaptation DBMS Data Managers Containers Copyright © 2000-2005, Data Access Technologies, Inc.
  • PIM: Service-Oriented Component Architecture Each Work Component in Each Work Component in the PIM implements a the PIM implements a Work Role from the CIM. Work Role from the CIM. Presentation Tier Application Tier Data Tier Service Managers Service Managers implement as system implement as system services the business services the business services defined in the services defined in the CIM. CIM. Copyright © 2000-2005, Data Access Technologies, Inc.
  • Information Model Business Transaction Note; Not expecting anyone To really read this Business Entity Copyright © 2000-2005, Data Access Technologies, Inc.
  • Messaging Note; Not expecting anyone Message To really read this Namesake Copyright © 2000-2005, Data Access Technologies, Inc.
  • Persistence Model Association indicates a reference to an entity persisted elsewhere. Copyright © 2000-2005, Data Access Technologies, Inc.
  • Enterprise Service Bus to Enable Target State Services driven from the business model One-GSA Business Model Reusable Enterprise Services are independent & easily Project adapted and interconnected Management Service Services communicate with each other like humans do with Contracting email Service Information systems become a lattice of cooperating components providing services SOA/Enterprise Service Bus using commercial standards s ice Industry best practice to avoid rv developing large monolithic Se applications e Funds ris Management rp Solution Service te Provider En Service Copyright © 2000-2005, Data Access Technologies, Inc.
  • Provisioning Model Copyright © 2000-2005, Data Access Technologies, Inc.
  • Example of XML provisioned from model Note; Don’t have to really read this either! <CustomerOrderEstablishment> <Inter-Work-RoleTransaction> <inter-work-roleTransactionID> … </inter-wor … </Inter-Work-RoleTransaction> <newOrder> <orderingCustomer> <customerID> … </customerID> </orderingCustomer> <controllingSalesInstrument> <salesInstrumentId> … </salesInstrumentI </controllingSalesInstrument> <customerOrderAmount> … </customerOrderAmoun … <lineItems> … </lineItems> </newOrder> </CustomerOrderEstablishment> Copyright © 2000-2005, Data Access Technologies, Inc.
  • Enterprise Service Bus * Complements of jBoss Copyright © 2000-2005, Data Access Technologies, Inc.
  • Many BPEL Processes support the CIM Copyright © 2000-2005, Data Access Technologies, Inc.
  • Copyright © 2000-2005, Data Access Technologies, Inc.
  • Common Environment for Intellectual Capital Meta Object Facility “Meta Models” Value Chain UML Workflow Business Collaboration Modeling Modeling Tools Modeling Modeling MDA Environment Intellectual MOF Models define the system Capital Apl 1 CICS EJB .NET Cust Sys Integration of infrastructure Copyright © 2000-2005, Data Access Technologies, Inc.
  • Net Effect of Enterprise MDA Clear path from needs to running technology Integrate business driven solutions with capital planning & the FEA Interoperable component architecture based on SOA Integrate legacy, COTS, GOTS and new development into a coherent solution Strategic evolution Reduced time, costs & risk Copyright © 2000-2005, Data Access Technologies, Inc.
  • Business Model (CIM) Terminology Role A specification of the responsibility to perform specific functions in the context of a business process. Work roles may be nested in organizing enterprise roles. Activity A specification of a business function in the context of a role. Activities may be decomposed into subactivities. Protocol A defined conversation between two roles that may be extended over time (i.e., responses of one party to the other may not be immediate). One role initiates and the other responds to the protocol, but information may flow both ways across the protocol. Flow An atomic flow of information across a protocol or into or out of an activity. Copyright © 2000-2005, Data Access Technologies, Inc.
  • Financial Management Discipline Enterprise Role Copyright © 2000-2005, Data Access Technologies, Inc.
  • Example: Receivables Accounting Work Roles Protocol initiated outside Receivables Accounting Protocol used internally within Protocol responded to outside Receivables Accounting Receivables Accounting Copyright © 2000-2005, Data Access Technologies, Inc.
  • Example: Billing Work Role Work Role Protocol Activity Flow Copyright © 2000-2005, Data Access Technologies, Inc.
  • Example: Establish Billing Activity Copyright © 2000-2005, Data Access Technologies, Inc.
  • Typical Simple Protocol Each accepted transaction effects a Each accepted transaction effects a change in the information and change in the information and behavior of the receiving role. behavior of the receiving role. The protocol is initiated by a The protocol is initiated by a requested transaction. requested transaction. Responses to the transaction Responses to the transaction may indicate success or failure. may indicate success or failure. Copyright © 2000-2005, Data Access Technologies, Inc.
  • Sample Billing Service Interfaces Provided Interfaces Required Interfaces Copyright © 2000-2005, Data Access Technologies, Inc.
  • One-GSA Methodology A simple methodology for creating collaborative business processes
  • Basic Steps Define business goals using Value Chain Analysis Refine to high-level activities 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 Use model as basis for acquisition Acquire/Implement roles Configure implementations for deployment with technology specifics Deploy Copyright © 2000-2005, Data Access Technologies, Inc.
  • Copyright © 2000-2005, Data Access Technologies, Inc.
  • Order to Payment Process Informal Diagram Order to Payment (Future State) - Involves only Purchases via Schedules Project Manager Determine Dev elop Conduct Develop Evaluate Aw ardDecision Customer: project need for Purchasing Receive Monitor and Inspect/Receive Acquisition Market vendor Accept Goods/ products and Request (SOW, Market Research Delivery document goods and Research/ responses Services Plan SLA, pricing, services I Survey A, J, L Schedule performance services I, R timeline) B, C, N, P B, C, N, P B, C,T Request review SOW of responses Acquisition Plan Input Receive Develop Coordinate Assign contract Conduct purchase Evaluation Conduct initial Evaluate Past Acquisition specialist researchusing Build RFQ Prepare Order Planning request data criteria/provide evaluation Performance e-Library/eBuy from PM A, F, I, L input A, J, L I A, J, L Contracting Goods/Services Delivery Request fund Delivery Schedule Receipt availability Combine Final fact Project Issue RFQ Verify IssueAw ard Check order Close out order finding w ith requirements A, I, Funds Notices status suppliers L A, I, K, B, C, S A, K, L L Obligation POs Responses Financial Officer via eBuy Customer: Perform3-w ay Process Funding validated Answ ers Receive invoice RFQ via eBuy Obligate funds Match Payment Record funding Questions B, E, O, S B, Q, S B, D, Q, S B, O Schedule Provide Supplier: Contract Provide Receive Officer Receive RFQ Answer delivery of copy of Close out Submit Receive schedule Ship Goods Delivery questions/ Distribute POs goods and receipt to Order A, J Response POs updates to FSS Receipt provide input services A, D, G, P A, D, G, N FSS A, D, G A, J A, D, G, P Payment or A, D, G, T K RFQ Funds Transfer POs Delivery Receipts Project Manager Develop Determine item RFQ price/ Acceptance response to response Supplier: Review RFQ Respond? Yes availability/ Customer Invoice RFQ A, D, J contract Delivery Receipt A, J A, D, J Answer Review POs questions/ PO No No interest, Customer w ill A, D, G, M provide input via eBuy review other quotes Delivery schedule updates Financial Supplier: Officer Receive Create Invoice Bill Customer Payment POs via eBuy D, G, M, P, Q D, G, M, P, Q G, O, Q Order Manager Receive Receive Receive Process Check order delivery Close out order FSS: Purchase delivery Notification of purchaseorders status schedule/ Orders receipts payment received A, E, L, S A, E, L, M, S A, E, L, M, S A, E, L, M, S updates Notification of order completion Financial Officer FSS: Realize revenue E, R, S A B C D E F G S Systems Customer eBuy (GUI interface) Customer financial Supplier Catalogs FSS-19 E-Library Supplier Financial Pegasys/Near Procurement systems Systems Systems Notification Information Schedule Aw a rd Purchase Goods and Delivery Payment Delivery s ow RFQ of Order information Notification Adv antageDB Order Services Funds Schedule Notification Receipt I J Completion (e-Library) K L M N O P Q R T H Copyright © 2000-2005, Data Access Technologies, Inc.
  • Order to Payment Process Diagram Order to Payment (Future State) - Involves only Purchases via Schedules Project Manager Determine Dev elop Conduct Develop Evaluate Customer: project need for Purchasing Acquisition Market vendor products and Request (SOW, Market Research Research/ responses Plan SLA, pricing, services I Survey A, J, L I, R timeline) Request review SOW of responses Acquisition Plan Input Receive Develop Coordinate Assign contract Conduct purchase Evaluation Conduct initial Evaluate Acquisition specialist researchusing Build RFQ Planning request data criteria/provide evaluation Perform e-Library/eBuy from PM A, F, I, L input I A, J, L Contracting Request fund availability Combine Final fact Project Issue RFQ finding w ith requirements A, I, suppliers L A, I, K, L Responses Financial Officer via eBuy Customer: Funding validated RFQ via eBuy Answer Record funding Questions B, O Supplier: Contract Officer Receive RFQ Answ er Submit questions/ A, J Response provide input A, J RFQ Manager Develop Determine item RFQ price/ response response to plier: Review RFQ Respond? Yes availability/ RFQ A D J contract A J A D J Copyright © 2000-2005, Data Access Technologies, Inc.
  • Finding the Roles and Inner Roles Roles in a Collaboration Order to Payment “Swim Lanes” Customer Procurement Supplier Broker Customer Project Manager Catalog Customer Contracting Project Manager Project Customer Financial Officer Manager Manager Supplier Financial Officer RFQ Manager Supplier Project Manager Contracting Contracting Supplier Contracting Officer Officer Order Officer FSS: Order Manager Manager FSS: Financial Officer Financial Financial Financial Officer Officer Officer Copyright © 2000-2005, Data Access Technologies, Inc.
  • High-level role identification Agency Industry GSA Partner Customer Customer Account Business Customer Contact Management Planning Strategy Offering Customer Customer Offering Line Finance Liaison Management Management Customer Solution Project Funds Program Provider Management Management Management Small Business Specialist Contracting Source Selection Authority Industry Team Customer Contracting Legal Officer Partner Contracting Technical Management Administrative Support Customer User Accounting Care Copyright © 2000-2005, Data Access Technologies, Inc.
  • Enterprise Context Simplified View - Level of detail is optional Copyright © 2000-2005, Data Access Technologies, Inc.
  • Co-Managed Services Collaboration Copyright © 2000-2005, Data Access Technologies, Inc.
  • Drilling Down into Customer Detail Customer Project Manager Contracting Officer Financial Officer Copyright © 2000-2005, Data Access Technologies, Inc.
  • Choreography of Process Copyright © 2000-2005, Data Access Technologies, Inc.
  • Protocols group Role Interactions into Conversations Project Manager Customer: Contracting Financial Officer Customer: Interaction Messages Supplier: Contract Officer Project Manager Supplier: Copyright © 2000-2005, Data Access Technologies, Inc.
  • Create Business Transactions Copyright © 2000-2005, Data Access Technologies, Inc.
  • Organize into protocols Copyright © 2000-2005, Data Access Technologies, Inc.
  • Inner Protocols Protocols represent conversations between roles Conversations frequently have sub-conversations, detail about a specific subject These sub-conversations are inner protocols Inner protocols can also be reused in other protocols or even as top-level protocols Protocols can “nest” to any level of detail Copyright © 2000-2005, Data Access Technologies, Inc.
  • Operations & Business Transactions The highest level of interaction detail is specified as the flow of documents - business information. This can be as events or “business transactions” Business transactions are a “request/reply” that usually results in creating or satisfying some business commitment - it may take place over an extended time We specify abstract document types to represent the information that flows. Empty – “Abstract” Copyright © 2000-2005, Data Access Technologies, Inc.
  • Modeling Collaboration Documents Fill in details of the documents Focus on business information - not technology Collaboration - Not an information model May be derived from existing sources Helps in creating technology mappings - E.G. Web Services Includes Composition Type Cardinality Copyright © 2000-2005, Data Access Technologies, Inc.
  • Attach Protocols to Roles as “Ports” Group transitions together into logical units Copyright © 2000-2005, Data Access Technologies, Inc.
  • Detailed Information Flows Inside the activities we can drill down to inner activities or detailed document flows - sending and receiving information This is used for the simulation, to validate the the model is correct and ultimately to test the implemented components. Copyright © 2000-2005, Data Access Technologies, Inc.
  • Drill-down Copyright © 2000-2005, Data Access Technologies, Inc.
  • Information Model Business Transaction Note; Not expecting anyone To really read this Business Entity Copyright © 2000-2005, Data Access Technologies, Inc.
  • Messaging Note; Not expecting anyone Message To really read this Namesake Copyright © 2000-2005, Data Access Technologies, Inc.
  • Persistence Model Association indicates a reference to an entity persisted elsewhere. Copyright © 2000-2005, Data Access Technologies, Inc.
  • Adding Data Managers <<Entity>> CompanyManager Entities are added to manage Manage entity data . Entity Roles are managers that Manages provides a view of the same «EntityData» «Key» 1 1 Company CompanyKey +Name : String identity in another context +CompanyId : String -CompanyId : String -. -. The Entities have ports for managing and accessing the «EntityData» «EntityData» Addtress «Key» 1 1 Account +Cust +Adr +Street : String entities AccountKey +Name : String +City : String +AccountNo : String +Balance : Decimal = 0 +State : String -. -. +AccountNo : long 1 1..* +Zip : String Non-entities which are owned by (aggregate into) an entity 1 -Manages 1 -. are managed by the entity <<EntityRole>> AccountManager Manage Copyright © 2000-2005, Data Access Technologies, Inc.
  • Simulating the Process Validation & Buy-in Business stakeholders SMEs Systems Implementers Copyright © 2000-2005, Data Access Technologies, Inc.
  • Initiating Activity Copyright © 2000-2005, Data Access Technologies, Inc.
  • Activity interacting externaly Copyright © 2000-2005, Data Access Technologies, Inc.
  • … With financial officer Copyright © 2000-2005, Data Access Technologies, Inc.
  • Who records the funding Copyright © 2000-2005, Data Access Technologies, Inc.
  • And the process returns to the PM Copyright © 2000-2005, Data Access Technologies, Inc.
  • Add implementation As component compositions In a programming language By using an external service By Wrapping legacy systems Copyright © 2000-2005, Data Access Technologies, Inc.
  • Enterprise Service Bus Application Server (jBoss) BPEL Engine Web Services Schema J2EE Copyright © 2000-2005, Data Access Technologies, Inc.
  • Add technology specifics for deployment Copyright © 2000-2005, Data Access Technologies, Inc.
  • Generated Web Service Copyright © 2000-2005, Data Access Technologies, Inc.
  • Dealing with Variation Multiple Implementations of a Role Customer Role (Logical) DOL Customer DOI Customer Internal Customer Component Component Component (Implementation) (Implementation) (Implementation) The “Inside” can change as long as the external “contract” is satisfied Copyright © 2000-2005, Data Access Technologies, Inc.
  • Architecture becomes part of Acquisition
  • ECA/CCA Implementation at GSA Data Access Technologies MDA experts, developers of ComponentX, One GSA EA support ⌧ enterprise-component.com Creators/contributors to OMG EDOC/ECA/CCA open standards ComponentX Implements ECA/CCA, used by GSA EAPMO to create collaborative role interaction models Supports ‘model to integrate’, combining design-time and run-time tools, with an extensible ‘component palette’ Supports FEA Line of Sight via aspect orientation Supports ‘just in time’ model driven generated documentation ComponentX is a J2EE application The models are executable – they’re java programs! Web enabled simulations integrate with existing IT systems Widely used EA tools (Mettis, Popkin, MS-Office) don’t compare! Copyright © 2000-2005, Data Access Technologies, Inc.
  • Federal Enterprise Architecture Support for the FEA as a view of the enterprise architecture
  • FEA (from reference) Copyright © 2000-2005, Data Access Technologies, Inc.
  • FEA/ComponentX Community Process Roles, processes, activities Reference model associations via aspect/properties Copyright © 2000-2005, Data Access Technologies, Inc.
  • B-P-A-A as ABM input Copyright © 2000-2005, Data Access Technologies, Inc.
  • Iterative Development Business Model Design Release Automation Build Build Build Build Build Build Deploy Infrastructure Development Copyright © 2000-2005, Data Access Technologies, Inc.
  • Generating Web Services & BPEL
  • PSM View - Mapping to [web] Services Service Service Service Service One-way Service Copyright © 2000-2005, Data Access Technologies, Inc.
  • Mapping of a WSDL Engine - <definitions xmlns="http://schemas.xmlsoap.org/wsd xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap xmlns:mime="http://schemas.xmlsoap.org/wsdl/mim xmlns:http="http://schemas.xmlsoap.org/wsdl/http/ ENC="http://schemas.xmlsoap.org/soap/encoding/ xmlns:xs2000="http://www.w3.org/1999/XMLSchem xmlns:xs2001="http://www.w3.org/2001/XMLSchem targetNamespace="urn:SellerServer" xmlns:tns="urn:S xmlns:CoreTypes="urn:CoreTypes" xmlns:Ordering="urn - <!-- definitions obtained from component /BuySell/Deployment/Seller Aspects WSDL WSDL-SOAP Copyright © 2000-2005, Data Access Technologies, Inc.
  • Mapping of an Enterprise Component - <service name="MySeller"> - <!-- implemented service role /BuySell/Deployment/SellerServer/MySeller --> <documentation><p> </p></documentation> - <port name="BuySellProtocol" binding="tns:BuySellProtocol"> - <!-- original service port was /BuySell/Deployment/SellerServer/MySeller/BuySellProtoc ol (extending Component &lt;/BuySell/SellerImplementation/MySeller/BuySellProtoc ol&gt; ) --> <soap:address Aspects location="http://localhost:8080/cx/app/BuyS WSDL ell/Deployment/SellerServer/MySeller/BuyS WSDL-SOAP ellProtocol" /> </port> Copyright © 2000-2005, Data Access Technologies, Inc.
  • Mapping of a protocol binding - <binding name="BuySellProtocol" type="tns:BuySellProtocol"> <soap:binding transport="http://schemas.xmlsoap.org/soap/h style="rpc" /> - <operation name="Order"> <soap:operation soapAction="urn:/BuySell/Community/BuySellPr col/Order" style="rpc" /> - <input name="Order"> <soap:body use="encoded" namespace="urn:SellerServ Aspects encodingStyle="http://schemas.xmlsoap.org/soa WSDL encoding/" /> WSDL-SOAP Copyright © 2000-2005, Data Access Technologies, Inc.
  • Mapping of a protocol - <portType name="BuySellProtocol"> - <!-- original cx operation = /BuySell/Community/BuySellProtocol/Order --> - <operation name="Order"> - <!-- original cx flow port = /BuySell/Community/BuySellProtocol/Order/Order --> <input name="Order" message="tns:Order" /> <output name="OrderConfirmation" message="tns:OrderConfirmation" /> <fault name="OrderDenied" message="tns:OrderDenied" /> Aspects </operation> WSDL </portType> WSDL-SOAP Copyright © 2000-2005, Data Access Technologies, Inc.
  • Mapping of message types - - <message name="Order"> <part name="Order" type="Ordering:Order" <message name="OrderConfirmation"> <part name="OrderConfirmation" type="Ordering:OrderConfirmation" /> </message> </message> - <message name="OrderDenied"> <part name="OrderDenied" Aspects type="Ordering:OrderDenied" /> WSDL </message> WSDL-SOAP Copyright © 2000-2005, Data Access Technologies, Inc.
  • Mapping of data types - <xs2001:complexType name="Order"> - - <xs2001:sequence> <xs2001:element minOccurs="1" maxOccurs="1" name="CompanyID" type="CoreTypes:CompanyID" /> <xs2001:element minOccurs="1" maxOccurs="1" name="OrderID" type="Ordering:OrderID" /> <xs2001:element minOccurs="0" maxOccurs="unbounded" name="Item" type="Ordering:Item" /> </xs2001:sequence> </xs2001:complexType> Copyright © 2000-2005, Data Access Technologies, Inc.
  • 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 Copyright © 2000-2005, Data Access Technologies, Inc.
  • 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 Copyright © 2000-2005, Data Access Technologies, Inc.
  • 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 Copyright © 2000-2005, Data Access Technologies, Inc.
  • Sample Applications Financial Management Enterprise Architecture, and One-GSA Executable Enterprise Architecture for the General Services Administration Enterprise Component Architecture for U.S. Army PEO-STRI Intelligence application for Raytheon & DARPA Collaboration Architecture for Kaiser Permanente Copyright © 2000-2005, Data Access Technologies, Inc.
  • Contact Cory Casanave Data Access Technologies www.enterprisecomponent.com cory-c@EnterpriseComponent.com Copyright © 2000-2005, Data Access Technologies, Inc.