Version 1 by Thor Henning Hetland
on Jul 06, 2009 17:10.

compared with
Current by Bård Lind
on Apr 04, 2011 15:48.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
h3. Motivation

We want to prevent service rot and duplication of services

h3. Argumentation

If a service does more than one thing, it will likely not do everything well. The success ratio of a service correlates nicely with the characteristics of reusable code, namely code which does one thing, and one thing well :)



h3. Exceptions/special cases


----
h3. Definitions


h3. Status

|| Doc status || [H2A] || [A2A] || [ACS] || [CS] || Last [PAB] discussion ||
| (/) | (+) | (-) | (-) | (-) | 2007.06.08 |


----
h3. PAB discussions

Can a H2A service to too little? We should add a new checklist item which ensures that we provide enough business value..

-----

h3. [Design-Time Governance - SOA Design Rules FAQ]

{include:Design-Time Governance - SOA Design Rules FAQ}
Content moved to [OWSOA:P3. A service shall do one only thing, and one thing well]