Analyzing the use of interfaces in large OO projects

Authors:
Philip Mayer
Affiliations:
University of Hannover, Hannover, Germany
Venue:
OOPSLA '03 Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Year:
2003

Citing 2
Cited 3

Towards the systematic use of interfaces in JAVA programming

PPPJ '03 Proceedings of the 2nd international conference on Principles and practice of programming in Java
A radical revision of UML's role concept

UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard

Interface utilization in the Java Development Kit

Proceedings of the 2004 ACM symposium on Applied computing
Decoupling classes with inferred interfaces

Proceedings of the 2006 ACM symposium on Applied computing
On the automated modularisation of java programs using service locators

SC'12 Proceedings of the 11th international conference on Software Composition

Quantified Score

Hi-index	0.00

Visualization

Abstract

Using partial interfaces, i.e. interfaces that cover only a subset of the total set of published methods of a class, has several advantages, among them being an increase in understandability of the code and extended substitutability of classes in frameworks. However, analysis of large frameworks such as the Java API suggests that partial interfaces are only sparsely used. We believe that this is partly due to the fact that introducing and maintaining partial interfaces is perceived as tedious by programmers [5]. Therefore, we have created a metrics suite and tool support to assist the developer in using partial interfaces.