2010•Unpublished venueRequires access

Supporting aspect-oriented component-based systems engineering

John Grundy

Open publisher page 4 citations

Abstract

Current approaches to component-based systems development do not adequately capture high-level knowledge about component provided and required services for use during design, implementation and run-time deployment. We describe a new approach to engineering such systems that characterises components by the various "aspects " of the overall system each component provides to or requires from end users or other components. These aspects include user interface, persistency, distribution, collaboration, inter-component relationships. Appropriate software architecture and CASE tool support is needed in order to effectively describe, reason about and implement this encoding of high level knowledge about components. We motivate the need for aspect-oriented component engineering, describe and illustrate our approach and its current software architecture and development tool support, and report on our component-based system development experiences. 1.

About this research paper

What this paper is about

Current approaches to component-based systems development do not adequately capture high-level knowledge about component provided and required services for use during design, implementation and run-time deployment. We describe a new approach to engineering such systems that characterises components by the various "aspects " of the overall system each component provides to or requires from end users or other components. These aspects include user interface, persistency, distribution, collaboration, inter-component relationships. Appropriate software architecture and CASE tool support is needed in order to effectively describe, reason about and implement this encoding of high level knowledge about components. We motivate the need for aspect-oriented component engineering, describe and illustrate our approach and its current software architecture and development tool support, and report on our component-based system development experiences. 1.

Why it matters

OpenAlex reports 4 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Current approaches to component-based systems development do not adequately capture high-level knowledge about component provided and required services for use during design, implementation and run-time deployment. We describe a new approach to engineering such systems that characterises components by the various "aspects " of the overall system each component provides to or requires from end users or other components. These aspects include user interface, persistency, distribution, collaboration, inter-component relationships. Appropriate software architecture and CASE tool support is needed in order to effectively describe, reason about and implement this encoding of high level knowledge about components. We motivate the need for aspect-oriented component engineering, describe and illustrate our approach and its current software architecture and development tool support, and report on our component-based system development experiences. 1.

Key concepts: Component (thermodynamics), Common Component Architecture, Computer science, Component-based software engineering, Software engineering, Software deployment, Systems engineering, Software development

Related papers

Back to paper searchBrowse research topicsOriginal source
Supporting aspect-oriented component-based systems engineering — Research Paper | ScholarLens