Re: proper use of .java files (layout)
On 12/27/2012 2:51 AM, Robert Klemme wrote:
....
Right. That's also the reason why I prefer Visio with the free set of
stencils for UML modeling over any other UML tool (especially those with
a proper UML model in the background or even roundtrip engineering)
because I can add visual elements not part of UML standard to help
getting ideas across.
....
Round trip UML reminds me of a situation I encountered in the early
1970's. We had a manager who insisted that there had to be an up-to-date
flow chart covering the entire code in each application. The
applications were written in NEAT/3 Level 2, an assembly language. There
was a flow chart standard that required a very rigid format, close to
single column.
We did really use flow charts in some situations, but not for whole
applications, and in much more flexible layouts. The whole program
design documents tended to be text describing the data structures,
functions, and main algorithms in a program.
Fortunately, someone had written an application that read the source for
a program, and generated an ASCII flow chart from it. We ran it, bound
the line printer paper in big binders, showed them to the manager, and
stowed them away.
The flow charts were longer than the assembly language code, no more
readable, and contained a proper subset of the information in the code,
including its comments, so they were really useless. They gave no
architectural or design insight. They existed only in order to be able
to say we had a flow chart.
Round trip UML smells of that situation.
Patricia