SOA and SOA Governance Training Course

Key concepts and themes

• Understanding SOA
• Selecting the appropriate architectural style
• The 'pipe and filter' architectural style
• Constraints on data types
• The development lifecycle
• Establishing the right level of abstraction
• Core themes covered in RUP for SOA

Service identification and specification

• Building a service model
• WSDL-defined services
• Developing service specifications
• Defining service providers
• Determining service granularity
• Behavioral specifications
• Policy specifications
• Identifying 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 web service

Partitioning service-oriented solutions

• Managing the models
• Categorizing elements
• Model reviews by diverse stakeholders
• Utilizing packages
• Representing views into the model
• Composite structures from UML 2.0
• Using 'parts' and 'connectors'
• Partitioning managed services

New and updated guidelines

• Managing message attachments
• Designing messages
• Ensuring message schema consistency
• Service data encapsulation
• Relationship data schema and service boundaries
• Service mediation
• State management
• Advantages of stateful versus stateless services
• Managing resource state
• Transitioning from services to service components
• The traditional design/implementation model

Message-centric design

• Focusing on the service domain
• Domain engineering
• Applying object-oriented analysis and design
• Producing highly reusable models
• The traditional business-to-business arena
• EDI standardization
• A hybrid message and service-centric approach
• Use case analysis
• Documenting requirements
• Utilizing business process models
• Non-functional requirements
• The requirements database

Service-centric design

• Exposing expected business functions
• Exposing operations of service providers
• Creating intuitive service interfaces
• Service-centric modeling
• Use-case driven approach
• Understanding actor needs
• Project goals from a business perspective
• Involvement of the software architect
• Policy information required by service consumers
• The role of the business executive
• Interaction with back-end systems
• Connecting services to the 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

What is SOA Governance?

• Compliance to standards or laws
• Change management
• Ensuring quality of services
• Managing the portfolio of services
• Managing the service lifecycle
• Using policies to restrict behavior
• Monitoring service performance

The SOA Governance issue

• Governance emerging through SOA initiatives
• A dynamic environment for service interaction
• Encouraging service reuse
• Controlling how services interact with each other

SOA Governance Stages

• First: Realizing the need for governance
• Second: Governance improving business execution
• Third: Mixing technology and behavioral changes
• Fourth: Technology selection and implementation

Service Management

• Design-time perspective
• Run-time perspective
• Repository of services for reuse
• Services contained in heterogeneous platforms
• Service virtualization for run-time management

Critical governance components

• Service registry and an asset repository
• Creating a 'SOA Centre of Excellence'
• Focusing on establishing SOA organizational guidelines
• Organizational maturity
• Agreed governance policies

SOA Governance tools

• Real-time monitoring of events
• Failures in a BSM framework
• Service-level instrumentation
• Hooking into operational management systems
• Virtualization as an enabler to separate governance/service logic
• Service virtualization managed by operational staff

Developing core SOA governance

• Why the SOA technology stack has grown complex
• Mixing COTS with in-house solutions
• Justifying external consultants
• Identifying the core business

Roles and responsibilities involved in SOA Governance

• Establishing a SOA Centre of Excellence
• Enterprise-wide planning and execution assistance
• Roles of the SOA architect/governance architect
• Solving potential conflicting interests
• Ensuring governance guidelines are followed

Barriers to SOA governance

• Not realizing the need for governance
• Lack of governance technologies
• Lack of service virtualizations

State of good governance

• Interaction with external parties
• Managing business rules and BRE mgmt
• Regulations for good governance
• The agreements repository
• Proactively embedding governance in the business
• Governance by action rather than by statement
• SLA monitoring to establish premium prices

Critical success factors

• Start thinking about governance early
• View governance as a moving target
• Manage policies as entities with their own lifecycles
• Choose a technology platform
• The platform should address immediate governance needs
• Future support as SOA infrastructure scales
• Enforce service level agreements