Name: Service Oriented Analysis and Design
Course Code: WA1369
Duration: 1
Scheduled Dates for WA1369
his course provides a brief introduction to the concepts of Service Oriented Architecture before going into the details of Service Oriented Analysis and Design. This course will help the participants understand how requirements are captured, business processes are modeled and services are identified. It describes the principles of service orientation. The principles will act like a checklist against which you can validate your own design.
* SOA Fundamentals
* Introduction to Service Oriented Analysis and Design (SOAD)
* Software Methodology
* Requirements management for SOA
* Business Process Modeling
* Service Identification
* Service Design and Implementation
* Process Implementation
* SOA Patterns
Target Audience
Business Analysts, developers, architects and any other technical IT staff involved in designing SOA applications.
Key Topics
- SOA Fundamentals
- - Service Oriented Architecture
- - What's a Service?
- - Example Services
- - Service Relationships/Roles
- - SOA and Business Process Implementation
- - Example Business Process
- - Traditional Integration Solution
- - SOA & Business Process
- - Need for Integration
- - Factors that Affect Integration
- - Challenges of Integration
- - Common Solution Implementations
- - Channel Implementation Choices
- - How SOA Does Integration
- - About Services in SOA
- - SOA Helps Business Address
- - Elements of a Service
- - SOA's Goal
- - The Value of Transitioning from Applications to Services
- - Is this a New Concept?
- - Service Architecture is
- - Interface Transparency
- - SOA Enhancements
- - Challenges to Services Assembly
- - Enterprise Service Bus (ESB)
- - ESB Features
- - Challenges in Process Implementation
- - SOA Capabilities
- - Web Services
- - Web Service and SOA
- - How Web Services Work
- - SOAP
- - SOAP HTTP Request Example
- - SOAP HTTP Response Example
- - UDDI
- Introduction to Service Oriented Analysis & Design (SOAD)
- - Introduction to SOAD
- - Applying OOAD Principles
- - Abstraction
- - Abstraction in SOAD
- - Encapsulation
- - Encapsulation in SOAD
- - Modularity
- - Modularity in SOAD
- - Hierarchy
- - Hierarchy in SOAD
- - Why OOAD is not Enough
- - Granularity
- - The Need for Loose Coupling
- - The SOAD Methodology
- - The SOAD Methodology Steps
- - Stage 1 - Process Modeling
- - Stage 2 - Service Identification
- - Stage 3 - Service Design & Implementation
- - Stage 4 - Process Implementation
- Software Methodology - RUP Approach
- - Software Methodology
- - The Rational Unified Process
- - Inception Phase
- - Elaboration Phase
- - Construction Phase
- - Transition Phase
- - Software Development Life Cycle and the Rational Unified Process
- - In a SOAD World
- - New Artifacts
- Stage 1 - Business Modeling and Use Cases
- - Stages of SOAD
- - Stage 1: Business Process Modeling
- - Requirements Workflow
- - What Is A Requirement?
- - Business Models
- - Use Cases
- - Example: Requirement For A Supply Chain Management Application
- - Classifying Use Cases
- - Use Case Modeling Steps
- - Finding Use Cases
- - Identified Use Cases or Business Processes
- - Finding Actors
- - Various Actors of: Supply Chain Management Application
- - Diagramming Use Cases
- - Example: Use Case Diagram in UML
- - UC1: Purchase Goods Use Case
- - Modeling the Business Processes
- - Use Case and Business Process
- - Trading Partner Design Pattern
- - Best Practices
- Stage 2 - Service Identification
- - Stages of SOAD
- - Identifying Services
- - Produce Service Specification
- - Functional Areas of The Business (a.k.a. Subsystems)
- - Services Belonging To These Functional Areas
- - Functionalities Belonging To These Services (User's Standpoint)
- - Documenting Service Hierarchy
- - Output of Stage 2
- - Retailer Service
- - The Service Is Further Described By Creating
- - Example of the WSDL File for the Retailer Service
- - Part Of The Schema File for the submitorder Operation
- - Best Practices
- Stage 3 - Service Design and Implementation
- - Stages of SOAD
- - Introduction
- - How is a Service Developed?
- - Top Down Development
- - Web Service Implementation Choices
- - Apply OOAD in New Service Development
- - Retailer System - Identifying System Level Use Cases
- - Finding Classes And Relationships From Use Cases
- - Noun/Verb Analysis
- - Example: Noun/verb Analysis
- - Refinement
- - Classes Identified for the Retailer Subsystem
- - Final List of Classes Identified for the Retail System
- - The Class Diagram
- - Class Notation in UML
- - Class Diagram The Retailer System
- - Top Down Summary
- - Bottom Up Development
- - Bottom Up Technology Choices
- - Example: JCA Based Service
- - Example: JAX-RPC Service
- - Data Mapping
- - Interface Mapping
- - Best Practices
- Stage 4 - Business Process Implementation
- - Stages of SOAD
- - Basics
- - Business Process Diagram
- - Challenges in Process Implementation
- - BPEL4WS
- - Partnership
- - Example: a Buy-Sell Partnership
- - Modeling Partnership in BPEL
- - Variables
- - Simple Activities
- - Invoke Activity
- - Structured Activities
- - Lifecycle of Process Development
- - Phase II Process Definition Details
- - Phase III Compilation Details
- - Phase IV Deployment Details
- - Phase V Business Process Execution
- - What is a Good Process Design?
- - Follow Integration Patterns
- - Example: A Simple Process
- - Additional Process Design Considerations
- Appendix A. Patterns
- - Patterns - Introduction
- - Patterns for e-business
- - Quick Note: Application Patterns
- - Quick Note: Runtime Patterns
- - SOA Patterns
- - Exposed Direct Connection Application Pattern
- - Exposed Direct Connection Runtime Pattern
- - Exposed Serial Process Application Pattern
- - Exposed Serial Process Runtime Pattern
- - Advantages of using a Service Bus
Objectives
- After completing this course, the student should be able to:
- * Describe the fundamentals of SOA
- * Understand the concepts and principles of SOAD and relate them to OOAD
- * Understand the various phases of SOAD
- * Get an overview of the Rational Unified Process (RUP) methodology to design and develop SOA based applications
- * Describe some patterns that can be used when designing SOA solutions
Required Skills/Experience
- Knowledge of what SOA is and its benefits. For example, the class Introduction to SOA (WA1405) Introduction to SOA is highly recommended as a prerequisite. Otherwise, no specific technical skill, such as Java or .NET is required.
Fee: $500.00
Course Schedule:
Back to Course Description
Austin
Charlotte
Columbia
Hunt Valley
Lansing
Madison
Milwaukee
Minneapolis
Oak Brook
Oklahoma City
Phoenix
Raleigh
San Antonio
Schaumburg
Tulsa
Washington DC
