Bank Teller Resumes by qmq41563

VIEWS: 55 PAGES: 25

More Info
									IS 1024                                   Fall 09                              Page 1




                                    Analysis Model
                                           For
                             The Banking Information System
                                        Version 1




                                      A. Stahl, L. Daberko




          A. Stahl, L. Daberko                                Date 1/15/2010
IS 1024                                                      Fall 09                                                                   Page 2



Table of Contents

Project Executive Summary ................................................................................................. 3
Actor-Goals Matrix ............................................................................................................... 4
Use Ca se Model – Banking System ..................................................................................... 5
Use Ca se Model – Loan Processing ..................................................................................... 6
UC: Open Account ............................................................................................................... 7
UC: Withdraw Funds ............................................................................................................ 9
UC: Deposit Funds ............................................................................................................. 11
UC: Transfer Funds ............................................................................................................ 12
UC: View Account Hi story .................................................................................................. 14
UC: Setup Bill Payment ...................................................................................................... 16
UC: Apply For Loan ............................................................................................................ 18
UC: Evaluate Loan ............................................................................................................. 20
UC: Make Loan Decision .................................................................................................... 22
Loan State Machine Model ................................................................................................. 24
Loan Processing Activity Diagram ..................................................................................... 25




          A. Stahl, L. Daberko                                                                                   Date 1/15/2010
IS 1024                                        Fall 09                                                  Page 3



Project Executive Summary

         This analysis model describes the feat ures and requirements that a new banking system
must meet. The banking system is being developed in two distinct phas es. The first phas e
focuses on the elementary business process of the day-to-day interactions between the system,
bank, and customers. This process includes, but is not limited to opening an account, depositing
funds, withdrawing funds, and trans ferring funds. The customer also has the opportunity to
perform advanced functions, such as viewing account history and setting up bill payment. The
second phase involves the loan application process. This process allows customers to apply for
a loan, and handles the procedures necessary to evaluat e the loan application and mak e a loan
decision.

         The actor-goals matrix is a comprehensive view of all of the elementary business
processes that was identified through the requirements workshops conducted with the
stakeholders. The core processes cover the basic actor interactions with the system such as
opening an account, depositing funds, withdrawing funds, and transferring funds. Upon opening
an account, the customer has the ability to deposit an initial amount. Subsequent deposits can
be made at anytime while the account is active. The customer is able to withdraw funds and
transfer funds between two existing accounts, however, procedures are performed to prevent
overdrafts and to ensure the customer owns the account in which they wish to withdraw funds.
The customer also has the ability to view the account history bet ween two valid dates, and set up
automatic bill payment.

          The loan application process of the banking system allows a customer to apply for a loan.
Once the customer has supplied all pertinent info rmation, the application is completed and
submitted for evaluation. The application is evaluated by a loan administrator and/or the loan
officer. E valuating the loan application ensures it is complete and retrieves the customer’s credit
rating. The loan application is then updated to evaluated, and passed directly to the loan officer
for a decision. The loan officer has the ability to change loan terms and loan amount according to
bank regulations. The loan offic er is the sole authority in making a dec ision on the loan and can
approve, reject, or defer the application. The loan state machine model and loan processing
activity diagram give a comprehensive view of the loan application process.

          The actor-goals matrix and use cases, and all diagrammed models are kept synchroniz ed
at all times to present a consistent view. The use case models are complimentary to the actors -
goals matrix in that eac h is an illustrated model that shows each actor and their int eractions with
the system. The loan state machine model and loan processing activity diagram enables easier
understanding of the interaction of the use cases in the system.

         The next phase of the project will further develop the existing banking system, complete
the loan cycle, and start development on the system maintenance functions.




          A. Stahl, L. Daberko                                                        Date 1/15/2010
   IS 1024                                  Fall 09                                                Page 4



   Actor-Goals Matrix

                Actor                                           Goals
                                        Open Account                      Close Account
Bank Manager                            Deposit Funds                     View Account History
                                        Withdraw Funds                    Create Customer
                                        Trans fer Funds                   Create Account
                                        Setup Bill Payment

                                        Deposit Funds
Bank Teller                             Withdraw Funds
                                        Trans fer Funds
                                        View Account History

                                        E valuate Loan
Credit Reporting Agency

                                        Deposit Funds                     View Account History
Customer                                Withdraw Funds                    View Account Balance
                                        Trans fer Funds                   Setup Bill Payment
                                        Apply For Loan

                                        Open Account                      Close Account
Customer Service Representative         Deposit Funds                     View Account History
                                        Withdraw Funds                    Create Customer
                                        Trans fer Funds                   Create Account
                                        Setup Bill Payment

                                        E valuate Loan
Loan Administrat or                     Bill Customer

                                        Deposit Funds                     E valuate Loan
Loan Officer                            Withdraw Funds                    Make Loan Decision
                                        Trans fer Funds
                                        View Account History

                                        Manage Users
System Administrator                    Maintain System
                                        Backup System

                                        Generat e Monthly Statement
Time                                    Generat e Reports
                                        Bill Payment




              A. Stahl, L. Daberko                                                Date 1/15/2010
IS 1024                          Fall 09                    Page 5



Use Case Model – Banking System




          A. Stahl, L. Daberko             Date 1/15/2010
IS 1024                          Fall 09                    Page 6



Use Case Model – Loan Processing




          A. Stahl, L. Daberko             Date 1/15/2010
IS 1024                                  Fall 09                                                 Page 7



UC: Open Account

Description: The use case allows a new customer to open a new checking or savings
account. The customer provides information. The account is then created and an initial
deposit is accepted. The amount is then added to the account balance, and a
transaction is created.


Actors: Bank Manager, Customer Service Representative


Preconditions: None


Base Scenario:

    1. System requests customer ID
    2. User enters customer ID                                                isCustomer(customerID)
    3. System confirms exists

    4.    System requests account type
    5.    User specifies account type                                      createAccount(accountType)
    6.    System creates account with unique number
    7.    System links account to customer

    8. System requests initial deposit
    9. User enters deposit amount                                                     deposit(amount)
    10. System adds deposit to balance
    11. System creates transaction
    12. System links transaction to account


Alternative Flows:

    3. System confirms customer does not exist
       3.1 System requests customer information
            Full name
            Current address
            Age
            Social security number
            Customer category
            Driver’s license
       3.2 User provides information                                      createCustomer(customerInfo)
       3.3 System creates customer with unique ID
       3.4 System resumes at step 4


Postconditions: None



          A. Stahl, L. Daberko                                             Date 1/15/2010
IS 1024                               Fall 09                    Page 8




Additional Information/Issues: None




          A. Stahl, L. Daberko                  Date 1/15/2010
IS 1024                                  Fall 09                                                Page 9



UC: Withdraw Funds

Description: The use case allows an existing customer who is the owner of an
existing account to withdraw a specified amount from the account. A desired withdrawal
amount is entered. The amount is checked to ensure it does not exceed the account
balance, subtracted from the current balance, and a transaction is created.


Actors: Bank Manager, Bank Teller, Customer, Customer Service Representative


Preconditions: None


Base Scenario:

    1. System requests customer ID
    2. User enters customer ID                                                isCustomer(customerID)
    3. System confirms customer exists

    4.    System requests account number
    5.    User enters account number                                isCustomerAccount(accountNumber)
    6.    System confirms account exists
    7.    System confirms customer owns account

    8. System requests withdraw amount
    9. User enters amount                                                           withdraw(amount)
    10. System verifies amount does not exceed account balance
    11. System subtracts amount from account balance
    12. System creates transaction
    13. System links transaction to account


Alternative Flows:

    3. System confirms customer does not exist
       3.1 System presents error message, resumes at step 1

    6. System confirms account does not exist
       6.1 System presents error message, resumes at step 4

    7. System confirms customer does not own account
       7.1 System presents error message, resumes at step 4

    10. System verifies amount exceeds account balance
        10.1 System presents error message, resumes at step 8


Postconditions: None


          A. Stahl, L. Daberko                                             Date 1/15/2010
IS 1024                               Fall 09                    Page 10




Additional Information/Issues: None




          A. Stahl, L. Daberko                  Date 1/15/2010
IS 1024                                    Fall 09                                              Page 11



UC: Deposit Funds

Description: The use case allows an existing customer to deposit a specified amount
into the account. The amount is then added to the account balance and a transaction is
created.


Actors: Bank Manager, Bank Teller, Customer, Customer Service Representative


Preconditions: None


Base Scenario:

    1. System requests account number
    2. User enters account number                                           isAccount(accountNumber)
    3. System confirms account exists

    4.    System requests deposit amount
    5.    User enters amount                                                          deposit(amount)
    6.    System adds amount to balance
    7.    System creates transaction
    8.    System links transaction to account


Alternative Flows:

    4. System confirms customer does not exist
       3.2 System presents error message, resumes at step 1


Postconditions: None


Additional Information/Issues: None




          A. Stahl, L. Daberko                                             Date 1/15/2010
IS 1024                                  Fall 09                                                  Page 12



UC: Transfer Funds

Description: The use case allows a current customer who is the owner of an existing
account to transfer funds into another existing account. The amount is checked to
ensure it is less than the withdraw account balance, subtracted from the withdraw
account balance, and added to the deposit account balance. A transaction is then
created for both accounts.


Actors: Bank Manager, Bank Teller, Customer, Customer Service Representative


Preconditions: None


Base Scenario:

    1. System requests customer ID
    2. User enters customer ID                                                 isCustomer(customerID)
    3. System confirms customer exists

    4.    System requests withdraw account number
    5.    User enters account number                                 isCustomerAccount(accountNumber)
    6.    System confirms account exists
    7.    System confirms customer owns account

    8. System requests deposit account number
    9. User enters account number                                           isAccount(accountNumber)
    10. System confirms account exists

    11. System requests transfer amount
    12. User enters amount                                                             transfer(amount)
    13. System verifies amount does not exceed withdraw account balance
    14. System subtracts amount from withdraw account balance
    15. System adds amount to deposit account balance
    16. System creates transaction and links to withdraw account
    17. System creates transaction and links to deposit account


Alternative Flows:

    5. System confirms customer does not exist
       3.3 System presents error message, resumes at step 1

    8. System confirms account does not exist
       6.1 System presents error message, resumes at step 4




          A. Stahl, L. Daberko                                              Date 1/15/2010
IS 1024                                Fall 09                                    Page 13



    9. System confirms customer does not own account
       7.2 System presents error message, resumes at step 4

    10. System confirms account does not exist
        10.1 System presents error message, resumes at step 8

    13. System verifies amount exceeds account balance
        13.1 System presents error message, resumes at step 11


Postconditions: None


Additional Information/Issues: None




          A. Stahl, L. Daberko                                   Date 1/15/2010
IS 1024                                     Fall 09                                                      Page 14



UC: View Account History

Description: The use case allows an existing customer who is the owner of an
existing account to view account history. The customer enters a valid start date and end
date, and the system displays all transactions for the time period. The system also
displays the account balance as of the end date, and the current account balance as of
the current date.

Actors: Bank Manager, Bank Teller, Customer, Customer Service Representative


Preconditions: None


Base Scenario:

    1. System requests customer ID
    2. User enters customer ID                                                         isCustomer(customerID)
    3. System confirms customer exists

    4.    System requests account number
    5.    User enters account number
    6.    System confirms account exists                                     isCustomerAccount(accountNumber)
    7.    System confirms customer owns account

    8. System requests start date, end date
    9. User enters dates                                                    viewHistory(startDate,endDate)
    10. System verifies start date is on or before end date
    11. System verifies start date to end date partially overlaps account open date to
        current date
    12. System presents all transactions between start date, end date
    13. System presents end date account balance
    14. System presents current account balance


Alternative Flows:

    3. System confirms customer does not exist
       3.1 System presents error message, resumes at step 1

    6. System confirms account does not exist
       6.1 System presents error message, resumes at step 4

    7. System confirms customer does not own account
       7.1 System presents error message, resumes at step 4

    10. System verifies start date is not earlier or identical to end date
        10.1 System presents error message, resumes at step 8



          A. Stahl, L. Daberko                                                      Date 1/15/2010
IS 1024                                   Fall 09                                             Page 15




    11. System verifies start date to end date does not partially overlap account open
        date to current date
        11.1 System presents error message, resumes at step 8


Postconditions: None


Additional Information/Issues: None




          A. Stahl, L. Daberko                                               Date 1/15/2010
IS 1024                                  Fall 09                                                 Page 16



UC: Setup Bill Payment

Description: The use case allows an existing customer who owns an existing
checking account to setup automatic monthly bill payments to a specified vendor. The
customer specifies payment amount, the day of the month payment is made, which
month to begin automatic payments, and the duration of monthly bill payments. The
vendor and customer’s checking account are then linked to bill payment information.

Actors: Bank Manager, Customer, Customer Service Representative


Preconditions: None


Base Scenario:

    1. System requests customer ID
    2. User enters customer ID                                                 isCustomer(customerID)
    3. System verifies customer exists

    4. System requests account number
    5. User enters account number                                 isCustomerChecking(accountNumber)
    6. System confirms account exists
    7. System confirms customer owns account
    8. System confirms checking account

    9. System requests vendor name
    10. User enters vendor name                                                 isVendor(vendorName)
    11. System verifies vendor exists

    12. System requests payment information
           7.2 Payment amount
           7.3 Payment day
           7.4 Beginning month
           7.5 Payment duration
    13. User provides information                                       createBillPayment(paymentInfo)
    14. System creates bill payment
    15. System links bill payment to vendor
    16. System links bill payment to account


Alternative Flows:

    3. System confirms customer does not exist
       3.1 System presents error message, resumes at step 1

    6. System confirms account does not exist
       7. System presents error message, resumes at step 4



          A. Stahl, L. Daberko                                             Date 1/15/2010
IS 1024                                 Fall 09                                      Page 17



    8. System confirms customer does not own account
       7.1 System presents error message, resumes at step 4

    9. System confirms account is not checking
       8.1 System presents error message, resumes at step 4

    11. System confirms vendor does not exist
        11.1 System requests vendor information
           i.  Name
          ii.  Bank routing number
         iii.  Account number
        11.2 User provides information                          create Vendor(vendorInfo)
        11.3 System creates vendor
        11.4 System links vendor to customer
        11.5 System resumes at step 12


Postconditions: None


Additional Information/Issues: None




          A. Stahl, L. Daberko                                Date 1/15/2010
IS 1024                                    Fall 09                                                  Page 18



UC: Apply For Loan

Description: The use case allows a customer to apply for a loan. It asks for the loan
amount and duration. All of the pertinent financial information is collected and the
application is submitted.


Actors: Customer, Loan Officer


Preconditions: None


Base Scenario:

    9. System requests customer ID
    10. User enters customer ID                                                   isCustomer(customerID)
    11. System confirms customer exists

    12. System requests loan application information
           a. Amount borrowed
           b. Loan length
           c. Loan purpose
    13. User enters information                                                  createLoanApp(loanInfo)
    14. System creates loan application with unique ID
    15. System links loan application to customer

    16. System requests employer information
           a. Employer contact information
           b. Employment length
           c. Monthly salary
    17. User enters information                                              updateLoanApp(employerInfo)
    18. System updates loan application with employer information

    19. System requests other income information
           a. Payer contact information
           b. Monthly income
    20. User enters information                                               updateLoanApp(incomeInfo)
    21. System updates loan application with other income information

    22. Steps 11-13 repeated until all income is entered

    23. System requests expense information
           a. Payee contact information
           b. Monthly payment
    24. User enters information                                              updateLoanApp(expenseInfo)
    25. System updates loan application with expense information

    26. Steps 15-17 repeated until all expenses are entered


          A. Stahl, L. Daberko                                                Date 1/15/2010
IS 1024                                     Fall 09                                           Page 19




    27. System requests asset information
           a. Asset name
           b. Current fair market value
    28. User enters information                                         updateLoanApp(assetInfo)
    29. System updates loan application with asset information

    30. Steps 19-21 repeated until all assets are entered

    31. System requests liability information
           a. Lender contact information
           b. Loan balance
    32. User enters information                                        updateLoanApp(liabilityInfo)
    33. System updates loan application with liability information

    34. Steps 23-25 repeated until all liabilities are entered

    35. System requests loan application submission
    36. User confirms submission                                             submitLoanApp(true)
    37. System sets loan application status to “submitted”


Alternative Flows:

    4. System confirms customer does not exist
       3.5 System requests customer information
            Full name
            Current address
            Age
            Social security number
            Customer category
            Driver’s license
       3.6 User provides information                                 createCustomer(customerInfo)
       3.7 System creates customer with unique ID
       3.8 System resumes at step 4


Postconditions: None


Additional Information/Issues:

Contact information:
    Institution name
    Contact person name
    Address
    Telephone number




          A. Stahl, L. Daberko                                        Date 1/15/2010
IS 1024                                   Fall 09                                                  Page 20



UC: Evaluate Loan

Description: The use case allows the loan officer to evaluate a completed loan
application. The applicant’s credit score is requested from a credit reporting agency.
The applicant’s net income and net worth are calculated and a summary is presented for
review. Once evaluation is complete, the loan application status is set to “evaluated.”


Actors: Loan Officer


Preconditions: None


Base Scenario:

    13. System requests loan ID
    14. User enters loan ID                                                      evaluateLoan(LoanID)
    15. System confirms loan application exists
    16. System confirms loan is complete
    17. System sends applicant name and SSN to credit reporting agency
    18. System receives credit score
    19. System updates application with credit score
    20. System calculates net income by adding incomes and subtracting expenses
    21. System calculates net worth by adding assets and subtracting liabilities
    22. System presents loan information

    23. System requests completion of evaluation
    24. User confirms evaluation completed                                  updateLoanStatus(evaluated)
    25. System sets loan application status to “evaluated”


Alternative Flows:

    5. System confirms loan application does not exist
       3.9 System presents error message, resumes at step 1

    4. System confirms loan application is not complete
       4.1 System presents error message, resumes at step 1

    5. System unable to send information to credit reporting agency
       5.1 System presents error message, resumes at step 5

    6. System receives invalid score or error message
       6.1 System presents error message, resumes at step 6

    13. System confirms that user does not complete evaluation
        13.1 System ends processing



          A. Stahl, L. Daberko                                               Date 1/15/2010
IS 1024                               Fall 09                    Page 21




Postconditions: None


Additional Information/Issues: None




          A. Stahl, L. Daberko                  Date 1/15/2010
IS 1024                                    Fall 09                                                   Page 22



UC: Make Loan Decision

Description: The use case allows the loan officer to approve, reject, or defer an
evaluated loan application. The loan officer has the ability to adjust loan amount and
decrease original loan term. The interest rate is set based on final values for loan term
and amount, and the borrower’s credit risk. Once approval is confirmed, the loan
application status is set to “approved.”


Actors: Loan Officer


Preconditions: None


Base Scenario:

26. System requests loan ID
27. User enters loan ID                                                               isEvaluated(loanID)
28. System confirms loan application exists
29. System confirms loan application is evaluated

30. System requests loan application rejection
31. User confirms loan application not rejected                                      rejectLoanApp(false)
32. System confirms loan application not rejected

33. System requests loan amount override
34. User enters loan amount                                                   updateLoanAmount(amount)
35. System updates loan application

36. System requests decrease term override
37. User enters term                                                               updateLoanTerm(term)
38. System confirms new term not greater than original term
39. System updates loan application

40. System requests interest rate
41. User enters interest rate                                                updateLoanRate(interestRate)
42. System updates loan application

43. System requests loan application approval
44. User confirms approval                                                          approveLoanApp(true)
45. System sets loan application status to “approved”



Alternative Flows:

    6. System confirms loan application does not exist
       3.10 System presents error message, resumes at step 1


          A. Stahl, L. Daberko                                                Date 1/15/2010
IS 1024                                   Fall 09                                 Page 23



    7. System confirms loan application is rejected
       7.1 System sets loan application status to “rejected”

    20. System confirms loan application is not approved
        20.1 System sets loan application status to “deferred”


Postconditions: None


Additional Information/Issues: None




          A. Stahl, L. Daberko                                   Date 1/15/2010
    IS 1024                                           Fall 09                                                   Page 24



    Loan State Machine Model



Prospective                  Loan          Loan                          Loan
   Loan                   Application   Application                   Application    Approved
Application               Submitted     Completed                      Evaluated




                                          Deferred                                  Loan Closed


                                                                Rejected


                   Loan
                Application                                                           Current
                 Canceled




                                                                                    Delinquent
                   Loan
                Application
                 Archived


                                                                                      Default




Deactivated                                                                         Foreclosed


                                                                                                    Loan Paid
                                                                                                       Off




              A. Stahl, L. Daberko                                                     Date 1/15/2010
IS 1024                                           Fall 09                           Page 25



Loan Processing Activity Diagram

Customer                         Loan Administrat or        Loan Officer




          A. Stahl, L. Daberko                                     Date 1/15/2010

								
To top