Presentation is loading. Please wait.

Presentation is loading. Please wait.

Sponsored by the U.S. Department of Defense © 2006 by Carnegie Mellon University Version E-Gov 2006Benefits, Misconceptions and SOA Governance Issues -

Similar presentations


Presentation on theme: "Sponsored by the U.S. Department of Defense © 2006 by Carnegie Mellon University Version E-Gov 2006Benefits, Misconceptions and SOA Governance Issues -"— Presentation transcript:

1 Sponsored by the U.S. Department of Defense © 2006 by Carnegie Mellon University Version E-Gov 2006Benefits, Misconceptions and SOA Governance Issues - 1 Pittsburgh, PA 15213-3890 SOA Benefits, Misconceptions and Needs for Addressing Governance Dennis Smith Software Engineering Institute

2 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 2 Agenda Benefits of SOA Common Misconceptions SOA Governance: Critical Factors for Achieving SOA Benefits

3 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 3 What is SOA? Service-oriented architecture is a way of designing systems that enables Cost-efficiency Agility Adaptability Leverage of legacy investments

4 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 4 Services Services are reusable components that represent business tasks. Customer lookup Account lookup Credit card validation Credit check Hotel reservation Interest calculation Services can be Globally distributed across organizations Reconfigured into new business processes

5 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 5 Services and Agility Order Processing Application Customer Lookup Service Credit Check Service Item Lookup Service Inventory Check Service Course Management Application Room Availability Service The new application can easily use available services. New services can be used by other applications as well.

6 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 6 Services and Adaptability Order Processing Application Customer Lookup Service Credit Check Service Item Lookup Service Inventory Check Service SOA Infrastructure The SOA Infrastructure provides a standard communication mechanism between applications and services. Changes in services have potentially no impact on existing applications that use them.

7 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 7 Services and Legacy Leverage Order Processing Application Customer Lookup Service Credit Check Service Item Lookup Service Inventory Check Service SOA Infrastructure Customer Management System The applications access the services in a standard way. It is the service’s task to invoke the legacy system. Legacy platform diversity and complexity is transparent to the application. Manufacturing System

8 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 8 Components of an SOA-Based System Application X Service A SOA Infrastructure Enterprise Information System Application Y Application Z Interne t External System Service B Service C Service D Internal Users DiscoverySecurity Development Tools Legacy or New Code

9 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 9 In Summary … SOA is an approach to software development where Services provide reusable functionality with well-defined interfaces. An SOA infrastructure enables discovery, composition and invocation of services. Applications are built using functionality from available services. If managed well, SOA adoption can lead to Cost-efficiency Agility Adaptability Leverage of legacy investments The hard part is the “if managed well”.

10 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 10 Agenda Benefits of SOA Common Misconceptions SOA Governance: Critical Factors for Achieving SOA Benefits

11 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 11 SOA Provides The Complete Architecture For A System SOA is an architectural pattern/style/paradigm and not the architecture of the system itself. An architectural pattern provides guidance that embodies best practices. The concrete elements and their interactions are the architecture of the system. Any number of systems can be developed based on an architectural pattern. An architecture based on SOA inherits both the good and the bad. Corollary: SOA cannot be bought off-the shelf. System qualities have to be built into the architecture of the system. Decisions have to be made—service design and implementation, technologies, tradeoffs.

12 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 12 Legacy Systems Can Be Easily Integrated Into An SOA Environment Upfront hands-on analysis on the technical feasibility and return on investment must be performed to avoid last minute surprises. Is it technically feasible to create a service from the legacy system or part of the system? How much would it cost to expose the legacy system as services? Is this cost plus the cost of maintaining the legacy system more than the cost of replacing it with a new one? What changes will have to be done to the legacy system? How much will these changes affect current users and other production systems?

13 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 13 SOA Is All About Standards and Standards Are All That Is Needed “The good thing about standards is that there are so many to choose from” Comes from misconception that SOA and Web Services are the same. Most Web Services standards are emerging—subject to multiple interpretations Basic standards are quite stable: WSDL, SOAP, XML Higher-level standards are immature / under development There are (too) many standards—overlaps and potential conflicts require careful evaluation -WSCL vs. WS-Coordination -SAML vs. WS-Security

14 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 14 Using XML and WSDL Guarantees Interoperability Among Web Services Provided by Multiple Organizations Web Services enable syntactic interoperability XML Schema defines structure and data types WSDL defines the interfaces: operations, parameters and return values Available information, technologies and tool support Web Services do not guarantee semantic interoperability XML and WSDL do not define the meaning of data WSDL does not define what a service does Active research area—unresolved issues Interoperability needs agreement on both syntax and semantics

15 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 15 In Summary … Our intent is not to discourage, but to caution. An SOA approach may be the best way to achieve common goals of interoperability, agility, and reuse. But … Most of the mentioned issues are active areas of research. Some solutions will require time to mature. Also keep in mind … Not everything in an SOA-based system has to be a service -It might not make sense for your whole system Most case studies will show that the key is governance -Which has very little to do with technology

16 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 16 Agenda Benefits of SOA Common Misconceptions SOA Governance: Critical Factors for Achieving SOA Benefits

17 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 17 Another Misconception: SOA Is All About Technology SOA not only means a shift in technology but also changes in the organizational governance model. Service definition Service repositories Ownership -Common services? Data? Evolution Conflict resolution Deployment mechanisms Monitoring mechanisms Enterprise-wide policies Service-level agreements As a result addressing unique concerns of governance are critical for achieving SOA benefits

18 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 18 Lack of Governance Inhibits SOA Adoption An InfoWorld 2006 SOA Trend Survey indicates that Lack of Governance is the main inhibitor for SOA adoption (48%) Greater than other inhibitors that would seem more obvious Unresolved security issues (40%) Performance and reliability (39%) Incomplete and immature standards (38%)

19 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 19 Policies and Procedures Service providers Service conception Service modeling Service development Service deployment Infrastructure providers Infrastructure versioning Upgrades Application developers Service composition Application testing

20 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 20 Design-Time Governance Strategic design of services Alignment with business goals Greater impact with less risk Consistent service implementation Consistent use of standards Consistent use of infrastructure Consistent implementation of governance Management of reuse Consistent evaluation of migration feasibility Consistent approach to legacy asset migration

21 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 21 Runtime Governance Policy enforcement Lots of vendor activity because it is a hard problem Security and access control Services introduce new access points into systems Service level agreements (SLAs) Runtime validation of promises made in SLAs Tracking and reporting

22 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 22 Benefits of SOA Governance Greater alignment with business goals Greater control over creation, deployment and use of services Centralized place for policies and regulations Can embed compliance with government and industry regulations Sarbanes-Oxley, HIPAA, GLBA

23 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 23 Challenges of SOA Governance Seems counterintuitive If SOA is all about loose coupling and flexibility, why all this central control? Multiple organizations How to create governance for service providers, infrastructure providers, and application developers? What if policies conflict? Dealing with exceptions How to record and maintain sometimes necessary exceptions? Enforcing compliance How to make sure that policies and procedures are being followed at design time and runtime? What are the incentives for compliance?

24 © 2006 by Carnegie Mellon UniversityBenefits, Misconceptions and SOA Governance Issues- 24 Conclusions SOA offers significant potential for Leveraging investments in legacy systems by providing a modern interface to existing capabilities Exposing functionality to a greater number of users They accomplish these benefits by promoting Assembly of applications from existing services Platform and language independence Reuse of services through loose coupling Easy service upgrade due to separation of service interface from implementation However, achieving these benefits require recognizing that SOA development is a complex engineering task avoiding common misconceptions addressing the unique needs of SOA governance.


Download ppt "Sponsored by the U.S. Department of Defense © 2006 by Carnegie Mellon University Version E-Gov 2006Benefits, Misconceptions and SOA Governance Issues -"

Similar presentations


Ads by Google