1 / 17

By: William Fahey Matt Willmer Ryan Beatty

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.

patrickcrodriguez
Download Presentation

By: William Fahey Matt Willmer Ryan Beatty

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. By: William Fahey Matt Willmer Ryan Beatty

  2. 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.

  3. Class Diagram

  4. Creating a New Account

  5. Add/Remove Funds

  6. Change/View Details

  7. Delete Account

  8. Change Passwords

  9. Creating a New Account

  10. Add/Remove Funds

  11. Change/View Details

  12. Delete Account

  13. Change Passwords

  14. 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.

  15. 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.

  16. 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.

  17. Questions

More Related