March 24, 2007 Demonstrating Model Driven Enterprise SOA Integrating Government Lines of Business “The Power of the A in SOA” NCOIC SOA CoP - Demo Ed Harrington 30 March 2007 A Division of Data Access Technologies, Inc.

March 30, 2007 Enterprise SOA Enterprise SOA Integrates –Business and Operations Viewpoints – The Business SOA A lattice of business services cooperating for a mission – about the business, the mission and the operation – not about the technology. Includes roles & processes of stakeholders inside and outside an organization. –Technology Viewpoints – The Technical SOA A lattice of technology components, serving the business and the mission – based on the business SOA. Includes services inside and outside the technical environment. Enterprise SOA –Puts the business and mission first, defines technology based on business goals, drivers and processes. –Provides a solid system of systems technical architecture independent of technology –Produces technology specifications and implementations that collaborate based on the SOA architecture

March 30, 2007 The Service Oriented Enterprise –Parts of the enterprise must be independent & loosely coupled –While being able to interoperate with each other using services –Making the enterprise a lattice of cooperating services SOA Enterprise Components –Enterprise Components must be independent & loosely coupled –While being able to interoperate with each other using services –Making the information system a lattice of cooperating components Service

March 30, 2007 Enterprise SOA Challenges Small Architectures –Architect in terms of small, agile and general packages of services that show how people, organizations or systems work together for a particular purpose Large Architectures –Bring small architectures together for missions and systems in the large – system of systems –Enterprise solutions involve hundreds to thousands of cooperating services Separation of Concerns –Keep mission and business concerns as separate as possible, interacting with services –Separate business and technology concerns – don’t trap business knowledge in technology terms –Keep technologies agile and independent – interacting with services

March 24, 2007 A Sample Model Driven Enterprise Service Oriented Architecture for Integrating Government Lines of Business

March 30, 2007 Example Business Need Following the lead of the Federal Transition Framework, The (Fictional) NEF program has outsourced both HR/Payroll and finance to other agencies lines of business. Due to the time-critical nature of the program they need real-time updates of their program costs on a dashboard. The program and the lines of business all use different technology stacks and have different systems. NEF doesn’t want to get overly tied into these other agencies or their systems, as commercial providers may become less expensive in the future.

March 30, 2007 Example Approach Using available standards the Lines of Business and NEF have agreed on a services oriented architecture to solve their problem. They have agreed on each organizations roles and responsibilities and what services each will provide and use. The service oriented architecture is defined generically, so that different systems, technologies, projects or lines of business can easily be substituted – this keeps both NES and the lines of business agile.

March 30, 2007 Sample Federal LoB Community Business Intelligence (Reports/Dashboard) NEF Program (Manages Projects) Employee (Reports Time) Finance LoB (Calculates Costs) HR/Payroll - LoB (Allocates Time to Projects) Contractor (Produces Invoices) Agreed Roles and Responsibilities

March 30, 2007 Notional Sample Process Project is established and registered with finance Finance sends charge codes to HR & Contractor Employee submits time sheet for project HR submits time to finance Contractor submits invoice to finance Project gets cost info from finance Project updates dashboard Business intelligence asks for summary information about project

March 30, 2007 SOA Community Architecture SOA “Contracts” SOA “Contracts”

March 30, 2007 SOA Community There is nothing about systems or technologies here, it is a model of the Roles and Services of the business units and how they work together for this business need – the Business SOA We will then see how a Technology SOA Facilitates the business

March 30, 2007 Example Service Timesheet Entry SOA “Contract”

March 30, 2007 Business View to Technology View Example XML Instance description sponsor

March 30, 2007 Model to Web Service platform:/resource/SoaLobModel/model/SoaLobEngine.edoc_1_0_b#148ab5c_10e56defc61_-706e platform:/resource/SoaLobModel/model/SoaLobEngine.edoc_1_0_b#148ab5c_10e56defc61_-706e platform:/resource/SoaLobModel/model/SOA-Demo-Messages.edoc_1_0_b# a2_10e4ad8fcd6_-7f06 platform:/resource/SoaLobModel/model/SOA-Demo-Messages.edoc_1_0_b# a2_10e4ad8fcd6_-7f06 platform:/resource/SoaLobModel/model/SOA-Demo-Messages.edoc_1_0_b# a2_10e4ad8fcd6_-7e79 platform:/resource/SoaLobModel/model/SOA-Demo-Messages.edoc_1_0_b# a2_10e4ad8fcd6_-7e79 platform:/resource/SoaLobModel/model/SOA-Demo-Messages.edoc_1_0_b# a2_10e4ad8fcd6_-7e9f platform:/resource/SoaLobModel/model/SOA-Demo-Messages.edoc_1_0_b# a2_10e4ad8fcd6_-7e9f platform:/resource/SoaLobModel/model/SoaLob.edoc_1_0_b#2b7632_10e0a054e79_-7fe0p platform:/resource/SoaLobModel/model/SoaLob.edoc_1_0_b#683e68_10e56984f16_-5f03 platform:/resource/SoaLobModel/model/SoaLob.edoc_1_0_b#683e68_10e56984f16_-5f03 platform:/resource/SoaLobModel/model/SoaLob.edoc_1_0_b#2b7632_10e0a054e79_-7fdcp platform:/resource/SoaLobModel/model/SoaLob.edoc_1_0_b#683e68_10e56984f16_-5efb platform:/resource/SoaLobModel/model/SoaLob.edoc_1_0_b#683e68_10e56984f16_-5efb platform:/resource/SoaLobModel/model/SoaLob.edoc_1_0_b#19d36f1_10e0e93c502_-7fbep platform:/resource/SoaLobModel/model/SoaLob.edoc_1_0_b#683e68_10e56984f16_-5f00 platform:/resource/SoaLobModel/model/SoaLob.edoc_1_0_b#683e68_10e56984f16_-5f00

March 30, 2007 Implementation Business Intelligence (Reports/Dashboard) NEF Program (Manages Projects) Employee (Reports Time) Finance LoB (Calculates Costs) HR/Payroll - LoB (Allocates Time to Projects) Contractor (Produces Invoices) MetaMatrix Data Services Sun MicroSystems DynAccSys Web Service Web Service Web Service Web Service Web Service Web Form Data Access Executable Model Data Access Executable Model Dashboard Client

March 30, 2007 Solutions Architecture Information Technology Solutions Platform Technology Platform Architecture Business Architecture Contract (What) Design (How) Resources Supports Implements Manages & Executes Defines Business Mission & Services Business Processes, Organization, Roles & Responsibilities Funding, People Assets & Capabilities Organizations Information Technology Services, Components & Shared Data Capabilities: Shared data, messaging, service infrastructure, security Business Logic, Data & Presentation, Rules Service & Component Composition, Workflow Standards & Methodologies WSDL, Schema Pub/Sub Subjects XML, Etc. Implementation code Java Code, SQL, Adapters, BPEL, Etc. Computers Networks Infrastructure ESB, Metadata Messaging, Web Services, UDDI, Security Services Application Servers, Transactions, DBMS, Clusters, User Interface Java Language, O/S Applications, Runtime Executable Components Shared Services Capabilities: Data, Deployment, Execution, Monitoring, Presentation, Rules Engine Standards & Methodologies Architecting Separation Of Concerns

March 30, 2007 Implementation Net Hardware Operating System Framework, Middleware & Container How this Works Roles to Systems Interaction Path Component in Role Interaction (With Information) Role Collaboration

March 30, 2007 Business view -Collaborating Roles with Services Project Payroll Role Finance LoB Role Business Intelligence Role SOA Contract

March 30, 2007 Role “Enterprise Digital Assistant” Finance LoB Component Finance LoB Role People, Organizations And systems play roles Components frequently help people play these roles Enterprise components help people and organizations play roles by automating and monitoring The business process From the system perspective. People and organizations become part of the implementation Of the role Components are the peoples Automated assistant Business Process People, organizations and systems components work together to realize roles Finance

March 30, 2007 Role People, Components & Organizations Collaborating Project Component Finance Component Role Payroll Component Enterprise [Web] Service Enterprise [Web] Service Business Roles Business Roles

March 30, 2007 Project Component Payroll Component Enterprise Component Internals Containers DBMS Data Managers Adaptation Legacy Systems Finance LoB Component UI Framework Browser Business Logic UI Server Tier UI Client Tier Enterprise [Web] Service Enterprise [Web] Service

March 30, 2007 Domain Architecture Simulated Model Driven Architecture Simulator Enterprise SOA ArchitectureModel(CIM) Live Process Simulation Refine/Iterate ECA Standard “Meta-Model” & UML Profile

March 30, 2007 Meta-Model UML Profile (E.G. ECA) Domain Architecture Automated Model Driven Architecture Framework & Infrastructure (E.G. -J2EE-WS) PSM InfrastructureMapping (E.G. J2EE-WS) Mapping is tuned to the infrastructure Tools Produce & Integrate EnterpriseComponents EnterpriseArchitecture Model (CIM) Minimize and structure manual implementation C Technical Architecture

March 30, 2007 Meta-Model UML Profile (E.G. ECA) Domain Architecture Automated Model Driven Architecture Framework & Infrastructure (E.G. -J2EE-WS) PSM InfrastructureMapping (E.G. J2EE-WS) Mapping is tuned to the infrastructure Tools Produce & Integrate J2EE-WSEnterpriseComponents EnterpriseArchitecture Model (CIM) C Technical Architecture SimulationInfrastructure Technical Architecture InfrastructureMapping (E.G..NET-WS) SimulatedEnterpriseComponents C Multiple and Changing Technology Support C

March 30, 2007 Business Advantages Business Focus – Architecture is fundamentally an enabler of the enterprise business agenda and will be based on, driven by, and traceable to that business agenda. Customer Focus – Architecture will represent and facilitate the core value propositions of the enterprise to its customers. Business Agility – Architecture will enable the enterprise to react quickly to business challenges and opportunities with IT systems that adapt quickly to new business requirements and processes. Strategic Transformation – Architecture will facilitate the transformation of the enterprise into a modern and competitive player.. Reduced Redundancy and Cost – Architecture will enable and encourage the reduction of unnecessarily redundant systems, information, services and processes and the reduction of IT procurement and maintenance costs. FEA and FTF – Architecture will enable and support the President’s management agenda as reflected in the Federal Enterprise Architecture (FEA) and Federal Transition Framework (FTF). Collaboration & Interoperability – Architecture will enable the ability for business units, the supply chain, processes and systems to work together seamlessly to achieve enterprise goals

March 30, 2007 Model Driven Solutions Business Enablement –Business Transformation –Enterprise Agility –Enterprise Integration Architecture –Enterprise Architecture –Business Architecture –Services Oriented Architecture –Model Driven Architecture –Business Process Architecture Open Source –www,ModelDriven.org – Open community for MDA, SOA and the Semantic web Opportunity to solution – architected, fast, strategic