Representation inheritance: a safe form of "White box" code inheritance

There are two approaches to using code inheritance for defining new component implementations in terms of existing implementations. Black box code inheritance allows subclasses to reuse superclass implementations as-is, without direct access to their internals. Alternatively, white box code inherita...

Full description

Saved in:
Bibliographic Details
Published in:IEEE transactions on software engineering 1997-02, Vol.23 (2), p.83-92
Main Author: Edwards, S.H.
Format: Article
Language:English
Subjects:
Applied sciences
Behavior
Code reuse
Computer science
Computer science
control theory
systems
Computer Society
Designers
Encapsulation
Exact sciences and technology
Functional programming
Inheritances
Object oriented modeling
Object oriented programming
Programming profession
Protection
Safety
Software
Software engineering
Studies
Variables
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:There are two approaches to using code inheritance for defining new component implementations in terms of existing implementations. Black box code inheritance allows subclasses to reuse superclass implementations as-is, without direct access to their internals. Alternatively, white box code inheritance allows subclasses to have direct access to superclass implementation details, which may be necessary for the efficiency of some subclass operations and to prevent unnecessary duplication of code. Unfortunately, white box code inheritance violates the protection that encapsulation affords superclasses, opening up the possibility of a subclass interfering with the correct operation of its superclass methods. Representation inheritance is proposed as a restricted form of white box code inheritance where subclasses have direct access to superclass implementation details, but are required to respect the representation invariant(s) and abstraction relation(s) of their ancestor(s). This preserves the protection that encapsulation provides, while allowing the freedom of access that component implementers sometimes desire.
ISSN:0098-5589
1939-3520
DOI:10.1109/32.585498