Dividing software systems in components improves software reusability as well as software maintainability. Components live at several levels, we concentrate on the implementation level where components are formed by source files, divided over directory structures. Such source code components are usually strongly coupled in the directory structure of a software system. Their compilation is usually controlled by a single global build process. This entangling of source trees and build processes often makes reuse of source code components in different software systems difficult. It also makes software systems inflexible because integration of additional source code components in source trees and build processes is difficult. This paper's subject is to increase software reuse by decreasing coupling of source code components. It is achieved by automized assembly of software systems from reusable source code components and involves integration of source trees, build processes, and configuration processes. Application domains include <em>generative programming</em>, <em>product-line architectures</em>, and <em>commercial off-the-shelf (COTS)</em> software engineering.

, , , , , ,
Software Engineering [SEN]
Software Analysis and Transformation

de Jonge, M. (2002). Source tree composition. Software Engineering [SEN]. CWI.