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 for government
  • Enter Service Oriented Architecture (SOA) for government
  • We Can Easily Change the Process for government
  • Changing Flow Using Legacy Approach for government
  • Replacing an Application for government
  • Other Advantages for government
  • Business Advantages for government
  • Adoption Stages for government

SOA Past and Present for Government

  • From XML to Web Service to SOA for government
  • How SOA was done before for government
  • Emerging standards for SOA for government
  • Compare SOA with other architectures for government

What is service oriented architecture? for government

  • What is 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 for government
  • The difference between model and methodology for government
  • Why use the Unified Modelling Language? for government
  • Identifying business processes for government
  • Notation, Patterns and Methodology for government
  • Which Methodology to choose? 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 interaction involving many services for government
  • Need for a coordinator service emerges for government
  • Birth of orchestration or business process for government
  • Composing processes using 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
  • Introductions to WS-* extensions for government
  • SOA tenets for government

Modelling SOA building blocks for government

  • Using UML to analyse and design interfaces for government
  • Generating a domain model for government
  • Implementing and realising Use Cases for government
  • Showing web service collaboration for government
  • 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 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 reference 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
  • Application service layer for government
  • Business service layer for government
  • 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.

 14 Hours

Number of participants


Price per participant

Testimonials (5)

Upcoming Courses

Related Categories