Skip to end of metadata
Go to start of metadata

Motivation

Ensure that a service is managed and governed sufficiently. An umanaged service can't be relied upon, and will not be successful.

Argumentation

If you are unable to find an owner for a service, chances are high that the service is unimportant which is not a good metric for success. Also if a service does not have an owner, there is no one to form a service level agreement with, thus no one can give any guarantees about the quality of the service or its service contract. The closer to the business departments you find the owner, the better chances for a successful service.

Exceptions/spesial cases

In general all services must have an owner, if they are to be included in a SOA-environment.


Definitions

In doubt..

PAB discussions


Responsibillity for the owner

  • Ensure a high quality of the service: rollout patches and updates
  • Perform changes to the service in collaboration with consumers with special requirements

Examples of good ownership candidates for each service type

H2A

  • users - they have the natural incentive for enhancments

A2A

  • business owners,
  • product owners,
  • marketing directors

ACS

  • product owner
  • data owner
  • fallback: IT manager

CS

  • data quality owners
  • product owner
  • data owner
  • fallback: IT manager

Design-Time Governance - SOA Design Rules FAQ

  • [Question still to be asked..]
Labels:
policy_h2a policy_h2a Delete
policy_cs policy_cs Delete
policy_acs policy_acs Delete
policy_a2a policy_a2a Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.