Hi, to all the People there.
Is it a good practice to model using UML when the software architecture
follows a procedural method.
We are using a procedural way of programming using Java.
It's like saying C' style of coding using Java.
Does UML qualify as the best modelling choice ?
As I see it procedural programming (with modules) can be regarded as a special case of object-oriented programming, and as such UML has a good deal to offer. That said, there are many useful models in UML that has nothing or little to do with the so-called object-oriented paradigm.
UML can model state-machines, swimlanes, (machine) nodes, dependencies between modules (if you regard a leaf class with static methods as a module), etc. So I would say that it qualifies as a good modelling choice (don't know if it is the best, though).
Søren Bak
