Groups > comp.lang.java.programmer > #2749

Re: Documenting tool

Path	csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.glorb.com!news2.glorb.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	Dirk Bruere at NeoPax <dirk.bruere@gmail.com>
Newsgroups	comp.lang.java.programmer
Subject	Re: Documenting tool
Date	Sat, 02 Apr 2011 14:49:51 +0100
Organization	Dirk Bruere at Neopax
Lines	32
Message-ID	<8vonrmFvbaU5@mid.individual.net> (permalink)
References	<8v6ppfF3lhU1@mid.individual.net> <bGqjp.4092$aV3.2731@newsfe02.iad>
Reply-To	dirk.bruere@gmail.com
Mime-Version	1.0
Content-Type	text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding	7bit
X-Trace	individual.net 4tAjYS9c38DA5CAR9A0oggeYUj8PaDcmiPbbsCwmYp99swm+qb
Cancel-Lock	sha1:y7jSJXJi4cnldWw947uCu610cw8=
User-Agent	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
In-Reply-To	<bGqjp.4092$aV3.2731@newsfe02.iad>
Xref	x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:2749

Show key headers only | View raw

On 26/03/2011 18:57, Arved Sandstrom wrote:
> On 11-03-26 03:32 PM, Dirk Bruere at NeoPax wrote:
>> Is there a documenting tool somewhere that draws out the method calls in
>> diagrammatic form? That can show you a graphical representation of your
>> program?
>>
> With all due respect, if you wanted static or dynamic diagrams of your
> code, you should have had them before you ever wrote a line of code.
>
> It's not too late to start: get a decent UML program and diagram (there
> are several useful UML diagrams that show method calls) what your code
> *should* do. Then compare that to what code inspection tells you about
> your code's actual behaviour.
>
> You could reverse engineer your existing stuff. I'd counsel against it,
> mainly because it will be fundamentally useless material.
>
> If I misunderstand you, and you are going about this the right way, and
> looking to design first, then I apologize in advance. As far as UML
> diagramming tools go, I'd myself recommend Visio (or an equivalent
> drawing tool like Omnigraffle on Mac OS X), that is about the _drawing_.
> I do *not* recommend design tools that can generate code or that
> "understand" a specific programming language. Also, if you go with UML,
> keep it simple and stick to the interesting application behaviours.

Currently looking at UML addon for Eclipse


-- 
Dirk

http://www.neopax.com/technomage/ - My new book - Magick and Technology

Back to comp.lang.java.programmer | Previous | Next | Find similar

Thread

Re: Documenting tool Dirk Bruere at NeoPax <dirk.bruere@gmail.com> - 2011-04-02 14:49 +0100

csiph-web