Service Oriented Analysis and Design

Setting the right scope

• Modelling profile for SOA
• Guidance to be added to RUP
• 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 RUP for SOA

Service identification and specification

• Constructing a model of a service
• WSDL-defined services
• Developing service specifications
• Defining service providers
• Determining the granularity of a service
• A behavioural specification
• Policy specification
• Defining candidate services
• Refactoring services

Managing a service portfolio

• Applications as a 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 web 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

RUP Update

• The RUP update for SOA
• Models of a service-oriented solution
• New and updated workfare
• 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 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 modelling
• 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 modelling
• 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 SOA 2.0?
• What's next?