The Concern Manipulation Environment

Matthew Chapman, IBM Hursley Park
William Chung, IBM T.J. Watson Research Center
Andrew Clement, IBM Hursley Park
Adrian Colyer, IBM Hursley Park
William Harrison, IBM T.J. Watson Research Center
Helen Hawkins, IBM Hursley Park
Vincent Kruskal, IBM T.J. Watson Research Center
Harold Ossher, IBM T.J. Watson Research Center
Tova Roth, IBM T.J. Watson Research Center
Stanley M. Sutton, Jr., IBM T.J. Watson Research Center
Peri Tarr, IBM T.J. Watson Research Center
Sian Whiting, IBM Hursley Park

Thursday, March 25, 11:00
Friday, March 26, 14:00

The Concern Manipulation Environment (CME) aims to provide a set of open, extensible components and a set of tools that promote aspect-oriented software development (AOSD) throughout the software lifecycle. It has two main goals. The first goal is to provide an open, integrated development environment (IDE) for those producing software using AOSD techniques throughout the software lifecycle, and to allow developers to use different AOSD approaches in an integrated manner. The second goal is to promote the rapid development of new tools supporting AOSD at any stage of the software lifecycle, and to serve as an integrating platform for such tools, enabling development and experimentation with new AOSD approaches.

This demonstration will highlight a number of tools that are useful to software developers and to AOSD tool providers and researchers. Tools for software developers include ones that identify, model and visualize concerns and aspects in software and relationships among software units (i.e., pieces of software artefacts of any type, including both code and non-code artefacts, including latent concerns or aspects that were not separated in the artefacts); that enable flexible queries over software; and that compose/integrate aspects and other concerns. Of interest to AOSD tool providers and researchers, the demonstration will describe some of the CME's support for integration of tools and approaches within the environment (highlighting the integration of AspectJ with the CME), and how to use the CME's extensible components to create new AOSD tools or prototypes more rapidly.