Understanding Business Services

Link: http://feedproxy.google.com/~r/Soapbox/~3/kfUmxUtVhuE/understanding-business-services.html

From Richard Veryard on Architecture

A business service represents an agreed delivery of some parcel of capability from one agent to another agent.

Understanding services properly requires a combination of all six of the viewpoints I have defined for business architecture.

  • The capability viewpoint describes the parcel of capability
  • The activity viewpoint captures the delivery protocol
  • The responsibility viewpoint captures the agreement aspect
  • The motivation viewpoint covers the outcomes and performance measurement (especially relevant for outcome-based pricing) 
  • The knowledge viewpoint covers service semantics
  • The cybernetic viewpoint covers service governance

For more on these viewpoints, see my post Towards a Metamodel of Business Architecture.

There are many different types of service. In Services Like Laundry, I explored the laundry metaphor, suggesting that many services are a bit like laundry, and some services are
very much like laundry, but few services are totally like laundry. In Services Not All Like Laundry, I list some other types of service. Other useful classifications of service include Philip Boxer’s characterization of rcKP – services at the edge.

Services may be active or latent. An active service is one that is regularly or continuously used, so we can observe it in operation at any time. An active service is expected to provide value to the receiving agent whenever it is used. A latent service may be rarely needed, but its existence may be necessary for business continuity and risk management, and therefore provides value even when it is not used. Latent services may only be observed at exceptional times, such as in a crisis. Some businesses therefore run crisis simulations from time to time in order to exercise the latent services and check they are working.

Related topics: Business-as-a-Platform, Mashup, Pricing
An archive of Twitter debate on this blogpost was captured by Storify