Page:
P1. A service shall have one named owner
(Open Knowledge Management)
Content moved to OWSOA:P1. A service shall have one named owner DesignTime Governance SOA Design Rules FAQ
|
Page:
P2. A service shall provide documented business value
(Open Knowledge Management)
Content moved to OWSOA:P2. A service shall provide documented business value
|
Page:
P20. All services shall be in the service universe
(Open Knowledge Management)
Content moved to OWSOA:P20. All services shall be in the service universe
|
Page:
P21. A service shall be categorized
(Open Knowledge Management)
Content moved to OWSOA:P21. A service shall be categorized (OW SOA category
|
Page:
P22. A service shall have an "authentication, authorization, endpoint strategy"
(Open Knowledge Management)
Content moved to OWSOA:P22. A service shall have an "authentication, authorisation, endpoint strategy
|
Page:
P23. A service shall document its Service Level Agreement SLA (response time, availability++)
(Open Knowledge Management)
Content moved to OWSOA:P23. A service shall document its Service Level Agreement SLA (response time, availabillity
|
Page:
P3. A service shall do one only thing, and one thing well
(Open Knowledge Management)
Content moved to OWSOA:P3. A service shall do one only thing, and one thing well
|
Page:
P4. A H2A service (webpart or portlet) shall be an independent component
(Open Knowledge Management)
Content moved to OWSOA:P4. A H2A service (webpart or portlet) shall be an independent component
|
Page:
P41. A service shall provide heartbeat and traffic monitoring
(Open Knowledge Management)
Content moved to OWSOA:P41. A service shall provide heartbeat and traffic monitoring
|
Page:
P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services
(Open Knowledge Management)
Content moved to OWSOA:P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services
|
Label: deletable