• Post Reply Bookmark Topic Watch Topic
  • New Topic

how to analyze programme?  RSS feed

 
de fa
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i have a java programme source code and it's size is about 2M. i want to know more information about the java programme's structure.how can i do?
i wish deduce the diagram like sequence diagram or workflow diagram,is it possible?
 
Joanne Neal
Rancher
Posts: 3742
16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How many more times are you going to ask this question ?
usually uml design before programme
need help
[ September 22, 2005: Message edited by: Joanne Neal ]
 
de fa
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
you haven't answered my question.
 
Henry Wong
author
Sheriff
Posts: 23295
125
C++ Chrome Eclipse IDE Firefox Browser Java jQuery Linux VI Editor Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I suggest you get yourself a good IDE that suit your needs.

For example, eclipse has some perspectives / views that can organize your source code in a manner that is more manageable.

Henry
 
Ernest Friedman-Hill
author and iconoclast
Sheriff
Posts: 24217
38
Chrome Eclipse IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by de fa:

i wish deduce the diagram like sequence diagram or workflow diagram,is it possible?


Not really. Many tools (profilers, mostly) can make call trees (diagrams of what calls what, ever) but that's a far cry from structurally meaningful flowcharts. You can use all the tools in the world, but there's actually no substitute for time. You still have to take all those charts and graphs and read them, and that's always the rate-limiting step.
 
de fa
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks
 
Stan James
(instanceof Sidekick)
Ranch Hand
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The challenge with most tools that try to analyze your code and generate UML or other reports is that they get bogged down in the details of String and StringBuffer and every class you never heard of in the libraries, making so much "noise" information that you can't see the shape of your program.

I work with a vendor framework that has a zillion levels of abstraction in many critical paths. I often doodle interaction diagrams or sequence diagrams on scrap paper as I read new code. They are usually throw-away pictures, but sometimes I keep one stuck on the wall for a week or two.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!