writing for programmers

[Barbara Hubert <barbara_hubert -at- epicdata -dot- com>]

I'd start by learning something about object oriented programming in
general.
Maybe take a course at your local community college.

Addison Wesley has a Java Tutorial that is pretty good. You also might
try Sun
Microsystem's Site as they have an excellent developer's network at
http://www.java.sun.com. You might look there for some decent examples
of
outlines.

Javadoc is utility that generates MIF files or HTML files from comments
in the
source code itself. The comments must be written and edited right in the
code.
There is another tool called DocWiz that is suppose to allow you to edit
the
code while protecting it. Unfortunately, DocWiz doesn't always save and
is
unreliable. Javadoc looks for packages, classes, constructors, methods,
inheritance, etc., then generates them as sub heads in a preformatted
HTML doc.
If you have commented these features/elements out, Javadoc will generate
the
text according to a predefined format that is executed using special
Javadoc
tags.

You can write package (.pkg) and overview files separately  and Javadoc
will
compile them into the final output, a .chm file.

A functional spec is the first document produced in the product life
cycle and
includes all the business logic, etc., for the product. I'm sure if you
check
the archives there is a couple of detailed descriptions there.

Finally, yes all those symbols in viso are very meaningful, some
indicate
processes, some applications, some server containers....

hope that helps