GROUP FUND

QUEUE MANAGEMENT
 System Requirements

1. USER CHARACTERISTICS:

There are three types of users in this system:

The highest level of user is the administrator who reserves all the rights of
administrative work in the bank. He is the one who can keep track of things that are going around and
does back up of system for safety reasons.

The second level of user is the staff that is responsible for interacting with the customers and
providing them with relevant information.

The third level of user is the customer who can just view his account and edit the details in his
account. Customer can also use the touch screen based system to obtain coupen number for the
relevant customer service desk.

2. REQUIREMENTS OF BANK MANAGMENT SYSTEM

Administrator:

1. Administrator will be given a unique ID and password to login.

2. Administrator can keep track of things that are going around.
3. Administrator can create list of branches, products, service desk counters and officers in master
page.
4. Administrator can edit list of branches, products, service desk counters and officers in master
page.
5. Administrator can delete list of branches, products, service desk counters and officers in master
page.
Staff:

6. Staff will be given a unique ID and password to login.

7. Staff provides the customer with 6 types of services: savings, current account, fixed deposits,
credit cards, debit cards and loans.
8. He will increase the ticket numbers
9. Staff will delete ticket from the queue.

Customer:

10. Customer will be given a unique ID and password to login.

11. Customer can edit his details.
12. Customers can specify the services they are interested in.
13. Customers can generate the ticket.

3. USE CASE ANALYSIS:

Use Case Analysis identifies the functionality provided by the system (use cases), the users who
interact with the system (actors), and the association between the users and the functionality. Use
Cases are used in the Analysis phase of software development to articulate the high-level
requirements of the system. The primary goals of Use Case diagrams include:

 Providing a high-level view of what the system does

 Identifying the users ("actors") of the system

 Determining areas needing human-computer interfaces

Use Cases extend beyond pictorial diagrams. In fact, text-based use case
descriptions are often used to supplement diagrams, and explore use case functionality in more
detail.

Graphical Notation

The basic components of Use Case diagrams are the Actor, the Use Case, and the
Association.

Actor An Actor, as mentioned, is a user of the system,

and is depicted using a stick figure. The role of
the user is written beneath the icon. Actors are
not limited to humans. If a system
 communicates with another application, and
expects input or delivers output, then that
application can also be considered an actor.

A Use Case is functionality provided by the

system, typically described as verb+object (eg.
Use Case Register Car, Delete User). Use Cases are
depicted with an ellipse. The name of the use
case is written within the ellipse.

Associations are used to link Actors with Use

Cases, and indicate that an Actor participates in
Association the Use Case in some form. Associations are
depicted by a line connecting the Actor and the
Use Case.

In Bank Management System, the actors are as follows:

1.

- The administrator is the one who is responsible for all the administrative work. He
A D M IN IS T R A T O R

is also responsible for all the backup of the system. He is the one who also looks after the
network problems. He can add, edit and delete staff profiles ,branches filffif,products and
services offered by the bank.

2.

STAFF

- The staff is the one who is responsible for looking after the customers of bank. The main
goal of staff is to solve all the queries of customer and provide them their best services.

3.
C U STO M ER
- The customer is the one who can login and generate the ticket for the service provided by
the staff.

Now the use cases (i.e. the functionality) of the system are as shown below:

1. Name: Add/Edit/Delete Staff profile

Description: Administrator is responsible for the staff details.

Actors: Administrator

Trigger: According to the need of administrator

Result: The profile of staff gets updated.

Essential process: 1. Identify administrator by login.

2. Perform task according to need.

3. Check whether the profile is updated or not.

2. Name: Add/Edit/Delete branches detail

Description: Administrator is responsible for the branch details.

Actors: Administrator

Trigger: According to the need of administrator

Result: The profile of branches get updated.

Essential process: 1. Identify administrator by login.

2. Perform task according to need.

3. Check whether the branch details is updated or not.

3. Name: Add/Edit/Delete services detail

Description: Administrator is responsible for the services details.

Actors: Administrator

Trigger: According to the need of administrator

Result: The profile of services get updated.

Essential process: 1. Identify administrator by login.

2. Perform task according to need.

3. Check whether the service details is updated or not.

4. Name: Add/Edit/Delete products detail

Description: Administrator is responsible for the services details.

Actors: Administrator

Trigger: According to the need of administrator

Result: The profile of products get updated.

Essential process: 1. Identify administrator by login.

2. Perform task according to need.

3. Check whether the products details is updated or not.

5 Name: Add/Edit/Delete Customer profile

Description: Administrator or staffs or customer are responsible for adding/editing/deleting customer

profile.

Actors: Administrator, Staff or customer.

Trigger: According to the need of administrator, staff or customer.

Result: The profile of customer gets updated.

Essential process: 1. Identify staff, administrator or customer by login.

2. Perform task according to need.

3. Check whether the profile is updated or not.

8. Name: checking the availability of ticket

Description: customer is responsible for availability of the ticket

Trigger: customer.

Result: the ticket is available

Essential process: 1. Identify customer by login.

2. Perform task according to need

3. specify the services / product they are interested in.

4. Check whether the ticket is available or not.

9. Name: generate the ticket

Description: customer are responsible for generating the ticket

Trigger: customer.

Result: the ticket is generated.

Essential process: 1. Identify customer by login.

2. Perform task according to need.

3. Check whether the ticket is generated or not.

10. Name: Add/Edit/Delete Staff profile

Description: staffs are responsible for adding/editing/deleting staff profile.

Actors: Staff.

Trigger: According to the need of staff.

Result: The profile of staff gets updated.

Essential process: 1. Identify staff by login.

2. Perform task according to need.

3. Check whether the profile is updated or not.

 11.Name: providing requested service to the customer.

Description: staffs are responsible for giving service to the customer.

Trigger: staff

Result: service provided to customer

Essential process: 1. Identify staff by login.

2. interact with the customer

3. increase the ticket number

4.delete the ticket number from the queue.

12. Name: Take action if network problem

Description: Administrator will take action on any network problem.

Actors: Administrator

Trigger: If there is any network problem administrator has to react.

Result: The network problem will be solved.

Essential process: 1. Identify administrator by login.

2. Take action on any network problem.

3. Check whether the problem is solved.

13. Name: Perform system backup.

Description: Administrator will be responsible for system backup.

Actors: Administrator.

Trigger: Administrator will do system backup for security purposes (ex. System crash).

Result: System will be backed up.

Essential process: 1. Identify Administrator by login.

2. Administrator will start system backup for security purpose.

3. System will be backed up.