Service Oriented Architecture (SOA)
Download as PPTX, PDF3 likes2,368 views
This document provides an overview of service-oriented architecture (SOA). It defines SOA and its key concepts, discusses the motivations for and applications of SOA, compares SOA to other methodologies, outlines implementation technologies, advantages and challenges. It also reviews SOA methodologies, describes the typical steps in a SOA approach, discusses the future of SOA and open research areas, and provides recommendations for adopting SOA.
![
• Other definitions adopted by the prominent companies,
as stated in [9], are presented below.
• “A SOA is an application framework that takes everyday
business applications and breaks them down into
individual business functions and processes, called
services.” –IBM
• “SOA is an approach to organizing IT in which data,
logic, and infrastructure resources are accessed by routing
messages between network interfaces.” – Microsoft
• “A paradigm for organizing and utilizing distributed
capabilities that may be under the control of different
ownership domains.” – The OASIS Group
… Definition of SOA](https://image.slidesharecdn.com/soapresentation-181108104206/85/Service-Oriented-Architecture-SOA-10-320.jpg)
![ SOA Repeatable Quality (RQ): SOA RQ is a proprietary methodology by Sun Microsystems that is based on a RUP-like
iterative and incremental process consisting of five phases: inception, elaboration, construction, transition, and conception.
UML compliant artifacts are used for documenting various deliverables of these phases.
CBDI-SAE Process: The CBDI Forum is currently developing a SOA methodology as part of its CBDI-SAE SOA Reference
Framework (RF). The four key discipline areas of the process are: consume, provide, manage, and enable. Each area groups
similar disciplines that are further broken down to process units and then to tasks. This methodology aims business-IT
integration through top-down analysis of business requirements as well as bottom-up legacy system integration. The CBDI-SAE
process aims to cover the whole SOA lifecycle, including deployment, monitoring, and governance activities.
Service Oriented Architecture Framework (SOAF): SOAF consists of five main phases: information elicitation, service
identification, service definition, service realization, and roadmap and planning. Service Oriented Unified Process (SOUP): As
the name suggests, this approach by K. Mittal is primarily based on the Rational Unified Process. Its life cycle consists of six
phases: incept, define, design, construct, deploy, and support. However, SOUP lacks detailed documentation and leaves room
for adaptation.
Methodology by Thomas Erl: The service oriented analysis and design methodology documented in Thomas Erl’s book is
considered the first vendor-agnostic one to be published. This methodology is a step by step guide through the two main
phases: analysis and design.
BPMN to BPEL: In this approach the business process is expressed in an abstract model (Business Process Modeling Notation or
BPMN) and according to transformation rules it is automatically mapped to an execution language (Business Process Execution
Language or BPEL) that can be executed by a process engine.
Steve Jones’ Service Architectures: It is technology agnostic and takes a top-down business view reaching up to the point of
service candidate discovery (i.e. identification). The methodology adopts a broadly four-step process (What, Who, Why, and
How), of which the first three are covered in preparation for the fourth step.
Ramollari et al. [] concluded that the service oriented development methodologies that have emerged are quite new and do not
yet offer the required level of maturity. It is too early to determine whether any one of these methodologies is more appropriate
than the others, or even to consider unifying some of them into a widely acceptable standard.
SOA Methodologies](https://image.slidesharecdn.com/soapresentation-181108104206/85/Service-Oriented-Architecture-SOA-32-320.jpg)
Ad
More Related Content
What's hot (20)
Similar to Service Oriented Architecture (SOA) (20)
Ad
More from Biniam Asnake (6)
Ad
Recently uploaded (20)
Service Oriented Architecture (SOA)
- 2. Introduction Definitions Architecture of Service Orientation Applications of SOA Difference between SOA and Other Software Engineering Methodologies Object-Oriented Computing Paradigms, Web services and CBSE Implementation Technologies Advantages and Challenges of SOA Methodologies Steps of the SOA Approach The Future of SOA and Open Research Areas Conclusion Recommendations Presentation Outline
- 3. Modern enterprises need to respond effectively and quickly to opportunities in today’s ever more competitive and global markets. Motivators for SOA: Too few software engineers and too many programmers increasing nature of distributed systems heterogeneity of systems and computing environments dynamics of operating environments transparency of communication infrastructure details and process-orientation requires multiple services. Introduction
- 4. SOA is designed to: allow developers to overcome many distributed enterprise computing challenges including: application integration transaction management security policies allow multiple platforms and protocols and leveraging numerous access devices and legacy systems. The SOA as a design philosophy is independent of any specific technology, e.g., Web-services or J2EE enterprise beans. … Introduction
- 5. Now, service-oriented architectures (SOAs) are being promoted as the next evolutionary step to help IT organizations meet their ever more- complex challenges. The purpose of this paper is to give brief introduction to the architecture, applications, advantages and challenges, similarity and difference with other methodologies, implementation technologies, the steps and the future and research areas of SOA. Finally, the recommendations are forwarded. … Introduction
- 6. Architecture is: the fundamental organization of a system embodied in its components, their relationships to each other and to the environment, and the principles guiding its design and evolution. A Service is: an implementation of a well-defined piece of business functionality, with a published interface that is discoverable and can be used by service consumers when building different applications and business processes. Basic Definitions
- 7. Features of Service in SOA Interface contract Interoperability Dynamically discovered Public vs. Published interface The most popular type of services available today utilize Web services Standards: Web Services Description Language (WSDL), Simple Object Access Protocol (SOAP), and Universal Description, Discovery and Integration registry (UDDI) … Basic Definitions
- 8. The World Wide Web Consortium (W3C) refers to SOA as: 'A set of components which can be invoked, and whose interface descriptions can be published and discovered'. CBDI rejects this definition on two counts: 1. the components (or implementations) will often not be a set. 2. the W3C definition of architecture only considers the implemented and deployed components, rather than the science, art or practice of building the architecture. Definition of SOA
- 9. Hence, CBDI recommends SOA is more usefully defined as: “The policies, practices, frameworks that enable application functionality to be provided and consumed as sets of services published at a granularity relevant to the service consumer. Services can be invoked, published and discovered, and are abstracted away from the implementation using a single, standards-based form of interface.” The Service-Oriented Computing (SOC) paradigm refers to: the set of concepts, principles, and methods that represent computing in SOA in which software applications are constructed based on independent component services with standard interfaces. … Definition of SOA
- 10. • Other definitions adopted by the prominent companies, as stated in [9], are presented below. • “A SOA is an application framework that takes everyday business applications and breaks them down into individual business functions and processes, called services.” –IBM • “SOA is an approach to organizing IT in which data, logic, and infrastructure resources are accessed by routing messages between network interfaces.” – Microsoft • “A paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.” – The OASIS Group … Definition of SOA
- 11. Enterprise Service Bus (ESB): an integration platform that utilizes web services standards to support a wide variety of communications patterns over multiple transport protocols and deliver value-added capabilities for SOA applications. The popularity of SOC is confirmed by industry observers and market research organizations. The prestigious Gartner Group predicted that: 45% of the U.S. companies will use SOA by 2006, and 80% by 2007. The Radicati Group predicted that: the SOA market will reach $6.2 billion by 2008 with an annual compound rate of 50%. … Basic Definitions
- 12. Figure 1: Three Architectural Perspectives Architecture of SO
- 13. SOA can provide a secure, reliable and agile architecture that benefits the entire institution. What makes SOA valuable is its ability to reuse business functions in different combinations. SOA can be applied in B2B e-commerce, Enterprise Application Integration (EAI), application-to-application, government, embedded systems and cloud computing. The SOA’s loose-coupling principle make them indispensable for enterprise-wide and cross-enterprise applications. Applications of SOA
- 14. All major software manufacturers and vendors are promoting support for SOA. As a result, every major development platform now officially supports the creation of service-oriented solutions. All major computer corporations, including BEA, IBM, Microsoft, Oracle, HP, SAP, Intel, Cisco, Juniper, and Sun Microsystems, have moved towards the SOC paradigm. Languages, protocols, and standards have been developed to support and to regulate SOC applications. Numerous frameworks, specification languages, and tools have been created. Furthermore, government agencies, such as the U.S. Department of Defense (DoD) and NASA, have adopted SOC. … Application of SOA
- 15. SOC is being adopted by major computer users including: banks (Web banking services), retailers (Web shopping services), airlines (Web booking services), travel agencies (Web composite services that link together the services from airlines, hotels, car rentals etc.). Universities around the world have geared their computing research toward SOC- based modeling languages, automated code generation, service verification, and validation. … Application of SOA
- 16. Features Object-Oriented Computing Service-Oriented Computing Methodology tightly coupled classes inheritance relationships loosely coupled services and composing them into executable applications. Level of abstraction and cooperation a single team responsible for the entire life cycle Developers must have knowledge of application domain and programming. Development is delegated to three independent parties: application builder, service provider, and service broker. Code sharing and reuse Code reuse through inheritance of class members and through library functions. Library functions have to be imported at compilation time and are platform dependent. Services have standard interfaces and are published on Internet repository. They are platform-independent and can be searched and remotely accessed. Dynamic binding and re-composition The method must have been linked to the executable code before the application is deployed. The services can be discovered after the application has been deployed. This feature allows an application to be recomposed at runtime. System maintenance Users need to upgrade their software regularly. The application has to be stopped to perform the upgrading. The service code resides on service providers' computers. Services can be updated without users' involvement. SO vs. OO Computing Paradigms
- 17. Web Service: Is a software system designed to support interoperable machine-to-machine interaction over a network. seem to become the preferred implementation technology for realizing the SOA promise of maximum service sharing, reuse, and interoperability. SOA is potentially much wider in its scope than simply defining service implementation, addressing the quality of the service from the perspective of the provider and the consumer. Web services are not a mandatory component of a SOA. SOA vs. Web services
- 18. As web services are purely the implementation of SOA, Component-Based Software Engineering (CBSE) is the discipline by which you ensure you are building components that are aligned with the business. SOA is the approach. SOA vs. CBSE
- 19. Includes: XML Web Services, Common Object Request Broker Architecture (CORBA), Java Remote Method Invocation (RMI), .Net Remoting, Message Oriented Middleware (MOM) – IMB’s MQSeries, Microsoft Message Queuing (MSMQ), Java Message Service, TCP/IP and Email The major platforms that support SOA are: IBM: WebSphere SOA Product Suite BEA: Aqualogic (WebLogic) Oracle: Fusion Middleware Microsoft: .NET SAP: NetWeaver LogicBlaze: open source solution from Apache foundation Implementation Technologies
- 20. To address the requirements of: loosely coupled, standards-based, and protocol- independent distributed computing, mapping enterprise information systems (EIS) appropriately to the overall business process flow. To help organizations succeed in the dynamic business landscape of today including: Leveraging existing assets Easier to integrate and manage complexity More responsive and faster time-to-market Reduced cost and increase reuse Risk mitigation by reusing existing components Continuous business-process improvement Process-centric architecture Advantages of SOA
- 21. Additional advantages of SOA includes: Security Interoperability Reusability Flexibility Ease of assembling new business processes Generally, SOA is by no means a silver bullet, and migration to SOA is not an easy task. Rather than migrating the whole enterprise, migrate an appropriate subset of business functions as the business need arises or is anticipated. … Advantages of SOA
- 22. Trust issues: because data from a large number of services from different partners is available Testing issues: All services work as designed? Security Is the level of security is adequate? Continuous updating, refinement and expansion. SOA is not valuable if there is no intention for reuse. Non- technical challenges - resistance to change Challenges of SOA
- 23. 1. IBM Service-Oriented Analysis and Design (SOAD) 2. IBM Service Oriented Modeling and Architecture (SOMA) 3. Service-Oriented Design and Development Methodology (SODDM) 4. SOA Repeatable Quality (RQ) 5. CBDI-SAE Process 6. Service Oriented Architecture Framework (SOAF) 7. Service Oriented Unified Process (SOUP) 8. Methodology by Thomas Erl 9. BPMN to BPEL (Business Process Modeling Notation to Business Process Execution Language) 10. Steve Jones’ Service Architectures The service oriented development methodologies that have emerged are quite new and do not yet offer the required level of maturity. Hence, it is too early to determine whether any one of these methodologies is more appropriate than the others, or even to consider unifying some of them into a widely acceptable standard. SOA Methodologies
- 24. are not necessarily linear and sequential but rather exploratory and iterative, incrementing functionality and understanding of the team as the project proceeds. The steps are: 1) Domain decomposition 2) Goal-service model creation 3) Subsystem analysis 4) Service allocation: 5) Component specification 6) Structure components and services using patterns 7) Technology realization mapping 7 Steps of the SOA Approach
- 25. Figure 2: Seven main steps of the SOA approach
- 26. Two new, emerging concepts are beginning to be implemented: grid computing and on demand computing. SOA becomes the DNA of grid computing and on demand computing. Applying SOA allows you to maximize resource utilization in a grid environment. SOA is an enabling architecture for on demand applications. Thus, applications must operate in an SOA to realize the benefits of on demand. The Future of SOA
- 27. Development of modeling and specification languages; Development infrastructure, related techniques and tools; Service-oriented system engineering; Service-oriented simulation and testing; Service-oriented reliability modeling evaluation; Application of SOC and SOA in embedded systems and robotics Application of SOC and SOA in mission-critical system Application of SOC and SOA in bio-engineering; Application of SOC and SOA in e-business and e-commerce; Application of SOC, SOA, and ontology in education. Open Research Areas
- 28. It became clear that organizations need to move toward SOA to prepare for future applications from vendors and peers. By making services generic and common to all business processes, organizations can improve the security and privacy of its transmissions while protecting its future technology investments and driving down the costs of replicating data and maintaining multiple interfaces. A successful migration to SOA requires that the developers, managers, and business process experts understand the concepts and the impacts of SOA. They all must understand the goals, difficulties, and gains. Conclusion
- 29. In our country, Ethiopia, a lot of manual systems should be automated to get the benefits provided by IT. But, software development is at an infant stage and most systems are being developed using traditional methodologies. Because we do not have many systems, there should be a way to use a service or functionality provided by other similar firms. SOA can be applied in different organizations and departments. Therefore, I recommend SOA to be adopted in major sectors such as airlines, banks, tour and travel agencies and universities to speed decision making, to provide relevant information, improve the security and privacy of information. In addition to the application in organizations, I also recommend teaching, specially university undergraduate students, about the SOA design and development to enable organizations use similar services with minimized cost. Recommendations
- 31. SOA Repeatable Quality (RQ): SOA RQ is a proprietary methodology by Sun Microsystems that is based on a RUP-like iterative and incremental process consisting of five phases: inception, elaboration, construction, transition, and conception. UML compliant artifacts are used for documenting various deliverables of these phases. CBDI-SAE Process: The CBDI Forum is currently developing a SOA methodology as part of its CBDI-SAE SOA Reference Framework (RF). The four key discipline areas of the process are: consume, provide, manage, and enable. Each area groups similar disciplines that are further broken down to process units and then to tasks. This methodology aims business-IT integration through top-down analysis of business requirements as well as bottom-up legacy system integration. The CBDI-SAE process aims to cover the whole SOA lifecycle, including deployment, monitoring, and governance activities. Service Oriented Architecture Framework (SOAF): SOAF consists of five main phases: information elicitation, service identification, service definition, service realization, and roadmap and planning. Service Oriented Unified Process (SOUP): As the name suggests, this approach by K. Mittal is primarily based on the Rational Unified Process. Its life cycle consists of six phases: incept, define, design, construct, deploy, and support. However, SOUP lacks detailed documentation and leaves room for adaptation. SOA Methodologies
- 32. SOA Repeatable Quality (RQ): SOA RQ is a proprietary methodology by Sun Microsystems that is based on a RUP-like iterative and incremental process consisting of five phases: inception, elaboration, construction, transition, and conception. UML compliant artifacts are used for documenting various deliverables of these phases. CBDI-SAE Process: The CBDI Forum is currently developing a SOA methodology as part of its CBDI-SAE SOA Reference Framework (RF). The four key discipline areas of the process are: consume, provide, manage, and enable. Each area groups similar disciplines that are further broken down to process units and then to tasks. This methodology aims business-IT integration through top-down analysis of business requirements as well as bottom-up legacy system integration. The CBDI-SAE process aims to cover the whole SOA lifecycle, including deployment, monitoring, and governance activities. Service Oriented Architecture Framework (SOAF): SOAF consists of five main phases: information elicitation, service identification, service definition, service realization, and roadmap and planning. Service Oriented Unified Process (SOUP): As the name suggests, this approach by K. Mittal is primarily based on the Rational Unified Process. Its life cycle consists of six phases: incept, define, design, construct, deploy, and support. However, SOUP lacks detailed documentation and leaves room for adaptation. Methodology by Thomas Erl: The service oriented analysis and design methodology documented in Thomas Erl’s book is considered the first vendor-agnostic one to be published. This methodology is a step by step guide through the two main phases: analysis and design. BPMN to BPEL: In this approach the business process is expressed in an abstract model (Business Process Modeling Notation or BPMN) and according to transformation rules it is automatically mapped to an execution language (Business Process Execution Language or BPEL) that can be executed by a process engine. Steve Jones’ Service Architectures: It is technology agnostic and takes a top-down business view reaching up to the point of service candidate discovery (i.e. identification). The methodology adopts a broadly four-step process (What, Who, Why, and How), of which the first three are covered in preparation for the fourth step. Ramollari et al. [] concluded that the service oriented development methodologies that have emerged are quite new and do not yet offer the required level of maturity. It is too early to determine whether any one of these methodologies is more appropriate than the others, or even to consider unifying some of them into a widely acceptable standard. SOA Methodologies
- 33. I. IBM Service-Oriented Analysis and Design (SOAD): it is an abstract framework rather than a holistic methodology. SOAD builds upon existing, proven techniques, such as OOAD, CBD, and BPM. II. IBM Service Oriented Modeling and Architecture (SOMA): SOMA is a full-blown modeling methodology by IBM consisting of three steps: identification, specification, and realization of services, flows (business processes), and components realizing services. The process is highly iterative and incremental. However, because SOMA is proprietary to IBM, its full specification is not available. SOA Methodologies
- 34. Figure 2: Phases of SOMA
- 35. III. Service-Oriented Design and Development Methodology (SODDM): from the point of view of both providers and consumers, which attempts to cover the full SOA lifecycle. It is partly based on well- established development models, such as the RUP, CBD, and BPM. The methodology utilizes an iterative and incremental process that comprises one preparatory and eight distinct main phases. SOA Methodologies
Editor's Notes
- #6: Service-Oriented Architecture (SOA) has received wide coverage in recent years with the proliferation of web services.
- #7: 1. Before defining what SOA is, it is desirable to have a thorough understanding about architecture, service and its principles. 2. Architecture: The term is more generally used to describe a style or set of practices.
- #8: A little description about each bullet Features of Service in SOA [6] Interface contract: Contract for the service provided by a component for use by any other component Interoperability: each component must provide an interface that can be invoked through a payload format and protocol that is understood by all of the potential clients of the service Dynamically discovered: a third party mechanism must be used to find the service. Public vs. published interface: Public interface: can be used by components within a system and are only used by known clients. Published interface: is exposed to the network and clients of the published interface are not known.
- #9: List of definitions of SOA are available given by scholars and companies in the IT industry. Looking around we see the term or acronym SOA becoming widely used, but there's not a lot of precision in the way that it's used.
- #12: Enterprise Service Bus (ESB): a highly distributable communications and integration backbone to build an SOA The Radicati Group, which is more conservative These numbers all point to exponential growth and enormous popularity of SOA and SOC in the U.S. economy [12].
- #13: For SOA there are three important architectural perspectives as shown in Figure 1. The Application Architecture. This is the business facing solution which consumes services from one or more providers and integrates them into the business processes. The Service Architecture. This provides a bridge between the implementations and the consuming applications, creating a logical view of sets of services which are available for use, invoked by a common interface and management architecture. The Component Architecture. This describes the various environments supporting the implemented applications, the business objects and their implementations.
- #14: The SOA’s loose-coupling principle—especially the clean separation of service interfaces from internal implementations—to guide planning, development, integration, and management of their network application platforms make them indispensable for enterprise-wide and cross-enterprise applications [11].
- #17: Universities around the world (e.g., US, UK, Japan, Germany, China, and Singapore), including Arizona State University (ASU),
- #18: While the objective is definitely not new, SOA seeks to eclipse previous efforts such as modular programing, code reuse, and object-oriented software development techniques [4]. Differences between Service-Oriented and Object-Oriented Computing Paradigms SOC evolved from the object-oriented computing paradigm but the idea of SOA departs significantly from that of OOP, which strongly suggests that you should bind data and it’s processing together [5]. As shown in Table 1, there are significant differences between the two paradigms.
- #19: WSs are software available as a service using Internet protocols. df web services are part of the wider picture, SOA.
- #22: Service orientation is a new software engineering paradigm that introduces opportunities as well as challenges [4]. The fundamental shift in SOA—from shipping data to providing services—has many potential benefits including agility in deploying applications, increased data security, and improved transparency [7]. An SOA can be evolved based on existing system investments rather than requiring a full-scale system rewrite.
- #24: Additional advantages of SOA includes: Security: The components behind the SOA-Interfaces are kept hidden Interoperability: Opening an inter-enterprise working and communication Reusability: Simplifying interconnection to - and usage of -existing IT (legacy) assets Flexibility: Responding more quickly and cost-effectively to changing market conditions Ease of assembling new business processes
- #26: A number of preliminary methodologies have emerged to address the huge demand for process guidance and proven best practices in SOA projects (Ramollari et al.).
- #27: This section introduces a method for discovering services (top-down) and leveraging services (bottom-up, from legacy and packaged applications). It includes a combination of techniques and steps that describe how to employ top-down and bottom-up techniques to successfully create and/or migrate to an SOA. The process can be optimized by determining which steps can be carried out in parallel and which are dependent on other steps. You will discover what works best for you and your team, depending on the project and organizational culture.
- #28: This section introduces a method for discovering services (top-down) and leveraging services (bottom-up, from legacy and packaged applications). It includes a combination of techniques and steps that describe how to employ top-down and bottom-up techniques to successfully create and/or migrate to an SOA. The process can be optimized by determining which steps can be carried out in parallel and which are dependent on other steps. You will discover what works best for you and your team, depending on the project and organizational culture.
- #30: While these models are distinct and have developed separately, they are closely related; and each makes the evolution to SOA even more imperative. Representing every application, resource or business capability as a service with a standardized interface allows you to quickly combine new and existing applications to address changing business needs and improve operational effectiveness — the essence of SOA.
- #35: A number of preliminary methodologies have emerged to address the huge demand for process guidance and proven best practices in SOA projects (Ramollari et al.).
- #36: A number of preliminary methodologies have emerged to address the huge demand for process guidance and proven best practices in SOA projects (Ramollari et al.).
- #37: A number of preliminary methodologies have emerged to address the huge demand for process guidance and proven best practices in SOA projects (Ramollari et al.).
- #39: A number of preliminary methodologies have emerged to address the huge demand for process guidance and proven best practices in SOA projects (Ramollari et al.).