Lab Four, Group One: James Clause and Elizabeth Zehner


ArgoUML does a fairly good job with class diagrams. It represents the relationship between classes well with its box and line figures. It also goes a decent job with sequence diagrams as long as the program that it represents is not too large. As the program size increases and the number of interactions between the classes increases the diagrams become more and more cluttered and harder and harder to read. ArgoUML also lacks good ways to express conditional sections of code in the diagrams. In lab 3 when an exception is thrown if the word is already in the table there is no way to expression the conditional nature of the program except by diagraming both and adding a note explaining why both paths exists and what must happen for each path to be taken. The program also does not express loops or iteration at all. There is no way to indicate that a method call will repeat itself x number of times except in a note. Or that a function will be called for each element in an iteration.


No real problems with the lab. The swing gui is slow and this makes it difficult to use. I also could not find a way to add return types to methods when creating class diagrams by hand. This isn't a huge deal since the import creates these diagrams for you but it was still something that I think needs to be brought out more.

Jim Clause Elizabeth Zehner

java -jar ArgoUML/argouml.jar

Link to this Page