John RoepkeAdam JaskiewiczDonnie Ford Team Software Project 1 Online Payment System
John RoepkeAdam JaskiewiczDonnie Ford Activity List Send/Receive Payment Schedule Payment Withdraw/Deposit from a Bank Validate Bank Account View Transactions
John RoepkeAdam JaskiewiczDonnie Ford Sources of Information Bank User Administrator OPS System
John RoepkeAdam JaskiewiczDonnie Ford Destination of Information User Administrator Bank OPS System
John RoepkeAdam JaskiewiczDonnie Ford k
John RoepkeAdam JaskiewiczDonnie Ford Validation Questions Data backup? How does the interface look? How secure does it need to be / what features? Access through a web browser? What kind of notification of failed transfers?
John RoepkeAdam JaskiewiczDonnie Ford Validation Questions When a user is deleted, how long do we keep a history of their transactions? Do we need to keep money in the OPS? Are accounts tied to a business or an individual? Do we allow non-periodic scheduled transactions? Do we link the transactions at all?
John RoepkeAdam JaskiewiczDonnie Ford System Design Web-based PHP/MySQL Check book register interface Concurrent development of the database and UI Notifications in have minimal information Non-periodic scheduled payments
John RoepkeAdam JaskiewiczDonnie Ford Security and Reliability Encryption Certificates Off-site backups Redundant servers Archive financial data of deleted users Separate transactions for sender and receiver
John RoepkeAdam JaskiewiczDonnie Ford Financial/Legal Concerns Financial institution status Testing Commission/fees Bounced transactions
John RoepkeAdam JaskiewiczDonnie Ford Use Case Diagram