Hi John:

yes, our project bridges this gap but in the area of aspect-oriented
architectures.

We have the following aspects describing the software from
different architectural angles:

The Traversal aspect: described by strategy graphs,
The Structure aspect: described by UML class diagrams,
The Behavior (Modification) aspect: described by visitor classes,
The Synchronization aspect: described by coordinators,
The Object Representation aspect: described by decorated UML class diagrams.

We are in the process of developing a weaver technology, including
a generic weaver, which
combines the aspects and generates an executable program.

As generators we use the Java Compiler Compiler from Sun Test,
Demeter/Java built in our project and
we will use P3, a product from Don Batory's Genvoca project.

Our mappings are not that simple. They are on the Web,
in adaptive form, at URL:

http://www.ccs.neu.edu/research/demeter/DemeterJava/use/latest-demjava/

-- Karl
==========================
Has anyone looked at defining the gap between ADLs and input to
generators? Is this a simple mapping (from any specific ADL to any
specific generator)? Would it be useful to document this?

John
John Salasin
Program Manager
DARPA Information Technology Office
3701 North Fairfax Drive
Arlington, Virgina 22203
703-696-2318