Communications of the ACM
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Architectural issues in software reuse: it's not just the functionality, it's the packaging
SSR '95 Proceedings of the 1995 Symposium on Software reusability
Architectural mismatch or why it's hard to build systems out of existing parts
Proceedings of the 17th international conference on Software engineering
Using adapters to reduce interaction complexity in reusable component-based software development
SSR '99 Proceedings of the 1999 symposium on Software reusability
A catalog of techniques for resolving packaging mismatch
SSR '99 Proceedings of the 1999 symposium on Software reusability
Domain analysis: an introduction
ACM SIGSOFT Software Engineering Notes
Component Software: Beyond Object-Oriented Programming
Component Software: Beyond Object-Oriented Programming
The Vienna Component Framework enabling composition across component models
Proceedings of the 25th International Conference on Software Engineering
A compositional formalization of connector wrappers
Proceedings of the 25th International Conference on Software Engineering
Patterns, frameworks, and middleware: their synergistic relationships
Proceedings of the 25th International Conference on Software Engineering
Systematic Component-Oriented development with Axiomatic Design
Journal of Systems and Software
Hi-index | 0.00 |
Efforts to integrate independently developed software components, to a large extent, have not been successful. Effective integration requires that component models agree on at least two different levels: "wiring"-level connectivity and semantic-level compatibility. While the use of adapters has been successful in dealing with the wiring-level, no viable approach exists for the semantic level. This is partly due to the availability of standards for components at the wire-level and the absence of similar standards at the semantic-level. In this paper we describe a framework for developing standards that deals with the semantic-level characteristic of components. Mismatches between components can then be eliminated systematically. Our approach is based on modeling a component with a set of three primary elements consisting of data, function, and control. An integration framework using this model automates the generation of mediating adapters. The framework provides developers with an abstract language, for specifying the required component interaction.