Behavior Protocols for Software Components
IEEE Transactions on Software Engineering
SOFSEM '02 Proceedings of the 29th Conference on Current Trends in Theory and Practice of Informatics: Theory and Practice of Informatics
Adapting Components with Mismatching Behaviours
CD '02 Proceedings of the IFIP/ACM Working Conference on Component Deployment
Automatic component protocol adaptation with the CoConut/J tool suite
Future Generation Computer Systems - Tools for program development and analysis
Trustworthy components-compositionality and prediction
Journal of Systems and Software - Special issue on: Component-based software engineering
Reliability prediction for component-based software architectures
Journal of Systems and Software - Special issue on: Software architecture - Engineering quality attributes
Reengineering standalone C++ legacy systems into the J2EE partition distributed environment
Proceedings of the 28th international conference on Software engineering
Trust-By-Contract: Modelling, Analysing And Predicting Behaviour Of Software Architectures
Journal of Integrated Design & Process Science
Empirical Research Similarity Metrics For Software Component Interfaces
Journal of Integrated Design & Process Science
Component contract-based formal specification technique
ICCSA'05 Proceedings of the 2005 international conference on Computational Science and Its Applications - Volume Part III
| Hi-index | 0.00 |
We present a new model of software component interfaces, using an extension of finite state machines to describe the protocol to use a component's offered services, and the sequences of calls to required external services. We focus on protocol interoperability: (a) Checking during system integration whether a component will be used according its protocol in its environment. (b) Adaptation of a component's provided services protocol, in case the environment does not offer all required resources. In this case, the adapted component still offers a subset of its services, opposed to today's component systems, which do not allow any integration in this case at all. (c) Computation the similarity of two interfaces, e.g., to see which legacy component fits some new requirements best. (d) Extension of component protocols by plug-ins during run-time in a correct, secure and reliable way. These algorithms are implemented in our CoCoNut/J-prototype.