1 / 10

Service Oriented Architecture An Enterprise Approach to Enabling the Business

Service Oriented Architecture An Enterprise Approach to Enabling the Business. Agenda. What is Service Oriented Architecture? Defined How does it help me? Case Study Overview What do I need to do? Guiding Principles Organization Governance What does tomorrow look like?

debra-sutton
Download Presentation

Service Oriented Architecture An Enterprise Approach to Enabling the Business

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Service Oriented ArchitectureAn Enterprise Approach to Enabling the Business

  2. Agenda • What is Service Oriented Architecture? • Defined • How does it help me? • Case Study Overview • What do I need to do? • Guiding Principles • Organization • Governance • What does tomorrow look like? • What resources are available to me?

  3. What is Service Oriented Architecture? SOA is about two things: Building services and practicing architecture ~ Gartner An architectural discipline that is defined by a set of design principles. This architectural discipline has fostered a new design paradigm for creating shared, reusable, distributed services. ~ Gartner SOA is about turning ad hoc communities of software and process into an integrated economy composed of towns that are part of larger counties that are part of larger states, and so on. SOA is about the design and execution of the master plan, the infrastructure and government and laws that all of an organizations IT entities must follow to enable peaceful, productive commerce all around. ~ Joe McKendrick, 2008 In a Nutshell: It’s an approach to designing and supporting IT Systems that isolates application specific functionality from non-specific functionality.

  4. Case Study Overview: EOHHS

  5. Case Study Overview: MassGIS Protect the Service: Deliver application functionality even when technical underpinnings are being upgraded – either side of the API • Middleware Upgrade • MapAccess replaced by Geoserver map server • All clients continued to function based on same interface • Client Upgrade • Upgraded the user interface for OLIVER to use Javascript • Functionality was kept the same • OLIVER application provided access built on web services API (programmatic) …….

  6. Case Study Overview: ITD

  7. What do I need to do: Guiding Principles

  8. What do I need to do? Governance Model Organizational Competencies

  9. What does Tomorrow Look Like? • The Ultimate Promise • Add support for emerging requirements without breaking the existing application • Communicate between applications without developing custom code every time • Browse available options and select only the functionality you need • Share what you’ve implemented with your business partners • See key performance indicators in real time/near real time • Enforce new compliance requirements in an automated way • Pinpoint environment failures efficiently, in a graphical manner without needing to read code

  10. Questions? Contact Information: Gillian Lockwood Gillian.lockwood@state.ma.us 617-626-4531

More Related