Improve component-based programs with connectors

Authors:
Joachim H. Fröhlich;Manuel Schwarzinger
Affiliations:
Department of Business Informatics – Software Engineering, Johannes Kepler University of Linz, Linz, Austria;Racon Software GmbH, Linz, Austria
Venue:
JMLC'06 Proceedings of the 7th joint conference on Modular Programming Languages
Year:
2006

Citing 10
Cited 0

Design patterns: elements of reusable object-oriented software

Design patterns: elements of reusable object-oriented software
Software architecture: perspectives on an emerging discipline

Software architecture: perspectives on an emerging discipline
Objects, components, and frameworks with UML: the catalysis approach

Objects, components, and frameworks with UML: the catalysis approach
Towards a taxonomy of software connectors

Proceedings of the 22nd international conference on Software engineering
Component Software: Beyond Object-Oriented Programming

Component Software: Beyond Object-Oriented Programming
Architecture-Centric Software Project Management: A Practical Guide

Architecture-Centric Software Project Management: A Practical Guide
Documenting Software Architectures: Views and Beyond

Documenting Software Architectures: Views and Beyond
Programming.NET Components

Programming.NET Components
Maximizing .Net Performance

Maximizing .Net Performance
Pro Spring

Pro Spring

Quantified Score

Hi-index	0.00

Visualization

Abstract

Interfaces rather than components carry component-based software architectures. This follows directly from the design of component interfaces and contractual obligations before the implementation of components. We suggest separating component interfaces and component services such as protocol checking, synchronization, parallelization and caching into dedicated components which we call connectors. Connectors channel the communication so that components do not communicate directly with each other. Thus connectors foster the standardization of identifiable component contracts, accelerate the development of complementing or competing components, and improve the test ability, portability and maintainability of component-based programs.