Component contracts in eclipse - a case study

Authors:
Jens Dietrich;Lucia Stewart
Affiliations:
School of Engineering and Advanced Technology, Massey University, New Zealand;School of Engineering and Advanced Technology, Massey University, New Zealand
Venue:
CBSE'10 Proceedings of the 13th international conference on Component-Based Software Engineering
Year:
2010

Citing 8
Cited 0

IDL: sharing intermediate representations

ACM Transactions on Programming Languages and Systems (TOPLAS)
IDL: the language and its implementation

IDL: the language and its implementation
Component software: beyond object-oriented programming

Component software: beyond object-oriented programming
Applying "Design by Contract"

Computer
Making Components Contract Aware

Computer
Uncovering Hidden Contracts: The .NET Example

Computer
Contributing to Eclipse: Principles, Patterns, and Plugins

Contributing to Eclipse: Principles, Patterns, and Plugins
On Analysis of Design Component Contracts: A Case Study

STEP '03 Proceedings of the Eleventh Annual International Workshop on Software Technology and Engineering Practice

Quantified Score

Hi-index	0.00

Visualization

Abstract

We present the results of an experiment investigating component collaborations in the OSGi/Eclipse component model. The aim of the experiment is to demonstrate the benefits of using a formal contract language. For this purpose, we have associated more than 1000 component collaborations in OSGi/Eclipse with formal contracts extracted from component metadata and extension point documentation. We discuss several characteristics of these contracts, including contract complexity, and verification results obtained with these contracts. To our surprise, there are numerous contract violations. This indicates that the use of a formal contract language can significantly improve the quality of dynamically composed systems.