| Title: |
Documenting Service Behavior |
| Author: |
John Dodd |
| Publication Date: |
19 December 2007 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
This report investigates different techniques for specifying service behavior. The techniques are illustrated using the same example so they can be compared.
We conclude that natural language pre- and postconditions offer the best general-purpose technique for most audiences. But further techniques can be used to amplify this basic specification, and which technique this should be varies according to service characteristics.
The Addendum (published on the CBDI Forum Web site) explores some additional examples and demonstrates how the behavior can be specified using pre- and postconditions. |
| Backgrounder: |
This report investigates ways in which service behavior can be specified. Since a service is a collection of operations, we narrow the investigation down by examining different techniques for describing the behavior of an operation. This report will disregard what is usually termed the non-functional requirements of the service, and focus solely on what is commonly termed the ‘functional specification’ or ‘business logic’ of the operation.
To keep the report within bounds, the reader is assumed to be familiar with the following concepts:
- Service, Software Service and Operation
- Service Specification Architecture (aka Service View) and Architectural Layers
- Specified Dependency and its stereotypes message dependency and integrity dependency
- The Service Information Model (part of the Service Specification)
- Service Implementation Architecture (aka Implementation View)
- Automation Unit: its stereotypes encapsulated component and quasi-Component and the notion of implementation-only dependency. |
| Report Size: |
29 pages |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home