Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #10054
| From | markspace <-@.> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Preferred Way to Show Java Dependencies? |
| Date | 2011-11-18 11:57 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <ja6dbe$2hl$1@dont-email.me> (permalink) |
| References | <Xns9FA1921D3A95Ajpnasty@94.75.214.39> |
On 11/18/2011 11:21 AM, Novice wrote: > When documenting a Java project, is it customary to create dependency > diagrams for the programs? If so, what is the best tool or technique for > creating these diagrams? Generating generic class diagrams isn't customary for software engineering, ime. It's more normal to focus on important classes, processes, or concepts and diagram those, rather than get out the auto tool and just dump a bunch of diagrams into the project documentation. As far as tool, the NetBeans UML page refers the reader to SDE for NetBeans and JDeveloper. I don't have an opinion, so I'm defering to theirs. http://netbeans.org/features/uml/
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread
Preferred Way to Show Java Dependencies? Novice <novice@example..com> - 2011-11-18 19:21 +0000 Re: Preferred Way to Show Java Dependencies? markspace <-@.> - 2011-11-18 11:57 -0800
csiph-web