Concepts for Describing Composition of Software Artifacts

This paper treats the “compositor” component as a new, distinct, kind of software component. This is analogous to recognizing that compilers, parsers, and UI-generators are distinct kinds of software components. Each has its own domain of discourse and base of concepts, its own structure for expressing desired results, its own internal solution structure, and its own set of research problems. This paper describes a base of concepts suitable for expressing composition and shows how a general composition engine realizing these concepts can be used to effect the composition needs of several existing AOSD approaches.

By: William Harrison, Harold Ossher, Peri Tarr

Published in: RC23345 in 2004


This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.


Questions about this service can be mailed to .