| Title: |
Practical Service Specification and Design Part 3: Specifying Services |
| Author: |
John Dodd |
| Publication Date: |
16 June 2005 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
Once the main requirements for a software service have been established, we recommend that a comprehensive service specification is put together. This defines the service interface, the quality of service, the standards followed and the functional service behavior. While this is demanding to produce, the rich specification remains of value throughout the service life cycle. Though it initially acts as an instruction to the developers and testers, it is subsequently utilized by the service consumers and solution architects. |
| Backgrounder: |
Before the specification effort begins in earnest, however, we need to have identified the service and gathered its main requirements. The first article4 in this series covered service identification, this being an aspect of Service Portfolio Planning. The second article concerned service requirements discovery: determining the operations needed, the service properties and quality requirements. This was split between two Journals, with Part 2a5 covering solutions-driven requirements, and Part 2b6 exploring provider-led service requirements. |
| Report Size: |
10 Pages |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home