The demand for software reuse is rather old and different approaches to support software reuse have been developed: patterns, modules, frameworks and component (architectures). Aspect-orientation deals with cross-cutting concerns and generative software engineering supports automatic system generation out of basic building blocks.

One problem, common to all of the aforementioned approaches, is how to model the different reusable assets (such as components, features or aspects) and the composition of assets. This problem partially occurs when dealing with, e.g., component interoperability, aspect weaving, feature interaction and (on a more abstract level) traceability between different views or models. Conventional object-oriented modelling languages (like the UML) are used for communicating users requirements and system designs, but fail to support the composition of separate parts or views.

One approach to deal with the reuse and related composition problem is to use models allowing to (a) check their interoperability, (b) support the configuration of assets, and (c) to predict properties of the assembled system (especially compliance with user requirements).

The workshop concentrates on this model-based approach to software reuse. As a result of the workshop the organisers like to see a common understanding on which properties such asset-models must have to ensure reuse and composition.

Last modified on May 20, 2002
Maintained by webmaster@2002.ecoop.org