The Use of Service Oriented Architecture In Tax and Revenue

Transcription

1 The Use of Service Oriented Architecture In Tax and Revenue Presented by: Bruce Baur & Adam Schaffer Revenue Solutions, Inc.

2 Introduction Adam Schaffer Director, Revenue Administration Practice Line More than 15 years experience working at Tax and Revenue Agencies Bruce Baur Director, Chief Information Officer More than 20 years experience working at Tax and Revenue Agencies 2

3 Revenue Solutions, Inc. Mission Statement Assist revenue agencies to maximize collections, increase compliance, improve customer service and streamline operations through the use of enabling technologies, in particular, integrated tax and tax data warehouse solutions Incorporated in May 1996 Headquartered in Pembroke, MA with Solution Centers in Roseville, CA and Charlotte, NC Dedicated exclusively to providing products & services to tax agencies Over 200 tax professionals with 1000 combined years of revenue systems consulting Deep tax administration domain expertise Software Solutions for Integrated Tax and Integrated Compliance Management (Data Warehousing, Audit, Collections, Fraud ) Committed to client partnerships in delivery of projects 3

4 Agenda Perspective Evolution Service Benefits Issues Modernization In Action 4

5 Perspective Past (or Current) Application Development Process Identify Tasks Define Requirements Build Logic for a Specific Purpose Benefits Can Be Built Efficiently Simplified Design Use of New Technology Limitations New Requirements Redundancy Complexity Integration Challenge 5

6 Evolution Origin and Influence of SOA Source: 6

7 Service Brief Definition Collection of related business capabilities Selfcontained Distinct from other services May be composed of other services Example: Service: Register Taxpayer Operation: Add a name Operation: Add an address Operation: Add an id 7

8 Benefits The Promises of an SOA Sharing of Data Federation Diversification Options Alignment Software Reuse Leaner IT 8

9 Principles Enabling SOA Benefits Standardized Service Contracts Loose Coupling Reusable Autonomous Discoverable Composable Interoperable 9

10 Issues Further Considerations of an SOA Design Complexity Standards Requirements Effort Governance 10

11 Modernization Different Options to Achieve Benefits Design Patterns Approaches based on problems to be solved Legacy System Modernization Expose web services on existing applications to modernize or create new applications Phased Approach Develop portions on a function-by-function basis Big Bang 11

12 References / / ti / / Erl, Thomas. SOA Principles of Service Design. Prentice Hall

13 Questions and Discussion 13

14 Appendix Other Definitions Application Service Orientation Service Composition 14

15 Appendix - Application Software program focused on solving a set of related problems. DiscoverTax Web User Edition (WUE) DiscoverTax Administrator Edition (SMF) SCITS Web Application Composition Create new applications from existing services SOA Enterprise Consequence Functionality of all applications is exposed Any service to be leveraged at-will 15

16 Appendix - Service Orientation A perspective on design that applications are built around services Services provide the bulk of business functionality Focus on: Business process encapsulation Service reuse Application integration 16

17 Appendix - Service Composition Creating a new service from other services. Results in: New applications New systems Enterprise data exchanges Usually automation of a business process Replaces enterprise application integration (EAI) 17

18 Appendix Alphabet SOAP Messaging SOAP (SOAP 1.1, SOAP 1.2) WS-Addressing WS-BrokeredNotification WS-MTOMPolicy WS-I Attachments Description and Discovery UDDI 3.0 WSDL (1.1, 1.2, 2.0) WS Semantics WS Metadata Exchange WS-PolicyAssertions WS-PolicyAttachment WS-Policy WS Resource Framework Transactions WS-AtomicTransaction WS-BusinessActivity WS-Coordination Security WS-Federation WS-Security 1.0 WS-Provisioning WS-SecureConversation Language WS Kerberos Binding WS-Trust Security Assertion Markup Language (SAML) Business Process WS-BPEL for People WS-BPEL for Web Services Management WSDM Distributed Management WS-Manageability WS Resource Transfer WS Service Registry and Repository 18