When you can take your model and generate the code for it, and then change the code and update the model from the modified source code. I.e. it goes both ways. Doing model->code is easy, doing code->model is harder, doing both is crazy difficult. So the idea is to get your model as rich as possible so that you don't have to do round tripping, you only do code generation. But to get there, you start programming in your modeling language, which just flattens the process back out (i.e. you're only doing programming, you're not doing modeling). So it's a delicate balancing act.
In the real world, the model is often expressed in UML, and then translated into a "real" langauge to be executed. In the ideal world, that happens without further modification by the developer. If you're not in an ideal world, you modify the generated code, and then need to round trip that information back to the UML so that next time you generate the code it doesn't have to have the same mods reapplied. cheers, barneyb On Tue, Feb 10, 2009 at 10:51 AM, Henry <[email protected]> wrote: > > What is round tripping? > -- Barney Boisvert [email protected] http://www.barneyb.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
