Title: H2A View Source
Author:Thor Henning Hetland May 24, 2009
Last Changed by:Thor Henning Hetland Jul 06, 2009
Tiny Link: (useful for email) http://wiki.cantara.no/x/nYAf
Wiki Markup: [KM:H2A]
Operations: Copy 
Incoming Links
Open Knowledge Management (18)
    P42. A Core service shall have orthogonal functionality
    P21. A service shall be categorized
    P4. A H2A service (webpart or portlet) shall be an independent component
    P90. A service shall have a documented coupling to the contractual and requirement for service usage
    Laws of SOA
    P22. A service shall have an "authentication, authorization, endpoint strategy"
    P32. A service shall document its Service Level Agreement SLA (response time=30ms, availability=99.995%)
    P20. All services shall be in the service universe
    P30. A service shall have a versioning strategy (ACS, CS)
    P23. A service shall document its Service Level Agreement SLA (response time, availability++)
    Policy Advisory Board (PAB)
    P6. A H2A service shall not have internal workflow
    P7. Too generic webparts or portlets shall be avoided
    P41. A service shall provide heartbeat and traffic monitoring
    P3. A service shall do one only thing, and one thing well
    P40. A service shall provide at least one Evolving Service Endpoint
    P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services
    P31. A service shall provide for audit and monitoring of service usage
KM: Service Oriented Architecture (SOA) (1)
    SOA - Service Categorization
Hierarchy
Parent Page
    Policy Advisory Board (PAB)
Labels
There are no labels assigned to this page.
Hot Referrers
(2) search.live.com/results.aspx?q=services
Recent Changes
Time Editor  
Jul 06, 2009 19:36 Thor Henning Hetland view changes
May 24, 2009 12:08 Thor Henning Hetland  
All content on this wiki is licensed under a Creative Commons Attribution 3.0 Unported License.