BOOK LPG FROM ANYWHERE (Mini Project 2016) During today’s busy life, no one is ready to waste the time by doing the time consuming and hassle refill booking like IVR Booking System. We are proposing a simple, interactive, hassle free, less time consuming and efficient LPG Booking System. This is beneficial for the Gas Agencies also, they get the refill booking requests and consumer details instantly. Our system is futuristic and can be updated according to the future needs easily. Features:- To book an LPG cylinder, you should be a authorised customer. An authorised customer can register to the website and get user id and password. After you have registered, you can log on to the LPG portal using the password and user id provided to you. Pros:- Consumers can book the refill by just one click, they can post queries or complaints. Needs only username and password. If they don’t have one, the valid consumers can get the username and passwords with simple registration process. The Admin can only access the database, only he can add the consumers and staff. So the system is secured. The authorized staff can see the bookings and the consumer details without any hassle. He can mark the status whether the refill delivered or not. If delivered then refill request will be automatically cleared.

1. A
Mini Project Report
on
LPG BOOKING SYSTEM
Submitted in partial fulfilment of the award of the degree
of
Bachelor of Technology
in
Computer Science and Engineering
of
Cochin University of Science and Technology
by
Aravind M(12151201)
Nandu B Rajan(12151210)
S Lekshmi Priya(12151215)
Arunima Ramakrishnan(14151203)
Department of Computer Science And Engineering
College of Engineering, Karunagappally- 690523
April 2017

2. COLLEGE OF ENGINEERING
KARUNAGAPPALLY
KOLLAM-690523, KERALA
BONAFIDE CERTIFICATE
Certified that this project report “ LPG BOOKING SYSTEM ” is a bonafide
work of the mini project carried out at our department by “ARAVIND M (12151201)
, ARUNIMA RAMAKRISHNAN (14151203) , NANDU B RAJAN (12151210) , S
LEKSHMI PRIYA (12151215)” 6th Semester in partial fulfilment of the require-
ments for award of Degree in Computer Science and Engineering by Bachelor of
Technology of Cochin University of Science and Technology.
PROJECT CO-ORDINATOR PROJECT GUIDE
Ms. REMYA R S Ms. SHEENA S NOWSHAD
Assistant Professor Assistant Professor
Dept.Of Computer Dept.Of Computer
Science and Engineering Science and Engineering
HEAD OF THE DEPARTMENT
Mr. BINU V.P
Associate Professor
Dept. of Computer science and Engineering
College of Engineering Karunagappally

3. ACKNOWLEDGEMENT
Success and happiness are directly related to the achievements of the predeter-
mined goals. The success of this project work is due to the varied contribution of
several distinguished personalities. We take this wonderful opportunity to thank
each and every one of them. It is our privilege to extend our sincere gratitude
to all those who helped our team in the fruition of the project entitled “LPG
BOOKING SYSTEM”.
First of all we thank God Almighty for being the guide light throughout the
project and helped us to complete it within stipulated time.
We remember with grateful thanks, the encouragement and support rendered
by our principal Ms. Jaya V.L. We express our deepest sense of gratitude to the
head of the department, Mr. Binu V.P. for his valuable guidance.
We also express our heartfelt gratitude to our internal guides, Ms. Remya R.S.
and Ms. Sheena.S.Nowshad (Assistant Professors of Department Of Computer
Science, College Of Engineering, Karunagappally) for timely suggestions and en-
couragement given for the successful completion of the project.We would always
oblige for the helping hands of all other staff members of the department who
directly or indirectly contributed in this venture.
Our overrunning debt also lays with family members, friends and well-wishers
who helped in bringing out this project successfully.

4. ABSTRACT
During today’s busy life, no one is ready to waste the time by doing the time
consuming and hassle refill cylinder booking like IVR Booking System. The ex-
isting sites are generalized where the consumers need to provide a huge round of
details. We are proposing a simple, interactive, hassle free, less time consuming
and efficient LPG Booking System for an individual agency. This is beneficial for
the Gas Agencies also, they get the refill booking requests and consumer details
instantly. Our system was futuristic and can be updated according to the future
needs easily.

5. Contents
1 INTRODUCTION 1
1.1 BACKGROUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 APPLICABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.6 ACHIEVEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 SURVEY OF TECHNOLOGIES 4
2.1 PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 JAVA SCRIPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 SUBLIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 REQUIREMENTS AND ANALYSIS 9
3.1 SYSTEM ANALYSIS . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.1 EXISTING SYSTEM . . . . . . . . . . . . . . . . . . . . . . 10
3.1.2 PROPOSED SYSTEM . . . . . . . . . . . . . . . . . . . . . 10
3.2 FEASIBILITY STUDY . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.1 TECHNICAL FEASIBILITY . . . . . . . . . . . . . . . . . 11
3.2.2 ECONOMIC FEASIBILITY . . . . . . . . . . . . . . . . . . 12
3.2.3 BEHAVIOURAL FEASIBILITY . . . . . . . . . . . . . . . 12
3.3 REQUIREMENTS SPECIFICATION . . . . . . . . . . . . . . . . . 13
3.3.1 FUNCTIONAL REQUIREMENTS . . . . . . . . . . . . . . 13
3.3.2 NON-FUNCTIONAL REQUIREMENTS . . . . . . . . . . . 14

6. 3.3.3 HARDWARE REQUIREMENTS . . . . . . . . . . . . . . . 14
3.3.4 SOFTWARE REQUIREMENTS . . . . . . . . . . . . . . . 15
4 PLANNING AND SCHEDULING 16
5 SYSTEM DESCRIPTION AND DESIGN 17
5.1 MODULE DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . 22
5.2 TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3 DATAFLOW DIAGRAMS . . . . . . . . . . . . . . . . . . . . . . . 24
6 SCREEN SHOTS 28
7 CONCLUSIONS AND FUTURE WORK 32
8 REFERENCES 33

7. List of Tables
3.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1 Tbl Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2 Tbl Con . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3 Tbl Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.4 Tbl Reg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.5 Tbl Staff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

8. List of Figures
5.1 Source/Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.2 Dataflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.3 Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.4 Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.5 DFD LEVEL 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.6 DFD LEVEL 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.7 DFD LEVEL 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1 HOME PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2 LOGIN PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.3 ADMIN PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.4 STAFF PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.5 CONSUMER PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.6 CONSUMER DETAILS . . . . . . . . . . . . . . . . . . . . . . . . 31
6.7 BOOKING DETAILS . . . . . . . . . . . . . . . . . . . . . . . . . 31

9. Chapter 1
INTRODUCTION
As a result of the detailed study carried out, various objectives were formulated.
The main objective of the mini project on LPG Booking System is to manage the
details of Consumers, Staffs and Bookings. It enables the consumers to book the
LPG refill very easily just as a click. Admin enters the essential details of consumer
and staff. The admin also provides username and password for staff. Staff handles
the booking details and keep track on complaints/queries. Authorised consumer of
that agency first registers and gets the username and password with which he/she
will be able to book refill and mention complaints/queries if any.
1. There should be an entry screen and report every stage of the application.
2. Facility for maintenance of all tables.
3. Facilities to accept, validate and process data.
4. Facilities to generate all essential reports.
5. The information flow should be developed.
6. The input screen should be provided with provision to select values or data
from a list of values thus minimizing errors.
7. Validation checks must be performed at each and every level.
8. Database should be designed with minimum redundancy.
9. Menu driven screens should be developed.
1

10. 1.1 BACKGROUND
LPG booking system will help the agency to maintain records securely and
accurately. The System is a PHP configuration and MySQL Database. Here
software is implemented with front end HTML, CSS and JAVACSCRIPT. HTML
provides skeleton for the website. CSS is used for providing styling. Javascript
performs validation. The back end uses PHP and MySQL Server. PHP was
selected due to its simplicity, portability and security. PHP is a powerful tool for
making dynamic and interactive web pages.
1.2 OBJECTIVES
The main objective of the mini project on LPG Booking System is to manage
the details of Consumers, Staffs and Bookings. It enables the consumers to book
the LPG refill very easily just as a click. Not only that the consumers can report
their complaints/queries.
1.3 PURPOSE
The purpose of developing lpg booking system is to provide a hassle free refill
booking that will help both the consumer and agency. The agency can record the
details easily and accurately. The system also helps the agency to maintain staff,
consumer and booking details.
1.4 SCOPE
The scope of the project is the system on which the software is installed, i.e.
the project is developed as a desktop application, and it will work for a particular
agency. But later on the project can be modified to operate it online.
2

11. 1.5 APPLICABILITY
The project was developed to manage refil booking system for a particular
agency. Our product is developed in PHP and MySQL Server. More reliable,
faster, maintainable and more user friendly. Admin enters the essential details of
consumer and staff. The admin also provides username and password for staff.
Staff handles the booking details and keep track on complaints/queries. Autho-
rised consumer of that agency first registers and gets the username and password
with which he/she will be able to book refill and mention complaints/queries if
any.
1.6 ACHIEVEMENTS
We could understand well about the language PHP and MySQL. Moreover we
could study more about database management system. We could achieve all goals
of our projects completely.
ADMIN
(a) Admin can add new staff and consumer details.
(b) Admin can update and delete existing details..
(c) Overall control.
STAFF
(a) Handles refill booking details.
(b) Verifies delivery records
(c) Keeps track on complaints and feedback.
CONSUMER
(a) Registered consumer can book refill.
(b) Consumer can login with unique user id and password.
(c) Consumer can provide remarks and feedback.
3

12. Chapter 2
SURVEY OF TECHNOLOGIES
To retain the integrity of data generated in different modules, to ensure smooth
flow of control from one module to other and also to avoid mistakes, which could
be due to irregular entries into different module of the program, Windows 7 Envi-
ronment, MySQL server as back end and PHP as front end. PHP is a widely-used
general-purpose scripting language that is especially suited for Web development
and can be embedded into HTML.
2.1 PHP
PHP is a server-side scripting language designed for Web development but also
used as a general-purpose programming language. PHP is now installed on more
than 20 million Web sites and one million Web servers. Originally created by
Rasmus Lerdorf 1995, the reference implementation of PHP is now produced by
The PHP Group. While PHP originally stood for Personal Home Page, it is now
said to stand for PHP: Hypertext Preprocessor, a recursive acronym.
PHP code is interpreted by a Web server with a PHP processor module which
generates the resulting Web page. PHP commands can be embedded directly into
an HTML source document rather than calling an external file to process data.
It has also evolved to include a command-line interface capability and can be
used in standalone graphical applications. PHP is free software released under the
PHP License, which is incompatible with the GNU General Public License (GPL)
4

13. due to restrictions on the usage of the term PHP. PHP can be deployed on most
Web servers and also as a standalone shell on almost every operating system and
platform, free of charge. PHP interpreters are available on both 32-bit and 64-bit
operating systems, but on Microsoft Windows the only official distribution is a
32-bit implementation, requiring Windows 32-bit compatibility mode while using
Internet Information Services (IIS) on a 64-bit Windows platform.
PHP syntax and semantics:
The following Hello world program is written in PHP code embedded in an
HTML document:
<!DOCTYPE html>
<meta charset=utf−8>
<title>PHP Test< /title>
<?php
echo ’Hello World’;
? >
The PHP interpreter only executes PHP code within its delimiters. Anything
outside its delimiters is not processed by PHP (although non-PHP text is still sub-
ject to control structures described in PHP code). The most common delimiters
are <?php to open and ? > to close PHP sections. <script language=”php”> and
< /script> delimiters are also available, as are the shortened forms <? or <? =
(which is used to echo back a string or variable) and ? > as well as ASP-style
short forms <
The first form of delimiters, <?php and ? >, in XHTML and other XML doc-
uments, creates correctly formed XML ’processing instructions’. This means that
the resulting mixture of PHP code and other markup in the server-side file is itself
well-formed XML. Variables are prefixed with a dollar symbol, and a type does
not need to be specified in advance. Unlike function and class names, variable
names are case sensitive. Both double-quoted (””) and heredoc strings provide
5

14. the ability to interpolate a variable’s value into the string. PHP treats newlines
as whitespace in the manner of a free-form language (except when inside string
quotes), and statements are terminated by a semicolon. PHP has three types of
comment syntax: /* */ marks block and inline comments; // as well as are used
for one-line comments. The echo statement is one of several facilities PHP pro-
vides to output text, e.g., to a Web browser. In terms of keywords and language
syntax, PHP is similar to most high level languages that follow the C style syntax.
if conditions, for and while loops, and function returns are similar in syntax to
languages such as C, C++, C, Java and Perl.
2.2 MySQL
With MySQL on Windows we get:
1. Performance and Scalability
2. Ease of Use and Administration
3. Reliability
4. Broad Platform support
5. Integration into the Windows Environment
MySQL provides a suite of tools for developing and managing MySQL- based
business critical applications on Windows. ”My Sequel” is (as of 2008) the world’s
most used open source relational database management system (RDBMS) that
runs as a server providing multi-user access to a number of databases. The SQL
phrase stands for Structured Query Language.
The MySQL development project has made its source code available under the
terms of the GNU General Public License, as well as under a variety of proprietary
agreements. MySQL was owned and sponsored by a single for-profit firm, the
Swedish company MySQL AB, now owned by Oracle Corporation. MySQL is a
popular choice of database for use in web applications, and is a central component
of the widely used LAMP open source web application software.
6

15. 2.3 JAVA SCRIPT
Javascript is one of the most simple, versatile and effective languages used to
extend functionality in websites. Uses range from on screen visual effects to pro-
cessing and calculating data on web pages with ease as well as extended func-
tionality to websites using third party scripts among several other handy features,
however it also possesses some negative effects that might make you want to think
twice before implementing Javascript on your website.
• Javascript is executed on the client side
This means that the code is executed on the user’s processor instead of the
web server thus saving bandwidth and strain on the web server.
• Javascript is a relatively easy language
The Javascript language is relatively easy to learn and comprises of syntax
that is close to English. It uses the DOM model that provides plenty of
prewritten functionality to the various objects on pages making it a breeze
to develop a script to solve a custom purpose.
• Javascript is relatively fast to the end user
As the code is executed on the user’s computer, results and processing is
completed almost instantly depending on the task (tasks in javascript on
web pages are usually simple so as to prevent being a memory hog) as it
does not need to be processed in the site’s web server and sent back to the
user consuming local as well as server bandwidth.
• Extended functionality to web pages
Third party add-ons like Greasemonkey enable Javascript developers to write
snippets of Javascript which can execute on desired web pages to extend
its functionality. If you use a website and require a certain feature to be
included, you can write it yourself and use an add-on like Greasemonkey to
implement it on the web page.
7

16. 2.4 SUBLIME
Sublime Text is a proprietary cross-platform source code editor with a Python
application programming interface (API). It natively supports many program-
ming languages and markup languages, and its functionality can be extended by
users with plugins, typically community-built and maintained under free-software
licenses.
The following is a list of features of Sublime Text:
1. ”Goto Anything,” quick navigation to files, symbols, or lines
2. ”Command palette” uses adaptive matching for quick keyboard invocation
of arbitrary commands
3. Simultaneous editing: simultaneously make the same interactive changes to
multiple selected areas
4. Python-based plugin API
5. Project-specific preferences
6. Extensive customizability via JSON settings files, including project-specific
and platform-specific settings
Benefit of using Sublime Text is that it looks the same across Linux, Windows,
and Mac OS X. This is because it uses its own custom cross-platform UI frame-
work, which also lends it some unique controls you won’t find in other editors. The
most noticeable one, and the only one you’ll see at first glance, is the minimap - a
miniaturized bird’s eye view of your code, which runs along the right-side gutter
of the editing pane. When working on long files, you can use the minimap as a
visual scrollbar and instantly scrub around the file for points of interest.
8

17. Chapter 3
REQUIREMENTS AND
ANALYSIS
3.1 SYSTEM ANALYSIS
System analysis is a process of gathering and interpreting facts, diagnosing
problems and the information to recommend improvements on the system. It is a
problem solving activity that requires intensive communication between the sys-
tem users and system developers. System analysis or study is an important phase
of any system development process. The system is studied to the minutest detail
and analysed. The system analyst plays the role of the interrogator and dwells
deep into the working of the present system. The system is viewed as a whole
and the input to the system are identified. The outputs from the organizations
are traced to the various processes. System analysis is concerned with becoming
aware of the problem, identifying the relevant and decisional variables, analysing
and synthesizing the various factors and determining an optimal or at least a
satisfactory solution or program of action.
A detailed study of the process must be made by various techniques like inter-
views, questionnaires etc. The data collected by these sources must be scrutinized
to arrive to a conclusion. The conclusion is an understanding of how the system
functions. This system is called the existing system. Now the existing system
is subjected to close study and problem areas are identified. The designer now
9

18. functions as a problem solver and tries to sort out the difficulties that the enter-
prise faces. The solutions are given as proposals. The proposal is then weighed
with the existing system analytically and the best one is selected. The proposal
is presented to the user for an endorsement by the user. The proposal is reviewed
on user request and suitable changes are made. This is loop that ends as soon as
the user is satisfied with proposal. Preliminary study is the process of gathering
and interpreting facts, using the information for further studies on the system.
Preliminary study is problem solving activity that requires intensive communica-
tion between the system users and system developers. It does various feasibility
studies. In these studies a rough figure of the system activities can be obtained,
from which the decision about the strategies to be followed for effective system
study and analysis can be taken.
3.1.1 EXISTING SYSTEM
The existing system mainly uses IVR system or by sending message, both can be
done only through registered mobile number. There will be some inconvenience.
Instead of these with the LPG Booking System consumer can book the refill and
also register complaints or queries from anywhere and through any device, all they
need is a valid username and password.
3.1.2 PROPOSED SYSTEM
Functionalities provided by LPG Booking System Are As Follows:
1. Consumers can book the refill by just one click, they can post queries or
complaints.
2. Needs only username and password. If they don’t have one, the valid con-
sumers can get the username and passwords with simple registration process.
3. The Admin can only access the database, only he can add the consumers
and staff. So the system is secured.
4. The authorized staff can see the bookings and the consumer details without
any hassle. He can mark the status whether the refill delivered or not. If
10

19. delivered then refill request will be automatically cleared.
3.2 FEASIBILITY STUDY
Feasibility study is made to see if the project on completion will serve the
purpose of the organization for the amount of work, effort and the time that
spend on it. Feasibility study lets the developer foresee the future of the project
and the usefulness. A feasibility study of a system proposal is according to its
workability, which is the impact on the organization, ability to meet their user
needs and effective use of resources. Thus when a new application is proposed it
normally goes through a feasibility study before it is approved for development.
The document provide the feasibility of the project that is being designed and
lists various areas that were considered very carefully during the feasibility study
of this project such as Technical, Economic and Operational feasibilities.
3.2.1 TECHNICAL FEASIBILITY
The system must be evaluated from the technical point of view first. The
assessment of this feasibility must be based on an outline design of the system
requirement in the terms of input, output, programs and procedures. Having
identified an outline system, the investigation must go on to suggest the type of
equipment, required method developing the system, of running the system once it
has been designed.
Technical issues raised during the investigation are:
(a) Does the existing technology sufficient for the suggested one?
(b) Can the system expand if developed?
The project should be developed such that the necessary functions and perfor-
mance are achieved within the constraints. The project is developed within latest
technology. Through the technology may become obsolete after some period of
time, due to the fact that never version of same software supports older versions,
11

20. the system may still be used. So there are minimal constraints involved with
this project. The system has been developed using Java the project is technically
feasible for development.
3.2.2 ECONOMIC FEASIBILITY
The developing system must be justified by cost and benefit. Criteria to ensure
that effort is concentrated on project, which will give best, return at the earliest.
One of the factors, which affect the development of a new system, is the cost it
would require.
The following are some of the important financial questions asked during pre-
liminary investigation:
(a) The costs conduct a full system investigation.
(b) The cost of the hardware and software.
(c) The benefits in the form of reduced costs or fewer costly errors
Since the system is developed as part of project work, there is no manual cost
to spend for the proposed system. Also all the resources are already available, it
give an indication of the system is economically possible for development.
3.2.3 BEHAVIOURAL FEASIBILITY
This includes the following questions:
(a) Is there sufficient support for the users?
(b) Will the proposed system cause harm?
The project would be beneficial because it satisfies the objectives when devel-
oped and installed. All behavioural aspects are considered carefully and conclude
that the project is behaviourally feasible.
12

21. 3.3 REQUIREMENTS SPECIFICATION
The system study aims at establishing requirements for the systems to be ac-
quired, developed and installed. It involves studying and analysing the ways of
an organization currently processing the data to produce information analysing
the problem thoroughly forms a vital part of system study. Analysis involves a
detailed study of the current system, leading to specifications of a new system
in system analysts the prevailing situation of a problem is carefully examined by
breaking them into sub problems. Problematic areas are identified and the infor-
mation is collected. Data gathering is essential to any analysis of requirements. It
is necessary that this analysis familiarizes the designer with objectives, activities
and functions of the organization in which the system is to be implemented.
The main points to be discussed in the system analysis are:
1. Specification of what the new system is to accomplish based on the user
requirements.
2. Functional hierarchy showing function to be performed by the new system
and relationship with each other.
3. Function network which was similar to function hierarchy but they highlight
those functions which are common to more than one procedure.
3.3.1 FUNCTIONAL REQUIREMENTS
Functional Requirements are those that refer to the functionality of the system,
i.e., what services it will provide to the user. The user is able to take the back up
at any time he wants or he can schedule the system to take the back up at a time
he wants and be free of it.
A use case in software engineering and system engineering is a description of
a system’s behaviour as it responds to a request that originates from outside of
that system. Use cases describe the interaction between one or more actors and
the system itself, represented as a sequence of simple steps. Actors are something
or someone which exists outside the system (’black box’) under study, and that
13

22. take part in a sequence of activities in a dialogue with the system to achieve some
goal. Actors may be end users, other systems, or hardware devices. Each use case
is a complete series of events, described from the point of view of the actor.
1. User Management: Here various roles and permissions of various users are
specified. Web side manages this.
2. Authentication: Only authenticated users (users registered through the web)
can make use of this application.
3. Search: We can search files for either deletion or uploading
3.3.2 NON-FUNCTIONAL REQUIREMENTS
There are requirements that are not functional in nature. Specifically, these
are the constraints the system must work within. The nonfunctional require-
ments include performance requirements. There are two types of performance
requirements- static and dynamic. Static requirement include a number of ter-
minals supported, number of simultaneous users to be supported, number of file
system has to process and their sizes etc. Dynamic requirements include execution
time behaviour of the system such as throughput, response time, expected time
for completion of operation etc. The nonfunctional requirements include design
constraints, logical database requirements, and standard compliance and so on.
3.3.3 HARDWARE REQUIREMENTS
Table 3.1: Hardware Requirements
Processor Pentium
CPU Speed 1 GHz
Main Memory 512 Mb
Hard Disk 1 GB Free Space
Internet Connection Broad Band
Keyboard 101 Standard Keyboard
Mouse PS/2 Compatible Mouse
Biometric Device LAN supported any device
14

23. 3.3.4 SOFTWARE REQUIREMENTS
Table 3.2: Software Requirements
Operating System Windows XP or new version
Front End Tool HTML,CSS,Javascript
Back End Tool PHP,MySQL Server
Tool Sublime Editor
Database MySQL
15

24. Chapter 4
PLANNING AND
SCHEDULING
This phase mainly deals with how we can plan and organize different stages
for each project. There are different stages for each project. A good software
engineer must go through these phases. Otherwise, chances for failure are very
high and also it is difficult to correct. A good programmer must go through these
following phases such as system study, data collection, design, coding, testing and
implementation.
The developing process of the LPG Booking System will be carried out in this
chapter as well as the system objectives, scope and scheduling
The project aims and objectives that will be achieved after completions of the
system were carried out in this chapter. The succession of this system will also be
evaluated through this sub chapter. The project objectives are:
1. To manage the details of Consumers and Staffs.
2. To maintain booking details and keep track of complaints and remarks.
3. To design a user friendly graphical user interface which suits the users.
4. To complete the system according to project schedule.
5. To produce technical report that documents the phases and tasks in the
project.
16

25. Chapter 5
SYSTEM DESCRIPTION AND
DESIGN
INTRODUCTION
Design is the first step into the development phase for any engineered product or
system. Design is a creative process. A good design is the key to effective system.
The term “design” is defined as “the process of applying various techniques and
principles for the purpose of defining a process or a system in sufficient detail
to permit its physical realization”. It may be defined as a process of applying
various techniques and principles for the purpose of defining a device, a process
or a system in sufficient detail to permit its physical realization. Software design
sits at the technical kernel of the software engineering process and is applied
regardless of the development paradigm that is used. The system design develops
the architectural detail required to build a system or product. As in the case of
any systematic approach, this software too has undergone the best possible design
phase fine tuning all efficiency, performance and accuracy levels. The design phase
is a transition from a user oriented document to a document to the programmers
or database personnel.
System design goes through two phases of development: Logical and Physical
Design.
17

26. INPUT DESIGN
The design of input focuses on controlling the amount of input required, con-
trolling the errors, avoiding delay, avoiding extra steps and keeping the process
simple. The input is designed in such a way so that it provides security and ease
of use with retaining the privacy. Input Design considered the following things:
(a) What data should be given as input?
(b) How the data should be arranged or coded?
(c) The dialog to guide the operating personal in providing input.
(d) Methods for preparing input validations and steps to follow when an
error occur.
OUTPUT DESIGN
A quality output is one, which meets the requirements of the end user and
presents the information clearly. In output design it is determined how the in-
formation is to be displaced for immediate need and also the hard copy output.
It is the most important and direct source information to the user. Efficient and
intelligent output design improves the system’s relationship to help user decision-
making.
Designing computer output should proceed in an organized, well thought out
manner; the right output must be developed while ensuring that each output
element is designed so that people will find the system can use easily and effectively.
When analysis design computer output, they should:
(a) Identify the specific output that is needed to meet the requirements.
(b) Select methods for presenting information.
(c) Create document, report, or other formats that contain information
produced by the system.
18

27. DATABASE DESIGN
A database is an organized mechanism that has the capability of storing infor-
mation through which a user can retrieve stored information in an effective and
efficient manner. The data is the purpose of any database and must be protected.
The database design is a two level process. In the first step, user requirements
are gathered together and a database is designed which will meet these require-
ments as clearly as possible. This step is called Information Level Design and it
is taken independent of any individual DBMS.
In the second step, this Information level design is transferred into a design
for the specific DBMS that will be used to implement the system in question.
This step is called Physical Level Design, concerned with the characteristics of
the specific DBMS that will be used. A database design runs parallel with the
system design. The organization of the data in the database is aimed to achieve
the following two major objectives.
(a) Data Integrity
(b) Data Independence
Normalization is the process of decomposing the attributes in an application,
which results in a set of tables with very simple structure. The purpose of nor-
malization is to make tables as simple as possible. Normalization is carried out in
this system for the following reasons.
(a) To structure the data so that there is no repetition of data, this helps
in saving.
(b) To permit simple retrieval of data in response to query and report
request.
(c) To simplify the maintenance of the data through updates, insertions,
deletions.
(d) To reduce the need to restructure or reorganize data which new appli-
cation requirements arise.
19

28. RELATIONAL DATABASE MANAGEMENT SYSTEM
(RDMS)
A relational model represents the database as a collection of relations. Each
relation resembles a table of values or file of records. In formal relational model
terminology, a row is called a tuple, a column header is called an attribute and the
table is called a relation. A relational database consists of a collection of tables,
each of which is assigned a unique name.A row in a table represents a set of related
values.
RELATIONS,DOMAINS and ATTRIBUTES
A table is a relation. The rows in a table are called tuples. A tuple is an
ordered set of n elements. Columns are referred to as attributes. Relationships
have been set between every table in the database. This ensures both Referential
and Entity Relationship Integrity. A domain D is a set of atomic values. A
common method of specifying a domain is to specify a data type from which the
data values forming the domain are drawn. It is also useful to specify a name for
the domain to help in interpreting its values. Every value in a relation is atomic,
that is not decomposable.
RELATIONSHIPS
Table relationships are established using Key. The two main keys of prime im-
portance are Primary Key Foreign Key. Entity Integrity and Referential Integrity
Relationships can be established with these keys. Entity Integrity enforces that no
Primary Key can have null values. Referential Integrity enforces that no Primary
Key can have null values.
(a) Referential Integrity for each distinct Foreign Key value, there must
exist a matching Primary Key value in the same domain. Other key
are Super Key and Candidate Keys.
(b) Relationships have been set between every table in the database. This
ensures both Referential and Entity Relationship Integrity.
20

29. NORMALIZATION
As the name implies, it denoted putting things in the normal form. The appli-
cation developer via normalization tries to achieve a sensible organization of data
into proper tables and columns and where names can be easily correlated to the
data by the user. Normalization eliminates repeating groups at data and thereby
avoids data redundancy which proves to be a great burden on the computer re-
sources.
These include:
(a) Normalize the data.
(b) Choose proper names for the tables and columns.
(c) Choose the proper name for the data.
First Normal Form
The First Normal Form states that the domain of an attribute must include
only atomic values and that the value of any attribute in a tuple must be a single
value from the domain of that attribute. In other words 1NF disallows “relations
within relations” or “relations attribute values within tuples”. The only attribute
values permitted by 1NF are single atomic or indivisible values.
The first step is to put the data into First Normal Form. This can be donor
by moving data into separate tables where the data is of similar type in each
table. Each table is given a Primary Key or Foreign Key as per requirement of
the project. In this we form new relations for each non atomic attribute or nested
relation. This eliminated repeating groups of data. A relation is said to be in first
normal form if only if it satisfies the constraints that contain the primary key only.
Second Normal Form
According to Second Normal Form, For relations where primary key contains
multiple attributes, no non key attribute should be functionally dependent on a
part of the primary key. In this we decompose and setup a new relation for each
21

30. partial key with its dependent attributes. Make sure to keep a relation with the
original primary key and any attributes that are fully functionally dependent on
it. This step helps in taking out data that is only dependent on apart of the key.
A relation is said to be in second normal form if and only if it satisfies all the first
normal form conditions for the primary key and every non-primary key attributes
of the relation is fully dependent on its primary key alone.
Third Normal Form
According to Third Normal Form, Relation should not have a non-key attribute
functionally determined by another non key attribute or by a set of Non key
attributes. That is, there should be no transitive dependency on the primary key.
In this we decompose and set up relation that includes the non key attributes
that functionally determines other non-key attributes. This step is taken to get
rid of anything that does not depend entirely on the Primary Key. A relation is
said to be in third normal form if only if it is in second normal form and more
over the non key attributes of the relation should not be depend on other non-key
attribute.
5.1 MODULE DESCRIPTION
BASIC MODULES
This software is divided into three modules:
i. Admin Module
ii. Staff Module
iii. Consumer Module
ADMIN MODULE
∗ Admin can add new staff and consumer details.
∗ Admin can update existing details.
∗ Admin can delete existing details.
∗ Overall control.
22

31. STAFF MODULE
∗ Handles refill booking details.
∗ Verifies delivery records
∗ Keeps track on complaints and feedback.
CONSUMER MODULE
∗ Registered consumer can book refill.
∗ Consumer can login with unique user id and password.
∗ Consumer can provide remarks and feedback.
5.2 TABLES
Table 5.1: Tbl Book
cn no varchar(6)
date datetime
comp varchar(800)
Table 5.2: Tbl Con
name varchar(25)
cn no varchar(6)
rc no varchar(10)
ph bigint(10)
Table 5.3: Tbl Login
email varchar(30)
password varchar(20)
role varchar(20)
no varchar(6)
23

32. Table 5.4: Tbl Reg
name varchar(25)
cn no varchar(6)
rc no varchar(10)
address varchar(200)
ph bigint(10)
email varchar(30)
password varchar(20)
Table 5.5: Tbl Staff
name varchar(25)
stf id varchar(6)
email varchar(30)
password varchar(20)
ph bigint(10)
5.3 DATAFLOW DIAGRAMS
Larry Constantine first developed the DFD as a way of expressing system re-
quirements in a graphical form that led to module design. A DFD also known
as “bubble chart” has the purpose of clarifying system requirements and identify
major transformations that will become programs in system design. So it is the
starting point of design phase that functionally decomposes the requirement spec-
ification down to the lowest levels of details. A DFD consists of series of bubbles
joined by lines. The bubbles represent data flow in the system.
A basic DFD consists of four symbols:
1. A square defines source or destination of the system data.
Figure 5.1: Source/Destination
2. An arrow identifies data flow, data in motion. It is a pipeline through which
information flows.
24

33. Figure 5.2: Dataflow
3. A circle or bubble represents a process that transforms incoming data flows
into outgoing data flows.
Figure 5.3: Process
4. An open rectangle is a data store.
Figure 5.4: Data Store
A DFD describes what data flow rather than how they are processed. So it
does not depend on negation. The key question we are trying to answer is: what
major transformation must occur for input to be correctly transformed to output
hardware, software and data structure or file. The creation of the designed system
takes place in the implementation phase. Development phase overview, preparing
of implementation, computer program development phase report and overview. It
also performs activities like writing, testing, debugging and documentation.
25

34. Figure 5.5: DFD LEVEL 0
Figure 5.6: DFD LEVEL 1
26

35. Figure 5.7: DFD LEVEL 2
27

36. Chapter 6
SCREEN SHOTS
Figure 6.1: HOME PAGE
28

37. Figure 6.2: LOGIN PAGE
Figure 6.3: ADMIN PAGE
29

38. Figure 6.4: STAFF PAGE
Figure 6.5: CONSUMER PAGE
30

39. Figure 6.6: CONSUMER DETAILS
Figure 6.7: BOOKING DETAILS
31

40. Chapter 7
CONCLUSIONS AND FUTURE
WORK
This system provides the facility to handle and manage details of consumer, staff
and lpg booking of a gas agency efficiently and securely. The system is simple and
easy to maintain. This can be implemented in any gas agency. The system is
futuristic. The system also handles the complaints and queries of consumers.
In future, the system can be enhanced with billing system and delivery status.
Availability of cylinders and details on subsidy will also be provided through this
system.
32

41. REFERENCES
1. Database System concepts 4th edition by Silberschatz. Korth.Sudarshan.
2. Fundamentals of Database Systems by RamezElmasri, ShamkantB. Navathe
3. Fundamentals of Software Engineering by Rajib Mall
4. www.w3school.com
5. www.codeproject.com
6. www.stackoverflow.com
7. www.codepen.com
8. www.formget.com
9. www.flatvicolorpicker.com
10. www.cssbuttongenerator.com
33