A Version Model for Aspect Dependency Management

One observed characteristic of AOP is that it results in a large number of additional (coarse-grained to fine-grained) system units (aspects, concerns) ready to be composed to the final application. With this growing number of system units, the dependencies between them become vast and tangling. Our paper investigates this problem, proposes a more general model (version model) to capture different facets of AOP as well as a partial solution towards unit consistency based on versions.