Course Outline
There are many facets of an enterprise Service Oriented Architecture (SOA), each facet typically requiring in depth knowledge of its usage and proper application.
UML for SOA Modelling provides completeness through all levels of a SOA, from concepts through architecture to implementation. Our course uses a SOA reference architecture that adheres to the OASIS SOA reference model and implemented as a navigable UML model.
With SOA, computing architectures are expanding beyond object-oriented self-sufficiency and now allowing for highly specialized and interoperable computing consumer/producer relationships. We will explore the relationships between SOA and objects oriented paradigms, and analysis and design activities.
What you will learn:
1. Participants will experience the advantages of Service Oriented Architecture modelling.
2. Learn how to use UML to model business services.
3. You will understand the advantages of a standardized framework for developing quality components.
4. How to apply best practices or business ‘patterns’.
5. How do I manage my models?
6. I have an existing base of UML models, how do I translate them to schemas?
7. What methodology do I use to discover base elements of business process?
8. What are UML Profiles for SOA, XSD or UDDI?
9. What is the SOA Reference Model?
UML for SOA Training Course Outline
Setting the right scope
Modeling profile for SOA
Guidance to be added to RUP
Developing service-oriented solutions.
Choosing the level of abstraction
The WS-* specifications
Security
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 is an architectural style?
The "pipe and filter" style
Constraints on data types have
The development lifecycle
Providing an appropriate level of abstraction
Key themes addressed within RUP for SOA
Service identification and specification
Constructing a model of a service
WSDL-defined services
Developing service specifications
Defining service providers
The structural specification.
A behavioural 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
The service portfolio lifecycle
The service portfolio management process
Elaboration phase and construction phase
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
RUP Update
The RUP 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 artefacts
New and updated guidelines
Managing message attachments
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
EDI standardization
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 the RUP for SOA
How to plan the different phases.
When does the project end?
What about UML 2.0?
What’s next?
