Architectural mismatch or why it's hard to build systems out of existing parts
Proceedings of the 17th international conference on Software engineering
Towards a taxonomy of architecture integration strategies
ISAW '98 Proceedings of the third international workshop on Software architecture
Software architecture classification for estimating the cost of COTS integration
Proceedings of the 21st international conference on Software engineering
Towards a taxonomy of software connectors
Proceedings of the 22nd international conference on Software engineering
The impact of component architectures on interoperability
Journal of Systems and Software
Developing New Processes for COTS-Based Systems
IEEE Software
Risk Reduction in COTS Software Selection with BASIS
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
Composing heterogeneous software architectures
Composing heterogeneous software architectures
Detecting architectural mismatches during systems composition
Detecting architectural mismatches during systems composition
Composable Process Elements for Developing COTS-Based Applications
ISESE '03 Proceedings of the 2003 International Symposium on Empirical Software Engineering
Extending the cocomo ii software cost model to estimate effort and schedule for software systems using commercial-off-the-shelf (cots) software components: the cocots model
A strategy for selecting multiple components
Proceedings of the 2005 ACM symposium on Applied computing
Software Connectors for Highly Distributed and Voluminous Data Intensive Systems
ASE '06 Proceedings of the 21st IEEE/ACM International Conference on Automated Software Engineering
Hi-index | 0.00 |
Software systems today are frequently composed from prefabricated commercial components that provide complex functionality and engage in complex interactions. Such projects that utilize multiple commercial-off-the-shelf (COTS) products often confront interoperability conflicts resulting in budget and schedule overruns. These conflicts occur because of the incompatible assumptions made by developers of these products. Identification of such conflicts and planning strategies to resolve them is critical for developing such systems under budget and schedule constraints. In this paper we present an attribute-based framework that can be used to perform automated interoperability assessment to filter out COTS product combinations whose integration will not be feasible within the project constraints. Our framework is built upon standard definitions of both COTS components and connectors and is intended for use by architects and developers during the design phase of a software system. Our preliminary experience in using the framework indicates an increase in interoperability assessment productivity by 50% and accuracy by 20%.