Design-Time Governance - SOA Design Rules

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

FAQ

  • [Question still to be asked..]
Labels:
featured featured Delete
glossary glossary Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.