Services Contract

1. Header
   
   1. Name: - The name of the service. Should indicate in general terms what it does, but not be the only definition
      
   2. Version - The version of this service contract
   
   
   3. RASI Attributes
      
      1. Responsible: Refers to the person(s) responsible for the deliverables produced — the "executor(s)." They're typically SOA project leaders, such as CIOs or enterprise architects
      
      
      2. Accountable: Characterizes the person who has the ultimate decision-making authority the "overseer."
      
      
      3. Consulted: Refers to the person(s) who must be consulted before action is taken. This is a two-way communication and occurs before an activity is completed.
      
      
      4. Informed: Characterizes those who should be informed that a decision or action is being taken. This is a one-way communication and may occur after an activity has been completed.
      
      
   4. Type - This is the type of service to help distinguish the layer it resides.
      
      1. Data
      
      
      2. Process
      
      
      3. Functionality
      
      
      4. Presentation

2. Functional




1. Functional Requirement - Indicates the functionality in specific bulleted items what exactly this service accomplishes

2. Service Operations


3. Infrastructure


4. Invocation - Indicates the invocation means of the service. This includes the URL, interface

1. SOAP


2. REST


3. Events Triggers

3. Non-Functional




1. Security Constraints - Defines who can execute this service in terms of roles or individual partners, etc.


2. Quality of Service -Determines the allowable failure rate


3. Transactional


4. Service Level Agreement - Determines the amount of latency the service is allowed to have to perform its actions<


5. Semantics - Dictates or defines the meaning of terms used in the description and interfaces of the service


6. Process, if applicable - Describes the process, if any, of the contracted service