P90. A service shall have a documented coupling to the contractual and requirement for service usage

h3. Motivation


h3. Argumentation


h3. Exceptions/special cases


----
h3. Definitions

h3. Producer - Consumer requirement/contract

* Information requirements
** data quality (freshness, correctness, validness/timespan...)
** data usage rights (Licensing of data ++)
** response time / availability
** usability o.l.
** peek (volume, traffic ..)
** error handling/response

* Service Level
** Expectations
** Agreement

----
Requirement - levels

{noformat}
Business
Consumer --> Producer

Semantics
Consumer --> Producer

Transport
Consumer --> Producer
{noformat}

{tip}
NB! SOA *consumer oriented*
{tip}


h3. Status

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

----
h3. PAB discussions


-----

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

{include:Design-Time Governance - SOA Design Rules FAQ}