• Browse
  • Pages
  • Blog
  • Labels
  • Attachments
  • Mail
  • Bookmarks
  • Activity
  • Advanced
• Log In

1. Dashboard
2. KM: Service Oriented Architecture (SOA)
3. SOA Community Home
4. Governance
5. Design-Time Governance - SOA Design Rules

Design-Time Governance - SOA Design Rules

Skip to end of metadata

• Page restrictions apply
• Added by Thor Henning Hetland, last edited by Thor Henning Hetland on Feb 23, 2012  (view change)

Comment:

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..]

P1. A service shall have one named owner	P2. A service shall provide documented business value	P21. A service shall be categorized (OW SOA category)	P3. A service shall do one only thing, and one thing well	P4. A H2A service (webpart or portlet) shall be an independent component
P41. A service shall provide heartbeat and traffic monitoring	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	P7. Too generic webparts or portlets shall be avoided	P90. A service shall have a documented coupling to the contractual and requirement for service usage

P1. A service shall have one named owner	P2. A service shall provide documented business value	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++)	P3. A service shall do one only thing, and one thing well	P30. A service shall have a versioning strategy (ACS, CS)	P31. A service shall provide for audit and monitoring of service usage	P31. A service shall provide for audit and monitoring of service usage
P41. A service shall provide heartbeat and traffic monitoring	P90. A service shall have a documented coupling to the contractual and requirement for service usage

P1. A service shall have one named owner	P2. A service shall provide documented business value	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++)	P3. A service shall do one only thing, and one thing well	P30. A service shall have a versioning strategy (ACS, CS)	P30. A service shall have a versioning strategy (ACS, CS)	P31. A service shall provide for audit and monitoring of service usage
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, availability=99.995%)	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
P90. A service shall have a documented coupling to the contractual and requirement for service usage

P1. A service shall have one named owner	P2. A service shall provide documented business value	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++)	P3. A service shall do one only thing, and one thing well	P30. A service shall have a versioning strategy (ACS, CS)	P30. A service shall have a versioning strategy (ACS, CS)	P31. A service shall provide for audit and monitoring of service usage
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, availability=99.995%)	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	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	P42. A Core service shall have orthogonal functionality	P90. A service shall have a documented coupling to the contractual and requirement for service usage

Labels parameters

Labels:

None

featured featured Delete

glossary glossary Delete

Enter labels to add to this page:

 

Looking for a label? Just start typing.

19 Child Pages

Reorder Pages

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

Powered by a free Atlassian Confluence Community License granted to Cantara AS. Evaluate Confluence today.

• Powered by Atlassian Confluence 3.5.17, the Enterprise Wiki
• Printed by Atlassian Confluence 3.5.17, the Enterprise Wiki.
•   |  Report a bug
•  |  Atlassian News