Link to state diagram: https://drive.google.com/file/d/1BPTHJmOLGr9hiQ0BJnvLTYXEDLRx6saK/view?usp=sharing
link to Ioan's sequence diagram: https://drive.google.com/file/d/1fHwd0fRkoscI03Zu2G8p7B5D6bBiBh87/view?usp=sharing link to Aidan's sequence diagram: https://drive.google.com/file/d/1L447NcwgO0GbktDt5HXLOZCDhwc7hFZX/view?usp=sharing
- UML Diagram - https://drive.google.com/file/d/1BKs9DEbUAkv-ynNGjp099HZ6vRylucr6/view?usp=sharing
- Use Case Diagram - https://drive.google.com/file/d/1OTOZ-MegXgHVpB8rYiUERVfmFXZhzAlF/view?usp=sharing
- freeze account sequence diagram - https://drive.google.com/file/d/19AFoU-Of_jHAxNgIwXVeigCMnlGSpC1D/view?usp=sharing
- unfreeze account sequence diagram - https://drive.google.com/file/d/1AA96lVdDmQhyHeB5tIYJtLMJNSpWDMh1/view?usp=sharing
Plan for Friday: Update the class diagram to better include the user class. Update the use case diagram to include confirm credentials and check balances. As well as clarify "request report" Change our code to better implement the user. Change the code to work again with both the collection of bankaccount and user.
Aidan - Code review notes: Class diagram - savings & checkings should inherit, transaction should be a composition to BankAccount Code - tests for multiple suspicious transactions, timestamps - multiple rapid transactions