“PETROL PUMP MANAGEMENT”

A
Project Report
submitted
in partial fulfillment
for the award of the Degree of
Bachelor of Technology
in Department of Computer Science and Engineering

Project Mentor: Submitted By :

Name : Mr. Pratipal Singh Abhishek Rajora (19ESKCS009)
Designation :Assistant Professor Aditya Nehra (19ESKCS018)
Ajay Prajapat (19ESKCS019)
Akash Gupta (19ESKCS020)

Department of Computer Science and Engineering

Swami Keshvanand Institute of Technology, M & G, Jaipur
Rajasthan Technical University, Kota
Session 2022-2023
 Swami Keshvanand Institute of Technology,
Management & Gramothan, Jaipur
Department of Computer Science and Engineering

CERTIFICATE

This is to certify that Mr Abhishek Rajora, a student of B.Tech(Computer Science

& Engineering) VII semester has submitted his/her Project Report entitled

”PetrolPumpManagementSystem” under my guidance.

Mentor Coordinator

Name : Mr. Pratipal Singh Name : Mr. Sumit Mathur

Designation : Assistant Professor Designation : Assistant Professor
Signature : Signature :

Department of Computer Science and Engineering, SKIT College, Jaipur ii

 Swami Keshvanand Institute of Technology,
Management & Gramothan, Jaipur
Department of Computer Science and Engineering

CERTIFICATE

This is to certify that Mr Aditya Nehra, a student of B.Tech(Computer

Science & Engineering) VII semester has submitted his/her Project Report
entitled
”PetrolPumpManagementSystem” under my guidance.

Mentor Coordinator

Name : Mr. Pratipal Singh Name : Mr. Sumit Mathur

Designation : Assistant Professor Designation : Assistant Professor
Signature : Signature :

Department of Computer Science and Engineering, SKIT College, Jaipur iii

Department of Computer Science and Engineering, SKIT College, Jaipur iv
 Swami Keshvanand Institute of Technology,
Management & Gramothan, Jaipur
Department of Computer Science and Engineering

CERTIFICATE

This is to certify that Mr Ajay Prajapat, a student of B.Tech(Computer

Science & Engineering) VII semester has submitted his/her Project Report
entitled
”PetrolPumpManagementSystem” under my guidance.

Mentor Coordinator

Name : Mr. Pratipal Singh Name : Mr. Sumit Mathur

Designation : Assistant Professor Designation : Assistant Professor
Signature : Signature :

Department of Computer Science and Engineering, SKIT College, Jaipur v

Department of Computer Science and Engineering, SKIT College, Jaipur vi
 Swami Keshvanand Institute of Technology,
Management & Gramothan, Jaipur
Department of Computer Science and Engineering

CERTIFICATE

This is to certify that Mr Akash Gupta, a student of B.Tech(Computer Science

& Engineering) VII semester has submitted his/her Project Report entitled

”PetrolPumpManagementSystem” under my guidance.

Mentor Coordinator

Name : Mr. Pratipal Singh Name : Mr. Sumit Mathur

Designation : Assistant Professor Designation : Assistant Professor
Signature : Signature :

Department of Computer Science and Engineering, SKIT College, Jaipur vii

 DECLARATION

We hereby declare that the report of the project entitled “Petrol Pump Management” is a
record of an original work done by us at Swami Keshvanand Institute of Technology,
Management & Gramothan, Jaipur under the mentorship of Mr. Pratipal Singh (Dept. of
Computer Science & Engineering) and coordinator Mr. Sumit Kumar (Dept. of
Computer Science & Engineering). This project report has been submitted as the proof of
original work for the particular fulfillment of the requirements for the award of the degree
Bachelor of Technology (B.Tech) in the Department of Computer Science. It has not been
submitted anywhere else, under any other program to the best of our knowledge.

Team Members: Signature:

Abhishek Rajora (19ESKCS009)
Aditya Nehra (19ESKCS018)
Ajay Prajapat (19ESKCS019)
Akash Gupta (19ESKCS020)

Department of Computer Science and Engineering, SKIT College, v

 Acknowledgement

A project of such vast coverage cannot be realized without help from numerous sources and
people in the organization. We take this opportunity to express our gratitude to all those who
have been helping us in making this project successful.

We are highly indebted to our faculty mentor Mr. Pratipal Singh. Hee has been a guide,
motivator and source of inspiration for us to carry out the necessary proceedings for the project
to be completely successful. We would also like to thank Mr. Sumit Mathur for his co-operation,
encouragement, valuable suggestions and critical remarks that galvanized our efforts in the right
direction.

We would also like to convey our sincere thanks to Prof. Dr. Mukesh Kumar Gupta,
HOD, Department of Computer Science and Engineering, for facilitating, motivating and
supporting us during each phase of development of the project. Also, we pay our sincere
gratitude to all the Faculty Members of Swami Keshvanand Institute of Technology,
Management & Gramothan, Jaipur and all our Colleagues for their co-operation and support.

Last but not least we would like to thank all those who have directly or indirectly helped and
cooperated in accomplishing this project.
.

Team Members:
Signature:
Abhishek Rajora (19ESKCS009)
Aditya Nehra (19ESKCS018)
Ajay Prajapat (19ESKCS019)
Akash Gupta (19ESKCS020)

Department of Computer Science and Engineering, SKIT College, i

Table of Content

1 Introduction 2
1.1 Problem Statement and Objective . . . . . . . . . . . . . . . . . . . 2
1.2 Literature Survey /Market Survey/Investigation and Analysis . . . . 2
1.3 Introduction to Project . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Proposed Logic / Algorithm / Business Plan / Solution / Device . . . 3
1.5 Scope of the Project . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Software Requirement Specification 5

2.1 Overall Description . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.1 Product Perspective . . . . . . . . . . . . . . . . . . . 5
2.1.1.1 System Interfaces . . . . . . . . . . . . . . . 5
2.1.1.2 User Interfaces . . . . . . . . . . . . . . . . . 5
2.1.1.3 Hardware Interfaces . . . . . . . . . . . . . . 6
2.1.1.4 Software Interfaces . . . . . . . . . . . . . . 6
2.1.1.5 Communications Interfaces . . . . . . . . . 6
2.1.1.6 Memory Constraints . . . . . . . . . . . . . 7
2.1.1.7 Operations . . . . . . . . . . . . . . . . . . . . 7
2.1.1.8 Project Functions . . . . . . . . . . . . . . . 7
2.1.1.9 User Characteristics . . . . . . . . . . . . . . 7
2.1.1.10 Constraints . . . . . . . . . . . . . . . . . . . 7
2.1.1.11 Assumption and Dependencies . . . . . . . 7

3 System Design Specification 8

3.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 Module Decomposition Description . . . . . . . . . . . . . . . . . 8
3.3 High Level Design Diagrams . . . . . . . . . . . . . . . . . . . . . 9
3.3.1 Use Case Diagram . . . . . . . . . . . . . . . . . . . . 9

Department of Computer Science and Engineering, SKIT, Jaipur viii

3.3.2 Activity Diagram.......................................................... 10
4 Methodology and Team 11
4.1 Introduction to Waterfall Framework.......................................................11
 4.2 Team Members, Roles & Responsibilities................................................14

5 Centering System Testing 15

5.1 Functionality Testing................................................................................15
5.2 Performance Testing................................................................................16
5.3 Usability Testing......................................................................................16

6 Test Execution Summary 17

7 Project Screen Shots 18

8 Project Summary and Conclusions 23

8.1 Conclusion................................................................................................ 23

9 Future Scope 25

References 25
List of Figures

3.1 Use Case diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.2 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3 Activity Diagram.......................................................................................10

4.1 WaterFall model........................................................................................12

Department of Computer Science and Engineering, SKIT College, x

List of Tables

6.1 Table to test captions and labels................................................................17

Department of Computer Science and Engineering, SKIT, x

Chapter 1
Introduction

1.1 Problem Statement and Objective

In present system all report work is done manually at the petrol pump. Admin user
have to check each petrol pump in city to buy petrol, but in our proposed system
user can check availability petrol from his monitor by clicking on some available
button. This system also keeps records of user. Admin can also check which pump
available how much petrol and what amount he submitted to ac- countant at the end
of the day. Admin can also check how much oil availability in one day. This system
also helps admin to generate the record of each pump on the basis of his position
and working hour.

1.2 Literature Survey /Market Survey/Investigation and Analy-

sis

Everything has been digitized. In many existing systems, almost all petrol pumps
have a controlling unit to perform the tasks like managing the electrical pump, drive
the display, measure the flow accordingly turn OFF the electrical pump. But still a
person is required to collect the money and there is a possi- bility of many human
errors. In this proposed petrol pump automation system, we are using RFID card to
access petrol at different petrol stations of different petrol companies across the
country and here.

1.3 Introduction to Project

The following project is about petrol pump management. Where three user are
possible which are admin, operator and customer. Admin has the highest au- thority
among three. He check for the attendance. Changes all the fuel price

Department of Computer Science and Engineering, SKIT, 1

according to government standard everyday. Operator mark his attendance ev- ery
day after login. And generate the bill according to customer usage. Apart from that
operator update the bill in the petrol pump management system. The project is web
based application where HTML (HyperText Markup Language) is used to create
framework for each page of web. While CSS is used to design the particular page.
And give various effect to the webpage, make it look more appealing. Javascript is
used to provide the functionality to the website. It is backbone of the web
application. Sql will be used to interact with the database. And update the database
according to the need. Most frequent use of database is to get the current fuel price
from the database, because every day price is updated and use for generating the
bill. Apart from that it is used to authenti- cate the user. By verifying the username
and password of the user , which can be either admin or operator. Database is also
use for the attendance purpose where all attendance of the employees are stored in
the database. It is also usedfor evaluation of employees .

1.4 Proposed Logic / Algorithm / Business Plan / Solution / De-

vice

Petrol pump software is a pioneer in fuel station management across globe. With the
advancement of technology it’s important for an business owner to utilize its
optimum resources for the enhancement of profits. We understand the technological
advancements and strive to deliver the best to our fuel station business owners. Our
comprehensive ERP software provides you complete in- sight of your business
including operation,inventory,income and profitability inhassle freeway.

1.5 Scope of the Project

There are four basic users – Administrator, Operator and User/Customer. All users
have their own profiles in PPMS. Customer can pay the fuel amount to the operator
via system Administrator check for the attendance. Administrator

Department of Computer Science and Engineering, SKIT College, Jaipur 2

update the fuel price every day according to government. And these fuel price is
used by the operator. All the employee has to go through authorization, for with
valid id. Operator has to pump the fuel.

Department of Computer Science and Engineering, SKIT College,

3
Chapter 2
Software Requirement Specification
2.1 Overall Description

Client on Internet Web Browser, Operating System (any) Client on Intranet Web
Browser, Operating System (any) Web Server WASCE, Operating System (any)
Data Base Server SQLite3, Operating System (any) Development End HTML, CSS,
OS (Windows), SQL, JavaScript, PHP

2.1.1 Product Perspective

2.1.1.1 System Interfaces

The application has been development which will show fuel avail-
ability status in fuel station vehicle has been improved with hardware
which will show exact fuel present in fuel tank and up to where the
vehicle will travel in the amount of fuel present in fuel tank. Low
fuel indication: The programming done in embedded C for interfacing
the load cell with the controller it will detect the fuel count of petrol
available in the fuel tank of two wheeler vehicle. If the fuel count is
sufficient or above average then flow will go on in continuous way but
if fuel count is detected low then it will get activated. .

2.1.1.2 User Interfaces

This is the most challenging phase of the System Development Life

Cycle. In this phase we decided how our project design will look

Department of Computer Science and Engineering, SKIT, 4

Like.
We designed several forms in VBwhich were to be include in our po-
ject. There were around 29forms which were designed byus in which
all the concepts was included. This designing of forms was helped by
our project guide..

2.1.1.3 Hardware Interfaces

Processor : Pentium ——— 2.0GHz

RAM : 1 GB
Hard Disk : 20 GB
Monitor : 15“ color monitor
Keyboard : 122 Keys .

2.1.1.4 Software Interfaces

Operating system: Windows 10/Ubuntu

Browser: Google Chrome / Mozilla Firefox
Language: HTML
PHP
CSS
Database: SQLite

2.1.1.5 Communications Interfaces

Client (customer) on Internet will be using HTTP/HTTPS protocol.

Client (system user) on Internet will be using HTTP/HTTPS protocol.

Department of Computer Science and Engineering, SKIT College, 5

2.1.1.6 Memory Constraints

GUI is only in English. Login and password is used for the identifi-
cation of users. Only registered patients and doctors will be authorized
to use the services. Limited to HTTP/HTTPS. This system is working
for single server.

2.1.1.7 Operations
 Add customer.
 Add users.
 Generate bill.

2.1.1.8 Project Functions

 Add customer.
 Add users.
 Generate bill.
 Add fuel
 Show Transactions.

2.1.1.9 User Characteristics

 Admin can delete customers.

 Admin can add users.

 Cashier can generate bill

2.1.1.10 Constraints

 GUI is only in English.

 Login and password is used for the identification of users.
  Only registered patients and doctors will be authorized to use
the services.
 Limited to HTTP/HTTPS.

2.1.1.11 Assumption and Dependencies

 User has internet connection
 User has browser

Department of Computer Science and Engineering, SKIT College, 6

Chapter 3
System Design Specification
3.1 System Architecture

Client on Internet Web Browser, Operating System (any) Client on

Intranet Web Browser, Operating System (any) Web Server WASCE,
Operating System (any) Data Base Server SQLite3, Operating System
(any) Development End HTML, CSS, OS (Windows), SQL,
JavaScript, PHP

3.2 Module Decomposition Description

POS : In this module a bill is generated according to selected fuel. And

the current price of the fuel.

Customer : Admin can manage customers and see their data.

Fuel : Here all details about fuel is stores which can be updated by the
admin.

Login : Login crenditional is checked for users.

Department of Computer Science and Engineering, SKIT, 7

3.3 High Level Design Diagrams

3.3.1 Use Case Diagram

Figure 3.1: Use Case diagram

Figure 3.2: Use Case

Department of Computer Science and Engineering, SKIT College, 8

Department of Computer Science and Engineering, SKIT College, 9
3.3.2 Activity Diagram

Figure 3.3: Activity Diagram

Department of Computer Science and Engineering, SKIT College, 1

Department of Computer Science and Engineering, SKIT College, 1
Department of Computer Science and Engineering, SKIT College, 1
Department of Computer Science and Engineering, SKIT College, 1
Chapter 4
Methodology and
Team

4.1 Introduction to Waterfall Framework

The Waterfall Model was first Process Model to be introduced. It is

also referred to as a linear-sequential life cycle model. It is very sim-
ple to understand and use. In a waterfall model, each phase must be
completed before the next phase can begin and there is no overlapping
in the phases. The waterfall Model illustrates the software develop-
ment process in a linear sequential flow; hence it is also referred to as
a linear-sequential life cycle model. This means that any phase in the
development process begins only if the previous phase is complete. In
waterfall model phases do not overlap. In ”The Waterfall” approach,
the whole process of software development is divided into separate
phases. In Waterfall model, typically, the outcome of one phase acts
as an input for the next phase sequentially. Following is a diagram-
matic representation of different phases of waterfall model.

Department of Computer Science and Engineering, SKIT, 1

Department of Computer Science and Engineering, SKIT, 1
 Figure 4.1: WaterFall model

The sequential phases in Waterfall model are-

1. Requirement Gathering and analysis: All possible requirements

of the system to be developed are captured in this phase and doc-
umented in a requirement specification doc.

2. System Design: The requirement specifications from first phase

are studied in this phase and system design is prepared. System
Design helps in specifying hardware and system requirements and
also helps in defining overall system architecture.

3. Implementation: With inputs from system design, the system

is first developed in small programs called units, which are inte-
grated in the next phase. Each unit is developed and tested for its
functionality which is referred to as Unit Testing.

4. Integration and Testing: All the units developed in the imple-

Department of Computer Science and Engineering, SKIT College, 1

 mentation phase are integrated into a system after testing of each
unit. Post integration the entire system is tested for any faults and
failures.

5. Deployment of system: All the units developed in the imple-

mentation phase are integrated into a system after testing of each
unit. Post integration the entire system is tested for any faults and
failures.

6. Maintenance: All the units developed in the implementation phase

are integrated into a system after testing of each unit. Post inte-
gration the entire system is tested for any faults and failures.

All these phases are cascaded to each other in which progress is seen
as flowing steadily downwards (like a waterfall) through the phases.
The next phase is started only after the defined set of goals are
achieved for previous phase and it is signed off, so the name ”Waterfall
Model”. In this model phases do not overlap.

Waterfall Model Pros & Cons

Advantage The advantage of waterfall development is that it allows
for departmentalization and control. A schedule can be set with dead-
lines for each stage of development and a product can proceed through
the development process model phases one by one. Development
moves from concept, through design, implementation, testing, instal-
lation, troubleshooting, and ends up at operation and maintenance.
Each phase of development proceeds in strict order.

Department of Computer Science and Engineering, SKIT College, 1

Disadvantage The disadvantage of waterfall development is that it
does not allow for much reflection or revision. Once an application is
in the testing stage, it is very difficult to go back and change something
that was not well-documented or thought upon in the concept stage.

4.2 Team Members, Roles & Responsibilities

Abhishek Rajora - PHP

Aditya Nehra - sql
Ajay Prajapat - HTML
Akash Gupta - CSS

Department of Computer Science and Engineering, SKIT College, 1

Chapter 5
Centering System Testing
The designed system has been testing through following test param-
eters.

5.1 Functionality Testing

In testing the functionality of the web sites the following features

were tested:

1. Links

(a) Internal Links: All internal links of the website were checked
by clicking each link individually and providing the appropri-
ate input to reach the other links within.

(b) External Links: Till now no external links are provided on our
website but for future enhancement we will provide the links
to the candidate’s actual profile available online and link up
with the elections updates online etc.
(c) Broken Links : Broken links are those links which so not di-
vert the page to specific page or any page at all. By testing
the links on our website, there was no link found on clicking
which we did not find any page.

2. Forms

Department of Computer Science and Engineering, SKIT, 1

 (a) Error message for wrong input : Error messages have been
displayed as and when we enter the wrong details (eg. Dates),
and when we do not enter any details in the mandatory fields.
For example: when we enter wrong password we get error
message for acknowledging us that we have entered it wrong
and when we do not enter the username and/or password we
get the messages displaying the respective errors.
(b) Optional and Mandatory fields : All the mandatory fields have
been marked with a red asterisk (*) and apart from that there is
a display of error messages when we do not enter the manda-
tory fields. For example: As the first name is a compulsory
field in all our forms so when we do not enter that in our form
and submit the form we get an error message asking for us to
enter details in that particular field.

3. Database Testing is done on the database connectivity.

5.2 Performance Testing

All the functions working properly. It generated bill according to

selected fuel and given discounts.

5.3 Usability Testing

Admin and fuel worker can use this system.All the functions of both
users working properly.

Department of Computer Science and Engineering, SKIT College, 2

Chapter 6
Test Execution Summary
Execution Test Summary Report is an overall view of Testing Pro-
cess from start to end. Test Plan comes at the starting of project while
Test Summary Report comes at the end of the testing process. This
report is given to the client for his understanding purpose. The Test
Summary Report contents are :
1. Test Case ID generated
2. Total number of resources consumed
3. Passed Test Cases
4. Failed Test Cases
5. Status of Test Cases

Test No. of
Test Case Test Case
S.No Case Resources
Description Status
Id Consumed
Adding
1 6 200
Customer
Adding
2 7 200
Customer
3 545 Add Fuel 200
4 545 Add Fuel 200
5 88 Delete Fuel 200

Table 6.1: Table to test captions and labels

Department of Computer Science and Engineering, SKIT, 2

Chapter 7
Project Screen Shots

Department of Computer Science and Engineering, SKIT, 2

Department of Computer Science and Engineering, SKIT, 2
Department of Computer Science and Engineering, SKIT College, 2
Department of Computer Science and Engineering, SKIT College, 2
Department of Computer Science and Engineering, SKIT College, 2
Department of Computer Science and Engineering, SKIT College, 2
Chapter 8
Project Summary and Conclusions
8.1 Conclusion

This is a Simple PHP Project entitled Gas/Petrol Station Manage-

ment System. This is a web-based application that provides the Gas or
Petrol Station with an automated platform to manage their sales, cus-
tomer credits, and customer payments. The application was developed
using PHP and SQLite3 Database. This can help the management to
store their records and easily retrieve the data. This has a simple user
interface and user-friendly functionalities.
This Gas/Petrol Station Management System has 2 types of sys-
tem users which are the Admin and the Cashier. The Admin User is in
charge of managing the important list in the system such as the petrol
type and customer list. They are only the ones who can view, edit,
or manage the customer credit, and payment details. The cashier user
can only access the point of sale feature and can generate sales re-
ports that he/she processed on the system. The POS feature has some
functionalities that can help the management to calculate the customer
transaction. This project generates a printable date-wise sales report
and receipt
We have left the options open so that if there is any other future
requirement in the system by the user for the enhancement of the sys-

Department of Computer Science and Engineering, SKIT, 2

tem then it is possible to implement them in the last we would like
to thanks all the persons involved in the system directly or indirectly.
We hope that the project will serve its purpose for when it is develop
thereby underlining success of process. .

Department of Computer Science and Engineering, SKIT College, 2

Chapter 9
Future Scope
• We can Add multiple customers in one Project

• We can give more advance software for Petrol Pump Management

System including more facilities

• Implement the backup mechanism for taking backup of codebase

and database on regular basis on different servers

• Create the master and slave database structure to reduce the over-
load of the database queries

Department of Computer Science and Engineering, SKIT, 3

References
[1] Object Oriented Modeling and Design with UML-Michael
Blaha, James Rambaugh.

[2] Learning PHP Book by Robin Nixon

[3] JavaScript: The Good Parts Book by Douglas Crockford

[4] Wikipedia - www.wikipedia.com

[5] HTML CSS: Design and Build Web Sites Book by Jon Duckett

Department of Computer Science and Engineering, SKIT, 3