I've found that the past few projects I've worked on, there's been too much muddled thinking from the outset in terms of planning and organization of code - although UML is a tool and will not in itself save you from this, I'm hoping that it will bring greater discipline to the process.
I'm thankful for all the feedback and grateful for the links to various editors provided. please give me your thoughts on this topic. I too believe pen and paper is fantastic but only for very very high level designs. Model for the system, not for the maintenance�.
In conclusion, the basis for modeling as documentation is pointless unless you want an overview of how the system work. A framework which fulfills requirements is a lot more difficult to modify than no framework, after all the framework will be basically perfect because design problems and requirements were nutted out in the pre-development stages
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 kommentar(er)
