When objects collide experiences with reusing multiple class hierarchies

Authors:
Lucy M. Berlin
Affiliations:
Human-Computer Interaction Department, Hewlett-Packard Laboratories, 1501 Page Mill Rd., Palo Alto, CA
Venue:
OOPSLA/ECOOP '90 Proceedings of the European conference on object-oriented programming on Object-oriented programming systems, languages, and applications
Year:
1990

Citing 12
Cited 11

SMALLTALK-80: the interactive programming environment

SMALLTALK-80: the interactive programming environment
Object oriented programming: an evolutionary approach

Object oriented programming: an evolutionary approach
Proceedings of an Alvey Workshop on Methodology of window management

Proceedings of an Alvey Workshop on Methodology of window management
Hypertext: An Introduction and Survey

Computer
Common LISP: the language

Common LISP: the language
PCLOS: a flexible implementation of CLOS persistence

on ECOOP '88 (European Conference on Object-Oriented Programming)
A programmer's guide to object-oriented programming in Common LISP

A programmer's guide to object-oriented programming in Common LISP
Problem-solution mapping in object-oriented design

OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Modular implementation of presentations

CHI '87 Proceedings of the SIGCHI/GI Conference on Human Factors in Computing Systems and Graphics Interface
An overview of C++

OOPWORK '86 Proceedings of the 1986 SIGPLAN workshop on Object-oriented programming
User-Interface Management Control and Communication

IEEE Software
THE X WINDOW SYSTEM

THE X WINDOW SYSTEM

Combination of inheritance hierarchies

OOPSLA '92 conference proceedings on Object-oriented programming systems, languages, and applications
Towards a methodology for explicit composition of metaobjects

Proceedings of the tenth annual conference on Object-oriented programming systems, languages, and applications
The effects of the business model on object-oriented software development productivity

IBM Systems Journal
Components, frameworks, patterns

Proceedings of the 1997 symposium on Software reusability
Framework integration problems, causes, solutions

Communications of the ACM
Integrating independent components with on-demand remodularization

OOPSLA '02 Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Integrating Independently-Developed Components in Object-Oriented Languages

ECOOP '93 Proceedings of the 7th European Conference on Object-Oriented Programming
A survey of object-oriented reuse

CASCON '95 Proceedings of the 1995 conference of the Centre for Advanced Studies on Collaborative research
Model checking the behavior of frameworks extended with other frameworks

OOPSLA '05 Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Software extension and integration with type classes

Proceedings of the 5th international conference on Generative programming and component engineering
Encapsulating and exploiting change with changeboxes

ICDL '07 Proceedings of the 2007 international conference on Dynamic languages: in conjunction with the 15th International Smalltalk Joint Conference 2007

Quantified Score

Hi-index	0.02

Visualization

Abstract

Well-designed reusable class libraries are often incompatible due to architectural mismatches such as error-handling and composition conventions. We identify five pragmatic dimensions along which combinations of subsystems must match, and present detailed examples of conflicts resulting from mismatches. Examples are drawn from our experiences of integrating five subsystem-level class hierarchies into an object-oriented hypertext platform. We submit that effective reuse will require that these pragmatic decisions be explicitly identified in descriptions of reusable software. Such descriptions will enable developers to identify and combine subsystems whose architectures are compatible.