Design-Time Governance - SOA Design Rules

Page: Design-Time Governance for H2A Services Page: P1. A service shall have one named owner Page: P2. A service shall provide documented business value Page: 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 Page: P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services Page: P6. A H2A service shall not have internal workflow Page: P7. Too generic webparts or portlets shall be avoided Page: P20. All services shall be in the service universe Page: P21. A service shall be categorized (OW SOA category) Page: P22. A service shall have an "authentication, authorisation, endpoint strategy" Page: P23. A service shall document its Service Level Agreement SLA (response time, availabillity++) Page: P30. A service shall have a versioning strategy (ACS, CS) Page: P31. A service shall provide for audit and monitoring of service usage Page: P32. A service shall document its Service Level Agreement SLA (response time=30ms, availabillity=99.995%) Page: P40. A service shall provide at least one Evolving Service Endpoint Page: P41. A service shall provide heartbeat and traffic monitoring Page: P42. A Core service shall have orthogonal functionality Page: P90. A service shall have a documented coupling to the contractual and requirement for service usage