Bank Locker Management System

Submitted by
Rehmat Ullah Shehzad
Registration No. 321730608

Under the supervision of

Ma’am Mehwish Rasheed

BSCS

National College of Business Administration and

Economics 40/F-1, Gulberg III, Lahore – 54660, Pakistan

Bank Locker Management System | P a g e | 1

 Bank Locker Management System

By
Rehmat Ullah Shehzad
Registration No. 321730608

Supervised by
Ma’am Mehwish Rasheed

A PROJECT SUBMITTED IN PARTIAL FULFILLMENT OF

THE REQUIREMENTS OF THE DEGREE

FEB 2022
Bank Locker Management System | P a g e | 2
Bank Locker Management System | P a g e | 3
 CERTIFICATION
This is to certify that Rehmat Ullah Shehzad bearing Registration No. 321730608
has completed the final project titled as “Bank Locker Management System” at the
Department of Computer Science, National College of Business Administration and
Economics Lahore, to fulfill the partial requirement for the degree of BS - CS.

NATIONAL COLLEGE OF BUSINESS ADMINISTRATION & ECONOMICS

LAHORE

For the award of the

degree of

BS (COMPUTER
SCIENCE)

Supervisor

Ma’am Mehwish Rasheed Signature:

__________________

Project Coordinator Head of Department

Bank Locker Management System | P a g e | 4
 DECLARATION

The work reported in this project was carried by me under the

supervision of Project Supervisor, Ma’am Mehwish Rasheed,at National
College of Business Administration and Economics Lahore.
I hereby declare that this project and the contents of project are the
product of my own research, and no part has been copied from any other
written or published source (accept the references, standard mathematical or
genetics models / equation / formulas / protocol etc.).
I further declare that this work has not been submitted for award of
any other degree / diploma.
The university may act if the provided information is found inaccurate at any
stage.

Name : Rehmat Ullah Shehzad

Registration No. : 321730608

Bank Locker Management System | P a g e | 5

 ACKNOWLEDGEMENT
A project like this is never the work of anyone alone. The
contributions of many people, in their different ways, have made it possible.
I would like to extend my appreciation especially to the following.
Thank God for the wisdom and perseverance that he has been
bestowed upon me during this project, and indeed, throughout my life: "I can
do everything through him who gives us strength."
Ma’am Mehwish Rasheed helps for making this project possible. Her
support, guidance, advice throughout the project, as well as her pain-staking
effort in proofreading the drafts, is greatly appreciated. Indeed, without her
guidance, I would not be able to put the topic together. Thanks Ma’am
Mehwish Rasheed. Ma’am Mehwish Rasheed, encouraging me to undertake
the honors program. The experience has been an interesting and rewarding
one. Of course, this project would not have been possible without the
participation of the subjects.
Finally, I would like to thank my parents for their unconditional
support, both financially and emotionally throughout my degree. In
particular, the patience and understanding shown by my mother, father and
brothers during the honors year is greatly appreciated. I know, at times, my
temper is particularly trying.

Bank Locker Management System | P a g e | 6

 Abstract
There are banks for people to keep their valuable things saved in an
allocated locker which they can access anytime they want Just like people
don’t keep the savings at home, use banks instead and make transactions
when needed.
It comes with a high level of accountability from bank’s side to make sure
that the right person gets access to the right locker and keep track of it for
security purposes. Most banks use paper documents to keep track of the
activity which at this point is very old school.
The purpose of IT is to replace as much paperwork as possible hence an
application to cover everything would be the best possible solution.
This web app is going to resolve the mentioned issue, it will give bank
locker manager the ability to register users, register lockers and book a
certain locker to a specific user.
The software will also give the option for check in and check out for the
users, the software will also generate activity report for the checked duration
of time.

Bank Locker Management System | P a g e | 7

 Table of Contents
CHAPTER 1: Introduction .............................................................................................. 13
Introduction ............................................................................................................. 13
1.1 Purpose of this Project .......................................................................................... 13
1.2 Project scope .......................................................................................................... 14
1.3 Project Planning .................................................................................................... 14
1.4 Risk Management.................................................................................................. 15
1.5 Project risk ............................................................................................................. 15
1.6 Product Risk .......................................................................................................... 15
CHAPTER 2: Review of Literature ............................................................................... 16
2.1 Area of Studies ....................................................................................................... 16
2.2 System Requirements Determination .................................................................. 16
2.3 Tools / Languages .................................................................................................. 16
2.4 Reason of Development ......................................................................................... 16
2.5 Main Reasons to Development ............................................................................. 17
CHAPTER 3: Materials and Methods ............................................................................ 18
3.1 System Functional Requirements ........................................................................ 19
3.1.1 Preliminary Investigation ............................................................................... 19
Feasibility Study ............................................................................................................................... 18
I) Technical Feasibility ..................................................................................................................... 18
II) Operational Feasibility ............................................................................................................... 18
III) Economic Feasibility .................................................................................................................. 19

3.1.2 Objectives of Preliminary Investigation........................................................ 19

3.1.3 Steps of Preliminary Investigation ................................................................ 19
Step 1: Obtain Authorization to proceed ........................................................................................ 19
Step 2: Identify the Necessary Information Feasibility .................................................................. 19
Step 3: Identify the Necessary Information Feasibility .................................................................. 19
Step 4: Identify the Necessary Information Feasibility .................................................................. 20
Step 5: Identify the Necessary Information Feasibility .................................................................. 20

3.2 System Analysis ..................................................................................................... 20

3.2.1 System Requirement Determination .............................................................. 20
3.2.2 Fact Finding Techniques ................................................................................. 21
I) Interviews ...................................................................................................................................... 21

Bank Locker Management System | P a g e | 8

 II) Data Collection ............................................................................................................................ 25
III) Reviewing the Documents ......................................................................................................... 22
IV) Observations ............................................................................................................................... 22
V) Questionnaires ............................................................................................................................. 23
VI) Research...................................................................................................................................... 23

3.3 Interface requirements ...................................................................................... 24

3.4 Regulatory Requirements ..................................................................................... 24
3.5 Security Requirements.......................................................................................... 24
3.6 System Non-functional requirements .................................................................. 25
3.7 Performance Requirements .................................................................................. 25
3.8 Safety Requirements ............................................................................................. 25
3.9 System Security Requirements ............................................................................ 25
3.10 Interface specifications ....................................................................................... 25
Software Quality Attributes............................................................................................................... 25
System Interfaces:............................................................................................................................... 25
Customer Interface: ........................................................................................................................... 25
Hardware Interfaces: ......................................................................................................................... 25
Software Interfaces: ........................................................................................................................... 25

CHAPTER 4: System Design Phase ............................................................................... 26

4.1 USE CASE DIAGRAM ........................................................................................ 26
4.2 Activity Diagram ................................................................................................... 27
4.3 Entity Relationship Diagram ............................................................................... 28
4.4 Add New Locker System Sequence Diagram ..................................................... 29
4.5 Modify Locker System Sequence Diagram ......................................................... 30
4.6 Delete Locker System Sequence Diagram ........................................................... 31
4.7 Add New User System Sequence Diagram .......................................................... 32
4.8 Modify User System Sequence Diagram ............................................................. 33
4.9 Delete User System Sequence Diagram ............................................................... 34
4.10 Level 0 DFD ......................................................................................................... 35
4.11 Level 1 DFD ......................................................................................................... 36
CHAPTER 5: System Development & Testing ............................................................... 37
5.1 Testing Methods .................................................................................................... 37
5.2 Black Box Testing .................................................................................................. 37
5.3 White Box Testing ................................................................................................. 37
5.4 Grey Box Testing ................................................................................................... 38

Bank Locker Management System | P a g e | 9

 5.5 TEST CASE ........................................................................................................... 38
5.6 INTEGRATION TESTING ................................................................................. 49
Top down ............................................................................................................................................. 49
Bottom up ............................................................................................................................................ 49

5.7 SYSTEM IMPLEMENTATION AND EVALUATION ................................... 49

CHAPTER 6: User Manual............................................................................................. 50
6.1 Login form ............................................................................................................. 50
6.2 Main Navigation bar ............................................................................................. 50
6.3 Add user form ........................................................................................................ 51
6.4 Edit user form ........................................................................................................ 52
6.5 Delete user .............................................................................................................. 53
6.6 Locker List View ................................................................................................... 54
6.7 Add Locekr Modal ................................................................................................ 54
6.8 Edit Locker Form .................................................................................................. 54
6.9 Booking Form ........................................................................................................ 55
6.10 Record List ........................................................................................................... 55
6.11 Check in................................................................................................................ 56
6.12 Check out ............................................................................................................. 56
6.13 Report Form ........................................................................................................ 57
6.14 Report View ......................................................................................................... 57
6.15 Admin Dashboard ............................................................................................... 58
CHAPTER 7: Results and Discussions ........................................................................... 59
7.1 Preliminary Investigation Report ........................................................................ 59
7.1.1 Introduction ............................................................................................................................... 59
7.1.2 Preliminary Investigation Findings .......................................................................................... 59
7.1.3 Recommendations ...................................................................................................................... 60
7.1.4 Time and Cost benefits .............................................................................................................. 60
7.1.5 Expected Benefits ....................................................................................................................... 61

7.2 System Requirement Document ........................................................................... 61

7.2.1 Context Level Diagram ............................................................................................................. 62
7.2.2 0 Level Diagram ......................................................................................................................... 63

7.3 Operational Information System ......................................................................... 64

7.4 Benefits ................................................................................................................... 65
7.5 Future work ........................................................................................................... 66
7.6 References .............................................................................................................. 66
Bank Locker Management System | P a g e | 10
 List of Figures
Fig 4.1 Use Case Diagram ........................................................................................... 26
Fig 4.2 Activity Diagram ............................................................................................. 27
Fig 4.3 Entity Relationship Diagram ......................................................................... 28
Fig 4.4 SSD Add New User ......................................................................................... 29
Fig 4.5 SSD Modify User............................................................................................. 30
Fig 4.6 SSD Delete User .............................................................................................. 31
Fig 4.7 SSD Add New Locker ..................................................................................... 32
Fig 4.8 SSD Modify Locker ........................................................................................ 33
Fig 4.9 SSD Delete Locker ...........................................................................................34
Fig 4.10 DFD Level 0 ................................................................................................... 35
Fig 4.11 DFD Level 1 ................................................................................................... 36
Fig 4.12 Context Level Diagram ................................................................................ 62
Fig 4.1Level Diagram .................................................................................................. 63

Bank Locker Management System | P a g e | 11

 List of Tables
Table 5.1 Test Case 1................................................................................................... 38
Table 5.2 Test Case 2................................................................................................... 38
Table 5.3 Test Case 3................................................................................................... 39
Table 5.4 Test Case 4................................................................................................... 39
Table 5.5 Test Case 5................................................................................................... 40
Table 5.6 Test Case 6................................................................................................... 40
Table 5.7 Test Case 7................................................................................................... 41
Table 5.8 Test Case 8................................................................................................... 41
Table 5.9 Test Case 9................................................................................................... 42
Table 5.10 Test Case 10............................................................................................... 42
Table 5.11 Test Case 11............................................................................................... 43
Table 5.12 Test Case 12............................................................................................... 43
Table 5.13 Test Case 13............................................................................................... 44
Table 5.14 Test Case 14............................................................................................... 44
Table 5.15 Test Case 15............................................................................................... 45
Table 5.16 Test Case 16............................................................................................... 45
Table 5.17 Test Case 17............................................................................................... 46
Table 5.18 Test Case 18............................................................................................... 46
Table 5.19 Test Case 19............................................................................................... 45
Table 5.20 Test Case 20............................................................................................... 47
Table 5.21 Test Case 21............................................................................................... 47
Table 5.22 Test Case 22............................................................................................... 48

Bank Locker Management System | P a g e | 12

CHAPTER 1: Introduction

Introduction
This project is mainly developed to manage the record of users and
lockers digitally so that the record will remain available for a long time
without error. The record is saved in the database so we can retrieve specific
data any time whenever we want. Manage the check in and checkout
process of users easily without error.
In this the payroll system is a system which organizes all the tasks of
employee payment.
The software has many functionalities such as
• Maintaining the records
• User Management
• Check-in check-out system
• Locker Management
• Generating Reports
• Retrieving data any time
• System authentication

1.1 Purpose of this Project

At present, manual system is being utilized in the bank lockers. It
requires the manager to manually monitor each activity that is available in
the bank locker. This usually leads to mistakes as the workload of the
manager increases. This management system is designed to improve
accuracy and to enhance safety and efficiency in the bank locker. This
cloud-based system will help the bank manager to improve check in check
out management, bookings, lockers etc.

Bank Locker Management System | P a g e | 13

 This project is amid to manage records and control check in check out
system. The bank is currently having a manual system which is not a
technical way to control the flow of the activity. This manual system also
has many problems. For example, data and hard copy can be damaged or
misplaced so finding record in such situation is very difficult, sometimes it
may take days to finding proper result.to overcome this problem and provide
the shop a good and automated system this project has been taken.

It manages the users of the lockers by registering them and keeps the
record of their check ins on daily bases. It has the facility to manage the
records of lockers.

1.2 Project scope

The basic purpose of this system is to manage all records and maintain
the bookings digitally. Basically, it will be used for managing large number
of data digitally so that data of users can remain intact for a long time
without error and can be used further.
The purpose of our system to help to save time for authorizes from
manual work. The system handles all the operations and generates reports in
seconds.

1.3 Project Planning

After selecting this project, I must plan how to complete it. So, this
project, Bank locker management system was a great task for me.
First, I consulted my supervisor and took guidelines to start the
project, after that analyzed the project, saw how to manual system works,
and took synopses of each aspect of the project. I consulted with the User
and took requirements and started to plan to work on the project according to
given requirements.
I planned to talk to a bank locker manager on weekly bases and
started to work on project according to their requirements.

Bank Locker Management System | P a g e | 14

After that I divided the project in three phases.
➢ Designing
➢ coding
➢ implementation

1.4 Risk Management

The basic risks involved in the project were the “System Familiarity”
and the “System Support”.
The elimination of such risks was made possible by making sure, the
system was “User Friendly, efficient and Interactive”, and by assuring there
was adequate support for the system to work i.e., in the form of the computer
systems that could serve the purposes, without slowing down the
performance, otherwise the system would have been of no use. Fortunately,
our system doesn’t need much of such processing requirements and most of
the system can easily accommodate this application. In business the
forecasting and evaluation of financial risks together with the identification
of procedures to avoid or minimize their impact. Upon the completion of the
project, I will analyze risks. Based on this analysis, the project supervisor
will identify any improvements that can be made to manage those risks and
develop risk management process to minimize its impact on project.

1.5 Project risk

• The methodology to solve the problem can’t work in a proper manner.
• Budget does not enough or there is no budget.
• Hardware requirements can’t come in the time

1.6 Product Risk

• Packages and development tools do not enough
• Cannot find the suitable components.
• The user may be computer illiterate.

Bank Locker Management System | P a g e | 15

CHAPTER 2: Review of Literature

2.1 Area of Studies

This section is related to the description of the system specifications
and the tools that were used to design and develop the project.
2.2 System Requirements Determination
• Software Requirements:
Microsoft Windows (xp, 7, 8, 8.1, 10)
A web browser (Chrome, Firefox etc.)
• Hardware Requirements:
A Computer
Internet connection

2.3 Tools / Languages

Tools are the backbone of any system. If there is no tool to develop
the system, then there is no meaning of any system. Tools are very necessary
for any system. That’s why we have also a combination of tools like:
• HTML/CSS
• Javascript
• PHP
• Mysqli (Database)
2.4 Reason of Development
This project is aimed to manage records and control check-in
checkout process of users, bookings, and activity system. The bank is
currently having a manual system which is not a technical way to control the
flow of user record. This manual system is also having many problems. For
example, data and hard copy can be damaged or misplaced so finding record
in such situation is very difficult, sometimes it may take days to finding
proper result.

Bank Locker Management System | P a g e | 16

 To overcome this problem and provide the shop a good and automated
system this project has been taken. Here the technique we already store data
in our data base along with detail to use this data to manage the record of
products as well as the data will also be used by the Bank lockers.

2.5 Main Reasons to Development

• Less price consumption
• Manage data digitally
• Privacy and security
• Easily manage activity without error
• Generate Reports
• Less time consuming
.

Bank Locker Management System | P a g e | 17

CHAPTER 3: Materials and Methods

3.10 Feasibility Studies

Feasibility study is to study about the problem and carries out the best
system which meets all the requirements which is needed or necessary.
Feasibility study is determining the financially and technically study to
develop the system. They involve in analysis the problem and collect all the
information about it.

Technical Feasibility
• Specifying equipment and system that will successfully satisfy the
User requirement.
• The facility to produce outputs in each time.
• Response time under certain conditions.
• Ability to process and generate repots at a particular speed.
• In technical feasibility, configuration of the system is given more
importance than the actual makes of hardware. What speeds of input
and output should be achieved at quality of printing?
Operational Feasibility
• What changes will be brought with the system?
• What organizational structures are disturbed?
• What new skills will be required? Do the existing staff members have
these skills? If not, can they be trained in due course of time?
In this operational feasibility is operate the system a person should be able
to know about the system and easily understand to it they should be skilled
full if system generate any error the person how controls it should be able to
remove it or manage.

Bank Locker Management System | P a g e | 18

Economic Feasibility
• How will it affect the system economically?
• What ease does it provide the people?
In Economic feasibility the system should be enhanced and play part in
making this better economically as well.

3.1.2 Objectives of Preliminary Investigation

The main objective of preliminary investigation is to make sure what we are

going to be developing is going to be useful for the system, Technically,
operationally, and economically.
• It provides ease of work for the managers.
• It brings a level of feasibility to the users and the conveniency that is
certainly needed.
• It makes the system work faster and smoother saving time and effort
on both sides.

3.1.3 Steps of Preliminary Investigation

Step 1: Obtain Authorization to Proceed

In is necessary to have an authorization from the authority to proceed
working on the system and if it’s useful and harmless in every way.

Step 2: Identify the Necessary Information

For the system to be built it is essential to have the necessary
information from the relevant people in our case the bank locker
managers and the bank locker users.

Step 3: Perform Fact Finding

It was a complex procedure because most of the countries that use this
bank locker system are in Europe and America, so I gathered the requisite
information online.

Bank Locker Management System | P a g e | 19

 Step 4: Analyze the Information
Once the information was gathered, I gave it a fair thought if it was
worth developing the bank locker management system or not, turns out it
is going to be very useful and certainly needed.

Step 5: Report to Management

After the whole process I made a proposal based on the points I’ve
made and reported to the management that gave me a go ahead to develop
the application.

3.2 System Analysis

3.2.1 System Requirement Determination

In system functional requirements we are describing that what things will
be done in the project.
• In this system all functionality is done by admin and user who can add,
delete and update.
• It manages have the facility to manage the bookings of the lockers,
every month.
• Admin manages the users of the bank lockers by registering them and
keeps the record of their activity on daily bases.
• It generates reports about check-in, check-out, bookings, users,
lockers.
• Our program provide functionality to print reports.
• Reports provide to the manager with the activity, time, date, user, the
locker and contract details.

Bank Locker Management System | P a g e | 20

3.2.2 Fact Finding Techniques

I) Interviews

An interview is the most used technique to collect information from

the face-to-face interviews. The purpose of the interview is to find, verify,
clarify facts, motivate end-users involved, identify requirements, and gather
ideas and opinions. The role of the interview includes the interviewer who is
a system analyst and the interviewee who is a system owner or user. The
interviewing technique needs good communication skills for interaction
between system analysts and users.

There are two types of interviews.

▪ Unstructured interviews
An interview that is conducted with only a general goal or
subject in mind and with few, if any, specific questions. The
open-ended questions type is used in an unstructured interview
that allows the user to answer freely in an appropriate way.
▪ Structured interviews
A structured interview is an interview that contains a predefined
set of questions. In a structured interview, close-ended questions
type is used to limit answers to specific choices, short and direct
responses from the interviewees.

II) Data Collection

Fact-finding techniques are used in the early stage of the System

Development Life Cycle including the system analysis phase, design, and
post-implementation review. Facts included in any information system can
be tested based on three steps: data facts used to create useful information,
process- functions to perform the objectives, and interface- designs to
interact with users.

Bank Locker Management System | P a g e | 21

III) Reviewing The Documents

The best way to analyze the existing system is to collect facts from
existing documentation rather than from human sources. There are various
kinds of documents to collect facts from existing documents. These include
e-mails, customer complaints, suggestion box notes, and reports that
document the problem area problem performance reviews, samples of
completed manual forms and reports, and samples of completed
computerized forms and reports various types of flowcharts and diagrams,
program documentation, and user training manuals. System analyst uses
sampling techniques to organize the above documentation. The sampling
technique is the process of combing a representative sample of documents,
forms, and records.

IV) Observations

Another fact-finding technique is observation. In this technique, the

system analyst participates in the organization, studies the flow of
documents, applies the existing system, and interacts with the users.
Observation can be a useful technique when the system analyst has a user
point of view. A sampling technique called work sampling is useful for
observation. By using this technique, system analysts can know how
employees spend their days.

Bank Locker Management System | P a g e | 22

V) Questionnaires

Questionnaires are also one of the useful fact-finding techniques to

collect information from many users. Users fill up the questions which are
given by the system analyst and then give the answers back to the system
analyst. Questionnaires can save time because the system analyst does not
need to interview each of the users and if the time of the interview is short,
questionnaires are more useful. To fulfill the requirements of the system
objective, a system analyst should have the ability to clearly define the
design and frame of questionnaires.

There are two types of questionnaires:

▪ Free-format questionnaires
In free format questionnaires, users are allowed to answer
questions freely without an immediate response. The results are
also useful in learning about the feelings, opinions, and
experiences of the respondents.
▪ Fixed-format questionnaires
The purpose of fixed-format questionnaires is to gather
information from the predefined format of questions. Users are
allowed to choose the result from the given answers. There are
three types of fixed-format questions: multiple-choice questions
(Yes or No type), rating questions (Strongly Agree, Agree, no
opinion, Disagree, strongly disagree), ranking questions.

VI) Research

Research and site visits are the process of examining the problems
which had previously solved by other sources that can be either human or
documents. To solve the requirements of the problem, the analyst visits other
organizations that had previously experienced similar problems. In addition,
the analyst can also find the information from the database, reference books,
case studies, and the Internet.

Bank Locker Management System | P a g e | 23

3.3 Interface requirements
The interface is highly user friendly. Labeled text boxes and buttons
are used that’s why a computer illiterate user can also perform different
tasks on the system easily. There are some fields that accept only numeric
data. There are some fields that accept the text data. The date field only
accepts the dates before the current date.
3.4 Regulatory Requirements
The system will have complete access to Admin or Controller who
control software only who can manage all kinds of transactions and
generates reports and invoice and send message to customers.
3.5 Security Requirements
In security requirements the following things/points are required:
• Admin/User login is provided security to unauthorized access.
3.6 System Non-functional requirements
In system non-functional requirements we are describing that how the
performance of the project will work. How will much the project work
efficiently? How the project provides the safety. How the project provides
the security to avoid from the unauthorized access.
3.7 Performance Requirements
The system will take minimum time to access data from database.
Customers get invoices.
3.8 Safety Requirements
To prevent data loss in case of system failure, we provide backup
function to backup all data added by user.
3.9 System Security Requirements
System needs username and password to secure our system privacy. If
anyone wants to use it or hack it, he/she will not allow using system.

Bank Locker Management System | P a g e | 24

3.10 Interface specifications
Software Quality Attributes
• The Quality of the System is maintained in such a way, that the system
is made Customer friendly.
• The system quality attributes are assumed as under:
➢ Accurate and hence reliable.
➢ Secured.
➢ Fast speed.
➢ Compatibility.

System Interfaces:
This section describes how the system interfaces with other software
products or Customers for input or output.

Customer Interface:
Application will be accessed over the windows. The system would be
fully compatible with Windows Operating system. No User would be able to
access any part of the application without logging on to the system.

Hardware Interfaces:
• A working PC.
• Data connection.

Software Interfaces:
• Microsoft Windows (xp, 7, 8, 8.1, 10)
• A browser

Bank Locker Management System | P a g e | 25

CHAPTER 4: System Design Phase

4.1 USE CASE DIAGRAM

Bank Locker Management System | P a g e | 26

4.2 Activity Diagram

Bank Locker Management System | P a g e | 27

4.3 Entity Relationship Diagram

Bank Locker Management System | P a g e | 28

4.4 Add New Locker System Sequence Diagram

Bank Locker Management System | P a g e | 29

4.5 Modify Locker System Sequence Diagram

Bank Locker Management System | P a g e | 30

4.6 Delete Locker System Sequence Diagram

Bank Locker Management System | P a g e | 31

4.7 Add New User System Sequence Diagram

Bank Locker Management System | P a g e | 32

4.8 Modify User System Sequence Diagram

Bank Locker Management System | P a g e | 33

4.9 Delete User System Sequence Diagram

Bank Locker Management System | P a g e | 34

4.10 Level 0 DFD

Bank Locker Management System | P a g e | 35

4.11 Level 1 DFD

Bank Locker Management System | P a g e | 36

CHAPTER 5: System Development & Testing

5.1 Testing Methods

There are different methods which can be used for system testing.
This chapter briefly describes those methods.

5.2 Black Box Testing

The technique of testing without having any knowledge of the interior
workings of the application is Black Box testing. The tester is oblivious to
the system architecture and does not have access to the source code.
Typically, when performing a black box test, a tester will interact with the
system's Admin interface by providing inputs and examining outputs
without knowing how and where the inputs are worked upon.

5.3 White Box Testing

White box testing is the detailed investigation of internal logic and
structure of the code. White box testing is also called glass testing or open
box testing. In order to perform white box testing on an application, the
tester needs to possess knowledge of the internal working of the code.
The tester needs to have a look inside the source code and find out
which unit/chunk of the code is behaving inappropriately.

Bank Locker Management System | P a g e | 37

 5.4 Grey Box Testing

5.5 TEST CASE

Test Case ID: Test 1 Test Engineer: Rehmat Ullah
Shehzad
Objective: Verify that system initialize successfully
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Initialization successful
Comments: Passed
Table 5.1 Test Case 1

Test Case ID: Test 2 Test Engineer: Rehmat Ullah

Shehzad
Objective: Verify that interface is displayed
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Program
2. Interface Displayed Successful

Comments: Passed

Table 5.2 Test Case 2

Bank Locker Management System | P a g e | 38

 Test Case ID: Test 3 Test Engineer: Rehmat Ullah
Shehzad
Objective: Verify that admin login successfully
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the program
2. Admin login successful
Comments: Passed

Table 5.3 Test Case 3

Test Case ID: Test 4 Test Engineer: Rehmat

Ullah Shehzad
Objective: Verify that system run successfully
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the program
2. Main Items inserted Successfully

Comments: Passed

Table 5.4 Test Case 4

Bank Locker Management System | P a g e | 39

 Test Case ID: Test 5 Test Engineer: Rehmat Ullah
Shehzad
Objective: Verify that the record is retrieved successfully
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Retrieve selected data.

Comments: Passed

Table 5.5 Test Case 5

Test Case ID: Test 6 Test Engineer: Rehmat
Ullah Shehzad
Objective: Verify that all record in definitions is updated successfully
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Retrieve selected data.
3. Update/Modify Data.

Comments: Passed

Table 5.6 Test Case 6

Bank Locker Management System | P a g e | 40

 Test Case ID: Test 7 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admin add Locker
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Click on Add button.
3. Enter data or information

Comments: Passed

Table 5.7 Test Case 7

Test Case ID: Test 8 Test Engineer: Rehmat

Ullah Shehzad
Objective: Admin update Lockers
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Click on update Locker and save data after updating.
3. Updated successfully.

Comments: Passed

Table 5.8 Test Case 8

Bank Locker Management System | P a g e | 41

 Test Case ID: Test 9 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admin deletes the locker.
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Click on delete item tab and search item to be deleted and after that press
delete button.
3. Deleted successfully.

Comments: Passed

Table 5.9 Test Case 9

Test Case ID: Test 10 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admin de-active the locker
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Click on delete function.
3. Record and items deactivate.

Comments: Passed

Table 5.10 Test Case 10

Bank Locker Management System | P a g e | 42

 Test Case ID: Test 11 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admin updates the user info.
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Click on Update employee tab.
3. Update/Modify category.

Comments: Passed

Table 5.11 Test Case 11

Test Case ID: Test 12 Test Engineer: Rehmat Ullah

Shehzad
Objective: Admin mark check in
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Click on check in mark.
3. Attendance Marked.

Comments: Passed

Table 5.12 Test Case 12

Bank Locker Management System | P a g e | 43

 Test Case ID: Test 13 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admin check activity
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Click on activity.
3. Check activity successfully.

Comments: Passed

Table 5.13 Test Case 13

Test Case ID: Test 14 Test Engineer: Rehmat Ullah

Shehzad
Objective: Admin generate activity report
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Click Activity Report button.
3. Activity report generated successfully.

Comments: Passed

Table 5.14 Test Case 14

Bank Locker Management System | P a g e | 44

 Test Case ID: Test 15 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admins creates activity report
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Create report
3. Save the report

Comments: Passed

Table 5.15 Test Case 15

Test Case ID: Test 16 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admin generates monthly/Yearly report
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Click on monthly/Yearly report.
3. Monthly/Yearly report generated.
4. Message send successfully

Comments: Passed

Table 5.16 Test Case 16

Bank Locker Management System | P a g e | 45

 Test Case ID: Test 17 Test Engineer: Rehmat Ullah
Shehzad
Objective: Check-out
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Check-out
3. Successfully completed return

Comments: Passed

Table 5.17 Test Case 17

Test Case ID: Test 18 Test Engineer: Rehmat Ullah

Shehzad
Objective: Admin make Request
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Log in the Web Application
3. Make the Request

Comments: Passed

Table 5.18 Test Case 18

Bank Locker Management System | P a g e | 46

 Test Case ID: Test 19 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admin random time report
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Log in the Web Application
3. Interact with random report input

Comments: Passed

Table 5.19 Test Case 19

Test Case ID: Test 20 Test Engineer: Rehmat Ullah

Shehzad
Objective: Admin generates Activity report.
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Log in the Web Application
3. Update activity status successfully

Comments: Passed

Table 5.20 Test Case 20

Bank Locker Management System | P a g e | 47

 Test Case ID: Test 21 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admin view the activity history
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Admin start the report.
3. All activity record shown in the form of report.

Comments: Passed

Table 5.21 Test Case 21

Test Case ID: Test 22 Test Engineer: Rehmat Ullah
Shehzad
Objective: Admin view User Record
Product: Bank Locker Management System
Environment: Web Application

Methods:
1. Launch the Web Application.
2. Log in the Web Application
3. Click on action Icon.
4. View the User Report

Comments: Passed

Table 5.22 Test Case 22

Bank Locker Management System | P a g e | 48

 5.6 INTEGRATION TESTING
Integration testing is the phase of software testing in which individual
software modules are combined and tested as a group. It occurs after unit
testing and before validation testing. Integration testing takes as its input
module that have been unit tested, groups them in larger aggregate, applies
tests defined in an integration test plan to those aggregates and delivers its
output that integrated system ready for system testing.
Two types of integration testing approach in software testing we used are:

Top down
All top-level integrated modules are tested first, and its sub modules
tested from top to bottom step by step.

Bottom up
All bottom level integrated sub modules are tested first, and its main
modules are tested from bottom to up step by step.

5.7 SYSTEM IMPLEMENTATION AND EVALUATION

Customer evaluation report means how much Customer get benefit
from locker. How he/she feels after using the locker. How much Customer
satisfied to this service?
• Reliability: Reliability does not fail or crash often.
• Usability: Usability is sufficiently convenient for the intended Customer.
• Availability: Availability is easy to access and available when needed.
Customer tests the system according to above defined factors and
he/she accepts that our system is according to his/her need

Bank Locker Management System | P a g e | 49

CHAPTER 6: User Manual

6.1 Login form

6.2 Main Navigation bar

Bank Locker Management System | P a g e | 50

6.3 Add User form

Bank Locker Management System | P a g e | 51

6.4 Edit user form

Bank Locker Management System | P a g e | 52

6.5 Delete User

6.6 Lockers List View

Bank Locker Management System | P a g e | 53

6.7 Add Locker Modal

6.8 Edit locker form

Bank Locker Management System | P a g e | 54

6.9 Booking form

6.10 Records List

Bank Locker Management System | P a g e | 55

6.11 Check In

6.12 Check out

Bank Locker Management System | P a g e | 56

6.13 Report Form

6.14 Report View

Bank Locker Management System | P a g e | 57

6.15 Admin Dashboard

Bank Locker Management System | P a g e | 58

CHAPTER 7: Results and Discussions

7.1 Preliminary Investigation Report

7.1.1 Introduction

As the world is progressing everything is going advanced day by day

and nothing and no one wants to be left behind, so is the case in this scenario
where bank locker systems are in need of a high digital upgrade to benefit
the users and the managers.
As of now managers must spend a lot of time keeping track of every
check in a and check out manually and user have to wait in line to get there
check ins and outs. The system is very slow and old, it needs and upgrade.
That’s exactly where our cutting-edge application comes in to play.
We take the old system and blend it in to the new very fast, reliable,
and quick digital system where both managers and user of the bank lockers
will be benefited. It is time saving, effort saving and comprehensive in its
field. Hence proving the need of the system in the first place.

7.1.2 Preliminary Investigation Findings

The whole system is currently slow and messy due to a lot of

paperwork. In today’s digital world where everything getting advanced day
by day there is no excuse for this system to be left behind.
Proving the need of our software preliminary investigation helped me
find out the real reason why it will be useful to have it developed.
There are number of bank locker owners waiting for a system like this to be
developed so we have customers in place even before the launch of the
product which is really good.

Bank Locker Management System | P a g e | 59

7.1.3 Recommendations

Up till this point it has been made clear what the current system needs
so with out further a due we can start designing and developing the software,
but the recommendations are always nice to keep in check in case something
that was not in out mind comes up and helps us make the final product more
useful and comprehensive.
Below are a couple of recommendations made by the manager and user we
talked to:
• Make the software user friendly
• Aesthetically appealing user interface
• Optimized system
• Less loading times
• Quick turn around
• Security
• Handy reports

7.1.4 Time and Cost Benefits

Like every other application our Bank locker management system also
brings a lot of benefits to the table. Two of them being the time and cost
which can be considered the main reasons why one would want to have a
digital management system in the first place.
The time will absolutely be decreased for both sides being managers
and user, managers won’t have to write notebooks and keep users waiting
for their turns.

Bank Locker Management System | P a g e | 60

User will be able to quickly get in and get out since nobody has extra time to
waste in the current day and age.
Once the software is developed the bank locker systems won’t have to cut
out a massive budget for the paperwork. The data can be saved in the
database at very cheap price making this also very cost beneficial.

7.1.5 Expected Benefits

There is actually nothing to lose here as the bank locker management

system brings nothing but benefits to the table for both the managers, user
and owners of the bank lockers.
Now the question may arise of as how will it be beneficial to the owner?
Owner can at anytime check when a user was checked in or checked out in
case of any trouble just like the managers.
A digital system to replace a manual system always comes with a number of
benefits like without even trying.
Same way our web application the bank locker management system brings a
lot to the organization.
We can list a lot of benefits of the bank locker management system off the
top of the head right away. Some of the a re below
• Cost beneficial
• Time beneficial
• User friendly environment
• Security
• Longevity in data recollection
• Little to no paperwork
• Quick access to the users
• Customer attraction because of the latest technology
• Trust-worthy bank locker system
• Efficiency in work

Bank Locker Management System | P a g e | 61

7.2 System Requirement Document

7.2.1 Context Level Diagram

Bank Locker Management System | P a g e | 62

7.2.2 0 Level Diagram

Bank Locker Management System | P a g e | 63

7.3 Operational Information System

Operational Information system, an integrated set of components for

collecting, storing, and processing data and for providing information in the
right way, knowledge, and digital products. Business firms and other
organizations rely on information systems to carry out and manage their
operations just like bank lockers, interact with their customers and suppliers,
and compete in the marketplace to keep going.
As major new technologies for recording and processing information were
invented over the times, new capabilities showed up, and people became
empowered in every way. The invention of the online systems by developers
in 21st century and the invention of a mechanical locker by banks in the 21st
century is but two examples. These inventions led to a profound revolution
in the ability to record, process, show, and reach for information and
knowledge. This led, in turn, to even deeper changes in individual
lives, bank lockers, and human governance.

The main components of information systems are computer hardware

and software, telecommunications, databases and data warehouses, human
resources, and procedures. The hardware, software, and
telecommunications constitute information technology (IT), which is now
ingrained in the operations and management of organizations.

Computer software bank locker management system falls into two broad
classes: system software and application software. The principal system
software is the world wide web host. It manages the hardware, data and
program files, and other system resources and provides means for the user to
control the computer, generally via a graphical user interface
(GUI). Application software is programs designed to handle specific tasks
for users. Mobile apps became a common way for individuals to access
information systems. Other examples include general-purpose application
suites with their spreadsheet and word processing programs, as well as
“vertical” applications that serve a specific industry segment—for instance,
an application that schedules, routes, and tracks package deliveries for an
overnight carrier. Larger firms use licensed applications developed and
maintained by specialized software companies, customizing them to meet
their specific needs, and develop other applications in-house or on an
outsourced basis. Companies may also use applications delivered as

Bank Locker Management System | P a g e | 64

software-as-a-service (SaaS) from the cloud over the Web. software,
available from and supported by its vendors, is being challenged by open-
source software available on the Web for free use and modification under a
license that protects its future availability.

7.4 Benefits

Like every other application our Bank locker management system also
brings a lot of benefits to the table. Two of them being the time and cost
which can be considered the main reasons why one would want to have a
digital management system in the first place.
The time will absolutely be decreased for both sides being managers
and user, managers won’t have to write notebooks and keep users waiting
for their turns.
User will be able to quickly get in and get out since nobody has extra time to
waste in the current day and age.
Once the software is developed the bank locker systems won’t have to cut
out a massive budget for the paperwork. The data can be saved in the
database at very cheap price making this also very cost beneficial.

There is actually nothing to lose here as the bank locker management system
brings nothing but benefits to the table for both the managers, user and
owners of the bank lockers.
Now the question may arise of as how will it be beneficial to the owner?
Owner can at any time check when a user was checked in or checked out in
case of any trouble just like the managers.
A digital system to replace a manual system always comes with a number of
benefits like without even trying.

Bank Locker Management System | P a g e | 65

Same way our web application the bank locker management system brings a
lot to the organization.

We can list a lot of benefits of the bank locker management system off the
top of the head right away. Some of the a re below
• Cost beneficial
• Time beneficial
• User friendly environment
• Security
• Longevity in data recollection
• Little to no paperwork
• Quick access to the users
• Customer attraction because of the latest technology
• Trust-worthy bank locker system
• Efficiency in work

7.5 Future Work

As the hardware of the Bank locker advances the web app will have
room for improvements as well. For instance, we can add fingerprint
scanners to enhance the check in and check out experience making the
process a lot convenient and quick for both the users and the admin as the
timestamps will automatically be updated in the database for each activity.
New features can be added after taking feedback from the admin and the
users on how to make it better. There’s always room for improvement for
everything.

7.6 References
https://www.w3schools.com/php/
https://www.php.net/
https://www.mysql.com/
https://www.w3schools.com/js/
https://stackoverflow.com

Bank Locker Management System | P a g e | 66