Skip to content
Skip to breadcrumbs
Skip to header menu
Skip to action menu
Skip to quick search
Quick Search
Browse
Pages
Blog
Labels
Attachments
Mail
Bookmarks
Activity
Advanced
Log In
Dashboard
KM: Service Oriented Architecture (SOA)
SOA Community Home
Governance
Design-Time Governance - SOA Design Rules
Design-Time Governance for H2A Services
Tools
A
ttachments (0)
Page History
Restrictions
Info
Link to this Page…
View in Hierarchy
View Wiki Markup
Design-Time Governance for H2A Services
Skip to end of metadata
Page restrictions apply
Added by
Thor Henning Hetland
, last edited by
Thor Henning Hetland
on Nov 01, 2008
(
view change
)
Comment:
Go to start of metadata
Unknown macro: {tasklist}
Design Rules
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
Labels parameters
Labels:
None
Enter labels to add to this page:
Looking for a label? Just start typing.