View Source

{composition-setup}

{section}
{column}
|| Policy rule || Doc status || H2A || A2A || ACS || CS || Last [PAB] discussion|
|[P1. A service shall have one named owner] | (x) | (+)| (+) | (+) | (+) | (off) |
|[P2. A service shall provide documented business value] | (x) | (+) | (+) | (+) | (+) | (off) |
|[P3. A service shall do one only thing, and one thing well] | (x) | (+) | (+) | (+) | (+) | (off) |
|[P4. A H2A service (webpart or portlet) shall be an independent component] | (x) | (+) | (-) | (-) | (-) | (off) |
|[P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services] | (x) | (+) | (-) | (-) | (-) | (off) |
|[P6. A H2A service shall not have internal workflow] | (/) | (+) | (-) | (-) | (-) | 2007.06.08 |
|[P7. Too generic webparts or portlets shall be avoided] | (x) | (+) | (-) | (-) | (-) | (off) |
|[P20. All services shall be in the service universe] | (x) | (-) | (+) | (+) | (+) | (off) |
|[P21. A service shall be categorized] | (x) | (+) | (+) | (+) | (+) | (off) |
|[P22. A service shall have an "authentication, authorization, endpoint strategy" ] | (x) | (-) | (+) | (+) | (+) | (off) |
|[P23. A service shall document its Service Level Agreement SLA (response time, availability++) ] | (x) | (-) | (+) | (+) | (+) | (off) |
|[P30. A service shall have a versioning strategy (ACS, CS) ] | (x) | (-) | (-) | (+) | (+) | (off) |
|[P31. A service shall provide for audit and monitoring of service usage]| (x) | (-) | (+) | (+) | (+) | (off) |
|[P32. A service shall document its Service Level Agreement SLA (response time=30ms, availability=99.995%) ] | (x) | (-) | (-) | (+) | (+) | (off) |
|[P40. A service shall provide at least one Evolving Service Endpoint] | (x) | (-) | (-) | (-) | (+) | (off) |
|[P41. A service shall provide heartbeat and traffic monitoring] | (/) | (+) | (+) | (+) | (+) | (off) |
|[P42. A Core service shall have orthogonal functionality ] | (x) | (-) | (-) | (-) | (+) | (off) |
|[P90. A service shall have a documented coupling to the contractual and requirement for service usage] | (x) | (+) | (+) | (+) | (+) | (off) |


* Attribution: This content is build on content from [http://wiki.community.objectware.no]

{column}
{column}
h3. [FAQ|Design-Time Governance - SOA Design Rules FAQ]

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


{column}
{section}


{deck:id=Design-Time Governance Policies / SOA Design Rules}

{card:label=Policy rules for Human to Application Services ([H2A])}
{navmap:policy_h2a|cellWidth=160|cellHeight=70}
{card}

{card:label=Policy rules for Application to Application Services ([A2A])}
{navmap:policy_a2a|cellWidth=160|cellHeight=70}
{card}

{card:label=Policy rules for Aggregated Core Services ([ACS])}
{navmap:policy_acs|cellWidth=160|cellHeight=70}
{card}

{card:label=Policy rules for Core Services ([CS])}
{navmap:policy_cs|cellWidth=160|cellHeight=70}
{card}

{deck}