Generated code when used properly will provide a framework for the whole system. I bet if you compared a model which was not generated with a complete reengineered model of the same system there would be great differences, differences alot more noticeable than with a generated code skeleton. If code generation does not occur your model doesn�t need to be complete (for system creation). Moreover, modeling without the intention of generation will lead to undefined requirements because the actual code is not affected by the model. During analysis if modeling is undertaken with a UML CASE tool without the intention of generating code then the modeling process seems less relevant in relation to the systems implementation, but provides a stagnate period of documentation.Įxample, if I am modeling using a UML CASE and I have a rough idea how I will design the system (which most designers have) and I have no intention of generating code, then the process of modeling is only a documentation task because if the model was complete then a skeleton code could be created (why wouldn�t you use a code generator if it will basically produced the same code that you will be forced to write). My primary reason for this is to completely define requirements. ![]() I am a strong believer in modeling with the goal of generating skeleton code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |