Title: PAB View Source
Author:Thor Henning Hetland Jun 10, 2008
Last Changed by:Thor Henning Hetland Apr 09, 2018
Tiny Link: (useful for email) https://wiki.cantara.no/x/XYCB
Wiki Markup: [OWSOA:PAB]
Operations: E-mail  Copy 
Incoming Links
KM: Service Oriented Architecture (SOA) (19)
    Page: P40. A service shall provide at least one Evolving Service Endpoint
    Page: P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services
    Page: P3. A service shall do one only thing, and one thing well
    Page: P90. A service shall have a documented coupling to the contractual and requirement for service usage
    Page: P42. A Core service shall have orthogonal functionality
    Page: P21. A service shall be categorized (OW SOA category)
    Page: P20. All services shall be in the service universe
    Page: P7. Too generic webparts or portlets shall be avoided
    Page: Old front page
    Home page: SOA Community Home
    Page: Design-Time Governance - SOA Design Rules
    Page: P22. A service shall have an "authentication, authorisation, endpoint strategy"
    Page: P32. A service shall document its Service Level Agreement SLA (response time=30ms, availabillity=99.995%)
    Page: P31. A service shall provide for audit and monitoring of service usage
    Page: P41. A service shall provide heartbeat and traffic monitoring
    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: P6. A H2A service shall not have internal workflow
    Page: P4. A H2A service (webpart or portlet) shall be an independent component
Hierarchy
Parent Page
    Page: Governance
Labels
Global Labels (1)
glossary
Outgoing Links
External Links (1)
    www.ietf.org/rfc/rfc2119.txt
KM: Service Oriented Architecture (SOA) (6)
    Page: Design-Time Governance - SOA Design Rules
    Page: CS
    Page: H2A
    Page: A2A
    Page: Governance
    Page: ACS