Design-Time Governance for A2A Services

0%

A2A Design Rules

P1. A service shall have one named owner	P2. A service shall provide documented business value	P20. All services shall be in the service universe	P21. A service shall be categorized (OW SOA category)	P22. A service shall have an "authentication, authorisation, endpoint strategy"
P23. A service shall document its Service Level Agreement SLA (response time, availabillity++)	P3. A service shall do one only thing, and one thing well	P30. A service shall have a versioning strategy (ACS, CS)	P31. A service shall provide for audit and monitoring of service usage	P31. A service shall provide for audit and monitoring of service usage
P41. A service shall provide heartbeat and traffic monitoring	P90. A service shall have a documented coupling to the contractual and requirement for service usage