Label: policy_cs

Content with label policy_cs in Open Knowledge Management (See content from all spaces)
Related Labels: policy_a2a, policy_acs

Page: P30. A service shall have a versioning strategy (ACS, CS)
Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () () () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ
Other labels: policy_acs, policy_a2a
Page: P31. A service shall provide for audit and monitoring of service usage
Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () () () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ
Other labels: policy_acs, policy_a2a
Page: P32. A service shall document its Service Level Agreement SLA (response time=30ms, availability=99.995%)
Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () () () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ
Other labels: policy_acs
Page: P40. A service shall provide at least one Evolving Service Endpoint
Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () (?) () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ
Other labels: policy_acs
Page: P42. A Core service shall have orthogonal functionality
Motivation Service behavior should be predictable and not produce bieffects in other services Argumentation Ensure that a services does its thing and not everything else.. Improved evolve ability of the service, as the impacts of change is understood. Exceptions/special cases Definitions If(!totto) Orthogonality ...