SV: [gme-users] Transforming models into source code (e.g. C)

[Jesper Berthing]

Hi Attila,
 
I have installed GReAT and looked into the samples included in the distribution. It is difficult for me to see the big picture of how to construct and separate the transformation rules in the right way (where should I start). I will try to run the samples in the GReAT debugger.
 
I have read your paper (Model-Driven Software Development of Model-Driven Tools: A Visually-Specified Code Generator for Simulink/Stateflow), that describes how a SF model is transformed into source code, this is actually what I am looking for.
 
>From the paper I understand that the source code is generated directly using GReAT, could you describe the workflow of the tool implemented in GReAT? how you generate source code directly, if I understand the paper correctly.
 
>From looking at the interpreter and GReAT approach, I think that building an interpreter is the fastest approach right now. But I expect the source model to be extended through the development, so GReAT would probably be the right solution for us in the end. What you said in your recommendations.
 
You can email me if it is more appropriate at (berthing @ mci.sdu.dk)
 
Thanks for your recommendations,
Jesper

________________________________

Fra: gme-users-bounces at list.isis.vanderbilt.edu på vegne af Attila Vizhanyo
Sendt: ma 1/30/2006 5:09
Til: A list for GME users to share thoughts and discuss bugs and fixes.
Emne: Re: [gme-users] Transforming models into source code (e.g. C)



Hi Jesper,

> In relation to the above.
>
> What is the best approach in order to transform a model (e.g. state
> diagram) into source code (e.g. C, not BDD implementations)?
>
> 
>
> GME Interpreter (BON), GReAT or another approach.
>
Using GReAT is feasible whenever you feel there is a large semantic gap
between your input and output domains, and a complex algorithm is needed
to bridge that gap. You may consider to write the transformation in
C++/Java if the domains do not differ too much, or use code templates is
the output has signigicant static content in it. GReAT visualizes the
semantic mapping between the domains, and let you concentrate on the
transformation algorithm, instead of having you lost in implementation
details. On the downside, it has a steep learning curve you must
overcome when you write your first GReAT program. We have some good
tutorials and example GReAT programs enclosed in the GReAT package.

Thanks,
Attila



_______________________________________________
gme-users mailing list
gme-users at list.isis.vanderbilt.edu
http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 6270 bytes
Desc: not available
Url : http://list.isis.vanderbilt.edu/pipermail/gme-users/attachments/20060131/18b874ca/attachment.bin