2002Unpublished venueRequires access

Meta-component architecture for software interoperability

L.D. Sauer, Robert L. Clay, Rob Armstrong

Open publisher page 6 citations

Abstract

Most existing software is one-of-a-kind, monolithic, non-interoperable, and consequently, non-reusable. In addition, this software is difficult to maintain, improve, and scale. More importantly, this software is vital to many enterprises and institutions. Thus, enterprises must continuously make trade-off decisions between developing new software and maintaining existing software. The meta-component architecture (Component Mill) presented in the paper will enable enterprises to continue using existing software while providing a mechanism to migrate the software into a format (meta-component) that supports software integration and reuse. This architecture provides the blueprint for realizing an environment that supports exposing existing software for reuse with other (heterogeneous) software while allowing software development based on reuse. The metacomponents are independent of any component model used in component technologies. Thus, this architecture provides components that are, in principle, executable in any component technology.

About this research paper

What this paper is about

Most existing software is one-of-a-kind, monolithic, non-interoperable, and consequently, non-reusable. In addition, this software is difficult to maintain, improve, and scale. More importantly, this software is vital to many enterprises and institutions. Thus, enterprises must continuously make trade-off decisions between developing new software and maintaining existing software. The meta-component architecture (Component Mill) presented in the paper will enable enterprises to continue using existing software while providing a mechanism to migrate the software into a format (meta-component) that supports software integration and reuse. This architecture provides the blueprint for realizing an environment that supports exposing existing software for reuse with other (heterogeneous) software while allowing software development based on reuse. The metacomponents are independent of any component model used in component technologies. Thus, this architecture provides components that are, in principle, executable in any component technology.

Why it matters

OpenAlex reports 6 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

Most existing software is one-of-a-kind, monolithic, non-interoperable, and consequently, non-reusable. In addition, this software is difficult to maintain, improve, and scale. More importantly, this software is vital to many enterprises and institutions. Thus, enterprises must continuously make trade-off decisions between developing new software and maintaining existing software. The meta-component architecture (Component Mill) presented in the paper will enable enterprises to continue using existing software while providing a mechanism to migrate the software into a format (meta-component) that supports software integration and reuse. This architecture provides the blueprint for realizing an environment that supports exposing existing software for reuse with other (heterogeneous) software while allowing software development based on reuse. The metacomponents are independent of any component model used in component technologies. Thus, this architecture provides components that are, in principle, executable in any component technology.

Key concepts: Resource-oriented architecture, Computer science, Component-based software engineering, Software construction, Software engineering, Software development, Package development process, Reference architecture

Related papers

Back to paper searchBrowse research topicsOriginal source
Meta-component architecture for software interoperability — Research Paper | ScholarLens