1

E-GAS SEWA
Software Requirement Specification

RAJIV GANDHI COLLEGE OF ENGG. AND RESEARCH

(FORMERLY : NYSSCER)

TEAM MEMBERS
Rahul Parihar
Tejal Mathurkar

TEAM GUIDE
Prashant Dahiwale
Lecturer,Department of computer science and engineering
2

Contents
1.0 Introduction ………………………………………………………..3

1.1 Purpose ………………………………………………………………3

1.2 Scope …………………………………………………………………3

1.3 Definition, Acronyms, and Abbreviations ………………..4

1.4 References ………………………………………………………….4

1.5 Technologies to be used ………………………………………4

1.6 Overview …………………………………………………………….5

1.7 Product Perspective …………………………………………….6

1.8 Software Interface ……………………………………………….6

1.9 Hardware Interface ………………………………………………7

2.0 Product Function ………………………………………………….8

2.1 User Characteristics …………………………………………….8

2.2 Constraints ………………………………………………………….8

2.3 Architecture Design ……………………………………………..9

2.4 Use Case Model Description ………………………………..10

2.5 Class Diagram …………………………………………………….11

2.6 Sequence Diagram ……………………………………………..12

2.7 Database Design ………………………………………………..15

2.7.1 ER Diagram ………………………………………………………17

3

2.7.2 Schema …………………………………………………………….18

2.8 Assumptions and Dependencies ………………………………18

2.9 Specific Requirements…………………………………………….18

2.9.1 Use Case Reports ………………………………………………..19

3.0 Activity Diagram………………………………………………………23

Introduction:
 E-Gas Sewa is always committed to provide high quality supply of LPG gas and
continuously develop its facilities .
 This helps to achieve the excellence in securing reliable services that would meet the
growing demand and exceed the future needs and expectations of our customers.
 Several e-facilities such as the on-line bill payments and payments through the banks
were introduced to provide more convenient services for the customers.

1.1 Purpose:
E-gas sewa is a web service which provides online gas booking services to everyone in
easy manageable way.
The users living in metro can connect through internet to get these services. This web service is
more effective, quick in providing help. This helps to maintain a neat record and leads to a well
managed LPG supply.
The purpose of E-Gas service is to provides an in-depth services for gas agency of Indian
company highly benefiting their customers in vast area of company’s services providing to them.

1.2 Scope:
This online E-gas service makes the path for LPG Gas Connection smooth one. .

 There are three basic users. Admin, Customer, Dealers and Franchise Owner.
 All users have their own profile on E-gas sewa
 A Guest user can see the procedures to be followed for getting a new LPG Gas
Connection.
 Customer can do online Booking and cancelation of LPG gas.
 Customer can search online and request of Accessories
 Customer can see the recent Rate of LPG Gas cylinder as declared by Indian Regime.
 Customer can see the Security aspects about Usability of LPG Gas.
 Dealers and franchise owner can request for accessories by logging on to EGS.
4

1.3 Definition, Acronyms, and

Abbreviations:

 EGS: E-gas sewa : It is a application that provides online LPG gas booking services for
people.
 Admin: Administrator. He has the authority to add/delete users.
 J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to the Java
platform, which is used for developing and running distributed java applications.
 WASCE (WebSphere Application Server Community Edition): It is an application
server that runs and supports the J2EE and the web service applications.
 DB2 (IBM Database 2): It is a database management system that provides a flexible
and efficient database platform to raise a strong "on demand“ business applications.
 HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server
protocol between a web browser and a web server.
 XML (Extensible Markup Language): It is a markup language that was designed to
transport and store data.
 RAD: Rational application developer is a development tool that helps to design web
pages and also helps to design the diagrams like ER, Database schema diagrams and to
generate DDL.

1.4 References:
 Object Oriented Modeling and Design with UML-Michael Blaha, James Rambaugh.
 Software Engineering, Seventh Edition, Ian Sommerville.
 IBM Red Books.
 IBM TGMC Sample Synopsis.
 IBM – www.ibm.in/developerworks
 Java - http://www.sun.com/
 Wikipedia - http://www.wikipedia.com/
 Database Management Systems - Navathe.
 Complete Reference - J2EE - Keogh.

1.5 Technologies to be used:

 Application architecture- J2EE Java Platform, Enterprise Edition or Java EE is a
widely used platform for server programming in the Java programming language. The
Java platform (Enterprise Edition) differs from the Java Standard Edition Platform (Java
SE) in that it adds libraries which provide functionality to deploy fault-tolerant, distributed,
5

multi-tier Java software, based largely on modular components running on an application

server.
 Web server – WASCE:- WebSphere Application Server Community Edition (from
now on WASCE) is a free, certified Java EE 5 server for building and managing Java
applications. It is IBM's supported distribution of Apache Geronimo that uses Tomcat for
servlet container and Axis 2 for web services. Over 15 WASCE developers are
committers in the Apache Geronimo project.
 Development tool –RAD :- IBM Rational Application Developer for WebSphere Software
(RAD) is an integrated development environment (IDE), made by IBM's Rational Software
division, for visually designing, constructing, testing, and deploying Web services, portals,
and Java (J2EE) applications.
 Database platform – DB2 DB2 Database is the database management system that
delivers a flexible and cost effective database platform to build robust on demand
business applications and supports the J2EE and web services standards.
 Design tool – Rational Software Modeler :- IBM Rational Software Modeler, (RSM)
made by IBM's Rational Software division, is a Unified Modeling Language UML 2.0-
based visual modeling and design tool. Rational Software Modeler is built on the Eclipse
open-source software framework and includes capabilities focused on visual modeling
and model-driven development (MDD) with the UML for creating resilient, thought-out
 Applications and web services.

1.6 Overview:

a) Overall Description:
Existing System:
 Registration for users
 Helpdesk support

Proposed System:
 Registration for users, Franchise owners
 Online search and request of Accessories
 Recent LPG cylinder rates

Our Plan:
 . Individual Account Creation Facility
 Account Updation Facility
 Online Booking Facility for LPG Gas
 View Delivery Status for Booked LPG Gas.
 Cancellation of Online Booked LPG Gas.
 Online application for New LPG Gas Connection.
 Online technical Support Query Form
 Online Application form for Dealership

b) Specific requirements
Actors included in the system are , the customer, the agency, and the administration.
6

 The customer has an account on the site and can carry out booking of LPG gas and
various aspects related to that facility
 Administration looks after the proper evaluation of requirements and proceeds for serving
them.
 Agency is responsible for delivery the products (including LPG gas cylinder + accessories
if required). Agency is basically engaged in deployment and feedback.

1.7 Product Perspective:

Web Java Beans

Browser Container
EJBs

HTTP Server
DB2

Web Messaging
Web Server Services Engine
Engine

1.8 Software Interface:

Front end client:
Web Browser, Operating System (Windows)
Web Server:
WASCE, Operating System (windows)
Data Base Server:
DB2, Operating System (windows)
Back end:
RAD (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), DB2, OS (Windows),
WebSphere(Web Server)
7

1.9HardwareInterface:
8

2.0 Product function:

Basic Function include:-

1. Online registry for getting the connection of LPG gas is possible with individual account
creation facility. Facility is also provided for updating the user account.
2. Online Booking Facility for LPG Gas is possible by using this E-gas sewa service.
Similarly, the delivery status for booked LPG gas can also be known to the user. This will
help the user to keep the record of their LPG usage
3. Cancellation of Online Booked LPG Gas is possible under applicable conditions.
4. Online application for New LPG Gas Connection is also made possible by this sewa to
some limited extent specified further.
5. Another feature enhancing the E-gas sewa service is that, Online search and request of
requisite Accessories along with LPG cylinder.
6. Online technical Support Query Form is also provided to the customer to ease the
interaction. This helps in knowing the customer requirements and queries and deals with
them in a better way.
7. 24 X 7 availability of doorstep help services.(online and offline help)

2.1 User Characteristics

 User should understand basic interface language, which can be either English/hindi.
 User must be capable enough to use basic browser such as internet explorer 6.
 User must have 24x7 internet connection.

2.2 Constraints:
 Login and password is required to use the facility of booking the gas, and other
activities related to it.
 Limited to HTTP/HTTPS.
 This system is working for single server.
 9

2.3 Architecture Design

Application layer Business layer Database Layer

Search UI Search UI

Register UI Register UI Customer

/Agencie
s
Login UI Login UI

Complaint Complaint
UI UI

Customer
Booking Booking

Cancelation Cancelation

Delivery status
Delivery status Delivery
status

Accessories Accessories
Accessories

Queries Queries Queries

10

2.4 Use Case Model Description

complaint maintain database

request accessories
customer
admin

gas booking

delete user

cancellation

create user authenticate user

register login view profile logout query/help desk search accessories

search

extend

update record

dealer/franchise

transport cylinder
delivery status

offline technical support

passbook update

Fig 2.4 Global view of use case model.

Customer:

Customer can register for individual account, can do online booking of gas. They can view their
records, delivery status, waiting number. They can book accessories. They can lodge query or
complaint.

Admin:
Admin has the authority to add/delete user, and can approve the request of franchise owner and
dealer to view and update records. He also can view customer complaints and queries and take
necessary action.
11

Franchise/dealer:
Possesses the responsibility to transport the LPG cylinder, do passbook update, forward the
information to admin. They also provide offline technical support and security to users.

2.5 Class Diagram:

admin

add customer()
remove customer()

has has/authenticate

Customer *
Login and logout Customer id * franchise/dealer
Is also an operation password employees
of class customer
delivery status
registrer()
search()
technical support()
door to door LPG service()

booking passbook update

booking id complaint customer id
date and time complaint id customer name
topic delivery detail transportation
book() vehicle
register complaint() update entries()
address of delivery

file query
cancellation
query topic
booking id date and time
date and time accessories
file query() stock
cancel()

records
customer name
customer id
delivery status

update()
recieve payment()

Fig 2.5 Class Diagram

12

2.6 Sequence Diagrams:

1. Sequence diagram for user login:

customer interface EGS admin

prompt user

enter username

enter password

verify password

result of verification

success
display results

failure
request rejected

2. Sequence diagram for booking gas:

13

customer interface
Admin
enquire for availability
check for avilability
show results
display reults

success
request for booking
book LPG

waiting number displayed waiting unumber granted

request rejected
failure
display results

3.Sequence diagram for cancellation:

customer interface admin

request for cancellation

cancel booking
display results

4.Sequence diagram for booking accessories

14

customer franchise admin

search accessories
check for availability
display availability

request accessories

deliver accessory

5.Sequence diagram for delivery of LPG:

customer franchise admin

search waiting number

customer details
gas delivery
pay money

forward updates
update passbook
15

6. Sequence Diagram for lodging complaint

customer interface admin

Enter complaint
Forward complaint

Generate complaint ID
Respond complaint

2.7 Database Design

16

CUSTOMER
CONTACTS DELIVERY STATUS
customer id COMPLAINT
contact id waiting number
phone number complaint id
name() issue date
email id subject
email() tentative delivery date
complaint
contact() date and time
address() recipient()
city() passbook update()
complaint number()
district()
occupation()
REGISTRATION
registration id
FRANCHISE OWNER
email() LISTS owner id
LOGIN
contact() list id owner name
username address() address
usertype city() phone number
customer id()
login status district() email id
franchise owner id()
password password() city
technical support

transport details()
providing security()
BOOKING CANCELLATION 24x7 service()
QUERY customer id customer id
booking date booking date
query number
booking time cancellation date
customer id
date of delivery cancellation time
date
last date of issue ACCESSORIES
time
last date of delivery
stock
response time() name
waiting number()
response date() accessories in demand
details of acc. manufacturers
allotment details
NEWS
description
date
subject
current LPG rate
 17

2.7.1 E R Diagram:-
Waiting no.

Record-ID
Booking date

Record
Date
of
delive
ry
Name Name
Password Admin_ID
Address Customer-ID
has Updates D Name

Customer Admin
Passbook
Interacts
Address
Passwor
d Contact
Content

lodges Complaint Views

Complaint ID

Approves
Possesses a

Recipient Employee
Nmae

Franchise
Report Generates
Passbook
update
Accessories
Transport

Passbook Entry
18

2.7.2 Schema:
Customer(name,address,occupation,passbook,password,contact,cust ID,waiting number,booking
date,complaint number,record ID);

Login(username,usertype,login status,password);

Query(query number,customer ID,date,time,response time,response date);

Booking(customer ID,booking date,booking time,date of delivery,last date of issue, last date of

delivery,waiting number);

Complaint( complaint ID,subject,complaint,date,time,complaint number):

Delivery status(waiting number,issue date,tentative delivery date,recipient,passbook update);

Cancellation(customer ID,booking date,cancellation, time);

Lists(list ID,customer ID,franchise owner ID);

Registration(employee, registration ID, email,contact,address,city,district,password);

Franchise owner(owner ID,owner name,address,phone number,email ID,technical

support,transport details,providing security,24x7 service,accessories);

Accessories(stock,name,accessories in demand,details of acc.manufactures,allotment details);

News(description ,date,subject,current LPG rate);

Contacts(contact ID,email, phone number);

Admin(name , password ,admin ID);

2.8 Assumptions and

Dependencies
1. For DB2:

Software considerations
DB2 .NET client applications and CLR server-side procedures require .NET 1.1 Service Pack 1
or .NET 2.0 framework runtime. In an x86-64 environment, 32-bit DB2 .NET applications will run
in the WOW64 emulation mode. 64-bit DB2 .NET applications are not supported.

One of the following browsers is required to view online help, run the DB2 install launchpad
(setup.exe), and to run First Steps (db2fs):
19

 Internet Explorer 5.5 and up

 Mozilla 1.4 and up
 Firefox 1.0 and up
 Netscape 7.0 and up

2.For RAD:
Software considerations:

 Windows Server 2003 Standard / Enterprise Edition (x86-32 and x86-64)

 Windows XP Professional (x86-32 and x86-64)
 Windows 7 Professional / Enterprise / Ultimate (x86-32 and x86-64

Hardware considerations:

 Display: 1024 x 768 minimum; 1280 X 1024 recommended

 Memory: 1GB RAM minimum; 2GB RAM or more recommended
 Processor: Intel® Pentium® III 800 MHz or higher recommended

2.9 Specific requirements:

2.9.1 Use Case Reports

1.Use case report of customer

20

register
cancel booking query
offline help
book gas

delivery status

customer security
login

complaint

update record

search

request accessories admin

create give feedback

search accessories

USE CASE DESCRIPTION

Register Customer can register for new LPG connection.
Search Customer can search the information about the E-
gas sewa.
Login Customer has to login in order to.
Book gas Customer can book the LPG cylinder.
Cancel booking Once booked, he can cancel the booking.
Update record Customer can update his/her passbook/record.
Delivery status Customer can check the LPG delivery status.
Search accessories Customer can search required accessories.
Request accessories Customer can request required accessories.
Complaint Customer can file complaint on franchise to admin.
Give feedback Customer can give feedback about the service to the
admin.
Security Customer can check details of his security service.
Offline help Customer can request for 24x7 home help service.
Query Customer

2.Use case report of Admin

21

view individual record

generate records includes

recieve query
update record
login response to query
admin

delivery status

authenticate franchise owners

delete users
view complaints

extend
include

response to complaints

take action

USE CASE DESCRIPTION

Login Admin has to login in order to begin his
work.
Generate record Admin can generate individual customer
record.
View individual record Admin can view record of each individual
customer.
Update record On delivery, booking, or cancellation,
admin can update each customer record.
Receive query Admin can receive the queries lodged by
customer.
Respond to query Admin responds to the query.
22

View complaint Admin can view the complaint filed by

customer.
Respond to complaint Admin responds to the complaint of
customer.
Take action Admin can take necessary action
Authenticate franchise owner Admin will authenticate franchise
users(dealers).
Delivery status Admin keep the record of delivery status of
each LPG.
Delete user Admin is given the option to delete the
user.
Get passbook update. Admin gets passbook update from franchise
owner/dealer.

3.Use case report of Franchise/ Dealer

transport cylinders

recieve payment

franchise/dealer
Login

update passbook

delivery details-admin

search

view logs offline technical support

DESCRIPTION
USE CASE
23

Register Franchise owner/dealer has to register

himself to admin.
Approval from admin Admin approves the registry.
Login Franchise owner/dealer has to login in order
to.
View logs Franchise owner/dealer can view all records
of all customers.
Search Franchise owner/dealer can search
throughout the website.
Transport cylinder Franchise owner/dealer has to transport
cylinder to customer.
Receive payment Franchise owner/dealer charges and collects
fees.
Update passbook Franchise owner/dealer updates passbook.
Offline technical support Franchise owner/dealer provides home
service to customers.
Delivery details Franchise owner/dealer keep record of
delivery details.

2.9.2 Activity Diagrams

Registry:
24

Registration activity dig:

25

Initially user is made to fill all mandatory fields filled in registration form. Once the user clicks
submit,
the username is verified. If the username is already present, then the user is again taken back,
so that he can change the username. If the username is not present then it checks for password
and
remaining mandatory fields. If any of the mandatory field is left empty or filled incorrect, then the
user is informed to enter the correct values. Once all these verifications are succeeded, then the
registration is done.
For franchise dealer, once the verification of mandatory details, they receive approval from admin
and then they are provided privileges

LOGIN:
26

Login account:

User has to enter the username and password. Verification takes place by admin accounts(record
of each individual user present). If that is invalid, user is again requested to enter username and
password. If username and password is authenticated, then login is successful and home page is
displayed

Booking:

Booking account:

For booking LPG, customer has to login through his account. Each customer is provided with
customer ID. Customer has to enter that customer ID , book LPG. Interface displays the
availability of LPG through contacting database. If the request is rejected, the message is
displayed on screen. If the booking is successful, then customer is provided with waiting number.
27

Complaint :

Complaint:

Customer enters the complaint or the query text and submits it to admin. Admin generates the
complaint or the query ID. Admin eventually responds to
the complaint or the query.
28

Thank you