| Title: |
Editorital: Rich Service Specification |
| Author: |
David Sprott |
| Publication Date: |
30 March 2009 |
| Report Type: |
Journal |
| Report Class: |
Editorial |
| 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 |
| Backgrounder: |
Last week we decided to make our rich service specification template available to all. We don’t think there’s any chance, or even need for a standard specification template. But we DO think there’s real merit in getting wider awareness of the need for some form of rich service specification. |
| Report Size: |
2 pages |
| Report Access Type: |
 | Bronze (FREE) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home