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

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

Changes (2)

View Page History
h3. Motivation

Improve the quality and consistency of communication between the services. Ensure correct implementation of the services.

h3. Argumentation

Since the service requirements vary a lot, it makes sense to categorize the services from a technical perspective to be able to pinpoint and standardize necessary technology to ensure the quality and productivity.

h3. Exceptions/special cases


----
h3. Definitions

{include:KM:SOA - Service Categorization}

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}
Content moved to [OWSOA:P21. A service shall be categorized (OW SOA category)]