loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Designing Extensible Classes
September/October 2007 (vol. 24 no. 5)
pp. 15-17
ASCII Text
x 
 
Rebecca J. Wirfs-Brock, "Designing Extensible Classes," IEEE Software, vol. 24, no. 5, pp. 15-17, September/October, 2007.
 
 
BibTex
x
 
@article{ 10.1109/MS.2007.137,
author = {Rebecca J. Wirfs-Brock},
title = {Designing Extensible Classes},
journal ={IEEE Software},
volume = {24},
number = {5},
issn = {0740-7459},
year = {2007},
pages = {15-17},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2007.137},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Designing Extensible Classes
IS - 5
SN - 0740-7459
SP15
EP17
EPD - 15-17
A1 - Rebecca J. Wirfs-Brock,
PY - 2007
KW - class
KW - subclass
KW - abstractions
VL - 24
JA - IEEE Software
ER -
 
Rebecca J. Wirfs-Brock, Wirfs-Brock Associates
Building clean abstractions with clearly defined extension points is satisfying, but the best design choice isn't always obvious. How much access should you give a subclass to a class's inner workings? How much freedom should you give a subclass designer to "bend" inherited behaviors to make a new abstraction fit in or to extend an existing one? These decisions involve nuanced reasoning. The contract between a class and its subclasses requires thoughtful design, experimentation, and careful specification.
Index Terms:
class, subclass, abstractions
Citation:
Rebecca J. Wirfs-Brock, "Designing Extensible Classes," IEEE Software, vol. 24, no. 5, pp. 15-17, Sep./Oct. 2007, doi:10.1109/MS.2007.137
Usage of this product signifies your acceptance of the Terms of Use.