Title: Design-Time Governance - SOA Design Rules View Source
Author:Thor Henning Hetland May 24, 2009
Last Changed by:Erik Drolshammer May 09, 2010
Tiny Link: (useful for email) https://wiki.cantara.no/x/rYAf
Wiki Markup: [KM:Design-Time Governance - SOA Design Rules]
Operations: E-mail  Copy 
Incoming Links
KM: Software Architecture (1)
    Page: Erik's core dump
Open Knowledge Management (1)
    Page: Laws of SOA
Hierarchy
Parent Page
    Home page: Knowledge Management Home
Children (19)
    Page: Design-Time Governance - SOA Design Rules FAQ
    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
Labels
Global Labels (1)
duplicate
Outgoing Links
External Links (1)
    wiki.community.objectware.no
Open Knowledge Management (20)
    Page: P30. A service shall have a versioning strategy (ACS, CS)
    Page: P42. A Core service shall have orthogonal functionality
    Page: P2. A service shall provide documented business value
    Page: P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services
    Page: P41. A service shall provide heartbeat and traffic monitoring
    Page: P31. A service shall provide for audit and monitoring of service usage
    Page: PAB
    Page: P4. A H2A service (webpart or portlet) shall be an independent component
    Page: P3. A service shall do one only thing, and one thing well
    Page: P22. A service shall have an "authentication, authorization, endpoint strategy"
    Page: P1. A service shall have one named owner
    Page: P40. A service shall provide at least one Evolving Service Endpoint
    Page: P23. A service shall document its Service Level Agreement SLA (response time, availability++)
    Page: P20. All services shall be in the service universe
    Page: P21. A service shall be categorized
    Page: P6. A H2A service shall not have internal workflow
    Page: P32. A service shall document its Service Level Agreement SLA (response time=30ms, availability=99.995%)
    Page: P7. Too generic webparts or portlets shall be avoided
    Page: P90. A service shall have a documented coupling to the contractual and requirement for service usage
    Page: Design-Time Governance - SOA Design Rules FAQ