170 likes | 183 Views
By: William Fahey Matt Willmer Ryan Beatty. Outline. The making of the class diagram. Using the class diagram to create the sequence diagrams with ArgoUML while maintaining our sanity. The state diagrams. Problems encountered during this project. Class Diagram. Creating a New Account.
E N D
By: William Fahey Matt Willmer Ryan Beatty
Outline • The making of the class diagram. • Using the class diagram to create the sequence diagrams with ArgoUML while maintaining our sanity. • The state diagrams. • Problems encountered during this project.
Problems Encountered • ArgoUML does not allow for adequate workload distribution. Its virtually impossible for multiple people to edit multiple files and merge the results. • ArgoUML sequence diagrams do not allow classes and actors to be distinguished. • ArgoUML does not allow the classes and methods in sequence diagrams to be connected to the actual class and method things in the explorer panel.
Problems Encountered (cont'd) • ArgoUML does not allow loop back arrows in sequence diagrams to indicate recursion. • ArgoUML is not very forgiving with mistakes. Often, the only recourse is to revert to a saved version of the file (no undo). • ArgoUML is not very intuitive. Excessive time must be spent to learn how to do simple things.
Problems Encountered (cont'd) • ArgoUML will sometimes not display things that are already there until some weird combination of events happens. • We think that ArgoUML is a good idea, however, the current software needs work in order to make it more usable.