Home > Research > Publications & Outputs > A generic component model for building systems ...

Electronic data

Links

Text available via DOI:

View graph of relations

A generic component model for building systems software

Research output: Contribution to Journal/MagazineJournal articlepeer-review

Published

Standard

A generic component model for building systems software. / Coulson, Geoffrey; Blair, Gordon; Grace, Paul et al.

In: ACM Transactions on Computer Systems, Vol. 26, No. 1, 1, 02.2008, p. 1-42.

Research output: Contribution to Journal/MagazineJournal articlepeer-review

Harvard

Coulson, G, Blair, G, Grace, P, Taiani, F, Joolia, A, Lee, K, Ueyama, J & Sivaharan, T 2008, 'A generic component model for building systems software', ACM Transactions on Computer Systems, vol. 26, no. 1, 1, pp. 1-42. https://doi.org/10.1145/1328671.1328672

APA

Coulson, G., Blair, G., Grace, P., Taiani, F., Joolia, A., Lee, K., Ueyama, J., & Sivaharan, T. (2008). A generic component model for building systems software. ACM Transactions on Computer Systems, 26(1), 1-42. [1]. https://doi.org/10.1145/1328671.1328672

Vancouver

Coulson G, Blair G, Grace P, Taiani F, Joolia A, Lee K et al. A generic component model for building systems software. ACM Transactions on Computer Systems. 2008 Feb;26(1):1-42. 1. doi: 10.1145/1328671.1328672

Author

Coulson, Geoffrey ; Blair, Gordon ; Grace, Paul et al. / A generic component model for building systems software. In: ACM Transactions on Computer Systems. 2008 ; Vol. 26, No. 1. pp. 1-42.

Bibtex

@article{bae48e4e15aa4c6c9b660ed6db3b1348,
title = "A generic component model for building systems software",
abstract = "Component-based software structuring principles are now commonplace at the application level; but componentization is far less established when it comes to building low-level systems software. Although there have been pioneering efforts in applying componentization to systems-building, these efforts have tended to target specific application domains (e.g., embedded systems, operating systems, communications systems, programmable networking environments, or middleware platforms). They also tend to be targeted at specific deployment environments (e.g., standard personal computer (PC) environments, network processors, or microcontrollers). The disadvantage of this narrow targeting is that it fails to maximize the genericity and abstraction potential of the component approach. In this article, we argue for the benefits and feasibility of a generic yet tailorable approach to component-based systems-building that offers a uniform programming model that is applicable in a wide range of systems-oriented target domains and deployment environments. The component model, called OpenCom, is supported by a reflective runtime architecture that is itself built from components. After describing OpenCom and evaluating its performance and overhead characteristics, we present and evaluate two case studies of systems we have built using OpenCom technology, thus illustrating its benefits and its general applicability.",
keywords = "design, standardization, management, component-based software, computer systems implementation, MIDDLEWARE",
author = "Geoffrey Coulson and Gordon Blair and Paul Grace and Francois Taiani and Ackbar Joolia and Kevin Lee and Jo Ueyama and Thirunavukkarasu Sivaharan",
year = "2008",
month = feb,
doi = "10.1145/1328671.1328672",
language = "English",
volume = "26",
pages = "1--42",
journal = "ACM Transactions on Computer Systems",
issn = "0734-2071",
publisher = "Association for Computing Machinery (ACM)",
number = "1",

}

RIS

TY - JOUR

T1 - A generic component model for building systems software

AU - Coulson, Geoffrey

AU - Blair, Gordon

AU - Grace, Paul

AU - Taiani, Francois

AU - Joolia, Ackbar

AU - Lee, Kevin

AU - Ueyama, Jo

AU - Sivaharan, Thirunavukkarasu

PY - 2008/2

Y1 - 2008/2

N2 - Component-based software structuring principles are now commonplace at the application level; but componentization is far less established when it comes to building low-level systems software. Although there have been pioneering efforts in applying componentization to systems-building, these efforts have tended to target specific application domains (e.g., embedded systems, operating systems, communications systems, programmable networking environments, or middleware platforms). They also tend to be targeted at specific deployment environments (e.g., standard personal computer (PC) environments, network processors, or microcontrollers). The disadvantage of this narrow targeting is that it fails to maximize the genericity and abstraction potential of the component approach. In this article, we argue for the benefits and feasibility of a generic yet tailorable approach to component-based systems-building that offers a uniform programming model that is applicable in a wide range of systems-oriented target domains and deployment environments. The component model, called OpenCom, is supported by a reflective runtime architecture that is itself built from components. After describing OpenCom and evaluating its performance and overhead characteristics, we present and evaluate two case studies of systems we have built using OpenCom technology, thus illustrating its benefits and its general applicability.

AB - Component-based software structuring principles are now commonplace at the application level; but componentization is far less established when it comes to building low-level systems software. Although there have been pioneering efforts in applying componentization to systems-building, these efforts have tended to target specific application domains (e.g., embedded systems, operating systems, communications systems, programmable networking environments, or middleware platforms). They also tend to be targeted at specific deployment environments (e.g., standard personal computer (PC) environments, network processors, or microcontrollers). The disadvantage of this narrow targeting is that it fails to maximize the genericity and abstraction potential of the component approach. In this article, we argue for the benefits and feasibility of a generic yet tailorable approach to component-based systems-building that offers a uniform programming model that is applicable in a wide range of systems-oriented target domains and deployment environments. The component model, called OpenCom, is supported by a reflective runtime architecture that is itself built from components. After describing OpenCom and evaluating its performance and overhead characteristics, we present and evaluate two case studies of systems we have built using OpenCom technology, thus illustrating its benefits and its general applicability.

KW - design

KW - standardization

KW - management

KW - component-based software

KW - computer systems implementation

KW - MIDDLEWARE

UR - http://www.scopus.com/inward/record.url?scp=40549141440&partnerID=8YFLogxK

U2 - 10.1145/1328671.1328672

DO - 10.1145/1328671.1328672

M3 - Journal article

VL - 26

SP - 1

EP - 42

JO - ACM Transactions on Computer Systems

JF - ACM Transactions on Computer Systems

SN - 0734-2071

IS - 1

M1 - 1

ER -