I would like to implement MDA with a fully formal language instead of UML as modeling language but I am out of ideas. My idea is to have a full MDA implementation, transforming a very abstract model to code. I have studied few customized UML profiles with stereotypes, but those made the model development rather unconventional and also UML is not precise enough.
Any idea would be appreciated.
Nick: Very thanks for the answer.
Can not we generate systems' Business Logic (apart from those abstract design implementations) from, for example, Activity Diagram which specifies the Business Processes and Sequential Diagrams?
Is it so that they are not detailed enough?
In my example, however, I need a Formal Tool to specify Activity Diagrams for example (or at least link my model to a Formal Tool for proofing, like you have mentioned earlier).
I suggest focusing on what decisions the developer needs to make (and why) before settling on a notation.
Nick: You are absolutely right, regarding trade-offs of a very abstract model or a fine-grained one. But I presume there for sure are tools to transform an abstract Activity Diagram to a code in any target language, then it will be useless any research in that type of code generation even if the transformation is with some Formal Proofs, with transforming back and forth between models, using side Tools.
Actually, I was also thinking of a declarative programming language, like Haskel, as the code's target language, that way we fill some gaps between the source and any imperative language as we focus more on what to do rather than how and omit some details that way. (Like your example Nick)
Could it compensate the weaknesses of an abstract source model?
Nick: Thanks for that paper, very relevant to our discussions. Even though no one of the debate's side admits the other side's point of view.
- Badges
- Science topic
- Similar topics
- Statistics
- Survey