![]() |
|
||
|
|
|||
![]() |
| Report Summary |
| Title: | Design Pattern: Differentiated Service (Fewer Interfaces than Components) | ||
| Author: | Richard Veryard | ||
| Publication Date: | 1 December 2000 | ||
| Report Type: | |||
| Abstract: | One of the risks of component-based development is that it merely shifts the complexity from the component itself to the wiring between components. One way to avoid this danger is to control the proliferation of different interfaces. If there are significantly fewer interfaces than components, this simplifies the wiring -leading to greater adaptability for the component-based system, and greater reuse opportunities for individual components. Given that different users or applications typically have different (but overlapping) requirements, and may require the same service at different quality levels, the principle of fewer interfaces leads to the provision of different levels of service (with different non-functional specifications) through a single interface. This is known as differentiated service. | ||
| Report Access Type: |
|
||
| Available for separate purchase | Single copies of recent CBDI Journals may be purchased | ||
| Login |
|
| © Everware-CBDI Inc 1999-2008 |