1. OPS Requirements Specification and Analysis Dustin Larson Bryan Campbell Charles Sears

2. Activity List  Create OPS Account –The user must be able to create an OPS account. They provide information that identifies them, including name, email, address, and phone number. The user chooses a password, attaches the OPS account to a bank account, and also selects notification options.  Login –The user logs in by typing in their account number and password. They are granted access to their OPS account if the account number and password are typed in correctly.  Perform Transactions –The user can make payments, schedule or delete scheduled transactions, and add money to the OPS account from their bank account.  Logging out –After the user has logged in, the user is able to log out of the OPS system.

3. Activity List (continued)  View Reports –The user can view their monthly report, request a report for a specific date range, and can also get a report for tax purposes.  Delete Account –If the user desires to discontinue their OPS account, they may delete their account.  Edit Account Information –If the user’s information changes after the original OPS account creation, the user information can be modified.  Manage Sub Accounts –The user is able to create sub accounts that will have the same functionality as a master account, except the sub accounts will have monthly quotas and will not be able to have their own sub accounts.  Modify Address Book –The user is able to add, edit, and modify aliases to identify account numbers by.

4. User Interface Assumptions  Clean  Concise  Doesn’t need to be “flashy”  Easy To Use

5. User Interface Assumptions

9. Sources Of Information  The user first provides data when they sign up for an account  The backend database stores account information for later processing  The bank provides info on whether the user has enough money in their bank account to add money to OPS

10. Destination Of Information  The backend database receives the data first put in by the user  The bank receives transfer information from the system  The system receives balance information from the bank

11. Validation Activities  Inconsistencies –We felt there were no inconsistencies in the original problem description –We did however feel that there were some improvements that should be added to the system in order to make it more user friendly.

12. Validation Activities - Questions  Requirement 1: Create an account for a person in the OPS system. Each OPS account should be associated with the bank account (savings/checking) of the account owner. (Identify a bank account by the union of a routing number and an account number. –How will we identify an OPS account number?  The account number will be twelve digits long with just numbers  After the twelve digit number, it will be followed by a colon and then a number. The following number is 0 if it is the master OPS account, otherwise it will be a number representing a sub account. –Will multiple bank accounts be allowed per OPS account?  Yes –Will multiple OPS accounts per bank account be allowed?  There will only be one master OPS account that can authorize transfers from the bank account to the OPS accounts. –How should joint accounts be handled?  It doesn’t matter how joint accounts are handled. Just make the OPS account the master account. –Are master and sub OPS accounts allowed (ie. as a hierarchy)  Yes. Maximum spending quotas per month can be set by the master account to control the slave accounts. You can only have two levels: master and sub account. Only one master is allowed per OPS account.

13. Validation Activities - Questions  Requirement 2: Initialize the OPS account by a credit taken out of the owner’s bank account. –Ask for initial amount to transfer into the OPS account?  Yes –Minimum amount of money for the OPS account?  Minimum of $50 to create the account, but allowed to have a minimum balance of $0 –Verify that the required starting amount is available in the bank account?  Yes. Check to be sure the bank account has enough for the minimum starting balance, then withdraw the $50 and place into the OPS account.

14. Validation Activities - Questions  Requirement 3: Delete an account in the OPS system. Note the deletion of an OPS account may lead to the return of the available money to the owner’s bank account, if any. –Should the transaction history still be kept?  Yes. Keep the transactions in a database, but do not allow the owner of the account to access it. –Is there a termination fee?  No

15. Validation Activities - Questions  Requirement 4: Place periodic (weekly/monthly) bill payment on an OPS account; A transaction for transferring a specific amount of money (identified by the account owner) to another account in the OPS system. –When are scheduled payments sent?  The OPS account owner gets to choose what date and time the payment is made.  Show a disclaimer that if the user does not have an OPS account then it may take extra business days to send a check to make the payment. –An address book will be available to the user in order so the OPS account number doesn’t have to be entered for a transaction. The alias can be used.

16. Validation Activities - Questions  Requirement 5: Notify the account owner of a coming periodic payment.  How soon in advance should the account owner be notified? –The user will be notified five business days in advance of the scheduled periodic payment by default, but the number of days can be specified by the user.  What is the notification method? –The OPS account users will have the choice of mail, email, text message, or phone to be notified.  Is there a charge for the notification? –There is no fee for the notification.

17. Validation Activities - Questions  Requirement 6: Notify the account owner of any transaction on his/her account; be it withdrawal or deposit. –How should the OPS account owner be notified?  The OPS account users will have the choice of mail, email, text message, or phone to be notified. –Should OPS account owners be charged for making a transaction?  A 1% charge will be added to each transaction as a service fee when the transaction occurs.

18. Validation Activities - Questions  Requirement 7: Notify the account owner of a possible payment bounce; ie. if the available money is less than the amount of a payment. –How should the OPS account owner be notified?  The OPS account users will have the choice of mail, email, text message, or phone to be notified. –Should the OPS account be checked for a possible bounce before the bounce actually occurs?  Yes. Check for a possible bounce before the payment is attempted. –How far in advance should the OPS account be checked for a possible bounce?  The account will be checked up to five business days in advance of the transaction.  A message will show up when logging into the system on the home screen.  If there is still the possibility of a bounce the day before a transaction, the user has a choice for notification to be sent to them via test message, email, or voice mail at 8 AM that day.

19. Validation Activities - Questions  Requirement 7 Continued –Is there a charge for a bounce if it occurs?  Don’t allow a bounce.  The user has a choice to send a partial payment or noting at all.  If a second account is available to the OPS user, take available money out of that account to make the payment if the user requests it.  If the account is a sub account, send a request to go over the monthly sub quota to the master account owner. –Send this notification by the master account owner’s choice of text message, email, or voice mail.  Send this notification 5 business days in advance by default, but can be changed by the account owner. –If the slave’s monthly quota will be reset due to a new month and the available money at that point will cover the transaction, do not send an email. –How often are accounts checked for possible bounces?  Every time a transaction occurs or money moves a check is made.  Every morning within the time frame specified by the user to check for bounces. The next scheduled transaction date will be used to determine this time frame.

20. Validation Activities - Questions  Requirement 8: Generate a history of all transactions for the account owner monthly or by request.  Where is the transaction history located? –There is a master database to store all data for all OPS users.  Where can the transaction history for an OPS account be viewed by request? –The OPS account owner can access all of their transactions by request on the web site. –An option to request a listing of all transactions in a user specified date range is available. –The master OPS account can view slave OPS account transactions.  How is the monthly transaction history sent to the OPS user? –The user has a choice for an emailed web link to check their transactions online or to receive a hard copy of their transactions through regular mail.  Tax information can be generated upon request. –Information will include transactions, interest gained, total in, total out, net change, and amount paid to OPS.

21. Validation Activities - Questions  Requirement 9: Verification and Security –How do you verify the bank account belongs to the OPS user?  Send two small deposits to the bank account, under 25 cents each.  The person setting up the OPS account must confirm the exact amount deposited to their account. –The OPS account owner must decide on a password  The password must contain one or more of the following: capital letter, a lowercase letter, number, non alpha-numeric character. –The password will be 4-16 characters long, inclusive.

22. Use Case Diagram

27. Questions?