1. Dustin Larson Bryan Campbell
OPS Design
Dustin Larson
Bryan Campbell

2. What We Did Examined, Refined, and Simplified Use Case Model
Created Class Diagram
Created Sequence Diagrams
Created State Diagrams
Documentation
Fixed Inconsistencies between diagrams
Ex. Sequence Diagrams had functions that were not in the class diagram

3. Problems
Team members had different “pictures” of what the overall project should conceptually look like
Little time to complete Part 2
Lost Team Member
Only able to have one person editing at a time (ArgoUML could not merge files)
ArgoUML
Unimplemented Functions
Glitches in editing (especially Sequence Diagrams and text boxes)
Had to restart program every few minutes

4. Use Case Diagram

5. Class Overview

6. Initialize Account

7. Make Scheduled Payment

8. View Report

9. User State Diagram

10. Server State Diagram

11. Address Book State Diagram

12. Questions???