|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
ABSTRACT
When building a system by connecting components, the connection itself, the connector, becomes a hot-spot of abstraction for any interaction. In contrary to most existing component models, we introduce explicit connectors as first class architectural entities. They materialize detailed contracts regarding composition, deployment and interaction and hence provide fine granular information on composed structures. Using explicit connectors results in customtailored and consequently light-weight middleware, as any interaction logic is contained within them. Modeling component architectures with explicit connectors allows the usage of off-the-shelf connector libraries. Thereby, developing a distributed component based application becomes less complex and more competitive due to reduced costs and increased reliability. We contribute by adopting a model driven development process for the use of explicit connectors by extending the syntax of UML 2.0 and defining a set of required model transformations. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
General Terms:
|
|||||||||||||||||||||||||||||||