1 / 28

BANKING SYSTEM

BANKING SYSTEM. Software Requirements Document. CEN5011 - Advanced Software Engineering Fall Term - 2004. TEAM MEMBERS. Jing Zhang Wei Peng Erliang Zeng Ramakrishna Varadarajan Xiaosi Zhou Fernando Farf á n. Bank with services in South Florida. +200K Clients Next 5 years:

herreras
Download Presentation

BANKING SYSTEM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. BANKING SYSTEM Software Requirements Document CEN5011 - Advanced Software Engineering Fall Term - 2004

  2. TEAM MEMBERS Jing Zhang Wei Peng Erliang Zeng Ramakrishna Varadarajan Xiaosi Zhou Fernando Farfán

  3. Bank with services in South Florida. +200K Clients Next 5 years: Statewide coverage. More clients and transactions. Easy to learn, easy to use. Integration with peers. BANKING SYSTEM

  4. OBJECTIVES • Robust and flexible system => high-volume operations. • Expand the branch office number => cost-effective computer network. • Versatile system for client management and savings accounts transactions. • Flexible infrastructure, interconnection with other systems and peers. • Open systems to OLAP solutions .

  5. FUNCTIONAL REQUIREMENTS • Bank Officers:Maintenance to client records.Open and update clients’ accounts. • Bank Tellers:Register monetary transactions.

  6. NONFUNCTIONAL REQUIREMENTS • User-friendly, easy to learn and use. • Application and network security will be priorities. • Highly infallible, fault traceable and transaction-based. • The system has to respond within 5 seconds after any taken action.

  7. USE CASE DIAGRAMS

  8. SCENARIO: Opening an Account Scenario name: Opening an Account Participating Actors: John: Bank Officer. Flow of Events: • John has all the necessary information of a customer to open an account. • John then enters all the customer information like the SSN, first, middle and last names, address and telephone number in the system. • The system then opens a new account and assigns a unique account number for the account for future references.

  9. USE CASE: Open Account

  10. SEQUENCE DIAGRAM: Open Account

  11. SCENARIO: Update Account Scenario name: Update an Account Participating Actors: John: Bank Officer. Flow of Events: 1. A customer enters the bank and wants to make some changes in her personal information. 2. John gives the customer an information changing form containing account number, address, date of birth, telephone number, and Email address, etc. 3. The customer fills out the form and hands it to John. 4. John makes those changes in the customer’s account and tells her whether it is done.

  12. USE CASE: Update Account

  13. SEQUENCE DIAGRAM: Update Account

  14. SCENARIO: Close Account Scenario name: Close an Account Participating Actors: John: Bank Officer. Flow of Events: • John has all the necessary information of a customer to close an account. • John enters customer’s account number into the system. • John returns the balance to customer if customer has any in his account. • John confirms the account closing. • Customer leaves the bank with an acknowledgement for closing the account.

  15. USE CASE: Close Account

  16. SEQUENCE DIAGRAM: Close Account

  17. SCENARIO: Cash Deposit Scenario name: Cash Deposit Participating Actors: Brenda: BankTeller. Flow of Events: • Brenda requests the deposit ballot and the money to be deposited. • Brenda verifies all the information in the ballot, and verifies against the cash received. • Brenda records the transaction in the system, typing the account number and the cash amount. • Brenda prints the acknowledgement on the ballot. • Brenda puts the cash in the drawer. • Brenda keeps the original ballot for her file and gives the copy of the ballot to the customer.

  18. SCENARIO: Check Deposit Scenario name: Check Deposit Participating Actors: Andrea: BankOfficer. Flow of Events: • Andrea requests the deposit ballot and the check to be deposited. • Andrea verifies all the information in the ballot, and verifies the check received. • Andrea records the transaction in the system, typing the account number and the check amount. • Andrea prints the acknowledgement on the ballot. • Andrea puts the check in the drawer. • Andrea keeps the original ballot for her file and gives the copy of the ballot to the customer.

  19. SCENARIO: Cash and Check Deposit Scenario name: Cash and Check Deposit Participating Actors: Lucy: BankOfficer. Flow of Events: • Lucy requests the deposit ballot and the check to be deposited. • Lucy verifies all the information in the ballot, and verifies the check received. • Lucy records the transaction in the system, typing the account number, the cash amount and the check amount. • Lucy prints the acknowledgement on the ballot. • Lucy puts the check in the drawer. • Lucy keeps the original ballot for her file and gives the copy of the ballot to the customer.

  20. USE CASE: Deposit

  21. SEQUENCE DIAGRAM: Deposit

  22. SCENARIO: Withdraw Scenario name: Withdraw Participating Actors: John: BankOfficer. Flow of Events: • A custom enters the bank and wants to withdrawn some money from account. • She meets John and tells him that she needs to withdrawn some amount from her account. • John asks for her account number and identifications. • The custom gives her account number and identifications. • The custom specifies the amount she wants to withdraw to John. • John checks if she has sufficient balance to withdraw the amount. • If she has sufficient balance John

  23. USE CASE: Withdraw

  24. SEQUENCE DIAGRAM: Withdraw

  25. SCENARIO: CheckBalance Scenario name: CheckBalance Participating Actors: John: BankEmployee. Flow of Events: • A custom enters the bank and meets john. She asks John to check her account balance. • John asks for the customer’s account number • The customer gives John her account number. • John enters the customer’s account number into the banking system, checks her account balance and prints it. • The customer gets her balance information and leaves the bank.

  26. USE CASE: CheckBalance

  27. SEQUENCE DIAGRAM: Check Balance

  28. CLASS DIAGRAM

More Related