BANK OF NAIA

System Requirements Specification

Version 1.0 | November 18th, 2019

2
Bank of Naia SRS |

TABLE OF CONTENTS

1. Introduction.....................................................................................................3
1.1 Purpose.............................................................................................3
1.2 Intended Audience.............................................................................3
1.3 Conventions.......................................................................................3
2. Overall Description.........................................................................................4
2.1 Product Perspective..........................................................................4
2.2 Product Features...............................................................................4
2.3 User Class and Characteristics.........................................................5
2.4 Operating Environment......................................................................5
2.5 User Documentation..........................................................................5
2.6 Assumptions and Dependencies.......................................................6
3. System Features............................................................................................. 7
Core Features..................................................................................................7
3.1 Register.............................................................................................7
3.2 Log in.................................................................................................7
3.3 Open Account....................................................................................7
3.4 Select Account...................................................................................8
3.5 Deposit.............................................................................................. 8
3.6 Withdraw............................................................................................8
3.7 Close Account...................................................................................9
3.8 Contact Bank.....................................................................................9
3.9 View History.......................................................................................9
3.10 Change Password.............................................................................10
3.11 Check Messages...............................................................................10
Additional Features.........................................................................................10
3.12 Welcome Page..................................................................................10
3.13 Help Page..........................................................................................11
3.14 Log out.............................................................................................. 11
4. External Interface Requirements...................................................................12
4.1 User Interface....................................................................................12
4.2 Hardware Interface............................................................................13
4.3 Software Interface.............................................................................13
4.4 Communications Interfaces...............................................................13
5. Milestones........................................................................................................15
6. Key Resource Requirements.........................................................................16
7. Appendix A Glossary......................................................................................17
8. Appendix B Use-Case Diagram.....................................................................18
9. Appendix C Use-Case Documents................................................................19

2
 
3
Bank of Naia SRS |

1. INTRODUCTION

1.1 PURPOSE
The purpose behind this Software Requirements Specification document is to describe
in detail the functionalities of the Bank of Naia bank automation system. Over the
course of this document, various aspects of the system will be covered, including the
both the functional and non-functional features along with descriptions. It will also
address the interface requirements as well as the milestones toward completing the
system.

1.2 INTENDED AUDIENCE

The intended audience for this document is all parties involved in the development
process of the Bank of Naia bank automation system, as well as any banks or other
financial groups with interest in purchasing usage of this system for their own
enterprises.

1.3 CONVENTIONS
Some of the terms used in this document may not be familiar to all readers. For these
terms along with their definitions, see Appendix A (Glossary).

1.4 SUMMARY
The Bank of Naia bank automation system includes a Graphic User Interface that
allows for the customer to create a new user or log in to their previously created user.
From there they can open, close, and modify their accounts, allowing for them to
deposit and withdraw funds as well as organize their money however they see fit. The
employees of the bank can access the customer’s user history to view the account
activity, as well as address any messages that bank users have sent. The system saves
the user data to the bank’s database after each transaction.

3
 
4
Bank of Naia SRS |

2. OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

The purpose of the Bank of Naia bank automation system is manage the users of a
large number of customers. This includes allowing for new customers to create users,
returning customers to access their users, and all actions the customers will take
concerning their users thereafter. It will allow for them to open accounts within their
users, as well as deposit to or withdraw from these accounts, and close an account
once they no longer need it. The customer can also view their account history to keep
track of what they’ve done, view a FAQ help page should they not understand a
process, and contact the bank should they not find the answer to their question. The
employees that are in charge of managing the system can access the employee user,
which they can change the password of, view a user’s history, and address the
messages that the customers have submitted. Overall, this system should encompass
all the necessary features for a fully automated banking system.

2.2 PRODUCT FEATURES

Later in this Software Requirements Specification document will be a further in-depth
look at the features of this project. The subsequent list provides an overview and brief
description of these features. Those designated as core features are the features that
are essential to the operation of the system, while those designated as additional
features offer additional functionality that is deemed useful but the program will still
function without them.

CORE FEATURES
1. Register
2. Log in
3. Open Account
4. Select Account
5. Deposit
6. Withdraw
7. Close Account
8. Contact Bank
9. View History
10. Change Password
11. Check Messages

ADDITIONAL FEATURES
12. Welcome Page
13. Help Page
14. Log out

4
 
5
Bank of Naia SRS |

2.3 USER CLASSES AND CHARACTERISTICS

The types of users that will be utilizing the system can be divided into three main
categories: new customers, returning customers, and bank employees. The subsequent
list provides potential scenarios in which each user might be using the system.

NEW CUSTOMER
- Deposit money into a single account
- Deposit money into multiple accounts for organization
- Contact bank to resolve question

RETURNING CUSTOMER
- Deposit money into one or more accounts
- Withdraw money from one or more accounts
- Withdraw money from one account and deposit it into another
- Create a new account
- Close an account
- View user history
- Contact bank to resolve question

BANK EMPLOYEE
- Change management password
- Check the history of a customer’s user
- Address messages submitted by customers

2.4 OPERATING ENVIRONMENT

Version 1.0 of the Bank of Naia bank automation software will be run on a system that
supports Java, typically a Windows OS. With enough backing from interested parties,
the system will eventually be moved to its own bank machine that will be able to
securely store the funds that are deposited and withdrawn by the customers. The
specifications of these machines have yet to be fully developed.

2.5 USER DOCUMENTATION

As the three main types of users that are to be using this system can be divided into the
categories of Bank Customer and Bank Employee, it follows that different user
documentation will be made available to each category.

Bank customers will have access to the Help Page within the software itself, as well as
being able to contact the bank in order to have the employees, who will have access to
a more in-depth knowledge of the program, help solve any problems.

Bank employees will have access to the external documentation, which will contain
detailed instructions on how the program operates within the user’s manual. This will
allow for them to have a good understanding of how it works and then be capable of
assisting the customers should they need help.

5
 
6
Bank of Naia SRS |

2.6 ASSUMPTIONS AND DEPENDENCIES

The time constraints on which the project is based include the fact that though all core
features must be implemented in order to have a software that functions in all the
necessary ways that were planned, additional features will be implemented based on
the amount of time available to work on the project after all core features have been
completed. This means that in the end, it is possible that not all additional features will
be present, for example being able to log out at any time. The decision on which
additional features to implement will be made during the implementation stage of the
software development process.

A core feature of the program that relies heavily on an external API is the method in
which the program will share the information given by the users with the bank. It is
important that there is a secure method of data transmission so that bank users and
accounts cannot be tampered with. The best method for this to be done is still being
reviewed.

Another external dependency of the system is the mechanism for dispensing and
receiving money from the customer. Version 1.0 of this software will simply use
keyboard input and screen display output to represent this, as the automatic banking
machine that is hoped to be in use for version 2.0 has not been developed yet.

6
 
7
Bank of Naia SRS |

3. SYSTEM FEATURES

The features of the Bank of Naia bank automation system qualify as either core features
or additional features, as mentioned previously. This section of the Software
Requirements Specifications of the program covers the Stimulus/Response Sequence,
User Requirements, and System Requirements for each feature.

CORE FEATURES

3.1 REGISTER

STIMULUS/RESPONSE SEQUENCE
1. The customer selects Register.
2. The customer is prompted to enter their full name, along with a username, password
and password again to confirm.
3. User data is saved.
4. Welcome page is displayed.
USER REQUIREMENTS
1. Valid username entered
2. Matching passwords entered
SYSTEM REQUIREMENTS
1. Access to bank data

3.2 LOG IN

STIMULUS/RESPONSE SEQUENCE
1. The customer selects Log In.
2. The customer is prompted to enter their username and password.
3. The system confirms that the user exists and the password matches the records.
4. Welcome page is displayed.
USER REQUIREMENTS
1. Valid username and password entered
SYSTEM REQUIREMENTS
1. Access to bank data

3.3 OPEN ACCOUNT

STIMULUS/RESPONSE SEQUENCE
1. The customer selects Open Account
2. The customer is prompted to enter the name of their new account.
3. Account is created and user data is saved.
USER REQUIREMENTS
1. Customer is logged in

7
 
8
Bank of Naia SRS |
2. Valid account name entered
SYSTEM REQUIREMENTS
1. Access to bank data

3.4 SELECT ACCOUNT

STIMULUS/RESPONSE SEQUENCE
1. The customer selects Select Account.
2. A list of user owned accounts are displayed and the customer is prompted to select one.
3. The deposit or withdraw page is displayed.
USER REQUIREMENTS
1. Customer is logged in
2. Valid account selected
SYSTEM REQUIREMENTS
1. Bank data available

3.5 DEPOSIT

STIMULUS/RESPONSE SEQUENCE
1. The customer selects Deposit.
2. The customer is prompted to enter the amount of money to deposit into their
account. 3.The money is deposited and the balance is updated.
4. User data is saved.
USER REQUIREMENTS
1. Customer is logged in
2. Account has been selected
3. Valid amount entered
SYSTEM REQUIREMENTS
1. Bank data available

3.6 WITHDRAW

STIMULUS/RESPONSE SEQUENCE
1. The customer selects Withdraw.
2. The customer is prompted to enter the amount of money to withdraw from their
account. 3.The money is withdrawn and the balance is updated.
4. User data is saved.
USER REQUIREMENTS
1. Customer is logged in
2. Account has been selected
3. Valid amount entered
SYSTEM REQUIREMENTS
1. Bank data available

8
 
9
Bank of Naia SRS |

3.7 CLOSE ACCOUNT

STIMULUS/RESPONSE SEQUENCE
1. The customer selects Close Account.
2. A list of user owned accounts are displayed and the customer is prompted to select one.
3. The account is closed and user data is saved.
USER REQUIREMENTS
1. Customer is logged in
2. Valid account selected
SYSTEM REQUIREMENTS
1. Bank data available

3.8 CONTACT BANK

STIMULUS/RESPONSE SEQUENCE
1. The customer selects Contact Bank.
2. The customer is prompted to enter the message they wish to send.
3. The message is recorded and user data is saved.
4. Message sent page is displayed.
USER REQUIREMENTS
1. Customer is logged in
2. Message is entered
SYSTEM REQUIREMENTS
1. Bank data available

3.9 VIEW HISTORY

STIMULUS/RESPONSE SEQUENCE
1. The customer or employee selects View History.
2. A list of user activity is displayed.
USER REQUIREMENTS
1. Customer or employee is logged in
2. If employee then user account selected
SYSTEM REQUIREMENTS
1. Bank data available

9
 
10
Bank of Naia SRS |

3.10 CHANGE PASSWORD

STIMULUS/RESPONSE SEQUENCE
1. The employee selects Change Password.
2. The employee is prompted to enter the current password, the new password, and the
new password again to confirm.
3. The system confirms that the current password matches the records and the new
passwords match.
4. The password is updated and user data is saved.
USER REQUIREMENTS
1. Employee is logged in
2. Correct current password entered
3. Matching new passwords entered
SYSTEM REQUIREMENTS
1. Bank data available

3.11 CHECK MESSAGES

STIMULUS/RESPONSE SEQUENCE
1. The employee selects Check Messages.
2. First pending message is displayed for the employee to mark as addressed or save
for later.
USER REQUIREMENTS
1. Employee is logged in
SYSTEM REQUIREMENTS
1. Bank data available
2. Messages are pending

ADDITIONAL FEATURES

3.12 WELCOME PAGE

STIMULUS/RESPONSE SEQUENCE
1. The customer successfully logs in
2. Welcome page is displayed
USER REQUIREMENTS
none
SYSTEM REQUIREMENTS
1. Bank data available

10
 
11
Bank of Naia SRS |

3.13 HELP PAGE

STIMULUS/RESPONSE SEQUENCE
1. The customer selects Help
2. Help page is displayed
USER REQUIREMENTS
none
SYSTEM REQUIREMENTS
none

3.14 LOG OUT

STIMULUS/RESPONSE SEQUENCE
1. The customer or employee selects Log out
2. The Sign In page is displayed
USER REQUIREMENTS
1. The customer or employee is logged in
SYSTEM REQUIREMENTS
none

11
 
12
Bank of Naia SRS |

4. EXTERNAL INTERFACE REQUIREMENTS

4.1 USER INTERFACE

DROP DOWN MENU

The main functionalities of this program can be accessed from the drop down menu bar
located at the top of the Graphic User Interface. These functionalities are divided into
two subheadings: Accounts and My User. Under the Accounts subheading can be found
all options relating to the user’s accounts, including Open Account, Select Account, and
Close Account. Under the My User subheading, located at the far right of the screen,
unlike the previous subheading which is located at the far left, can be found the View
History, Help, Contact Bank, and Log Out options.

SIGN IN PAGE
When the program is opened, the initial page that will be shown is the Sign In page.
This page allows for the customer to register for an account with the Bank of Naia or for
a returning customer to log into their existing user. This page also allows for an
employee to log in to the management account. This will be the page that is returned to
when the current user logs out.

REGISTER PAGE
When a new customer wants to register for a user at the bank, they are taken to the
Register page. This page prompts them to enter their first name, last name, username,
password, and password again as confirmation into the corresponding fields provided.
Once entered, they are to select the button labeled Enter.

LOG IN PAGE
When a returning customer wants to log in to their existing account at the bank, they are
taken to the Log In page. This page allows for them to enter their previously registered
username and password into the corresponding fields provided. Once entered, they are
to select the button labeled Enter.

SELECTION SCREEN
The Selection screen is one that will appear in three scenarios. It appears when a
customer is selecting which account they would like to deposit or withdraw form after
selecting Select Account, when a customer is selecting which account they would like to
close after selecting Close Account, and when an employee is selecting which
customer’s user history to view after selecting View User History. The Selection screen
consists of a table completed with the relevant information, whether that be a list of a
user’s accounts and balances, or a list of users for the employee to select from. In both
cases, the rows that are filled in are selectable, and after selecting one, the Enter button
can be clicked, moving on to the next screen.

12
 
13
Bank of Naia SRS |

DEPOSIT/WITHDRAWAL SCREEN
The Deposit/Withdrawal screen begins by allowing the user to select one of two
buttons: Deposit or Withdrawal. If the Deposit button is selected, then the user is
prompted to enter the amount they wish to deposit into the deposit field. If the
Withdrawal button is selected, then the user is prompted to enter the amount they wish
to withdraw into the withdraw field.

CONTACT BANK
If the customer selects the Contact Bank option, then they are taken to the Contact
Bank page. This page allows them enter a message that can be viewed by the bank’s
employees.

EMPLOYEE MENU
Once an employee logs into the system they will be taken to the Employee Menu. This
menu consists of three buttons: Change Password, View User History, and Check
Messages.

CHANGE PASSWORD
If an employee selects the Change Password option from the employee menu, then
they will be taken to the Change Password page. This page will prompt them to enter
the current management password, the new password, as well confirming the new
password in the corresponding fields.

CHECK MESSAGES
If an employee selects the Check Messages option, then they are taken to the Check
Messages page. This page allows for them to view the messages previously sent in by
customers. From here they have the options to either mark a message as addressed or
to save it for later, at which point they will be able to view the next message.

4.2 HARDWARE INTERFACE

For Version 1.0 of the Bank of Naia bank management software, it will be supported on
hardware able to run Java, typically Windows Personal Computers. In the future, with
enough financial backing, it is hoped that the software will be able to be moved onto its
own hardware, in the form of a specially designed banking machine able to properly
handle deposits and withdrawals. Version 1.0 will receive user input via keyboard and
mouse, but future versions are planned to support touchscreen capabilities with an on-
screen virtual keyboard. A secure data storage system for these machines will also
need to be developed.

4.3 SOFTWARE INTERFACE

For Version 1.0 of the Bank of Naia bank management software, it will be supported on
operating systems able to run Java, such as the Microsoft Windows OS. In the future, it
is hoped to bring the software onto its own banking machine, allowing for the program
to continue being run in Java in this new setting.

13
 
14
Bank of Naia SRS |

4.4 COMMUNICATION INTERFACE

Apart from communication with the user, this software will need to have the capacity to
securely communicate with a secured bank server, ensuring that the sensitive data
being transmitted cannot be intercepted nor tampered with. The specification of these
communication methods have yet to be developed.

14
 
15
Bank of Naia SRS |

5. MILESTONES
MILESTONE DEADLINE
th
System Requirements Analysis November 18 , 2019
Document
System Design: November 20th, 2019
- Class Diagrams
- Sequence Diagram
Implementation and Testing November 24th, 2019
- Source Code
- Unit Test Reports
- System Test Report
External Documentation November 26th, 2019

15
 
16
Bank of Naia SRS |

6. KEY RESOURCE REQUIREMENTS

MAJOR TASK REQUIRED SKILL/ TEAM ISSUES/CONSTRAINTS

KNOWLEDGE
Designing user GUI design Naia Kamawar- Limited banking
interface experience, bank MacLeod experience; external
UI knowledge research necessary
Implementing user Java swing GUI Naia Kamawar- Unfamiliar with some
interface programming MacLeod features; additional
experience research may be
required
Designing program Planning skills, Naia Kamawar- Some unfamiliar
structure knowledge of MacLeod features; additional
program research may be
structure required
Programming Math and Java Naia Kamawar- Some unfamiliar
programming MacLeod features; additional
knowledge, logic research may be
required

16
 
17
Bank of Naia SRS |

7. APPENDIX A: GLOSSARY

Account: Within the context of the Bank of Naia bank management system, an
account is a bank account made within a customer’s user. A user can
store an unlimited number of bank accounts, provided there is sufficient
space on the server. A user’s accounts each have a unique name, and
hold their own funds, which can be deposited to and withdrawn from by
the customer.

Customer: Within the context of the bank of Naia bank management system, a
customer is a person who has joined the bank or is in the process of
joining the bank by having already created or by being in the process of
creating a user with the bank.

Employee: Within the context of the Bank of Naia bank management system, an
employee is a person who works for the bank and has management
privileges sufficient enough to be allowed access to the employee account
of the software.

User: Within the context of the Bank of Naia bank management system, a user
is a sort of personal account (not to be confused with account [see above])
created by the customer that stores their first and last names, as well as all
accounts that they create. A user must be made for a customer to utilize
the bank.

17
 
18
Bank of Naia SRS |

8. APPENDIX B: USE-CASE DIAGRAM

18
 
19
Bank of Naia SRS |

9. APPENDIX C: USE-CASE DOCUMENTS

Bank of Naia – Register

1. Description
This use case describes how a new customer at the Bank of Naia can register for a user.

2. Actors
2.1 Bank Customer

3. Preconditions
Bank data is accessible.

4. Basic Flow of Events

1. The customer selects Register.
2. The customer is prompted to enter their full name, along with a username, password
and password again to confirm.
3. User data is saved.
4. Welcome page is displayed.

5. Alternative Flows
5.1 Username Taken
If the username entered in step 2 is already in use by another user then
1. The user is notified and prompted to enter a different username

5.2 Passwords Do Not Match

If the passwords entered in step 2 do not match then
1. The user is notified and prompted to enter matching passwords

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The customer now has a user with the Bank.
7.2 Failure Condition
The customer did not complete the user creation process and their user was not created.

19
 
20
Bank of Naia SRS |

Bank of Naia – Log In

1. Description
This use case describes how a customer at the Bank of Naia can log in to their user.

2. Actors
2.1 Bank Customer

3. Preconditions
Bank data is accessible.

4. Basic Flow of Events

1. The customer selects Log In.
2. The customer is prompted to enter their username and password.
3. The system confirms that the user exists and the password matches the records.
4. Welcome page is displayed.

5. Alternative Flows
5.1 Incorrect Username or Password
If the username and password entered in step 2 do not match then
1. The user is notified and prompted to try again

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The customer can now access their user.
7.2 Failure Condition
The customer did not successfully log in.

20
 
21
Bank of Naia SRS |

Bank of Naia – Open Account

1. Description
This use case describes how a customer at the Bank of Naia who is logged in to their user can create a
new account.

2. Actors
2.1 Bank Customer

3. Preconditions
Bank data is accessible.
Customer is logged in to user.

4. Basic Flow of Events

1. The customer selects Open Account
2. The customer is prompted to enter the name of their new account.
3. Account is created and user data is saved.

5. Alternative Flows
5.1 Account Name in Use
If the account name entered in step 2 is already in use by the user then
1. The user is notified and prompted to enter a different account name

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The customer now has an addition account within their user.
7.2 Failure Condition
The customer did not successfully create a new account.

21
 
22
Bank of Naia SRS |

Bank of Naia – Select Account

1. Description
This use case describes how a customer at the Bank of Naia can select an existing account within their
user to modify.

2. Actors
2.1 Bank Customer

3. Preconditions
Bank data is accessible.
Customer is logged in to user.

4. Basic Flow of Events

1. The customer selects Select Account.
2. A list of user owned accounts are displayed and the customer is prompted to select one.
3. The deposit or withdraw page is displayed.

5. Alternative Flows
5.1 No Account Selected
If the user selects enter without first selecting an account in step 2 then
1. The system does not proceed until an account is selected and enter is selected again
5.2 No Accounts
If there are no accounts owned by the user to display in step 2 then
1. A message informing the user how to create an account is displayed

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The customer can now make a deposit or withdrawal to or from their selected account.
7.2 Failure Condition
The customer did not successfully select an account.

22
 
23
Bank of Naia SRS |

Bank of Naia – Deposit

1. Description
This use case describes how a customer at the Bank of Naia can deposit money into the account they
selected previously.

2. Actors
2.1 Bank Customer
2.2 Bank

3. Preconditions
Bank data is accessible.
Customer is logged in to user.
User account has been selected.

4. Basic Flow of Events

1. The customer selects Deposit.
2. The customer is prompted to enter the amount of money to deposit into their
account. 3.The money is deposited and the balance is updated.
4. User data is saved.

5. Alternative Flows
5.1 Invalid Amount
If the amount of money entered in step 2 contains more than two decimal places then
1. The amount is rounded to the nearest hundredth
5.2 Invalid Number
If the amount of money entered in step 2 is not a number then
1. A message informing the customer is displayed and they are able to enter a new amount

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The user’s account balance has been updated.
7.2 Failure Condition
The customer did not successfully deposit into their account.

23
 
24
Bank of Naia SRS |

Bank of Naia – Withdraw

1. Description
This use case describes how a customer at the Bank of Naia can withdraw money from the account they
selected previously.

2. Actors
2.1 Bank Customer
2.2 Bank

3. Preconditions
Bank data is accessible.
Customer is logged in to user.
User account has been selected.

4. Basic Flow of Events

1. The customer selects Withdraw.
2. The customer is prompted to enter the amount of money to withdraw from their
account. 3.The money is withdrawn and the balance is updated.
4. User data is saved.

5. Alternative Flows
5.1 Invalid Amount
If the amount of money entered in step 2 contains more than two decimal places then
1. The amount is rounded to the nearest hundredth
5.2 Invalid Number
If the amount of money entered in step 2 is not a number then
1. A message informing the customer is displayed and they are able to enter a new amount
5.3 Insufficient Funds
If the amount of money entered in step 2 is greater than the amount currently held in the account then
1. A message informing the user that there is not enough money in the account displays and
they are able to enter a new amount

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The user’s account balance has been updated.
7.2 Failure Condition
The customer did not successfully withdraw from their account.

24
 
25
Bank of Naia SRS |

Bank of Naia – Close Account

1. Description
This use case describes how a customer at the Bank of Naia can select an existing account within their
user to remove.

2. Actors
2.1 Bank Customer

3. Preconditions
Bank data is accessible.
Customer is logged in to user.

4. Basic Flow of Events

1. The customer selects Close Account.
2. A list of user owned accounts are displayed and the customer is prompted to select one.
3. The account is closed and user data is saved.

5. Alternative Flows
5.1 No Account Selected
If the user selects enter without first selecting an account in step 2 then
1. The system does not proceed until an account is selected and enter is selected again
5.2 No Accounts
If there are no accounts owned by the user to display in step 2 then
1. A message informing the user how to create an account is displayed
5.3 Funds Remaining
If there are funds remaining in the account the user selects in step 2 then
1. A message informing the user to withdraw all funds before closing an account is displayed

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The customer has successfully closed the selected account.
7.2 Failure Condition
The customer did not successfully close an account.

25
 
26
Bank of Naia SRS |

Bank of Naia – Contact Bank

1. Description
This use case describes how a customer at the Bank of Naia can contact the bank.

2. Actors
2.1 Bank Customer
2.2 Bank

3. Preconditions
Bank data is accessible.
Customer is logged in.

4. Basic Flow of Events

1. The customer selects Contact Bank.
2. The customer is prompted to enter the message they wish to send.
3. The message is recorded and user data is saved.
4. Message sent page is displayed.

5. Alternative Flows

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The message has been sent to the Bank.
7.2 Failure Condition
The message was not sent to the Bank.

26
 
27
Bank of Naia SRS |

Bank of Naia – View History

1. Description
This use case describes how a customer or employee at the Bank of Naia can view user history.

2. Actors
2.1 a Bank Customer
2.1b Bank Employee

3. Preconditions
Bank data is accessible.
Customer or employee is logged in.

4. Basic Flow of Events

1. The customer or employee selects View History.
2. A list of user activity is displayed.

5. Alternative Flows
5.1 Employee Viewing
If the user selecting View History in step one is an employee then
1. The employee must first select which user’s history to view before step 2 can occur

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The customer or employee has viewed the user history.
7.2 Failure Condition
The customer or employee did not successfully view the user history.

27
 
28
Bank of Naia SRS |

Bank of Naia – Change Password

1. Description
This use case describes how an employee at the Bank of Naia can change the administrative password.

2. Actors
2.1 Bank Employee

3. Preconditions
Bank data is accessible.
Employee is logged in.

4. Basic Flow of Events

1. The employee selects Change Password.
2. The employee is prompted to enter the current password, the new password, and the
new password again to confirm.
3. The system confirms that the current password matches the records and the new
passwords match.
4. The password is updated and user data is saved.

5. Alternative Flows
5.1 Incorrect Current Password
If the current password entered in step 2 does not match the records then
1. The employee is notified and prompted to try again
5.2 Different New Passwords
If the new passwords entered in step 2 do not match then
1. The employee is notified and prompted to try again

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The management password has been updated.
7.2 Failure Condition
The employee failed to change the management password.

28
 
29
Bank of Naia SRS |

Bank of Naia – Check Messages

1. Description
This use case describes how an employee at the Bank of Naia can check the messages left by the users.

2. Actors
2.1 Bank Employee
2.2 Bank

3. Preconditions
Bank data is accessible.
Employee is logged in.

4. Basic Flow of Events

1. The employee selects Check Messages.
2. First pending message is displayed for the employee to mark as addressed or save
for later.

5. Alternative Flows
5.1 No Messages
If there are no messages to be displayed in step 2 then
1. Text informing employee of no pending messages is displayed
5.2 One Message
If there is only one message to be displayed in step 2 then
1. The employee is unable to save for later

6. Key Scenarios
6.1 No Available Bank Data

7. Post-Conditions
7.1 Successful Completion
The employee can successfully address messages or save them for later.
7.2 Failure Condition
The employee did not successfully access the messages.

29
 