ONLINE PAYMENT SYSTEM Matt Willmer Ryan Beatty William Fahey
OVERVIEW Activity List UI Assumptions Sources of Information Assumptions Destination of Information Assumptions Inconsistencies Use Case
ACTIVITY LIST A User Must be able to: Create User Account. Schedule Periodic Payment. Make one time payment. View/Change account details. Close account. Add/Remove funds from the account.
ACTIVITY LIST CONT'D An Administrator must be able to: Create a user account. Close a user account. Transfer funds from one user account to another. Monitor all transfers. Change/Reset passwords. Be aware of possible security problems.
SCREEN SHOTS
MORE SCREENSHOTS
MORE SCREENSHOTS
MORE SCREENSHOTS
MORE SCREENSHOTS
MORE SCREENSHOTS
MORE SCREENSHOTS
MORE SCREENSHOTS
SOURCES OF INFORMATION ASSUMPTIONS Personal Information is provided by the user. User's identity is confirmed through another financial institution (their bank).
DESTINATIONS OF INFORMATION ASSUMPTIONS Information is maintained on a secure database. Users will be able to view all information about his or her account. Administrators will be able to view all information about all accounts, as well as the system as a whole.
INCONSISTENCIES What happens if the OPS account doesn't have enough funds to make an automated payment? A withdrawal is attempted from the user's bank account. If this is not possible, the payment fails and the user is notified. How are users notified? User are always notified by email. All users are required to have an email address to create an account.
INCONSISTENCIES (CONT'D) If an OPS account is identified by the user's bank account, how is this information kept private while allowing the user to log in by bank account number, and how can a user have multiple bank accounts associated with the OPS account? This OPS system should not identify users by bank account number, but rather by a unique user name. This allows users to have multiple bank accounts, and keeps our user's information secure.
INCONSISTENCIES (CONT'D) How are payments specified? A payment is specified by user name or email address. The payment will appear in the user's history by user name. Can a user cancel a payment? Yes, but only if the payment has not been completed. Can a user request a payment? Yes, if he or she knows the email address or user name of the other user.
INCONSISTENCIES (CONT'D) Can a user make a one-time payment? Yes, the OPS system allows a variety of ways to make payments. What All happens when an account is deleted? payments are halted, and the user's account is frozen. All money on the system is put back into the user's bank account.
INCONSISTENCIES (CONT'D) Can outside systems (credit cards, etc. ) pay into an OPS account? No. Only another OPS account can pay in, or the user's bank account. Are users charged for transactions? No, the system will be funded through ads from companies that would be willing to pay for ad space in the system.
USE CASE
QUESTIONS?
Скачать презентацию ONLINE PAYMENT SYSTEM Matt Willmer Ryan Beatty William
64f596d3ece5949cc0059ac448827994.ppt