RE: [Andromda-devel] Roadmap, Development Plan

[seba]

Hi Tony,

I'm writing my reaction below, as I'm thinking (for about a week ago) of choosing androMDA as support for an UML-to-process_calculus translation; I have some XMI-based algorithms (based on DOM accessing) for extracting, relating and formatting information about elements of the UML model; it is also diagram directed, in the sense that there are specific semantic equivalences for class, activity and collaboration diagrams.

So, this is some good news you're giving here (about the activity diagram, "the workflow" generation cartridge, at least for me )...

Juergen,

I actually plan to develop a new cartridge, document the process of that
in this mailing list, and produce developers guide for cartridge development
from the contents of those emails.  I have two cartridges in mind

1) XML Schema Docuemnt (XSD) generation cartridge
2) A workflow generation cartridge from Activity Diagrams

Item 1 is the easy task and I need that functionality immediately. But unfortunately
it would be yet another cartridge that uses only static model elements (classes,
packages).

Item 2 is more interesting, and would make use of something other than just
Static Object model elements and that was my reason in the first place for
porting  AndroMDA to the Netbean MetaDataRepository.

Tony

You told me also before that having support for "anything other than a class diagram you
almost certainly will want to write your own scriptHelper".
So, what you're saying above about the workflow etc, would concern this, I suppose?
I mean you want yourself to develop a ScriptHelper for activity diagram - which would be nice, again .

And is the idea of the 2)nd cartridge somehow related with template engine interchangeability
(I saw in some previous emails)? I also posted a feature request about this kind .

Thanks
Sebastian

<<attachment: smiley-3.png>>