Implementing reusable object-oriented components

Object oriented (OO) classes are generally not reusable because they are not meaningful in isolation; most classes only have meaning as members of cooperating suites of classes (e.g., design patterns). These suites usually arise in designs, but rarely exist as encapsulated entities in OO implementat...

Full description

Saved in:
Bibliographic Details
Published inProceedings. Fifth International Conference on Software Reuse (Cat. No.98TB100203) pp. 36 - 45
Main Authors Smaragdakis, Y., Batory, D.
Format Conference Proceeding
LanguageEnglish
Published IEEE 1998
Subjects
Collaboration
Collaborative work
Computer languages
Design methodology
Laboratories
Large-scale systems
Object oriented modeling
Object oriented programming
Protocols
Online AccessGet full text
ISBN9780818683770
0818683775
ISSN1085-9098
DOI10.1109/ICSR.1998.685728

Cover

More Information
Summary:Object oriented (OO) classes are generally not reusable because they are not meaningful in isolation; most classes only have meaning as members of cooperating suites of classes (e.g., design patterns). These suites usually arise in designs, but rarely exist as encapsulated entities in OO implementations. We present a method for directly mapping cooperating suites of classes into encapsulated C++ implementations. Our method is an improvement over the VanHilst and Notkin approach (M. VanHilst and D. Notkin, 1996) for implementing collaboration based designs and constitutes a step towards more reusable (object oriented) components.
ISBN:9780818683770
0818683775
ISSN:1085-9098
DOI:10.1109/ICSR.1998.685728