Course Outline
A Service-Oriented Methodology for Government
- Introduction to a SOA Adoption Roadmap for Government
- Three Analysis Approaches for Government
- Service-Oriented Analysis for Government
Advantages of SOA for Government
- Traditional EAI Approach for Government
- Problems with Traditional EAI Approach in Government
- The Introduction of Service-Oriented Architecture (SOA) for Government
- We Can Easily Change the Process for Government
- Changing Flow Using a Legacy Approach for Government
- Replacing an Application for Government
- Other Advantages of SOA for Government
- Business Advantages of SOA for Government
- Adoption Stages for SOA in Government
SOA: Past and Present for Government
- The Evolution from XML to Web Services to SOA for Government
- How SOA Was Implemented Before for Government
- Emerging Standards for SOA in Government
- Comparing SOA with Other Architectures for Government
What is Service-Oriented Architecture for Government?
- Definition of SOA for Government
- Creating a Common Understanding of SOA for Government
- The Evolution of SOA for Government
- Introducing the Concepts of Services and SOA for Government
- Design Principles of SOA for Government
- The Relationship Between SOA and Web Services for Government
- The Advantages and Risks of SOA for Government
Introduction to Modelling and UML for Government
- Why Use Models with SOA in Government?
- The Difference Between Model and Methodology for Government
- Why Use the Unified Modeling Language (UML) for Government?
- Identifying Business Processes for Government
- Notation, Patterns, and Methodology for Government
- Selecting the Appropriate Methodology for Government
Introduction to Business Processes for Government
- How a Collection of Services Performs a Task for Government
- Simple Request-Response Interaction for Government
- Complex Interactions Involving Multiple Services for Government
- The Need for a Coordinator Service in Government
- The Emergence of Orchestration or Business Processes for Government
- Composing Processes Using the Business Process Execution Language (BPEL) for Government
- BPM-Based Solutions for Orchestration for Government
- Example Business Processes for Government
Web Services for Government
- Basic Web Services Elements for Government
- Core Web Services Standards Stack for Government
- The Importance of WSDL for Government
- The Design of SOAP for Government
- The Use of Registries via UDDI for Government
- The Basic Concepts of Service Orientation for Government
Distributing Services Across a Network for Government
- Aligning Functional and Non-Functional Requirements for Government
- The Role of Intermediaries in Service Networks for Government
- Introduction to WS-* Extensions for Government
- SOA Tenets for Government
Modeling SOA Building Blocks for Government
- Using UML to Analyze and Design Interfaces for Government
- Generating a Domain Model for Government
- Implementing and Realizing Use Cases for Government
- Showing Web Service Collaboration for Government
- The Usage of Communication Diagrams for Government
Enterprise Service Bus (ESB) for Government
- Objectives for Government
- Service Invocation for Government
- Legacy System Integration for Government
- Web Services to the Rescue for Government
- The Role of ESB in SOA for Government
- Security and ESB for Government
Process-Driven Services for Government
- Service Layer Abstraction for Government
- Introduction to the Business Process Layer for Government
- Process Patterns for Government
- Orchestration and Choreography for Government
- The Use of WS-BPEL for Process Automation for Government
Service-Oriented Reference Model for Government
- Reference Models and Architectures for Government
- The IMPACT SOA Reference Model and Architecture for Government
- SOA Vendors and Their Relationship with SOA for Government
- SOA Support in .NET and Java EE Platforms for Government
Layered Architecture for Government
- The Layers Pattern for Government
- Classic Three-Tier Architecture for Government
- Connecting to the Domain Layer for Government
- Linking to the User Interface for Government
- Using Packages to Decompose a System for Government
- Avoiding Mutual Dependencies for Government
- What is Layering and Why Do We Need It for Government?
- The Application Service Layer for Government
- The Business Service Layer for Government
- The Orchestration Service Layer for Government
Requirements
General knowledge of corporate IT systems is required. Knowledge of IT system integration may be beneficial for government applications.
Testimonials (5)
Trainer had a good rapport and was very helpful and kept it interesting; makes a big difference when learning.
Andy Johnston - QA Ltd
Course - REST API - a pattern of exchange of information between sites
It's a hands-on session.
Vorraluck Sarechuer - Total Access Communication Public Company Limited (dtac)
Course - Talend Open Studio for ESB
extensive knowledge cover many things.
metab alanazi - Saudi Arabian Monetary Authority
Course - Enabling SOA with BPM and BPMN
I really enjoyed the interactif.
Jan Lenie - APB
Course - Mule: Integrating Your Applications
The theory felt quite complete, we handled all important subjects. It was very nice we could zoom in on our use-case Achievements, which helped us with understanding the theory.