1 / 22

Service-oriented Architecture

Service-oriented Architecture. Connecting the Dots. What do we want?. Flexible software Low cost software maintenance Platform independence Business responsiveness Open standards In short, a MIRACLE!. What do our customers want?. Instant response to a changing business

benard
Download Presentation

Service-oriented Architecture

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-orientedArchitecture • Connecting the Dots

  2. What do we want? • Flexible software • Low cost software maintenance • Platform independence • Business responsiveness • Open standards • In short, a MIRACLE!

  3. What do our customers want? • Instant response to a changing business • Decreasing infrastructure costs • Real-time event-driven information • Support of strategic business initiatives • User friendly applications • In short, a MIRACLE!

  4. Can an SOA help? • Yes – if appropriately and incrementally combined with other improvements • Maybe – if the justice industry gets its act together on standards and the vendors follow • No – if we expect a magic bullet

  5. Some definitions • Enterprise Architecture • consistent principled guidelines for making decisions about technology • collection of risk mitigation strategies • Service-oriented Architecture: • asynchronous, event-driven • loosely coupled, flexible • public interfaces • reuse of components & logic

  6. What should an EA include? • Business values, goals and principles • performance measures • Business processes & best practices • functional standards • Enterprise data model • data exchange standards, GJXDM, GJXDD • Enterprise technology stack • web services, SD process, PM process

  7. EA Issues • Can be IT-centric or process-centric • Before choosing framework, determine: • business drivers (is there an ROI?) • scope (how much commonality?) • governance (who will enforce?) • Need executive business support • choose pilot that spans business silos • show value of architectural standards

  8. What should an SOA Include? • Registry of services • Reusable distributed services • Open standards-based interfaces • Reusable business logic • Event-driven asynchronous messaging • Focus on systems—not databases • Incremental delivery strategy

  9. How do web services fit in? • SOA is a design principle • Web services are a technology stack • Applies primarily to automatic data exchanges between applications • Excludes some business benefits of EA & SOA: • Internal application flexibility • Alignment with performance measures

  10. CTA Performance Standards • Top level of Enterprise Architecture • Identifies specific business goals • Guides IT alignment with the business • Requires IT support to implement

  11. CTA Functional Standards • Middle of Enterprise Architecture • Describes common business processes • Describes IT requirements as use cases • Supports IT alignment with the business

  12. CTA Data Exchange Standards • Lower level of Enterprise Architecture • Based on web services • Based on GJXDD • Need to validate relevant parts of GJXDM using critical reference documents • Need to align with JIEM Reference Model to support CJIS projects

  13. GJXDD & GJXDM • GJXDD – a common justice vocabulary • needs more modularity • needs more transparency • GJXDM – a common justice semantics • needs tighter sub-domain models • needs standard bindings for J2EE and .Net

  14. Software Development Process • Has implications for EA and SOA • What risks to mitigate? • What granularity to use? • How much ambiguity to tolerate? • What organizations (business processes) are appropriate? • High or low ceremony? • Agile or rigorous processes? • Traditional unified PM’s or not?

  15. Project Management Process • Standardized architectures and processes require special expertise in business process reengineering. [EA] • Emphasis on services requires special expertise in customer requirements definition. [SOA]

  16. There is a plan! • The ASCA and CTA standards fit into an overall Corrections and Justice EA and SOA strategy. • Business benefits of compliance will include faster, cheaper and more value-laden satisfaction of business needs.

More Related