Training

In London

£ 1,295 + VAT

Description

  • Type

    Training

  • Location

    London

  • Duration

    3 Days

Experience the advantages of UML in the context of SOA.
Suitable for: Business consultants, Business analysts, Project Managers, IT professionals.

Facilities

Location

Start date

London
See map
Grosvenor Gardens, 19, SW1

Start date

On request

About this course

Basic Windows knowledge, OO technology knowledge may be useful.

Questions & Answers

Add your question

Our advisors and other users will be able to reply to you

Who would you like to address this question to?

Fill in your details to get a reply

We will only publish your name and question

Reviews

Teachers and trainers (2)

Alain Dries

Alain Dries

Trainer

Van der Stighelen Philippe

Van der Stighelen Philippe

Trainer

Philippe Van der Stighelen is an independent consultant, lecturer and author. As a coach/consultant he has advised a multitude of organizations on designing their information processing and service oriented architecture. Worldwide, Philippe has built a very good reputation as a speaker on conferences and seminars. His lectures are always received with great enthusiasm and get excellent evaluations.

Course programme

"Everybody is going on about SOA, rushing into BPM tools and such, but the real focus should be on the development of basic services first, and then you will see real added value."

UML for SOA - 3 days

SOAD

The focus of any SOA initiative should be the development of highly cohesive and reusable services. Our service oriented analysis and design (SOAD) training gives a detailed overview of how UML and agile methodology can help you build services at the right level of granularity. We will focus on analysis and design of basic services which are considered mandatory for an SOA -after which more project-specific services are defined such as intermediate and process-centric services.

During this course, we also give a comprehensive insight into the importance of an architecture-first approach that allows the services to be put to the test as soon as possible, and possible risks retired early. You will learn the capabilities of an SOA maturity model, and you will gain insight into the added value of using advanced techniques such as service oriented development patterns and industry best practices.

course contents

We offer unparalleled training content by combining standard course material with extensive business knowledge and real-life examples.

What you will learn :

Setting the right scope

  • Modeling profile for SOA
  • Guidance to be added to the agile methodology
  • Developing service-oriented solutions
  • Choosing the level of abstraction
  • The WS-* specifications
  • UML for SOA: tangible advantages
  • Quality-of-service
  • Manageability
  • Using a UML Profile
  • UML profile for software services
  • OMG profile document
  • Using tools conforming to the profile
  • Guidance on SOA architecture & design topics
  • Extensibility mechanisms

Key concepts and themes

  • What is SOA?
  • What kind of architectural style to choose?
  • The "pipe and filter" style
  • Constraints on data types
  • The development lifecycle
  • Providing an appropriate level of abstraction
  • Key themes addressed within Agile for SOA

Service identification and specification

  • Analysis and design of a service
  • Use cases and services
  • Constructing a model of a service
  • The service contract
  • Developing service specifications
  • Defining service providers
  • Determining the granularity of a service
  • A behavioral specification
  • Policy specification
  • Defining candidate services
  • Refactoring services

Managing a service portfolio

  • Applications as dynamic entities
  • A portfolio of available capabilities
  • Process time-binding
  • Run-time binding
  • WSDL, XSD and WS-Policy
  • The service portfolio management process
  • Configuring an SLA for a service

Partitioning service-oriented solutions

  • Managing the models
  • Categorizing the elements
  • Different stakeholders reviewing the model
  • Using packages
  • Representing views into the model
  • Composite structure from UML 2.0
  • Using "parts" and "connectors"
  • Partitioning the managed services

Agile Update

  • The Agile update for SOA
  • Models of a service-oriented solution
  • New and updated workflows
  • Guidance for SOA solution construction
  • Identifying services
  • Responsibilities of the software architect
  • Service design
  • Designer tasks within analysis & design
  • New and updated artifacts

New and updated guidelines

  • Managing messages
  • Designing messages
  • Assuring consistency of message schema
  • Service data encapsulation
  • Relationship data schema - service boundaries
  • Service mediation
  • State management
  • The merits of stateful and stateless services
  • Managing resource state
  • Going from services to service components
  • The traditional design/implementation model

Message-centric design

  • Focus on the service domain
  • Domain engineering
  • Applying object-oriented analysis and design
  • Producing highly reusable models
  • The traditional business-to-business arena
  • Legacy and SOA
  • Hybrid message and service-centric approach
  • Use case analysis
  • Documenting requirements
  • Using business process models
  • Non-functional requirements
  • The requirements database

Service-centric design

  • Exposing functions expected of the business
  • Exposing operations of service providers
  • Making intuitive service interfaces
  • Service-centric modeling
  • Use-case driven approach
  • Understanding the needs of the actors
  • The project goals -from a business standpoint
  • Involvement of the software architect
  • Policy information, required by service consumers
  • The business executive role
  • Interaction with the back-end system
  • Connecting service to implementation model
  • Refining the service model
  • Addressing performance concerns

Collaboration-centric design

  • Collaborating services
  • Process view of the services
  • Traditional business modeling
  • Fulfilling roles in the collaboration
  • Partner Interchange processes (PIPs)
  • OAGIS standards
  • Process-centric mindset
  • The “business vs. IT gap"
  • "Black box" activities
  • Defining key performance indicators (KPIs)
  • Versioning and publishing a model
  • Producing metrics for monitoring
  • Choreography language
  • Business process execution language (BPEL)
  • Monitoring the services

Conclusions

  • When to use UML and Agile for SOA
  • How to plan the different phases
  • When does the project end?
  • What about SOA 2.0?
  • What’s next?

UML for SOA

£ 1,295 + VAT