Print this Page

Service-Oriented Analysis & Design (SOAD)
How to Design SOA Composite Applications using Patterns & Web Services

Management has committed to Services-Oriented Architecture.  Your architects have built a SOA.  They’ve selected and specified the “3 Ps”…Protocols, policies and platforms.  Now, it’s time for the business application designers and developers to actually create and construct the composite applications and Web Services that will run on the SOA.

How do they do that?

What’s different about designing composite applications & Web Services?

Service-Oriented Analysis & Design teaches how to identify business function patterns, analyze service candidates, and work through the design decisions to create Web services for use in a SOA composite application.  In this two-day seminar, participants will learn how to recognize and evaluate Web service candidates to ensure their business advisability, logical viability and technical feasibility.

Service-Oriented Analysis & Design examines the special issues of the application patterns commonly implemented in each major SOA stage:

  • Tactical Web Services: Data Integration, Portals, Manifolds & Legacy Wrappers

  • Internal SOA: Collections of Reusable & Shareable Web Services

  • External SOA: Software as a Service (SaaS) and B2B Cross-Organization Business Process Integration

Service-Oriented Analysis & Design explains how to design Web services that implement the principles and characteristics critical for Web service success:

  • Cohesion, to achieve autonomy

  • Generalization, to achieve extensibility

  • Abstraction, to achieve agility

  • Externalization, to achieve reusability

  • Standardization, to achieve interoperability

Service-Oriented Analysis & Design draws from the course developer’s experience assisting clients, from published reports and from vendor white papers to explore the current best practices and real-world issues organizations encounter as they design and deploy Web services.  Participants learn practical design approaches, including:

  • SOBA (Service-Oriented Business Applications)

  • SOAD (Service-Oriented Application & Design)

  • SODA (Services-Oriented Development of Applications)

  • Informal (but well proven) techniques developed by the course developer

Who Should Attend?

Staff members and managers who need a solid understanding of the principles and practices of designing Web Services and composite applications, including:

  • Analysis and design professionals, including Business Systems Analysts, Business Analysts and other related positions

  • Application development professionals, who design and build business applications

  • SOA Architects

  • Project Managers and Team Leaders guiding SOA application projects

  • IT Managers responsible application design and development

What Will You Learn?

How to analyze and validate the business advisability and technical feasibility of exposing business processes as Web services.

  • Identify SOA application project motivators, e.g. Re-use, Agility, Integration

  • Isolate and model business processes, including the current (as is) and potential re-engineered (can be) states

  • Recognize patterns and service candidates

  • Classify service candidate priorities, limitations and constraints

  • Determine if service candidate can be sufficiently generalized

  • Verify technical feasibility of service candidate

  • Decide whether service candidate can be successfully deployed within the technical architecture

Seminar Outline

Part 1: SOA Application Design Principles

  • Case Study Composite Application Example

  • Composite Application Architecture

    • Requestor & Consumer

    • Middle-Tier Roles & Responsibilities

    • Web Service

  • Web Service Principles & Characteristics

    • Cohesion

    • Generalization

    • Abstraction

    • Externalization

    • Standardization

Part 2: Tactical Web Service Patterns & Applications

  • Legacy Application SOAP Wrappers

    • How to apply the Web Service principles

      • Converting from tightly-coupled to loosely-coupled

      • Converting from synchronous to asynchronous

      • Converting from fine-grained to coarse-grained

    • Design decisions

      • What goes inside the wrapper?

      • What goes in the middle tier?

      • Should the wrapper become a Web Service?

      • Should you build or buy wrapper frameworks?

  • Cross-Platform Integration using SOAP

    • Wrapper

    • Native SOAP

  • Data Integration

    • Fundamental Design Issues

      • Data integrity: Transformation & Semantics

      • Data currency & performance

      • Business process relationship patterns

    • Data Manifolds: Many sources, one view

      • Solution steps

        • Define & expose

        • Semantic Abstraction

        • Creation of composite application

      • Semantic integrity & reconciliation

    • Portals: One source, many views

      • Data aggregation services

      • Data presentation services

Part 3: Internal SOA: Strategic collections of Web Services

  • Design Principles & Approaches

    • Business objective design drivers

      • Business process sharing and reuse

      • Business agility

      • Cost reduction via standardization

    • Design/Development Approaches

      • SOBA… Service-Oriented Business Application

      • SOAD (Service-Oriented Application & Design)

      • SODA (Services-Oriented Development of Applications)

      • SOHK (School of Hard Knocks)

  • Design Issues & Reality Checks

    • Methodology…Application potential & practicality

      • Identify & model Business Processes

      • Identify patterns & service candidates

      • Identify service priorities, limitations & constraints

    • Technology…Application feasibility

      • Analyze Web Service technical feasibility

      • Analyze architecture fit

    • Sociology…Application culture & organization

      • Service Governance & Oversight

      • Operational Governance & Stewardship

Part 4: External SOA: B2B Relationships throughout the Supply & Value Chains

  • Business objective design drivers

    • Business process integration

    • Single business façade

  • Design Issues

    • Long-running processes

      • Extended workflows

      • Stateful workflows

      • Asynchronous processes

    • Complex processes

      • Parallel service threads

      • Distributed workflows

      • Error detection, correction & compensation

  • Design Decisions, Considerations & Constraints

    • Crossing organizational boundaries

      • Shared ownership & governance

      • Shared stewardship

    • When should a process become a service?

      • Services invoking services

      • Web Service Coordination (WS-Coordination)

    • Extending Semantics from data to process

      • Consistent interpretation across organizations

      • Moving from Semantics to Description

    • Ontology

      • Identifying and defining relationships

      • Cross-organization ontology