Design-Time Governance for H2A Services

Unknown macro: {tasklist}

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