Home > Research > Publications & Outputs > A “framework” for object oriented frameworks de...

Research

Links

Text available via DOI:

View graph of relations

A “framework” for object oriented frameworks design

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

A “framework” for object oriented frameworks design. / Parsons, David; Rashid, Awais; Speck, Andreas et al.
Technology of Object-Oriented Languages and Systems, 1999. Proceedings of. Washington, DC, USA: IEEE Computer Society, 1999. p. 141-151.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Parsons, D, Rashid, A, Speck, A & Telea, A 1999, A “framework” for object oriented frameworks design. in Technology of Object-Oriented Languages and Systems, 1999. Proceedings of. IEEE Computer Society, Washington, DC, USA, pp. 141-151. https://doi.org/10.1109/TOOLS.1999.779007

APA

Parsons, D., Rashid, A., Speck, A., & Telea, A. (1999). A “framework” for object oriented frameworks design. In Technology of Object-Oriented Languages and Systems, 1999. Proceedings of (pp. 141-151). IEEE Computer Society. https://doi.org/10.1109/TOOLS.1999.779007

Vancouver

Parsons D, Rashid A, Speck A, Telea A. A “framework” for object oriented frameworks design. In Technology of Object-Oriented Languages and Systems, 1999. Proceedings of. Washington, DC, USA: IEEE Computer Society. 1999. p. 141-151 doi: 10.1109/TOOLS.1999.779007

Author

Parsons, David ; Rashid, Awais ; Speck, Andreas et al. / A “framework” for object oriented frameworks design. Technology of Object-Oriented Languages and Systems, 1999. Proceedings of. Washington, DC, USA : IEEE Computer Society, 1999. pp. 141-151

Bibtex

@inproceedings{f981bf099851429db2171e551e2efa22,
title = "A “framework” for object oriented frameworks design",
abstract = "Object-oriented frameworks are established tools for domain-specific reuse. Many framework design patterns have been documented, e.g. reverse engineering framework architectures from conventionally built applications for a given domain. The framework development cycle generally evolves from an open framework to a closed application. We describe a more flexible component-based approach to framework design that stresses a common interface for `plugging-in' new components at different lifecycle stages. An analysis of framework-related user roles shows that the classical developer/end-user boundary is too rigid. We see the framework's development as a continuum within which its `actors' can customise its behavior. This both increases the system's flexibility and reduces its maintenance requirement. A case study of three frameworks for different application domains illustrates the presented principles.",
author = "David Parsons and Awais Rashid and Andreas Speck and Alexandru Telea",
year = "1999",
doi = "10.1109/TOOLS.1999.779007",
language = "English",
isbn = "978-0-7695-0275-5",
pages = "141--151",
booktitle = "Technology of Object-Oriented Languages and Systems, 1999. Proceedings of",
publisher = "IEEE Computer Society",

}

RIS

TY - GEN

T1 - A “framework” for object oriented frameworks design

AU - Parsons, David

AU - Rashid, Awais

AU - Speck, Andreas

AU - Telea, Alexandru

PY - 1999

Y1 - 1999

N2 - Object-oriented frameworks are established tools for domain-specific reuse. Many framework design patterns have been documented, e.g. reverse engineering framework architectures from conventionally built applications for a given domain. The framework development cycle generally evolves from an open framework to a closed application. We describe a more flexible component-based approach to framework design that stresses a common interface for `plugging-in' new components at different lifecycle stages. An analysis of framework-related user roles shows that the classical developer/end-user boundary is too rigid. We see the framework's development as a continuum within which its `actors' can customise its behavior. This both increases the system's flexibility and reduces its maintenance requirement. A case study of three frameworks for different application domains illustrates the presented principles.

AB - Object-oriented frameworks are established tools for domain-specific reuse. Many framework design patterns have been documented, e.g. reverse engineering framework architectures from conventionally built applications for a given domain. The framework development cycle generally evolves from an open framework to a closed application. We describe a more flexible component-based approach to framework design that stresses a common interface for `plugging-in' new components at different lifecycle stages. An analysis of framework-related user roles shows that the classical developer/end-user boundary is too rigid. We see the framework's development as a continuum within which its `actors' can customise its behavior. This both increases the system's flexibility and reduces its maintenance requirement. A case study of three frameworks for different application domains illustrates the presented principles.

U2 - 10.1109/TOOLS.1999.779007

DO - 10.1109/TOOLS.1999.779007

M3 - Conference contribution/Paper

SN - 978-0-7695-0275-5

SP - 141

EP - 151

BT - Technology of Object-Oriented Languages and Systems, 1999. Proceedings of

PB - IEEE Computer Society

CY - Washington, DC, USA

ER -