Editing Round-trip engineering (section)

== Disadvantages ==
There is a serious risk that the generated code will rapidly differ from the model or that the reverse-engineered model will lose its reflection on the code or a mix of these two problems as result of cycled reengineering efforts.<ref>{{Cite web |title=Help - |url=https://www.modeliosoft.com/modelio-help/41/en/index.jsp?topic=/csdesigner-doc/html/Csdesigner_choose_functional_mode_round_trip.html |access-date=2023-07-25 |website=www.modeliosoft.com}}</ref>

Regarding behavioral/dynamic part of [[UML]] for features like [[State diagram|statechart diagram]] there is no equivalents in programming languages. Their translation during code-generation will result in common programming statement (.e.g {{Code|if,switch,enum}}) being either missing or misinterpreted. If edited and imported back may result in different or incomplete model.<ref name=":0">{{Cite web |last=Siegl |first=Daniel |title=Why Round-Trip Engineering does not work {{!}} LieberLieber Modelling Expert |url=https://blog.lieberlieber.com/2015/09/05/why-round-trip-engineering-does-not-work/ |access-date=2023-07-25 |language=en-US}}</ref><ref name=":1">{{Cite web |title=8 Reasons Why Model-Driven Approaches (will) Fail |url=https://www.infoq.com/articles/8-reasons-why-MDE-fails/ |access-date=2023-07-29 |website=InfoQ |language=en}}</ref> The same goes for code snippets used for code generation stage for the pattern-implementation and user-specific logic: intermixed they may not be easily reverse-engineered back.<ref name=":0" /><ref name=":1" />

There is also general lack of advanced tooling for modelling that are comparable to that of modern IDEs (for testing, debugging, navigation, etc.) for [[general-purpose programming language]]s and [[domain-specific language]]s.<ref name=":1" />