SOA and SOA Governance Training Course

Key concepts and themes

• Understanding SOA fundamentals
• Selecting the appropriate architectural style
• The "pipe and filter" architectural pattern
• Data type constraints and management
• The development lifecycle framework
• Achieving the correct level of abstraction
• Core themes within Rational Unified Process (RUP) for SOA

Service identification and specification

• Building service models
• WSDL-defined services
• Creating service specifications
• Defining service providers
• Determining service granularity
• Establishing behavioural specifications
• Policy specification requirements
• Identifying candidate services
• Refactoring existing services

Managing a service portfolio

• Viewing applications as dynamic entities
• Curating a portfolio of available capabilities
• Process-time binding techniques
• Run-time binding mechanisms
• Utilizing WSDL, XSD, and WS-Policy
• Executing the service portfolio management process
• Configuring Service Level Agreements (SLA) for web services

Partitioning service-oriented solutions

• Managing conceptual models
• Categorizing model elements
• Reviewing models with diverse stakeholders
• Effective use of packages
• Representing various views of the model
• Composite structures using UML 2.0
• Applying "parts" and "connectors"
• Partitioning managed services

New and updated guidelines

• Managing message attachments
• Designing effective messages
• Ensuring message schema consistency
• Service data encapsulation strategies
• Relationship data schema and service boundaries
• Implementing service mediation
• State management approaches
• Evaluating the merits of stateful versus stateless services
• Managing resource state
• Transitioning from services to service components
• Understanding the traditional design/implementation model

Message-centric design

• Focusing on the service domain
• Principles of domain engineering
• Applying object-oriented analysis and design
• Creating highly reusable models
• The traditional business-to-business context
• EDI standardization practices
• Hybrid message and service-centric approaches
• Conducting use case analysis
• Documenting functional requirements
• Leveraging business process models
• Defining non-functional requirements
• Maintaining a requirements database

Service-centric design

• Exposing functions aligned with business needs
• Revealing service provider operations
• Designing intuitive service interfaces
• Service-centric modelling techniques
• Adopting a use-case driven approach
• Understanding actor requirements
• Defining project goals from a business perspective
• The role of the software architect
• Policy information required by service consumers
• The role of the business executive
• Interacting with back-end systems
• Connecting services to implementation models
• Refining the service model iteratively
• Addressing performance concerns

Collaboration-centric design

• Facilitating collaborating services
• The process view of services
• Traditional business modelling
• Fulfilling roles within collaboration
• Partner Interchange Processes (PIPs)
• OAGIS standards
• Adopting a process-centric mindset
• Bridging the "business vs. IT gap"
• Handling "black box" activities
• Defining Key Performance Indicators (KPIs)
• Versioning and publishing models
• Generating metrics for monitoring
• Choreography language
• Business Process Execution Language (BPEL)
• Monitoring service operations

What is SOA Governance?

• Compliance with standards and legal regulations
• Change management processes
• Ensuring service quality
• Managing the service portfolio
• Oversight of the service lifecycle
• Using policies to restrict behavior
• Monitoring service performance

The SOA Governance issue

• Governance emerging within SOA initiatives
• Creating a dynamic environment for service interaction
• Encouraging service reuse
• Controlling inter-service interactions

SOA Governance Stages

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

Service Management

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

Critical governance components

• Service registry and asset repository
• Establishing a "SOA Centre of Excellence"
• Defining organizational SOA guidelines
• Assessing organizational maturity
• Agreed governance policies

SOA Governance tools

• Real-time event monitoring
• Handling failures within a BSM framework
• Service-level instrumentation
• Integrating with operational management systems
• Using virtualization to separate governance and service logic
• Service virtualization managed by operational staff

Developing core SOA governance

• Understanding the complexity of the SOA technology stack
• Balancing COTS and in-house solutions
• Justifying the need for external consultants
• Clarifying core business focus

Roles and responsibilities involved in SOA Governance

• Establishing a SOA Centre of Excellence
• Enterprise-wide planning and execution support
• The role of the SOA/governance architect
• Resolving conflicting interests
• Ensuring adherence to governance guidelines

Barriers to SOA governance

• Failing to recognize the need for governance
• Lack of governance technologies
• Insufficient service virtualization

State of good governance

• Interaction with external parties
• Managing business rules and BRE management
• Regulatory requirements for good governance
• Agreements repository
• Proactively embedding governance in the business
• Governance by action rather than by statement
• SLA monitoring to establish premium pricing

Critical success factors

• Considering governance early in the process
• Viewing governance as an evolving target
• Managing policies as entities with their own lifecycles
• Selecting an appropriate technology platform
• Ensuring the platform addresses immediate governance needs
• Securing future support as SOA infrastructure scales
• Enforcing service level agreements