CONTENTS

S.No DESCRIPTION PAGE NO

1 SYNOPSIS 2

2 INTRODUCTION 3

3 SYSTEM REQUIREMENT 5

3.1 HARDWARE SPECIFICATION 5

3.2 SOFTWARE SPECIFICATION 6

4 SYSTEM DESCRIPTION 7

5 SYSTEM ANALYSIS 10

6 SYSTEM DESIGN 12

6.1 DESIGN INTRODUCTION 12

6.2 DATA FLOW DIAGRAM 24

7 IMPLEMENTATION & TESTING 30

APPENDIX
8 32

8.1 SAMPLE CODE 32

8.2SCREEN LAYOUTS 43

9 CONCLUSION 58

10 FUTURE ENHANCEMENT 59

11 BIBLIOGRAPHY 60

1
 1. SYNOPSIS
“Bank Locker Management System” is responsible for keeping all the record of
assign lockers which is assign by banker. This system helps the locker holder who
wants to keep their valuable with bank with high safety.

The main objective of “Bank Locker Management System” project is to provide easier
to bank and locker holder.

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.

2
 2. INTRODUCTION

Bank Locker Management System is a web based application which deals with bank
lockers which stores valuables things of bank customers. All details of lockers are
saved in database. This project is developed using PHP with MySQL extension.

This project has three modules i.e. Banker, Sub-banker and User

Modules
In this project user is those who have locker in bank. With the help of locker number
user can see the details of lockers.

Banker Modules

Dashboard: In this section, Banker briefly views the Total assign lockers, Total Sub-
Banker and Total Locker Type.

Sub-Banker: In this section, banker manage sub-banker (Add/Update/Delete).

Locker-Type: In this section, banker mange locker type (Add/Update/Delete).

Assign Locker: In this section, banker assign the locker to customers or users with
providing unique locker number and key number of lockers through locker
number users or customer can view the details of their locker.

Reports: In this section, two reports are available.

▪ B/w Dates Report: Banker can view a number of assign lockers in particular
periods.

▪ Search Report: Banker can search locker details by using Locker

Number/Key Number.

3
Pages: In this Section, Admin can manage the content of about us and contact us
pages.

Account Settings:

▪ Profile: In this section, admin can update his/her profile.

▪ Change Password: In this section admin can change his/her own

passwords

▪ Logout: Through this button admin can log out.

Sub-Banker Module
Sub-Banker and Banker features are the same except Sub-Banker creation. Sub-Banker
can’t create the Sub-Banker.

Purpose

The main purpose of the "Bank Locker Management System" is to offers better
solution for bank security system. It manages all the information about assign bank
locker. Banks offers locker facilities to individuals at vey small annual fee. These
lockers are maintained in a secure facility that is under constant surveillance and
security.

Scope

The Software design document would demonstrate how the design will accomplish
the functional and non- functional requirements captured in the Software
Requirement specification (SRS). The document will provide a framework to the
programmers through describing the high level components and architecture, sub
systems, interfaces, database design and algorithm design. This is achieved through
the use of architectural patterns, design patterns, sequence diagrams, class diagrams,
relational models and user interfaces.

4
 3.SYSTEM REQUIREMENT

3.1 Hardware specification:

Client Side:
RAM 512 MB

Hard disk 10 GB

Processor 1.0 GHz

Server side:
RAM 1 GB

Hard disk 20 GB

Processor 2.0 GHz

3.2 Software specification:

Client side:
Google Chrome or any compatible
Web Browser browser
Operating System
Windows or any equivalent OS

5
Server Side:

Web Server APACHE

Server side Language PHP5.6 or above version

Database Server MYSQL

Google Chrome or any compatible

Web Browser browser

Operating System Windows or any equivalent OS

6
 4. SYSTEM DESCRIPTION

APACHE
The Apache HTTP Server Project is an effort to develop and maintain an open-
source HTTP server for modern operating systems including UNIX and Windows.
The goal of this project is to provide a secure, efficient and extensible server that
provides HTTP services in sync with the current HTTP standards.
The Apache HTTP Server ("httpd") was launched in 1995 and it has been the most
popular web server on the Internet since April 1996. It has celebrated its 20th
birthday as a project in February 2015.

PHP

PHP (Hypertext Processor) is a general-purpose scripting language and interpreter that is freely
available and widely used for web development. The language is used primarily for server-side
scripting, although it can also be used for command-line scripting and, to a limited
degree, desktop applications.
The acronym PHP was originally derived from Personal Home Page Tools, but it now stands for
PHP: Hypertext Preprocessor, which the PHP Group's documentation describes as a "recursive
acronym."
When used for server-side scripting, PHP is added to a webpage for the purpose of
generating dynamic content when the page is accessed through a client browser. The web server
runs the script before transmitting the page to the browser.

To support this process, the web server requires PHP to be installed on the server, along with a
PHP parser -- either a Common Gateway Interface (CGI) parser or a server module.

7
When a user requests a webpage from the server, the parser interprets the PHP portion of the
page, performs the operations called for in the PHP script, and generates the Hypertext Markup
Language (HTML) that results from those operations. The HTML is then sent to the client
browser, along with any other HTML on the page, providing a seamless rendering of the content.
Webpages that contain PHP script are considered to be dynamic HTML pages because content
varies based on the results of interpreting the script.

• PHP stands for PHP: Hypertext Preprocessor.

• PHP is a server-side scripting language, like ASP.

• PHP scripts are executed on the server.

• PHP supports many databases (MYSQL, Informix, Oracle, Sybase, Solid,

Generic ODBC, etc.).
• PHP is an open source software .

• PHP is free to download and use.

MYSQL

MySQL is an open-source relational database management system we can interact with using
Structured Query Language (SQL). A query language is a simple programming language that can
help you access, manipulate and manage data in a relational database. We use MySQL to store all
the information you need to efficiently run large, complex websites.

MySQL represents the M in LAMP (Linux, Apache, MySQL, PHP/Perl/Python), which is a

collection of tools used to build web applications. In order to build a web application, we need an
operating system, a web server to hold our web application, a database that stores and allows us
to access the data and a programming language to develop our application.

8
Since MySQL is a commonly used database management system, it’s supported by various
programming languages like Python, PHP and JavaScript, hence we can run it on any platform or
operating system.
MySQL is used by many of the world’s most powerful web applications
like Uber, Netflix, Slack, Twitter, Shopify and Airbnb.

• MYSQL is a database server

• MYSQL is ideal for both small and large applications

• MYSQL supports standard SQL

• MYSQL compiles on a number of platforms

• MYSQL is free to download and use

9
 5. SYSTEM ANALYSIS

The analysis of the requirement has lead to a conclusion that the project is feasible
with respect to time and cost. The data collection from the field is assured by the client
to provide. The technology used to develop is almost Open Source, therefore less cost
for implementation and maintenance will be involved.
A feasibility study is an analysis used in measuring the ability and likelihood to
complete a project successfully including all relevant factors. It must account for
factors that affect it such as economic, technological and time factors.
It is used to assess the strengths and weaknesses of a proposed project and present
directions of activities which will improve a project and achieve desired results.

Economic feasibility
The purpose of economic feasibility assessment is to determine the positive economic
benefits to the organization that the proposed system will provide. The assessment
typically involves a cost/benefits analysis.

Technical feasibility
Technical analysis is a trading tool employed to evaluate securities and attempt to
forecast the future movement. I am using java language and other tools like net beans
to develop the software.

10
Operational feasibility
Operational feasibility is a measure of how well proposed system solves the
problems, and takes advantage of the opportunities identified during scope definition
and how it satisfies the requirements analysis phase of the system development.

Analysis and Design

Analysis:

In present all doctor appointment work done on the paper. The whole year data is

stored in the registers. We can’t generate reports as per our requirements because its

take more time to calculate report of doctor appointments.

Disadvantage of present system:

• Not user friendly: The present system not user friendly because data is not

stored in structure and proper format.

• Manual Control: All report calculation is done manually so there is a chance of

error.

• Lots of paper work: Visitors maintain in the register so lots of paper require

storing details.

• Time consuming

11
 6.SYSTEM DESIGN

6.1 Design Introduction:

Design is the first step in the development phase for any techniques and principles for
the purpose of defining a device, a process or system in sufficient detail to permit its
physical realization.

Once the software requirements have been analyzed and specified the software design
involves three technical activities - design, coding, implementation and testing that
are required to build and verify the software.

The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its
ease of maintenance are made. These decisions have the final bearing upon
reliability and maintainability of the system.
Design is the only way to accurately translate the customer’s requirements into
finished software or a system.

Design is the place where quality is fostered in development. Software design is a

process through which requirements are translated into a representation of software.
Software design is conducted in two steps. Preliminary design is concerned with the
transformation of requirements into data

12
UML Diagrams:
Actor:

A coherent set of roles that users of use cases play when interacting with the use
`cases.

Use case:A description of sequence of actions, including variants, that a system

performs that yields an observable result of value of an actor.

UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any
product after analysis. The goal from this is to produce a model of the entities
involved in the project which later need to be built. The representation of the entities
that are to be used in the product being developed need to be designed.

13
USECASE DIAGRAMS:

Use case diagrams model behavior within a system and helps the developers
understand of what the user require. The stick man represents what’s called an actor.

Use case diagram can be useful for getting an overall view of the system and clarifying
who can do and more importantly what they can’t do.

Use case diagram consists of use cases and actors and shows the interaction between
the use case and actors.

• The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.

• An actor could be the end-user of the system or an external system.

A Use case is a description of set of sequence of actions. Graphically it is rendered

as an ellipse with solid line including only its name. Use case diagram is a behavioral
diagram that shows a set of use cases and actors and their relationship. It is an
association between the use cases and actors. An actor represents a real-world
object. Primary Actor – Sender, Secondary Actor Receiver.

14
Use Case Diagrams:

Banker
Sign In

Dashboard

Manage Sub-Banker

Manage Locker Type

Manage Assign Locker

Search Assign Lockers

Generate Reports

Update Profile

Change Password

Password Recovery

15
Sub-Banker

Sign In

Dashboard

Manage Locker Type

Manage Assign Locker

Search Assign Lockers

Generate Reports

Update Profile

Change Password

Password Recovery

16
User

Visit Website

Search Locker Details

View Contact

View About Us

17
Class Diagram:
A description of set of objects that share the same attributes operations, relationships,
and semantics.

18
ER Diagram:

The Entity-Relationship (ER) model was originally proposed by Peter in 1976

[Chen76] as a way to unify the network and relational database views. Simply stated
the ER model is a conceptual data model that views the real world as entities and
relationships. A basic component of the model is the Entity-Relationship diagram
which is used to visually represent data objects. Since Chen wrote his paper the
model has been extended and today it is commonly used for database design for the
database designer, the utility of the ER model is:

• It maps well to the relational model. The constructs used in the ER model can
easily be transformed into relational tables.
• It is simple and easy to understand with a minimum of training.
Therefore, the model can be used by the database designer to
communicate the design to the end user.
• In addition, the model can be used as a design plan by the database developer
to implement a data model in specific database management software.

ER Notation

There is no standard for representing data objects in ER diagrams. Each modeling

methodology uses its own notation. The original notation used by Chen is widely used
in academics texts and journals but rarely seen in either CASE tools or publications
by non-academics. Today, there are a
number of notations used; among the more common are Bachman, crow's foot,
and IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality
of a connection. The notation used in this document is from Martin. The symbols used
for the basic ER constructs are:

19
 • Entities are represented by labeled rectangles. The label is the name of the

entity. Entity names should be singular nouns.

• Relationships are represented by a solid line connecting two entities.

The name of the relationship is written above the line. Relationship

names should be verbs

• Attributes, when included, are listed inside the entity rectangle.

Attributes which are identifiers are underlined. Attribute names should be

singular nouns.

• Cardinality of many is represented by a line ending in a crow's foot.

If the crow's foot is omitted, the cardinality is one.

Existence is represented by placing a circle or a perpendicular bar on the line.

Mandatory existence is shown by the bar (looks like a 1) next to the
entity for an instance is required. Optional existence is shown by placing a circle next
to the entity that is optional.

20
ER Diagram

21
 MySQL Data Tables
Assign Locker Table:(Table name is tblassignlocker)
This store the details of lockers holders and their locker.

Banker details table(Table name is tblbanker)

This table stores the bankers and sub banker details.

22
 Locker type Table: (Table name is tbllockertype)
This table stores the locker type available in the bank.

Website page Table: (Table name is tblpage)

This table stores the details of website.

23
6.2 Data Flow Diagrams

A Data Flow Diagram (DFD) is a traditional visual representation of the information

flows within a system. A neat and clear DFD can depict the right amount of the
system requirement graphically. It can be manual, automated, or a combination of
both.

It shows how data enters and leaves the system, what changes the information, and
where data is stored.

The objective of a DFD is to show the scope and boundaries of a system as a whole. It
may be used as a communication tool between a system analyst and any person who
plays a part in the order that acts as a starting point for redesigning a system. The DFD
is also called as a data flow graph or bubble chart.

The following observations about DFDs are essential:

1. All names should be unique. This makes it easier to refer to elements in the
DFD.
2. Remember that DFD is not a flow chart. Arrows is a flow chart that represents
the order of events; arrows in DFD represents flowing data. A DFD does not
involve any order of events.
3. Suppress logical decisions. If we ever have the urge to draw a diamond-shaped
box in a DFD, suppress that urge! A diamond- shaped box is used in flow
charts to represents decision points with multiple exists paths of which the only
one is taken. This implies an ordering of events, which makes no sense in a
DFD.
4. Do not become bogged down with details. Defer error conditions and error
handling until the end of the analysis.

Standard symbols for DFDs are derived from the electric circuit diagram analysis and
are shown in fig:

24
Circle: A circle (bubble) shows a process that transforms data inputs into data
outputs.

Data Flow: A curved line shows the flow of data into or out of a process or data store.

Data Store: A set of parallel lines shows a place for the collection of data items. A
data store indicates that the data is stored which can be used at a later stage or by the
other processes in a different order. The data store can have an element or group of
elements.

Source or Sink: Source or Sink is an external entity and acts as a source of system
inputs or sink of system outputs.

25
Zero Level DFD

Locker-Type Password
Management
Management

Banker Login
Management BLMS Management

Sub-Banker Authorization
Management Management

Webpages Assign Locker

Management Management

26
First Level DFD

Locker-Type Password
Management
Management

Banker Webpages

Management BLMS Management

Sub-Banker Login

Management Management

Generate
Authorization
Report
Management

Assign Locker Search Report

Management Management

27
Second Level DFD
Login to Check Roles
Banker system of access

Manage Sub-
Banker

Manage Locker
Type
Forgot
Password Check
Credential
Assign Locker

Manage
Modules
Manage Web
Pages

Generate Report
Change Update Profile Search Locker
Password Details

28
 Login to
Check Roles
Sub-Banker system
of access

Manage Locker
Type
Forgot
Password Check
Credential
Assign Locker

Manage
Modules
Manage Web
Pages

Generate Report
Change Update Profile Search Locker
Password Details

29
 7. IMPLEMENTATION AND TESTING

After all phase have been perfectly done, the system will be implemented to the server
and the system can be used.

System Testing

The goal of the system testing process was to determine all faults in our

project .The program was subjected to a set of test inputs and many explanations were made and
based on these explanations it will be decided whether the program behaves as expected or not.
Our Project went through two levels of testing

1. Unit testing

2. Integration testing

Unit Testing

Unit testing is commenced when a unit has been created and effectively reviewed .In
order to test a single module we need to provide a complete environment i.e. besides
the section we would require

• The procedures belonging to other units that the unit under test calls
• Non local data structures that module accesses
• A procedure to call the functions of the unit under test with
appropriate parameters

30
1. Test for the admin module

• Testing admin login form-This form is used for log in of

administrator of the system. In this form we enter the username and
password if both are correct administration page will open otherwise
if any of data is wrong it will get redirected back to the login page and
again ask the details.
• Report Generation: admin can generate report from the main
database.

INTEGRATION TESTING

In the Integration testing we test various combination of the project module

by providing the input.

The primary objective is to test the module interfaces in order to confirm that
no errors are occurring when one module invokes the other module.

31
 8. APPENDIX

Sample Code:

SQL to create the tables:

sql
Copy
-- Create database
CREATE DATABASE bank_locker_system;

USE bank_locker_system;

-- Users table
CREATE TABLE users (
user_id INT AUTO_INCREMENT PRIMARY KEY,
name VARCHAR(100) NOT NULL,
email VARCHAR(100) NOT NULL UNIQUE,
password VARCHAR(255) NOT NULL
);

-- Lockers table
CREATE TABLE lockers (
locker_id INT AUTO_INCREMENT PRIMARY KEY,
locker_number VARCHAR(50) NOT NULL,
status ENUM('available', 'booked') DEFAULT 'available'
);

32
-- Transactions table (for tracking locker bookings)
CREATE TABLE transactions (
transaction_id INT AUTO_INCREMENT PRIMARY KEY,
user_id INT,
locker_id INT,
booking_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
FOREIGN KEY (user_id) REFERENCES users(user_id),
FOREIGN KEY (locker_id) REFERENCES lockers(locker_id)
);

Step 2: Frontend (HTML Forms)

Let’s start by creating the forms needed for the Bank Locker Management System:
1. Registration Form (register.php)
html
Copy
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Register - Bank Locker</title>
</head>
<body>
<h2>Register</h2>
<form action="register.php" method="POST">
Name: <input type="text" name="name" required><br>
Email: <input type="email" name="email" required><br>

33
 Password: <input type="password" name="password" required><br>
<button type="submit" name="submit">Register</button>
</form>
</body>
</html>

2. Login Form (login.php)

html
Copy
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Login - Bank Locker</title>
</head>
<body>
<h2>Login</h2>
<form action="login.php" method="POST">
Email: <input type="email" name="email" required><br>
Password: <input type="password" name="password" required><br>
<button type="submit" name="submit">Login</button>
</form>
</body>
</html>

34
3. Locker Booking Form (book_locker.php)
html
Copy
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Book Locker - Bank Locker</title>
</head>
<body>
<h2>Available Lockers</h2>
<form action="book_locker.php" method="POST">
<select name="locker_id">
<!-- Lockers will be populated dynamically -->
<?php
// Connect to the database and retrieve available lockers
$conn = new mysqli("localhost", "root", "", "bank_locker_system");
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

$result = $conn->query("SELECT * FROM lockers WHERE status = 'available'");

while ($row = $result->fetch_assoc()) {
echo "<option value='" . $row['locker_id'] . "'>" . $row['locker_number'] .
"</option>";
}

35
 ?>
</select><br>
<button type="submit" name="book">Book Locker</button>
</form>
</body>
</html>

Step 3: Backend Logic (PHP)

1. Registration Logic (register.php)

php
Copy
<?php
if (isset($_POST['submit'])) {
$name = $_POST['name'];
$email = $_POST['email'];
$password = password_hash($_POST['password'], PASSWORD_DEFAULT);

$conn = new mysqli("localhost", "root", "", "bank_locker_system");

if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

$sql = "INSERT INTO users (name, email, password) VALUES ('$name', '$email',
'$password')";

36
 if ($conn->query($sql) === TRUE) {
echo "Registration successful!";
} else {
echo "Error: " . $sql . "<br>" . $conn->error;
}

$conn->close();
}
?>

2. Login Logic (login.php)

php
Copy
<?php
session_start();
if (isset($_POST['submit'])) {
$email = $_POST['email'];
$password = $_POST['password'];

$conn = new mysqli("localhost", "root", "", "bank_locker_system");

if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

$sql = "SELECT * FROM users WHERE email = '$email'";

$result = $conn->query($sql);

37
 if ($result->num_rows > 0) {
$user = $result->fetch_assoc();

if (password_verify($password, $user['password'])) {
$_SESSION['user_id'] = $user['user_id'];
header("Location: book_locker.php");
} else {
echo "Invalid password!";
}
} else {
echo "User not found!";
}

$conn->close();
}
?>

3. Locker Booking Logic (book_locker.php)

php
Copy
<?php
session_start();
if (!isset($_SESSION['user_id'])) {
echo "Please login first!";
exit;
}

38
if (isset($_POST['book'])) {
$locker_id = $_POST['locker_id'];
$user_id = $_SESSION['user_id'];

$conn = new mysqli("localhost", "root", "", "bank_locker_system");

if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}

// Check if locker is available

$sql = "SELECT * FROM lockers WHERE locker_id = '$locker_id' AND status =
'available'";
$result = $conn->query($sql);

if ($result->num_rows > 0) {
// Update locker status to 'booked'
$conn->query("UPDATE lockers SET status = 'booked' WHERE locker_id =
'$locker_id'");

// Record the transaction

$conn->query("INSERT INTO transactions (user_id, locker_id) VALUES
('$user_id', '$locker_id')");

39
 echo "Locker booked successfully!";
} else {
echo "Locker is already booked or does not exist.";
}

$conn->close();
}
?>

<?php
include('config.php');

function display_lockers() {
global $conn;

// Fetch available and booked lockers

$sql = "SELECT * FROM lockers";
$result = $conn->query($sql);

if ($result->num_rows > 0) {
while($row = $result->fetch_assoc()) {
echo "Locker " . $row['locker_id'] . ": " . $row['status'] . "<br>";
}
} else {
echo "No lockers available.";
}
}
40
function book_locker($user_name, $locker_id, $pin) {
global $conn;

// Check if locker is already booked

$sql = "SELECT * FROM lockers WHERE locker_id = '$locker_id' AND status =
'Booked'";
$result = $conn->query($sql);

if ($result->num_rows > 0) {
echo "Locker $locker_id is already booked.<br>";
return;
}

// Book the locker

$sql = "UPDATE lockers SET status = 'Booked', user_name = '$user_name', pin = '$pin'
WHERE locker_id = '$locker_id'";

if ($conn->query($sql) === TRUE) {

echo "Locker $locker_id successfully booked for $user_name.<br>";
} else {
echo "Error: " . $conn->error . "<br>";
}
}

function cancel_locker($locker_id) {
global $conn;

41
 // Check if the locker is booked
$sql = "SELECT * FROM lockers WHERE locker_id = '$locker_id' AND status =
'Booked'";
$result = $conn->query($sql);

if ($result->num_rows > 0) {
// Cancel booking
$sql = "UPDATE lockers SET status = 'Available', user_name = NULL, pin = NULL
WHERE locker_id = '$locker_id'";

if ($conn->query($sql) === TRUE) {

echo "Booking for Locker $locker_id canceled successfully.<br>";
} else {
echo "Error: " . $conn->error . "<br>";
}
} else {
echo "Locker $locker_id is not booked yet.<br>";
}
}
?>

42
Screen Layouts:

Project URL: http://localhost/blms

Home Page

43
Search Locker Details

44
View Locker Details

45
Banker or Sub Banker Login Page

Forgot Password

46
Dashboard

Profile

47
Change Password

Add Sub-Banker

48
Manage Sub-Banker

Update Sub-Banker

49
Add Locker Type

Manage Locker Type

50
Update Locker Type

Assign Locker

51
Manage Assign Locker

52
Update Assign Locker

53
Update Image

Between Dates Report

54
View Between Dates Report

Search Report

55
View Search Report

About Us Page

56
Contact Us Page

57
 9.CONCLUSION

This Application provides a computerized version of bank lockers facility which will
benefit the people who locker in bank.

It makes entire process online and can generate reports. It has a facility of bankers
login, sub-banker login where banker can manage assign lockers and generate
assign lockers report.

The application was designed in such a way that future changes can be done easily.
The following conclusions can be deduced from the development of the project.

• Automation of the entire system improves the productivity.

• It provides a friendly graphical user interface which proves to be better
when compared to the existing system.
• It gives appropriate access to the authorized users depending on their
permissions.
• It effectively overcomes the delay in communications.
• Updating of information becomes so easier.
• System security, data security and reliability are the striking features.
• The System has adequate scope for modification in future if it is
necessary.

58
 10.FUTURE ENHANCEMENT

I have tried to design the software in such a way that the user may not have any
difficulty in using this system and further expansion is also possible. New
requirements will be added and risk will be analyzed in every phase until the
requirement of user will not be fulfilled. The most priority will be given to keep
confidential data secure and easy and simple for use.

The further enhancements which can be made in the system are:

• Any requirement that will make system easy to use or make a system secure, these
requirement will be add using Spiral Model. Other requirement related to government

or municipality will be added when required.

• For the identity of user and for their data integrity, digital signature can be added to this
system.
• For the identity of user and for verification, image of user can be added to this system.
• There will be provision of filling form in multiple languages.
• A great concern will be given on frontend design which will make user to use system
easily and enjoy while using this system.

59
 11.BIBLIOGRAPHY

For PHP

• https://www.w3schools.com/php/default.asp
• https://www.sitepoint.com/php/
• https://www.php.net/

For MySQL

• https://www.mysql.com/
• http://www.mysqltutorial.org

For XAMPP

• https://www.apachefriends.org/download.html

60