FMEA: A services oriented executable enterprise architecture for financial management  September Expedition Workshop  Cory...
One-GSA Initiative LOB H.R. Finance Marketing PBS FTS FSS Schedules Buildings I.T. Telecoms Stovepipes One GSA Un-Architec...
Approach <ul><li>Business focus, facilitated with technology </li></ul><ul><li>Services Oriented Architecture (SOA) at bot...
FMEA in Context US Federal Government General Services Administration GSA  Office of the  Chief Financial Officer One GSA ...
Business Focus Using Model Driven Architecture Business Concerns Goals Policy Customers Costs Agility Technology Specifica...
Incorporating Legacy Analysis
Value derived from the architecture Component Acquisition  Specification Technology Interfaces  Test & Simulation OMB 300 ...
Focus on the Business Model Business Concerns Technology Specification Web Services WSDL, BPEL, XML Schema Logical System ...
How does XBRL fit in? XBRL Concepts XBRL Interfaces System Component One GSA/FMEA  Business Model Business Services (b-SOA...
The enterprise as services <ul><li>Think about the enterprise as a set of interacting roles providing and using services t...
SOA Using Roles and Collaborations <ul><li>Role:   A specification of the responsibility to perform specific functions in ...
Collaborative Process Model Enterprise Role.  A major area of functional responsibility within the discipline of financial...
“One GSA” Disciplines (Simplified View) Focus of FMEA Service Interfaces Financial Management Policy Acquisition Human Res...
Financial Management Discipline Role Protocol representing delegated responsibility for interaction with an entity externa...
Service Delivery Protocol The protocols between discipline roles are composites that “roll up” the set of services provide...
Financial Management Enterprise Roles (Simplified) Financial Reporting collects financial data from all other enterprise r...
Example Enterprise Role Business service provided by this enterprise role. Business service this enterprise role requires ...
Example Business Service Protocol The protocols between enterprise roles model business services provided by one role to o...
Activities and Choreographies <ul><li>Activity:  A specification of a business function in the context of a role. </li></u...
Example Activities Activity Incoming business transaction Outgoing business transaction Work Role
Example Subactivity Requirements
Information Model This means “zero or more” This means “one or more” This indicates a compositional (as opposed to referen...
Information Model: What Is It For? Business transaction Business transaction The  information model  details the vocabular...
Producing the logical model Business Concerns Technology Specification Web Services WSDL, BPEL, XML Schema Logical System ...
Platform Independent Model <ul><li>Financial Management Discipline </li></ul><ul><ul><li>Protocols </li></ul></ul><ul><ul>...
Three-Tier Component Architecture Presentation Tier Application Tier Data Tier Presentation Manager components provide use...
Example Work Role (from CIM) Related to Customer Orders Related to Receivables
Corresponding Work Component Presentation Tier Application Tier Data Tier Explicit component for scheduling triggers Expli...
Producing Web Services Business Concerns Technology Specification Web Services WSDL, BPEL, XML Schema Logical System Model...
Platform Specific Model <ul><li>Core Financial System Specification </li></ul><ul><ul><li>Service Interfaces </li></ul></u...
MDA Generated Web Services Definition <ul><li><wsdl:portType name=&quot; CustomerOrderEstablishment.CustomerOrderEstablish...
Example Transaction Message XML Document <ul><li><CustomerOrderEstablishment> </li></ul><ul><li><customerOrderEstablishmen...
Summary <ul><li>FMEA is a general architecture of the federal financial services domain, done by GSA. </li></ul><ul><li>It...
SOA Demo <ul><li>The SOA Community of Practice is sponsoring a demonstration of the business value and technical feasibili...
Upcoming SlideShare
Loading in...5
×

Copyright © 2006 Data Access Technologies, Inc.

147

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
147
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Copyright © 2006 Data Access Technologies, Inc.

  1. 1. FMEA: A services oriented executable enterprise architecture for financial management September Expedition Workshop Cory Casanave cory-c (at) enterprisecomponent.com
  2. 2. One-GSA Initiative LOB H.R. Finance Marketing PBS FTS FSS Schedules Buildings I.T. Telecoms Stovepipes One GSA Un-Architected Solution Architected Solution Auto Supplies One-GSA Solutions FAS
  3. 3. Approach <ul><li>Business focus, facilitated with technology </li></ul><ul><li>Services Oriented Architecture (SOA) at both the business and technical level </li></ul><ul><li>Described with Collaborative Role Interactions, Processes and Information models based on OMG standards </li></ul><ul><li>Model Driven Architecture (MDA) to connect the business and technical architectures </li></ul><ul><li>Web services as the technical interface to the line of business </li></ul><ul><li>Tools Used </li></ul><ul><ul><li>Component-X for Collaboration/Role modeling of the SOA </li></ul></ul><ul><ul><li>Magic draw UML for the information, data and message model </li></ul></ul><ul><ul><li>OsEra (open source eGov project) to generate web services </li></ul></ul>
  4. 4. FMEA in Context US Federal Government General Services Administration GSA Office of the Chief Financial Officer One GSA EA Federal EA FMEA Financial Management Line of Business
  5. 5. Business Focus Using Model Driven Architecture Business Concerns Goals Policy Customers Costs Agility Technology Specification Web Services WSDL, BPEL, XML Schema Logical System Model Technology Services (t-SOA), Components Interfaces, Messages & Data One GSA/FMEA Business Model Business Services (b-SOA) Roles, Collaborations & Interactions Process & Information Refinement & Automation Line-Of-Sight Computation Independent Model Platform Independent Model Platform Specific Model MDA Terms
  6. 6. Incorporating Legacy Analysis
  7. 7. Value derived from the architecture Component Acquisition Specification Technology Interfaces Test & Simulation OMB 300 FEA/FTF BRM SRM DRM* Business Driven Technology Facilitating Business Processes Adapters Components Data XBRL
  8. 8. Focus on the Business Model Business Concerns Technology Specification Web Services WSDL, BPEL, XML Schema Logical System Model Technology Services (t-SOA), Components Interfaces, Messages & Data One GSA/FMEA Business Model Business Services (b-SOA) Roles, Collaborations & Interactions Process & Information
  9. 9. How does XBRL fit in? XBRL Concepts XBRL Interfaces System Component One GSA/FMEA Business Model Business Services (b-SOA) Roles, Collaborations & Interactions Process & Information Generated FMEA includes transaction and enactment as well as reporting. XBRL was one of many inputs. FMEA must be able to Support multiple interface Standards and technologies. XBRL is one of these.
  10. 10. The enterprise as services <ul><li>Think about the enterprise as a set of interacting roles providing and using services to enable agility, cost savings and an effective transition framework </li></ul><ul><li>Externally </li></ul><ul><ul><li>The enterprise is part of the global supply chain, providing services to customers and using the services of suppliers </li></ul></ul><ul><li>Internally </li></ul><ul><ul><li>Consider parts of the enterprise as providing services to other parts of the enterprise, and in term using the service of others </li></ul></ul><ul><ul><li>Like everything was outsourced as a service, it just happens to be done inside the organization. </li></ul></ul><ul><li>Business is modeled in terms of interacting roles – providing and using services – the essential concepts of business SOA </li></ul>
  11. 11. SOA Using Roles and Collaborations <ul><li>Role: A specification of the responsibility to perform specific functions in the context of a business process. </li></ul><ul><li>Collaboration: A closed set of roles interacting to carry out a business process to achieve some joint purpose. </li></ul><ul><li>Service: At the business level – a capability provided by one party to another. </li></ul><ul><li>Protocol: A defined conversation between two roles providing and consuming services. </li></ul>Commerce (Collaboration) Buyer (Role) Seller (Role) Purchase (Protocol)
  12. 12. Collaborative Process Model Enterprise Role. A major area of functional responsibility within the discipline of financial management. Work Role. A role responsible for a specific functional area within an enterprise role, such as might be assigned to a single worker or supported by an IT system. Activity. A specification of a business function in carried out the context of a work role. Protocol. A defined conversation between two roles that may be extended over time. One role initiates and the other responds to the protocol, but information may flow both ways across the protocol. Information Flow. An individual flow of information across a protocol or into or out of an activity. Subactivity. A specification a subfunction within necessary to carry out an activity.
  13. 13. “One GSA” Disciplines (Simplified View) Focus of FMEA Service Interfaces Financial Management Policy Acquisition Human Resources Marketing Property Management Solutions Business Intelligence
  14. 14. Financial Management Discipline Role Protocol representing delegated responsibility for interaction with an entity external to GSA. Protocol representing interaction with another discipline within GSA.
  15. 15. Service Delivery Protocol The protocols between discipline roles are composites that “roll up” the set of services provided by one discipline to another. The sub-protocols within a roll-up protocol model specific business services provided by a discipline.
  16. 16. Financial Management Enterprise Roles (Simplified) Financial Reporting collects financial data from all other enterprise roles. Receivables Accounting Funds Management Payables Accounting Asset Accounting Financial Planning General Ledger Cost Allocation Cash Management Financial Reporting
  17. 17. Example Enterprise Role Business service provided by this enterprise role. Business service this enterprise role requires from another role. Time triggers for scheduled events.
  18. 18. Example Business Service Protocol The protocols between enterprise roles model business services provided by one role to others. The protocol is initiated by a business transaction request. Responses to the request may indicate success or failure. Note that, while one role initiates and the other responds to the protocol, information may flow both ways across the protocol. Each accepted transaction effects a change in the information and behavior of the receiving role.
  19. 19. Activities and Choreographies <ul><li>Activity: A specification of a business function in the context of a role. </li></ul><ul><li>Choreography : A specification of the sequencing of external interactions required in order to carry out given business responsibilities. </li></ul><ul><ul><li>A work role is choreographed in terms of the activities required to perform the business services provided by the work role. </li></ul></ul><ul><ul><li>A complicated activity may be choreographed in terms of subactivities. </li></ul></ul><ul><ul><li>A subactivity (or simple activity without subactivity decomposition) is choreographed directly in terms of the event-triggered sequencing of its acceptance of inputs and sending of outputs. </li></ul></ul>
  20. 20. Example Activities Activity Incoming business transaction Outgoing business transaction Work Role
  21. 21. Example Subactivity Requirements
  22. 22. Information Model This means “zero or more” This means “one or more” This indicates a compositional (as opposed to referential) association. This is a constraint that defines the sub-classification. An un-shaded class is further detailed on a different diagram. A term in the vocabulary represents a class of things to be described. Attributes specify descriptive information having simple types. Entities may be described as having a unique identity . A relation between terms is described by an association between classes. A class may be specialized into sub-classifications.
  23. 23. Information Model: What Is It For? Business transaction Business transaction The information model details the vocabulary of the business entities and transactions used in the process model. The process model describes how business activities are (or are to be) carried out. State changes due to the activities Work role Activities Implicit memory of business information
  24. 24. Producing the logical model Business Concerns Technology Specification Web Services WSDL, BPEL, XML Schema Logical System Model Technology Services (t-SOA), Components Interfaces, Messages & Data One GSA/FMEA Business Model Business Services (b-SOA) Roles, Collaborations & Interactions Process & Information
  25. 25. Platform Independent Model <ul><li>Financial Management Discipline </li></ul><ul><ul><li>Protocols </li></ul></ul><ul><ul><li>Enterprise Roles </li></ul></ul><ul><ul><ul><li>Work Roles </li></ul></ul></ul><ul><ul><ul><ul><li>Activities </li></ul></ul></ul></ul><ul><ul><li>Information Model </li></ul></ul><ul><ul><ul><li>Classes </li></ul></ul></ul><ul><li>Core Financial System Specification </li></ul><ul><ul><li>Service Interfaces </li></ul></ul><ul><ul><li>Enterprise Components </li></ul></ul><ul><ul><ul><li>Work Components </li></ul></ul></ul><ul><ul><ul><ul><li>Service Manager Components </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Behavioral Specifications </li></ul></ul></ul></ul></ul><ul><ul><li>Data Model </li></ul></ul><ul><ul><ul><li>Message Specifications </li></ul></ul></ul><ul><ul><ul><li>Data Manager Components </li></ul></ul></ul><ul><ul><ul><ul><li>Persistent Data Specifications </li></ul></ul></ul></ul>Computation Independent Model Platform Independent Model
  26. 26. Three-Tier Component Architecture Presentation Tier Application Tier Data Tier Presentation Manager components provide user access to application services. Service Manager components provide transactional implementation of application services. Data Manager components persist data between application transactions.
  27. 27. Example Work Role (from CIM) Related to Customer Orders Related to Receivables
  28. 28. Corresponding Work Component Presentation Tier Application Tier Data Tier Explicit component for scheduling triggers Explicit cross-transactional coupling via the data tier Role for human participation in the process
  29. 29. Producing Web Services Business Concerns Technology Specification Web Services WSDL, BPEL, XML Schema Logical System Model Technology Services (t-SOA), Components Interfaces, Messages & Data One GSA/FMEA Business Model Business Services (b-SOA) Roles, Collaborations & Interactions Process & Information
  30. 30. Platform Specific Model <ul><li>Core Financial System Specification </li></ul><ul><ul><li>Service Interfaces </li></ul></ul><ul><ul><li>Enterprise Components </li></ul></ul><ul><ul><ul><li>Work Components </li></ul></ul></ul><ul><ul><ul><ul><li>Service Manager Components </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Behavioral Specifications </li></ul></ul></ul></ul></ul><ul><ul><li>Data Model </li></ul></ul><ul><ul><ul><li>Message Specifications </li></ul></ul></ul><ul><ul><ul><li>Data Manager Components </li></ul></ul></ul><ul><ul><ul><ul><li>Persistent Data Specifications </li></ul></ul></ul></ul><ul><li>Core Financial System Implementation </li></ul><ul><ul><li>Web Services </li></ul></ul><ul><ul><li>Enterprise Information Systems </li></ul></ul><ul><ul><ul><li>System Components </li></ul></ul></ul><ul><ul><ul><ul><li>System Functions </li></ul></ul></ul></ul><ul><ul><li>Data Definition </li></ul></ul><ul><ul><ul><li>XML Schemas </li></ul></ul></ul><ul><ul><ul><li>Data Bases </li></ul></ul></ul><ul><ul><ul><li>Data Base Schemas </li></ul></ul></ul>Platform Specific Model (PSM) Platform Independent Model (PIM)
  31. 31. MDA Generated Web Services Definition <ul><li><wsdl:portType name=&quot; CustomerOrderEstablishment.CustomerOrderEstablishment &quot;> </li></ul><ul><li><wsdl:operation name=&quot; CustomerOrderEstablishment &quot;> </li></ul><ul><li><wsdl:input message=&quot; tns:CustomerOrderEstablishmentPanopticInheritanceCluster “ </li></ul><ul><li>name=&quot; CustomerOrderEstablishment &quot;> </li></ul><ul><li></wsdl:input> </li></ul><ul><li></wsdl:operation> </li></ul><ul><li></wsdl:portType> </li></ul><ul><li><wsdl:portType name=&quot; CustomerOrderEstablishment.CustomerOrderEstablishmentCallback &quot;> </li></ul><ul><li><wsdl:operation name=&quot; CustomerOrderEstablished &quot;> </li></ul><ul><li><wsdl:input message=&quot; tns:CustomerOrderEstablishedPanopticInheritanceCluster “ </li></ul><ul><li>name=&quot; CustomerOrderEstablished &quot;> </li></ul><ul><li></wsdl:input> </li></ul><ul><li></wsdl:operation> </li></ul><ul><li><wsdl:operation name=&quot; CustomerOrderEstablishmentRejected &quot;> </li></ul><ul><li><wsdl:input message=&quot; tns:CustomerOrderEstablishmentRejectedInheritance “ </li></ul><ul><li>name=&quot; CustomerOrderEstablishmentRejected &quot;> </li></ul><ul><li></wsdl:input> </li></ul><ul><li></wsdl:operation> </li></ul><ul><li></wsdl:portType> </li></ul>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.
  32. 32. Example Transaction Message XML Document <ul><li><CustomerOrderEstablishment> </li></ul><ul><li><customerOrderEstablishment> </li></ul><ul><li><newOrder> </li></ul><ul><li><customerOrder> </li></ul><ul><li><customerOrderID> … </customerOrderID> </li></ul><ul><li><customerOrderAmount> … </customerOrderAmount> </li></ul><ul><li><orderingCustomer> </li></ul><ul><li><customer> </li></ul><ul><li><customerID> … </customerID> </li></ul><ul><li></customer> </li></ul><ul><li><party> </li></ul><ul><li><name> … </name> </li></ul><ul><li></party> </li></ul><ul><li></orderingCustomer> </li></ul><ul><li><controllingSalesInstrument> </li></ul><ul><li><salesInstrumentID> … </salesInstrumentID> </li></ul><ul><li></controllingSalesInstrument> </li></ul><ul><li>… </li></ul><ul><li><lineItems> </li></ul><ul><li>… </li></ul><ul><li></lineItems> </li></ul><ul><li></customerOrder> </li></ul><ul><li></newOrder> </li></ul><ul><li></customerOrderEstablishment> </li></ul><ul><li><businessDomainTransaction> </li></ul><ul><li><transactionID> … </transactionID> </li></ul><ul><li></businessDomainTransaction> </li></ul><ul><li></CustomerOrderEstablishment> </li></ul>
  33. 33. Summary <ul><li>FMEA is a general architecture of the federal financial services domain, done by GSA. </li></ul><ul><li>It supports both internal GSA needs as well as the “line of business”. </li></ul><ul><li>It uses MODA and SOA to provide a business centric architecture, drilling down to technology models. </li></ul><ul><li>Artifacts can be generated for model based acquisition, the FEA, testing, service interfaces, data management, workflow and components. </li></ul><ul><li>FMEA is entering the next phase of acquisition and implementation. </li></ul>
  34. 34. SOA Demo <ul><li>The SOA Community of Practice is sponsoring a demonstration of the business value and technical feasibility of SOA. This demonstration will encompass the full life-cycle of a multi-party SOA solution using multiple participants and multiple technologies collaborating via SOA standards in an architected community. </li></ul><ul><li>Goals; </li></ul><ul><ul><li>To provide a concrete example of how the SOA approach provides business value to a community </li></ul></ul><ul><ul><li>To provide confidence that the approach and technologies are real – secure, reliable, performing and practical. </li></ul></ul><ul><ul><li>To validate that independently developed applications can interoperate using SOA standards </li></ul></ul><ul><li>The subject scenario for this demo is the interaction between the HR and Financial lines of business </li></ul><ul><li>There are multiple government and industry participants </li></ul><ul><li>This will be shown at the upcoming SOA-COP conference in October. </li></ul><ul><li>If you are interested in participating, please contact me. </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×