What sort of documentation is most useful for a java application?
- From: frustratedprogrammer@xxxxxxxxx
- Date: 30 Mar 2007 13:47:10 -0700
I'm interested in other's experiences as to what types of
documentation for java are most useful. Obviously Java docs are very
common and very widely used. Apart from java docs however what do
people find useful?
I know a lot of managers feel that a system should have a certain
amount of documentation supporting it, but in my experience often
documentation that is produced for this purpose never gets used after
it is written. I would suspect some sort of high level design of the
system which describes it's interfaces, major architectural components
and design patterns is useful. Perhaps also a support/operations
manual for those that need to support the system in production can be
useful. However when it gets down to detailed design documents such
as class diagrams and sequence diagrams I rarely find them useful.
Usually they don't get maintained and they just don't help you
understand the system that much.
Although I'm not totally convinced I'm starting to lean towards the
idea that good software is self documenting and software quality is
more important than documentation. Also having been involved in some
agile projects lately, I'm starting to see how the automated tests for
a system can be the best documentation of what the system does.
What do others think?
.
- Follow-Ups:
- Re: What sort of documentation is most useful for a java application?
- From: Arne Vajhøj
- Re: What sort of documentation is most useful for a java application?
- Prev by Date: Re: alternative to lua
- Next by Date: Re: problems with Java
- Previous by thread: problems with Java
- Next by thread: Re: What sort of documentation is most useful for a java application?
- Index(es):
Relevant Pages
|