Paragraph Format
Page 1: Introduction
Service-Oriented Engineering: Overview of course content.
Page 2: Outline
Topics Covered:
Introduction to Web Services & Service-Oriented Architecture (SOA)
The Business Case for SOA
Basic Concepts of Web Services: SOAP, WSDL, UDDI
Workflow Management
Page 3: What is SOA?
Definition: A collection of services that communicate with each other.
Services: Components (typically web services) that connect and interact.
Communication: Requires interface agreements and internet protocols.
Historical Context: Concept is not new; akin to RPC, RMI, CORBA, DCOM.
Page 4: Formal Definition of SOA
Architectural Style: Aims for loose coupling among services through communication protocols.
Model: Internet-native distributed computing model emphasizing service description, publication, discovery, and usage.
Page 5: Trinity of SOA
Components:
Service Broker: UDDI Registry
Service Provider: Supplies the service.
Requestor: Consumes the service.
Page 6: Web Service Defined
Brief Definition: Loosely coupled components communicating via XML interfaces over internet protocols.
Features:
Loosely coupled: Independent modifications possible.
Contracted: Behavior and parameters are publicly available.
Component: Encapsulated code with hidden implementation.
XML: Self-describing, human-readable, and firewall friendly.
Page 7: Key Web Service Technologies
SOAP: Messaging framework for information transfer using XML in distributed environments.
WSDL: XML format that describes a web service and its interface.
UDDI: Repository for WSDL documents.
Page 8: Confusion Around Web Services and SOA
Clarification: Web services are not synonymous with SOA; SOA encompasses broader architectural principles.
Page 9: Motivation for SOA - Business Perspective
Business Needs:
Interoperability within and across business sectors through the internet.
Challenges:
High IT complexity and costs
Demand for rapid responses.
Benefits:
Cost reduction by leveraging legacy services.
Revenue increase through service assembly.
Integration for enhanced collaboration.
Page 10: Motivation for SOA - Technical Perspective
Technical Needs: Software reuse and integration.
Legacy Issues: RPC legacy problems persist (e.g., tightly coupled systems).
SOA Goals: Addressing interoperability and integration issues.
Page 11: Interoperability in SOA
WSI Goal: Ensure web services can interact across various platforms and languages.
Standards: Set to accelerate deployment through guidance, tools, and forums.
Page 12: E-business Defined
Concept: Integration of traditional supply chain management with internet processes.
Includes:
E-commerce (B2C, C2C)
E-procurement (B2B)
E-collaboration (B2B)
Future Trends: Consideration for Business-to-Team (B2T) interactions.
Page 13: Business Goals
Objectives Include:
Cost reduction
Streamlined processes
Execution monitoring
Exception management
Timeliness in response.
Page 14: Business Trends
Categories of Interaction:
Scale and Time dimension
Intra-enterprise vs. Inter-enterprise
Manual vs. Electronic vs. Web interactions.
Page 15: IT Trends
Transitions from Mainframe to Sets of Services via a network.
Page 16: Integration Challenges
Diversity Issues: Varying operating systems, formats, and protocols among different parties.
Solution: Effective integration needed to automate supply chains.
Page 17: Types of Integration
Categories:
EAI (Enterprise Application Integration)
B2B (Business-to-Business)
B2C (Business-to-Consumer)
EDI (Electronic Data Interchange).
Page 18: Enterprise Application Integration (EAI)
Overview: Integration of existing applications to support business processes.
Integration Types:
User interface, Data, Method/Function, and Business Process.
Page 19: Overview of EAI Process
Components: Adapters facilitate data transformation between systems during business process execution.
Page 20: Business-to-Business (B2B) Integration
Definition: Integrating electronic data transmission between enterprises across various networks, both secured and unsecured.
Page 21: Overview of B2B Integration
Components:
Data transformation, security, and contract negotiation.
Page 22: Business-to-Consumer (B2C) Integration
Definition: Enables consumers to buy/sell goods & services online; example: Amazon.com.
Page 23: Electronic Data Interchange (EDI)
Definition: Facilitates inter-industry electronic transactions.
Standards Development: By the Accredited Standards Committee.
Page 24: Business Logic Defined
Concept: The sequence of functions necessary for achieving business goals.
Page 25: Example of Business Logic
Steps in Purchasing:
Determining goods, requesting quotes, purchasing, payment.
Phases:
Selection, Request, Purchase, Payment.
Page 26: Composition of Business Logic
Description: Integration of smaller processes into complex ones, defining flows and compensations.
Page 27: Workflow Management
Definition: Technology organizing processes between humans and legacy systems, comprised of sequential steps.
Page 28: Centralized vs. Peer-to-Peer (P2P) Workflows
Workflow Management System: Centralized organization of work processes.
P2P Model: Reflects conversational interactions in e-business settings.
Page 29: Workflow Example
Nodes: Input checks, quotations, and condition-based routing illustrate workflow structure.
Page 30: Integration through Middleware
Role of Middleware: Acts as an indirection layer that integrates transactions and simplifies interface design.
Page 31: Centralized Middleware Example
Features: Combines message brokers and adapters for interoperability in centralized workflows.
Page 32: P2P Middleware Example
Structure: Facilitates communication between disparate systems and clients.
Page 33: Multi-Middleware in P2P
Overview: Handles multiple interfaces and interactions between various parties and systems.
Page 34: Limitations of Conventional Middleware
Issues include lack of trust and standardization in cross-organizational contexts.
Page 35: Evolution of Web Services
Transformation: Leveraging global web technologies to unify integration methods beyond traditional middleware.
Page 36: Web Services Hype
Concerns: Many proposals lack clarity and effectiveness, overshadowing the true potential of web services.
Page 37: Advantages of Standardization
Simplification: Avoids multiple middleware infrastructures for various data interactions.
Page 38: Local Services and Web Services
Access: Web services serve as entry points for local service access across the internet.
Page 39: Enterprise Example of Web Services
Components: Integrates various applications for reduced heterogeneity and enhanced interaction.
Page 40: Comparison of Web Services and Object-Oriented (OO) Concepts
Similarities: Both concepts promote modularization and reusability.
Differences: Web services emphasize data/process separation, while OO binds them together.