Label: policy_h2a

Content with label policy_h2a in KM: Service Oriented Architecture (SOA) (See content from all spaces)
Related Labels: policy_cs, policy_a2a, policy_acs

Page: P1. A service shall have one named owner
Motivation Ensure that a service is managed and governed sufficiently. An umanaged service can't be relied upon, and will not be successful. Argumentation If you are unable to find an owner for a service, chances are high that the service is unimportant which is not a good metric for success. Also if a service ...
Other labels: policy_cs, policy_acs, policy_a2a
Page: P2. A service shall provide documented business value
Motivation If the service does not provide business value, it will never be of any use/interest Discussion In establishing the business value of a service, we can easily add the Key Performance Indicator for the service, and automatically monitor the generated value against the target values ...
Other labels: policy_cs, policy_acs, policy_a2a
Page: P21. A service shall be categorized (OW SOA category)
Motivation Improve the quality and consistency of communication between the services. Ensure correct implementation of the services. Argumentation Since the service requirements vary a lot, it makes sense to categorize the services from a technical perspective to be able to pinpoint and standardize necessary technology to ensure ...
Other labels: policy_cs, policy_acs, policy_a2a
Page: P3. A service shall do one only thing, and one thing well
Motivation We want to prevent service rot, duplication and loose coupled services, in other words good building blocks Argumentation If a service does more than one thing, it will likely not do everything well. The success ratio of a service correlates ...
Other labels: policy_cs, policy_acs, policy_a2a
Page: P4. A H2A service (webpart or portlet) shall be an independent component
Motivation We want the H2A services to be reusable building blocks. Argumentation WebParts and portlets shall be selfcontained components to be conform to the specification and to be reusable in different scenarios and contexts. It is also very important to be able to automatically test the service in isolation, which is almost ...
Page: P41. A service shall provide heartbeat and traffic monitoring
Motivation A heartbeat is necessary to be able pro actively react when a service is not responding according to SLA We want to keep track of the following: Does the service provide business value? Is the service functioning according to its SLA Where is a servicecomposition failing ...
Other labels: policy_cs, policy_acs, policy_a2a
Page: P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services
Motivation Argumentation It is the responsibility of the portlet framework/application to be the coordinating framework. If the H2A services start stepping on the toes of its surroundings, we end up with chaos. Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS ...
Page: P6. A H2A service shall not have internal workflow
Motivation H2A services are pieces. If the pieces includes a lot of internal workflow, they will loose their abillity for reuse, and are in all practical terms not services but applications. Argumentation We create a conflict of responsibility between services when the services start manipulating other services ...
Page: P7. Too generic webparts or portlets shall be avoided
Motivation We want our H2A services to be easy to use and to give great service/value. Argumentation Too generic webparts or portlets just moves the complexity to the configuration and shall be avoided. Usually these services are just a very thin presentation layer ...
Page: P90. A service shall have a documented coupling to the contractual and requirement for service usage
Motivation Argumentation Exceptions/special cases Definitions Producer Consumer requirement/contract Information requirements data quality (freshness, correctness, validness/timespan...) data usage rights (Licensing of data ) response time / availability usability o.l. peek (volume ...
Other labels: policy_cs, policy_acs, policy_a2a