A service contract should have following components:
1. Header – The header specifies
a. Service Name & brief explanation
b. Service Contract Version
c. Owner or service in-charge
d. RACI (Responsible Accountable Consulted Informed)
i. Responsible - The people/person responsible for service deliverables.
ii. Accountable – The decision maker in service contract.
iii. Consulted – The person/members who are consulted before any action is taken. These people have say on the any decision taken.
iv. Informed – Person who must be informed about any decision or action taken. These people bear impact of decision, but have no control over the action.
e. Service Type (service layer) – It differs with implementations. Examples of service types are , business, presentation, data, integration and process.
2. Functional Aspects
a. Functional Requirement – It is stated in the Requirements Document. It indicates the functionality of highlighted items and what the service renders.
b. Service Operations – This describes the procedure, methods, actions the service renders.
c. Invocation – It tells how the given service can be invoked. It specifies URL, interface, multiple invocations (if any). There can be same functionality for internal/external clients, but these have different invocation means and interface. Examples-
3. Non-Functional Aspects
a. Security Constraints –This section describes accessibility (invocation mechanism) limitations of individuals and partners.
b. Quality of Service – It determines acceptable level of quality and allowable failure rate.
c. Transactional – This section describes if system is capable of acting as part of a larger transaction.
d. Service Level Agreement – It dictates degree of latency a service is allowed, to enable it perform certain actions.
e. Semantics – Semantics defines terms used in the contract.
f. Process – It elaborates any process in the contracted service.
Subscribe to this comment's feed
| < Prev | Next > |
|---|
