The document provides an introduction to service-oriented architecture (SOA). It discusses the history and evolution of SOA from earlier approaches like COBOL and SQL. The key components of SOA are services, service consumers, providers, contracts, and registries. Services are reusable components that communicate by exchanging messages. SOA allows for loosely coupled integration of distributed systems and provides benefits like increased return on investment and improved adaptability. Adoption of SOA remains in early stages, with only 19% of organizations having implemented it so far.

2. Group Members Salma Arshad Mehwish Amina Kehkashan

3. SOA (Service Oriented Architecture) An Introduction

4. A little history In the Beginning…. Computers were the domain of scientists for scientists Business and Government discovered the value of computing Business requirements needed to be captured and programmed

5. Some Past Attempts … COBOL – It was designed to be business-problem oriented, machine-independent, and capable of continuous change and development. SQL – The SQL "language" allows anyone with a computer terminal to access and use relational databases. Originally thought to be an end-user tool. C language

6. SOA in the past SOA was first invented in 1960’s in those days it is called procedural programming. Service-oriented architectures are not a new thing. The first service-oriented architecture for many people in the past was with the use DCOM (Distributed Component Object Model) or Object Request Brokers (ORBs) based on the CORBA(Common Object Request Broker Architecture) specification. XML and Web services have shaped SOA.

7. Revolution Revolution COBOL Basic programming language C programming language SQL Structured analyses and design Electronic data exchange Evolution Web Services Information Engineering CASE C++ Java Object-Oriented Analysis and Design HTML Common Record (XML) Ecosystem Standards SOA

8. What is SOA? SOA is a TLA, ATLA, YADA TLA mean Three Letter Acronym ATLA mean Another TLA YADA mean Yet Another Demand Acronym It is basically an architecture for building business applications as a set of loosely coupled. To deliver a well define Level of Service by linking together business processes.

9. What is SOA? Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. SOA is essentially collection of services. These services communicate with each other.

10. Components of SOA There are four basic components of SOA Service Consumer Service Provider Service Contract Service Registry

11. SOA vs. WS SOA typically refers to the web services. SOA is made by the combination of web services. All web services are interrelated through or via SOA.

12. What is Service? A service is a reusable component that can be used as a building block to form larger, more complex business-application functionality. A facility that supply some public demand. A Windows Service? RPC Locator, EventLog, Desktop env, Software Service? Distribution Service, Alert Service Security Service, Log Service Business Service? Common Operational Picture, Navigation Accounts Receivable, Customers

13. Cont’d Services Revolve Around Messages Services Are “Black Boxes” Messages go in and out Many Kinds of Message transports Email, IP, TCP/IP, HTTP, and more Many Kinds of Message structures XML, Binary, whatever

14. Service Properties A service can take requests Given a well-formed request, a service will send a response A service can use other services

15. Architecture? Architecture represents the set of earliest design decisions Hardest to change Most critical to get right Architecture is the first design artifact where a system’s quality attributes are addressed

16. Why Architecture? Architecture serves as the blueprint for the system but also the project: Team structure Documentation organization Work breakdown structure Scheduling, planning, budgeting Unit testing, integration Architecture establishes the communication and coordination mechanisms among the components.

17. SOA elements

18. Private If a transaction is involved then the data should be save on Database at backend Service Data is private Keep DB private Keep transactions private Keep exceptions private Don’t share classes or other internal data structures Don’t share too much – or you’ll lose autonomy (or tempt others to lose it)

19. SOA Loosely coupled Loosely coupled modular services to support both business and IT requirements. What is Loosely coupled? Services are independent. They don’t know or care whether the service is: Running on Windows, J2EE or a Mainframe Written in assembler, C, Java, or COBOL. Running on a machine in the U.S., India, or China Being served by a CRM system, a DDA system, or a database Oracle etc.

20. SOA

21. Benefits of SOA Increased Return on Investment Greater Security Improved Business Processes Reduced Integration Costs Improve adaptability

22. SOA Adoption Trend: By all accounts, SOA is still early in its adoption cycle. Only about 19% of all organizations have SOA in place, of which 12% plan to increase their use of SOA and 7% have no further plans. 11% are in the midst of piloting or implementing SOA 22% are researching the use of this technology.