SOA and SOA Governance Training Course

Key Concepts and Themes for Government

• What is Service-Oriented Architecture (SOA)?
• Choosing the Appropriate Architectural Style
• 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 for Government

• Constructing a Model of a Service
• WSDL-Defined Services
• 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 for Government

• 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 for Government

• 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

New and Updated Guidelines for Government

• 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 for Government

• 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 for Government

• 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 for Government

• 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 for Government?

• 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 Performance of Services

The SOA Governance Issue for Government

• Governance Appearing as SOA Initiatives
• A Dynamic Environment for Services to Interact
• Encouraging the Reuse of Services
• Controlling How Services Interact with Each Other

SOA Governance Stages for Government

• First: Realization That Governance Is Needed
• Second: Governance Improving Business Execution
• Third: Mixing Technology and Changes in Behavior
• Fourth: Technology Selection and Implementation

Service Management for Government

• Design-Time Perspective
• Run-Time Perspective
• Repository of Service for Reuse
• Services Contained in Heterogeneous Platforms
• Service-Virtualization for Run-Time Management of Services

Critical Governance Components for Government

• Service Registry Service and an Asset Repository
• Creating a "SOA Centre of Excellence"
• Focusing on Establishing SOA Organizational Guidelines
• The Organizational Maturity
• Agreed Governance Policies

SOA Governance Tools for Government

• Real-Time Monitoring of Events
• Failures in a BSM Framework
• Service-Level Instrumentation
• Hooking into Operational Management Systems
• Virtualization as Enabler to Separate Governance/Service Logic
• Service Virtualization Managed by Operational Staff

Developing Core SOA Governance for Government

• Why the SOA Technology Stack Has Grown Complex
• Mixing Between COTS and In-House Solutions
• Justifying External Consultants to Help Out
• Figuring Out Which Business We Are Really In

Roles and Responsibilities Involved in SOA Governance for Government

• Establishing a SOA Centre of Excellence
• Enterprise-Wide Planning and Assistance in Execution
• The Roles of the SOA Architect/Governance Architect
• Solving Potential Conflicting Interests
• Ensure That Governance Guidelines Are Followed

Barriers to SOA Governance for Government

• Not Realizing the Need for Governance
• Lack of Governance Technologies
• Lack of Service Virtualizations

State of Good Governance for Government

• Interaction with External Parties
• Managing Business Rules and BRE Management
• 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 for Government

• 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