1. March 24, 2007 SOA CoP Demo Model Driven Enterprise SOA GSA Financial Management Enterprise Architecture Cory Casanave cory-c (at) modeldriven.com Oct 1 st, 2007 Formerly Data Access Technologies

2. March 24, 2007 FMEA Background OneGSA is an overall enterprise architecture for the GSA using model driven SOA methodology The Financial Management Enterprise Architecture (FMEA) project was sponsored by the US General Services Administration (GSA) Offices of the Chief Information Officer and Chief Financial Officer. FMEA is a more detailed enterprise architecture for their financial line of business. Asset Accounting is a full SOA implementation of one of the components defined in the PIM portion of FMEA – asset accounting, with adapters to several COTS & legacy systems. This is associated with the open source community for model driven development: modeldriven.org – where all generic capabilities will be made open source

3. March 24, 2007 Business Concerns Goals Mission Policy Customers Collaborators Costs Agility Technology Specification Web Services WSDL, BPEL, XML Schema Technology Specification Web Services WSDL, BPEL, XML Schema Logical Systems of Systems Model Technology Services (SOA-SoS), Components Interfaces, Messages & Data Logical Systems of Systems Model Technology Services (SOA-SoS), Components Interfaces, Messages & Data Business Focus Using Model Driven Services Architecture SOA Business Model Business Services (SOA-Enterprise) Roles, Collaborations & Interactions Process & Information SOA Business Model Business Services (SOA-Enterprise) Roles, Collaborations & Interactions Process & Information Refinement & Automation Line-Of-Sight Computation Independent Model Platform Independent Model Platform Specific Model MDA Terms

4. March 24, 2007 GSA Context & Business Services

5. March 24, 2007 A Service Oriented Architecture Asset Management Asset Accounting General Ledger Receivables Accounting Asset Data Asset Transfer Asset DisposalGL Updates Asset Disposal Revenue Asset Service Collaboration The Asset service collaboration shows the service interactions supporting the management of asset records and the posting of general ledger as a result of asset transactions. Service: The offer of a capability to another party based on a set of terms and conditions This is the service, it depends on a service contract

6. March 24, 2007 Bottoms out in a supporting technology platform JEE Application Server EJB Container JEE Application Server JBI Runtime JMS Broker ESB Centralized Management Server Queue Topic JBI Runtime JMS BC JMS BC Normalized Message Router File BC Files JEE SE JMS JBI Runtime NMR JMS BC HTTP BC Feeder Systems JMS SOAP/HTTP XSLT SE Transform Script FTP Transaction Manager RMI BPEL SE Adapter Process JMX SOAP/JMS JMS Data Manager JAX-WS JMS BC Components to be prototyped JMS BC Other components Server-Side Presentation

7. March 24, 2007 Core Service Technical Specification Collaboration View Structural View

8. March 24, 2007 Behavior for service Specifies the contract of interaction – not what a party does Behavior View

9. March 24, 2007 Information model captures domain concepts, essentially an ontology of the domain

10. March 24, 2007 Information model captures domain concepts, essentially an ontology of the domain

11. March 24, 2007 Messages exchange this content in services Usage Information View

12. March 24, 2007 Technology Components support services Role in a service becomes type of port Component View

13. March 24, 2007 Service components use services Core business logic goes at this level, and is then quite simple

14. March 24, 2007 Core Financial System Specification Service Interfaces Enterprise Components Work Components Service Manager Components Behavioral Specifications Data Model Message Specifications Data Manager Components Persistent Data Specifications Core Financial System Specification Service Interfaces Enterprise Components Work Components Service Manager Components Behavioral Specifications Data Model Message Specifications Data Manager Components Persistent Data Specifications Platform Specific Model Core Financial System Implementation Web Services Enterprise Information Systems System Components System Functions Data Definition XML Schemas Data Bases Data Base Schemas Core Financial System Implementation Web Services Enterprise Information Systems System Components System Functions Data Definition XML Schemas Data Bases Data Base Schemas Platform Specific Model (PSM)Platform Independent Model (PIM)

15. March 24, 2007 Supports Standard Development IDE

16. March 24, 2007 Producing Web Application

17. March 24, 2007 Example Web Services Definition <wsdl:input message="tns:CustomerOrderEstablishmentPanopticInheritanceCluster“ name="CustomerOrderEstablishment"> <wsdl:input message="tns:CustomerOrderEstablishedPanopticInheritanceCluster“ name="CustomerOrderEstablished"> <wsdl:input message="tns:CustomerOrderEstablishmentRejectedInheritance“ name="CustomerOrderEstablishmentRejected"> The primary port type has operations corresponding to the request flows in the protocol. The callback port type has operations corresponding to the response flows in the protocol.

18. March 24, 2007 Example Transaction Message XML Document … … … … … … … … … … … … … …

19. March 24, 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

20. March 24, 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 www.ModelDriven.com