Service-Oriented Architecture Governance for the Services Driven Enterprise

1.11. ADDRESSING SOA STAKEHOLDER BIASES

Governance is essential to represent the needs of your stakeholders. However, you must realize that while all stakeholder perspectives are valid, they must be balanced with the needs and requirements of the enterprise. There are some natural SOA stakeholder biases to watch for as you begin formulating your SOA governance model:

• Services Governance. Focus is too narrow in scope: Many SOA governance enthusiasts mistakenly restrict SOA governance focus to governing services from a technical design- or runtime perspective. In this mode, the focus tends to be technical service design, service interface design, and service implementation.

• SOA Security Emphasis. While critical, security often focuses only on technology issues and not business or process issues, and does not encompass organizational requirements or business decisions.

• Partial SDLC Governance. Design-time bias or run-time/operations bias: Another common stakeholder bias derives from focusing on either design-time governance of services, which emphasizes compliance to architecture and technical design standards, or on run-time governance, which emphasizes operational requirements for performance, quality of service (QoS), service-level agreements (SLA), and security. IT Bias: SOA governance focused on optimizing IT goals, which often are concentrated on service reuse, design-time governance, and architecture and technical compliance. These biases tend to emphasize provider-side goals ...