A Project Report on

“FUEL STATION MANAGEMENT SYSTEM”

By

Yash Sharma 22225

Ritik Sharma 22203

Aniket Dhakate 22109

MCA – I, SEM – II

2021-2022

To

Savitribai Phule Pune

University Pune- 411041

In Partial Fulfillment of the Degree of

Master in Computer Application (M. C.
A.)

Under The Guidance Of

Prof. Anagha Chaudhari

Suryadatta Group of Institutes, Pune

Suryadatta Institute of Management and Mass Communication (SIMMC)
 Date:-

CERTIFICATE

This is to certify that Mr. Yash Sharma, Mr. Ritik Sharma, Mr. Aniket Dhakate has successfully

completed his/her project work entitled “Fuel Station Management System” in partial

fulfillment of MCA – I Semester-II program for the year A.Y. 2021-2022 . He have worked

under our guidance and direction.

Prof. Anagha Chaudhari Dr. Manisha

Kumbhar Project Guide HoD-MCA,SGI

Examiner 1 Examiner 2

Date :
Place : Pune(Maharashtra)
 Acknowledgment

We would like to express our sense of guidance to Dr. Manisha Kumbhar, The H.O.D
and co-ordinator Dr. Vidya Gavekar for his valuable suggestions and moral support to
carry out this project.

We would like to express our heartiest gratitude and solemn thanks to our guide Miss.
Anagha Chaudhary . Whose ever encouraging supervision and experienced guidance has
helpful to accomplish this project. We are very much dependent on her.

We would like to thank our principal Dr. Sanjay B. Chordiya. For his kindly supportand
providing us with facilities for our successful completion of the project.

Finally at last but not least we would like to thank all our colleagues and friends who have
been always there to help us, who helped us directly or indirectly in completion for this
project.

Thank You.

Student Name:

Yash Sharma

Ritik Sharma

Aniket Dhakate
 Index

Chapter Page number

CHAPTER 1 : INTRODUCTION
1.1 Existing System 2
1.2 Need for System 3

1.3 Operating Environment Hardware and 3

Software
CHAPTER 2 : PROPOSED SYSTEM
2.1 Proposed System (Introduction of system) 4
2.2 Module specifications (Scope)
2.3 Objectives of System 5
CHAPTER 3 : ANALYSIS & DESIGN
3.1 Use Case Diagrams 6

3.2 Activity Diagram 11

3.3 Class Diagram 12

3.4 Entity Relationship Diagram 13

3.5 Module Hierarchy Diagram 14

3.6 Table specifications (Database design) 15

3.7 Data Dictionary 18

CHAPTER 4 : STUDENT MANUAL

4.1 User Interface Screens (Input) 19

4.2 Output Screens with data 22

4.3 Data Reports 24

4.4 Sample program code 25

4.5 Limitations and Bibliography 31

 CHAPTER 1: INTRODUCTION

Introduction:

The “Fuel Station Management System" has been developed to override the problems
prevailing in the practicing manual system. This software is supported to eliminate and, in
some cases, reduce the hardships faced by this existing system. Moreover, this system is
designed for the particular need of the company to carry out operations in a smooth and
effective manner.
The application is reduced as much as possible to avoid errors while entering the data. It
also provides error message while entering invalid data. No formal knowledge is needed for
the user to use this system. Thus, by this all it proves it is user-friendly. Petrol Pump
Management System, as described above, can lead to error free, secure, reliable and fast
management system. It can assist the user to concentrate on their other activities rather to
concentrate on the record keeping. Thus, it will help organization in better utilization of
resources. Every organization, whether big or small, has challenges to overcome and
managing the information’s of Stocks, Fuels, Tankers, Inventory, Meter Readings. Every
Petrol Pump Management System has different Fuels needs, therefore we design exclusive
employee management systems that are adapted to your managerial requirements. This is
designed to assist in strategic planning, and will help you ensure that your organization is
equipped with the right level of information and details for your future goals. Also, for
those busy executives who are always on the go, our systems come with remote access
features, which will allow you to manage your workforce anytime, at all times. These
systems will ultimately allow you to better manage resources.

1
1.1 Existing System:

The old manual system was suffering from a series of drawbacks. Since whole of
the system was to be maintained with hands the process of keeping, maintaining
and retrieving the information was very tedious and lengthy. The records were
never used to be in a systematic order. there used to be lots of difficulties in
associating any particular transaction with a particular context. If any
information was to be found it was required to go through the different registers,
documents there would never exist anything like report generation. There would
always be unnecessary consumption of time while entering records and
retrieving records. One more problem was that it was very difficult to find errors
while entering the records. Once the records were entered it was very difficult to
update these records.
The reason behind it is that there is lot of information to be maintained and have
to be kept in mind while running the business. For this reason we have provided
features Present system is partially automated (computerized), actually existing
system is quite laborious as one has to enter same information at three different
places.

2
1.2 Need for system:

Documents and reports that must be provided by the new system: there can also be few
reports, which can help management in decision-making and cost controlling, but
since these reports do not get required attention, such kind of reports and information
were also identified and given required attention.

Details of the information needed for each document and report.

The required frequency and distribution for each document.

Probable sources of information for each document and report.

With the implementation of computerized system, the task of keeping records in an

organized manner will be solved. The greatest of all is the retrieval of information,
which will be at the click of the mouse. So, the proposed system helps in saving the
time in different operations and making information flow easy giving valuable reports.

1.3 Operating Environment Hardware and Software

Processor : Intel Core Duo 2.0 GHz or more

Front End : Html ,CSS, Java-Script

Back End : PHP, SQLite 3

Operation System : Windows 7 Or More

3
 CHAPTER 2 : PROPOSED SYSTEM

2.1 Proposed System

The proposed system has the following requirements:

 System needs store information about new entry of Fules.

 System needs to help the internal staff to keep information of Stocks and find them
as per various queries.

 System need to maintain quantity record.

 System need to keep the record of Sales. System need to update and delete the
record. System also needs a search area.

 It also needs a security system to prevent data.

2.2 Module specifications

In this system following are functions and process.

• Fuels Management Module: Used for managing the Fuels details.

• Meter Readings Module: Used for managing the details of Meter Readings

• Inventory Module: Used for managing the details of Inventory

• Stocks Management Module: Used for managing the information and details of the
Stocks.

• Sales Module: Used for managing the Sales details

• Tankers Module: Used for managing the Tankers information’s

• Login Module: Used for managing the login details

4
2.3 Objectives of System

 The main objective of the Project on Petrol Pump Management System is to

manage the details of Fuels, Stocks, Sales, Tankers, Meter Readings.

 It manages all the information about Fuels, Inventory, Meter Readings, Fuels.

 It tracks all the information of Stocks, Inventory, Tankers etc. Manage the
information of Stocks.

 Shows the information and description of the Fuels, Sales To increase efficiency of
managing the Fuels, Stocks.

 It deals with monitoring the information and transactions of Tankers. Manage the
information of Fuels.

 Editing, adding and updating of Records is improved which results in proper

resource management of Fuels data.

 Manage the information of Tankers Integration of all records of Meter Readings.

5
 CHAPTER 3 : ANALYSIS & DESIGN

3.1 Use Case Diagrams

Use Case Name : Global

Title : Fuel Station Management System

Actor : Admin/Cashier
Precondition : Enter username, password and Validate(correct/incorrect).
Main Flow : Admin and cashier can access the information and sales report.
Post Condition :Successfully Access the data

6
Use Case Name : Customer

Title : Fuel Station Management System

Actor : Admin
Precondition : Login is compulsory for admin.
Main Flow : Enter username, password and Validate(correct/incorrect).
Post Condition :Admin Can access Fuel Station Management system.

7
Use Case Name : Login

Title : Fuel Station Management System

Actor : Admin/Cashier
Precondition : Admin/Cashier Must have to enter a valid username and password.
Main Flow : Enter username, password and Validate(correct/incorrect).
Post Condition : Admin/Cashier Can Access the Components of Fuel Station Management
System.

8
Use Case Name : Inventory

Title : Fuel Station Management System

Actor : Admin
Precondition : Admin Must have to enter a valid username and password.
Main Flow : Enter username, password and Validate(correct/incorrect).
Post Condition : Admin Can Access the Components of Fuel Station Management System.

9
Use Case Name : Sales

Title : Fuel Station Management System

Actor : Admin/cashier
Precondition : Admin/Cashier Must have to enter a valid username and password.
Main Flow : Enter username, password and Validate(correct/incorrect).
Post Condition : Admin can access the information and Admin/Cashier can generates sales
report.

10
3.2 Activity Diagram

Start

11
3.3 Class Diagram

12
3.4 Entity Relationship Diagram

13
3.5 Module Hierarchy Diagram

Start

14
3.6 Table specifications(Database Design)

Table Name : Admin

Description : Login page requires users identification regularly performed by entering a
username and password combination
Primary Key : usename

Field name Data Type Size Constraint Description

Username Varchar 15 PK Enter Username

Password Varchar 10 Not Null Enter password

Table Name : customer

Description : customer information

Primary Key : CID

Field Name Data Type Size Constraint Description

CID int 10 PK Customer Id

Customername Varchar 20 Not Null Customer Name

CustomerEmail varchar 30 Not Null Customer Email

Customercontact int 10 Not Null Customer

Contact

status int 1 Not Null status

15
Table Name : User
Description : User who can access the System

Primary Key : userid

Field name Data Type Size Constraint Description

Userid Int 10 PK User Id

username Varchar 10 Not Null Username

Type Varchar 1 Not Null Select Type

Table Name : Inventory

Description : To add Types of Fuel

Primary Key : fuelid

Field name Data Type Size Constraint Description

Fuelid Int 10 PK Fuel Id

fuelname Varchar 10 Not Null Fuel Name

30 Not Null Fuel Price

fuelprice Varchar

Varchar 15 Not Null status

status

16
Table Name : POS
Description : To generate Sales Report

Primary Key : customerid

Field name Data Type Size Constraint Description

customerid Int 10 PK Customer Id

Varchar 10 Not Null Customer Name

customername

10 Not Null amount of Fuel

fuelamount int

Varchar 12 Not Null Fuel Price

fuelprice

Varchar 12 Not Null Discount

discount

Varchar 1 Not Null Payment Mode

paymentmode

Varchar 10 Not Null Total Amount

totalamount

17
3.7 Data dictionary

Sr. No Field Name Description Table Data Type Constraints

01 cid Customer Id customer int PK

02 customercontact Customer Name customer varchar Not Null

03 customereemail Customer Email customer varchar Not Null

04 customername Customer customer varchar Not Null

Contact
05 discount Discount POS int Not Null
Amount
06 fuelid Fuel Id POS int PK

07 fuelid Fuel Id inventory int PK

08 fuelamount Fuel Amount POS int Not Null

09 fuelname Fuel Name inventory varchar Not Null

10 fuelprice Fuel Price inventory int Not Null

11 password User Password admin varchar Not Null

12 paymentmode Payment Mode POS text PK

13 status Fuel Status inventory varchar Not Null

14 total Total Amount POS int Not Null

15 type user user varchar Not Null

16 userid User Id user int PK

17 username User Username admin varchar Not Null

18
 CHAPTER 4 : USER MANUAL

4.1 User Interface Screens (Input)

Login Page

Add Customer

19
Add New User

Add New Petrol Type

20
Petrol Transactions

21
4.2 Output Screens with data

Admin Dashboard

Cashier Dashboard

22
List of Customers

List of Customer Payable Balances

23
4.3 Data Reports

24
 4.4 Sample program code

<?php
session_start();
if(!isset($_SESSION['user_id'])){
header("Location:./login.php");
exit;
}
require_once('DBConnection.php');
$page = isset($_GET['page']) ? $_GET['page'] : 'home';
if($_SESSION['type'] != 1 && in_array($page,array('maintenance','products','stocks'))){
header("Location:./");
exit;
}
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title><?php echo ucwords(str_replace('_',' ',$page)) ?> | Petrol Station</title>
<link rel="stylesheet" href="./Font-Awesome-master/css/all.min.css">
<link rel="stylesheet" href="./css/bootstrap.min.css">
<script src="./js/jquery-3.6.0.min.js"></script>
<script src="./js/popper.min.js"></script>
<script src="./js/bootstrap.min.js"></script>
<link rel="stylesheet" href="./DataTables/datatables.min.css">
<script src="./DataTables/datatables.min.js"></script>
<script src="./Font-Awesome-master/js/all.min.js"></script>
<script src="./js/script.js"></script>
<style>
:root{
--bs-success-rgb:71, 222, 152 !important;
}
html,body{ hei
ght:100%;
width:100%;
}
main{
height:100%;
display:flex;
flex-flow:column;
}
#page-container{
25
 flex: 1 1 auto;
overflow:auto;
}
#topNavBar{ fl
ex: 0 1 auto;
}
.thumbnail-img{
width:50px;
height:50px;
margin:2px
}
.truncate-1 {
overflow: hidden;
text-overflow: ellipsis;
display: -webkit-box;
-webkit-line-clamp: 1;
-webkit-box-orient: vertical;
}
.truncate-3 {
overflow: hidden;
text-overflow: ellipsis;
display: -webkit-box;
-webkit-line-clamp: 3;
-webkit-box-orient: vertical;
}
.modal-dialog.large {
width: 80% !important;
max-width: unset;
}
.modal-dialog.mid-large {
width: 50% !important;
max-width: unset;
}
@media (max-width:720px){

.modal-dialog.large {
width: 100% !important;
max-width: unset;
}
.modal-dialog.mid-large {
width: 100% !important;
max-width: unset;
}

}
.display-select-image{
26
 width:60px;
height:60px;
margin:2px
}
img.display-image {
width: 100%;
height: 45vh;
object-fit: cover;
background: black;
}
/* width */
::-webkit-scrollbar {
width: 5px;
}

/* Track */
::-webkit-scrollbar-track {
background: #f1f1f1;
}

/* Handle */
::-webkit-scrollbar-thumb {
background: #888;
}

/* Handle on hover */
::-webkit-scrollbar-thumb:hover {
background: #555;
}
.img-del-btn{
right: 2px;
top: -3px;
}
.img-del-btn>.btn{
font-size: 10px;
padding: 0px 2px !important;
}
</style>
</head>
<body>
<main>
<nav class="navbar navbar-expand-lg navbar-dark bg-primary bg-gradient" id="topNavBar">
<div class="container">
<a class="navbar-brand" href="./">
Petrol Station
</a>
27
 <button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-
target="#navbarNav" aria-controls="navbarNav" aria-expanded="false" aria-label="Toggle
navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarNav">
<ul class="navbar-nav">
<li class="nav-item">
<a class="nav-link <?php echo ($page == 'home')? 'active' : '' ?>" aria-
current="page" href="./">Home</a>
</li>
<?php if($_SESSION['type'] == 1): ?>
<li class="nav-item">
<a class="nav-link <?php echo ($page == 'customer')? 'active' : '' ?>" href="./?
page=customer">Customers</a>
</li>
<li class="nav-item">
<a class="nav-link <?php echo ($page == 'balances')? 'active' : '' ?>" href="./?
page=balances">Balances</a>
</li>
<?php endif; ?>
<li class="nav-item">
<a class="nav-link <?php echo ($page == 'sales')? 'active' : '' ?>" href="./?
page=sales">POS</a>
</li>
<li class="nav-item">
<a class="nav-link <?php echo ($page == 'sales_report')? 'active' : '' ?>" href="./?
page=sales_report">Sales</a>
</li>
<?php if($_SESSION['type'] == 1): ?>
<li class="nav-item">
<a class="nav-link <?php echo ($page == 'users')? 'active' : '' ?>" aria-
current="page" href="./?page=users">Users</a>
</li>
<li class="nav-item">
<a class="nav-link" href="./?page=maintenance">Maintenance</a>
</li>
<?php endif; ?>

</ul>
</div>
<div>
<div class="dropdown">
<button class="btn btn-secondary dropdown-toggle bg-transparent text-light border-
0" type="button" id="dropdownMenuButton1" data-bs-toggle="dropdown" aria-
expanded="false">
Hello <?php echo $_SESSION['fullname'] ?>
28
 </button>
<ul class="dropdown-menu" aria-labelledby="dropdownMenuButton1">
<li><a class="dropdown-item" href="./?page=manage_account">Manage
Account</a></li>
<li><a class="dropdown-item" href="./Actions.php?a=logout">Logout</a></li>
</ul>
</div>
</div>
</div>
</nav>
<div class="container py-3" id="page-container">
<?php
if(isset($_SESSION['flashdata'])):
?>
<div class="dynamic_alert alert alert-<?php echo $_SESSION['flashdata']['type'] ?>">
<div class="float-end"><a href="javascript:void(0)" class="text-dark text-decoration-
none" onclick="$(this).closest('.dynamic_alert').hide('slow').remove()">x</a></div>
<?php echo $_SESSION['flashdata']['msg'] ?>
</div>
<?php unset($_SESSION['flashdata']) ?>
<?php endif; ?>
<?php
include $page.'.php';
?>
</div>
</main>
<div class="modal fade" id="uni_modal" role='dialog' data-bs-backdrop="static" data-bs-
keyboard="true">
<div class="modal-dialog modal-md modal-dialog-centered" role="document">
<div class="modal-content">
<div class="modal-header py-2">
<h5 class="modal-title"></h5>
</div>
<div class="modal-body">
</div>
<div class="modal-footer py-1">
<button type="button" class="btn btn-sm rounded-0 btn-primary" id='submit'
onclick="$('#uni_modal form').submit()">Save</button>
<button type="button" class="btn btn-sm rounded-0 btn-secondary" data-bs-
dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="modal fade" id="uni_modal_secondary" role='dialog' data-bs-backdrop="static"
data-bs-keyboard="true">

29
 <div class="modal-dialog modal-md modal-dialog-centered" role="document">
<div class="modal-content">
<div class="modal-header py-2">
<h5 class="modal-title"></h5>
</div>
<div class="modal-body">
</div>
<div class="modal-footer py-1">
<button type="button" class="btn btn-sm rounded-0 btn-primary" id='submit'
onclick="$('#uni_modal_secondary form').submit()">Save</button>
<button type="button" class="btn btn-sm rounded-0 btn-secondary" data-bs-
dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="modal fade" id="confirm_modal" role='dialog'>
<div class="modal-dialog modal-md modal-dialog-centered" role="document">
<div class="modal-content rounded-0">
<div class="modal-header py-2">
<h5 class="modal-title">Confirmation</h5>
</div>
<div class="modal-body">
<div id="delete_content"></div>
</div>
<div class="modal-footer py-1">
<button type="button" class="btn btn-primary btn-sm rounded-0" id='confirm'
onclick="">Continue</button>
<button type="button" class="btn btn-secondary btn-sm rounded-0" data-bs-
dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
</body>
</html>

30
4.5 Limitations

• It is complex to implement.
• Lack of robustness in a variety of problems. Also local search techniques can get
stuck at local minima.
• It requires large amount of memory because the problem instances & best solution
found so far has to be stored .

BIBLIIOGRAPHY:

https://www.tutorialspoint.com
https://www.geeksforgeeks.org
https://www.w3schools.com ›sql
https://html.com

31