Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review
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
}
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 -