Table of Contents

1. Introduction 1.1 Methodology 1.2 Purpose 1.3 Scope 1.4 Definition, Acronyms, and Abbreviations 1.5 Tools used 1.6 Technologies used 1.7 References 1.8 Overview 3 4 4 5 5 6 6 7

2. Overall Description

2.1 Product Perspective 2.2 Software Interface 2.3 Hardware Interface 2.4 ER diagram 2.5 Constraints 2.6 Architecture Diagram 2.7 Use Case Model Description 2.8 Database Design 2.9 Class Diagram

8 8 9 10 10 11 12 14 15

3. Specific Requirements

3.1 Use-case Reports 3.2 Activity Diagrams 3.3 Sequence Diagrams

16 21 30

4. Supporting Information

4.1 Index 4.2 Special Thanks

36 37

e-Gas Sewa
1.Introduction 1.1 Methodology
Rational Unified Process The Rational Unified Process brings together elements from all of the generic process models, supports iteration and illustrates good practice in specification and design. The Rational Unified Process is normally described from three perspectives: A Dynamic Perspective that shows the phases of the model over time. A Static Perspective that shows the process activities that are enacted. A Practice Perspective that suggests good practices to be used during the process.

Fig.1.1 Phases of Rational Unified Process

The different phases in Rational Unified Process are Inception The goal of the inception phase is to establish a business case for the system. Identifying all external entities that will interact with the system and defining these interactions. This information is used to assess the contribution of system to business.

2|Page

e-Gas Sewa
Elaboration The goals of the elaboration phase are to develop an understanding of the problem domain, establish an architectural framework, develop project plan and identify key project risks.

Construction This phase is concerned with system design, programming and testing. Parts of the system are developed in parallel and integrated during this phase.

Transition This is the final phase of Rational UP and is concerned with moving the system from the development community to the user community and making it work in real environment.

1.2 Purpose
e-Gas is a web application which provides online-Gas booking services to everyone at their door step. The users living in metro or remote village can connect through internet or approach nearby agency to get these services. This web application is more effective, quick in providing connection help. This helps the customer to migrate already established connection to the new location accordingly.

1.3 Scope
Five basic users Customer, Guest User, Admin, Dealer and Kiosk Manager. All users have their own profiles in e-Gas Sewa. GUI is available in local languages i.e., Hindi, Bengali, Telugu, Marathi and Tamil also. Customer can search for agencies and make online connection request. They also can view their connection and delivery expenses. Customer can register complaints about connection to dealer and can also register complaint on any agency to admin. Guest user can see the recent rate of LPG gas cylinder declared by Indian Government, security aspects about usability of LPG gas. Guest user can also see the procedure to be followed for getting a new LPG as connection. Dealers can give connections, accept booking requests and can provide home delivery. Dealers can view complaints of customers and can take actions accordingly. Kiosk Manager views and manages the connections, performs day open and close activities and calculates his commission. He also sends reports to admin. Reports include daily order places report, daily delivered reports, daily cancelled order reports, daily customer reports and monthly dealers and franchise report.

3|Page

e-Gas Sewa
Admin has the authority to add/delete users, grant permission to dealers. He also views the complaints of customers and takes necessary actions.

1.4 Definitions, Acronyms and Abbreviations

HTML: Hyper Text Markup Language. It is used to create static web pages. JSP: Java Server Pages. It is used to create dynamic web content. 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. WSAD: WebSphere Studio Application Developer .It is a designer toolkit which is designed to develop more complex projects by providing a complete dynamic web service. 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. AJAX: Asynchronous Java Script and XML. It is a technique used in java script to create dynamic web pages. Web 2.0: It is commonly associated with web applications which facilitate interactive information sharing, interoperability, user-centered design and collaboration on the World Wide Web.

1.5 Tools Used

Following tools are used in this project JAVA Java is an object-oriented programming language developed by Sun Microsystems a company best known for its high end UNIX workstations. Java language was designed to be small, simple, and portable across platforms, operating systems, both at the source and at the binary level, which means that Java programs (applet and application) can run on any machine that has the Java virtual machine (JVM) installed.

4|Page

e-Gas Sewa
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, 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 toolRAD 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 Technologies Used

J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture. JAVA: Application architecture. WASCE: (WebSphere Application Server Community Edition) Web Server DB2: IBM Database. Ajax: Asynchronous Java Script and XML XML: Extension Markup Language. Web 2.0: RSS Feed 2.0. RAD 7.0: Development tool. Localization: 6 Languages - Hindi, , Bengali, Telugu, Marathi ,Tamil and English

5|Page

e-Gas Sewa

1.7 References
Software Engineering, Seventh Edition, Ian Sommerville. IBM Red Books IBM TGMC Sample Synopsis. IBM-www.ibm.in/developer works JAVA-www.sun.com. Wikipedia - www.wikipedia.com Database Management Systems - Navathe. Complete Reference - J2EE Keogh Object Oriented Modeling and Design with UML-Michael Blaha, James Rambaugh.

1.8. Overview
Existing System Registration for users Feedback forum Drawbacks No local language support. No online search and request of accessories. Remote area users and people who do not have knowledge of internet cannot use the system. Proposed System Registration for users. Kiosk Managers - help the customers who do not have knowledge of internet to use the system. Local language support i.e., Hindi, Bengali, Telugu, Marathi and Tamil. Online search and request for accessories. Online application form for Dealership.

Our Plan Registration for users. Online maintenance of demand and delivery record. Local language support. Online connection and booking facility.

6|Page

e-Gas Sewa
Online viewing delivery status for booked LPG. Online cancellation of booked LPG. Connection transfer facility to another location. Search nearest LPG dealer center. Online search and request for accessories. Online application form for Dealership. Guest user can view recent rates of LPG & security aspects etc.

2.Overall Description

2.1 Product Perspective

This application is based on 3-tier architecture. Database is maintained in DB2.Client end requires browser and HTTP server to request the website. Application server at the middle contains web container and messaging engine. Server listens for requests by client and maintain sessions. Server interacts with database.

Client
Browser

Application Server
Java Beans
JSPs
Servlets

Web Container
EJBs

HTTP Server
HTTP Server Plug ins

Database
Web Services Engine

Web Services Client

Messaging Engine

DB2

Fig.2.1 Product Perspective

7|Page

e-Gas Sewa

2.2 Software Interface

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 DB2, Operating System (any) Development End RAD (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), DB2, OS (Windows/Linux), WebSphere (Web Server)

2.3 Hardware Interface

Minimum Hardware Requirements

Client Side Processor RAM Disk Space

Internet explorer-6

Intel Pentium III or AMD -800 MHz

128 MB

100MB

Server side Processor RAM Disk Space

RAD Intel Pentium III or AMD -800

1 GB

3.5MB

8|Page

e-Gas Sewa
MHz DB2 256MB 500MB

2.4 ER- Diagram

Fig.2.2 ER Diagram

9|Page

e-Gas Sewa
2.5 Constraints
Login and password is used for the identification of user. Limited to HTTP/HTTPS. This system is working for single server.

2.6 Architectural Diagram

Application Layer Business Layer Database Layer

Fig.2.3 Architecture Diagram

10 | P a g e

e-Gas Sewa
2.7 Use Case Model Description

Customer:

Customer can register on portal and then login to search for agencies and make online connection request. They also can view their connection and delivery expenses. Customer can register complaints about connection to dealer and can also register complaint on any agency to admin. They can also give feedback. Customer is able to choose language i.e. Marathi, Telugu, Tamil, Hindi and Kannada.

Guest User:

Guest user can see the recent rate of LPG gas cylinder declared by Indian Government, security aspects about usability of LPG gas. Guest user can also see the procedure to be followed for getting a new LPG as connection.

Dealer:

Dealers can give connections, accept booking requests and can provide home delivery. Dealers can view complaints of customers and can take actions accordingly. Dealer is able to generate daily, weekly and monthly reports for admin.

Kiosk Manager:

Kiosk Manager views and manages the connections, performs day open and close activities and calculates his commission. He also sends reports to admin. Reports include daily order places report, daily delivered reports, daily cancelled order reports, daily customer reports and monthly dealers and franchise report.

Admin:

Admin has the authority to add/delete users. Admin authenticates and grant permission to dealers and kiosk manager. Admin views reports and accordingly takes action . He also views the complaints of customers and takes necessary actions. Admin is responsible for backup maintenance also.

11 | P a g e

e-Gas Sewa

Fig.2.8 Use case Model Diagram

12 | P a g e

e-Gas Sewa
2.8 Database Design

Fig.2.5 Database Diagram

13 | P a g e

e-Gas Sewa
2.9 Class Diagram

Fig.2.6 Class Diagram

14 | P a g e

e-Gas Sewa
3.Specific Requirements 3.1 Use-case Report
3.1.1 Customer Use-Case Report
Table 1: Customer Use-Case Report

USE CASE ChooseLanguage Login ViewProfile UpdateProfile GetConnection RemoveConnection Booking CancelBooking TransferConnection FileComplaint WithdrawComplaint SendMessage ReceiveMail GiveFeedback SearchDealers SearchAccessories RequestAccessories ViewDeliveryStatus

DESCRIPTION The customer can choose any local language to view website. The customer has to Login in order to start /begin his work. Every registered customer has his/her own profile containing personal and professional details. The customer has the option to update his/her own profile. The customer can apply request for connection. The customer can apply request for removing connection The customer can apply request for booking LPG. The customer can apply request to cancel booking. The customer can apply request for transfer connection to a new location (branch). The customer can file complaint on agency to admin. The customer has option to withdraw his/her complaint. The customer can send private message to dealers and admin. The customer can receive mail. The customers can give feedback to the admin. The customer can search for the nearest LPG dealer center. The customer can search for accessories. The customer can request for accessories. The customer can view delivery status for booked LPG.

Fig.3.1 Use Case diagram for Customer

15 | P a g e

e-Gas Sewa
3.1.2 Dealer Use-Case Report
Table 1: Dealer Use-Case Report

USE CASE Login ViewProfile UpdateProfile ViewComplaints AcknowledgeConnection AcceptBooking Deliver Search ChooseLanguage

DESCRIPTION The dealer has to Login in order to start /begin his work Every registered dealer has his/her own profile containing personal and professional details. The dealer has the option to update his/her own profile The dealer views the feedback of the admin to the complaints issued to a dealer. The dealer can accept/rejects the request of customers for a connection. The dealer can accept requests of customers for booking. The dealer can deliver cylinders to customers. The dealer can search for a particular item in website by entering the keyword. The dealer can choose any local language to view website.

Fig.3.2 Use Case diagram for Dealer

16 | P a g e

e-Gas Sewa
3.1.3 Guest User Use-Case Report
Table 2: Guest User Use-Case Report

USE CASE ChooseLanguage Register SeeRecentRate SeeSecurityAspects SeeProcedure KnowAboutSite SeeCurrentAffairs

DESCRIPTION The guest user can choose any local language to view website. The guest user has to register for website services. The guest user can see recent LPG rates decided by Indian Government. The guest user can see the security aspects about usage of LPG. The guest user can see the procedure to be followed for getting a new LPG connection. The guest user can view information about the site. The guest user can see the current affairs.

Fig.3.3 Use Case diagram for Guest User

17 | P a g e

e-Gas Sewa
3.1.4 KIOSK Manager Use-Case Report

Table 3: KIOSK Manager Use-Case Report

USE CASE Login ViewProfile UpdateProfile AddKIOSK ManageConnections CalculateCommission ViewLogs SendMessage ReceiveMail SendReport ApprovalFromAdmin ChooseLanguage Search

DESCRIPTION The KIOSK Manager has to Login in order to start begin his work. KM view his/her own profile containing personal and professional details. The KM has the option to update his/her own profile The KM can add new KIOSK. The KM can manage the connections for customers. The KM can charge commission from customers for using the facility of KIOSK . The KM can view the logs. The KM can send message. The KM can receive mail. The KM can send report to admin. The KM should get approval from admin. The KM can choose any local language. The KM can search for a particular item in website by entering the keyword.

Fig. 3.4 Use Case diagram for KIOSK Manager

18 | P a g e

e-Gas Sewa
3.1.5 Admin Use-Case Report
Table 4: Admin Use-Case Report

USE CASE Login ViewProfile UpdateProfile ViewComplaints TakeAction TakeBackup DeleteUsers SendMail ReceiveMessage ViewReport ViewLogs Search

DESCRIPTION The admin has to Login in order to start begin his work. Admin view his/her own profile containing personal and professional details. The admin has the option to update his/her own profile The admin views the complaint sent by other users The admin can take necessary actions The admin can take backup of the system The admin is given the option to delete the users The admin can send mail. The admin can receive private messages from customers, KMs and dealers. The admin views the report sent by kiosk manager. The admin can view the logs. The admin can search for a particular item in website by entering the keyword.

Fig.3.5 Use Case diagram for Admin

19 | P a g e

e-Gas Sewa
3.2 Activity Diagrams
3.2.1 User Registration Activity 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.

Fig.3.6 Activity Diagram for Representing User Registration

3.2.2 Dealer and Kiosk Manager Registration Activity The dealer and KM needs to fill all mandatory fields filled in registration form. Once they click submit, the User name is verified. If the username is already present, then they are again taken back, so that they 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 they are informed to enter the correct

20 | P a g e

e-Gas Sewa
values. These details are sent to admin for verification and the admin verifies the data and approves registration and grants privileges.

Fig.3.7 Activity Diagram for Representing Dealer & KM Registration

21 | P a g e

e-Gas Sewa
3.2.3 User Login Activity

User is prompt to enter the username and password, if he is signing in through KIOSK, KIOSK ID has to be entered, then entered values are verified. If it is a valid username and password, then the user is logged in, or else they are asked to re enter the correct values.

Fig. 3.8 Activity Diagram for User Login

3.2.4 Privileged User Login Activity Privileged User such as Dealer, Kiosk Manager and Administrator is made to enter the username and password, entered values are verified. If it is a valid username and password, then the user is logged in and assigned the respective privileges, or else they are asked to retry by entering the correct values. After logging in, privileged user is provided with its profile page from where it can perform various tasks.

22 | P a g e

e-Gas Sewa

Fig.3.9 Activity Diagram for Privileged User Login

3.2.5 Take Connection Activity

Customer first creates an account in portal. After logging in the portal, the customer will search for a dealer using search option. Then the customer selects a dealer from search results and selects the connection type and sends his request for connection to dealer. Dealer views the connection request. Then he can either reject the request or can approve it by sending an appropriate message to customer.

23 | P a g e

e-Gas Sewa

Fig.3.10 Activity Diagram for Taking Connection

3.2.6 Booking LPG cylinder The customer will have to login. Then customer will click on booking option. He will come to know the total charges (LPG cost + delivery charges etc). Then he will request for booking cylinder. Request is validated against last request for 22 days policy. If valid, customer can book the cylinder. If request for booking is accepted by the dealer, the customer will receive an acceptance email and a message or else he will receive a failure email and message.

24 | P a g e

e-Gas Sewa

Fig 3.11 Activity Diagram for Booking LPG

3.2.7 Transfer Connection

The customer will have to login. Then customer will go to opt for transfer connection. He will have to enter new records and details. The customer will search for nearest dealer and select the suitable dealer. Then he will enter the type of connection and request for transfer connection. If the request is approved he will receive a confirmation message or else he will receive a failure message.

25 | P a g e

e-Gas Sewa

Fig.3.12 Activity Diagram for Transfer Connection

26 | P a g e

e-Gas Sewa
3.2.8 LPG Delivery Activity The dealer will view all requests by customer. The dealer will either accept the request than deliver the cylinder to the customer or delays it for a certain period.

Fig.3.13 Activity Diagram for LPG Delivery

3.2.9 Lodging a Complaint Activity

After logging in, customer can go for making complaint. Customer is prompted to enter text. The customer enters the complaint text and sends it to admin and the system generated ComplaintId which is returned to the user for future reference.

27 | P a g e

e-Gas Sewa

Fig.3.14 Activity Diagram for Lodging Complaint

3.2.10 Replying a Complaint Activity The admin views the complaint and then he may reply to the user or he may select the respective dealer and forwards the complaint to him

Fig.3.15 Activity Diagram for Replying Complaint

28 | P a g e

e-Gas Sewa
3.2.11 Feedback Activity The customer will have to go for feedback and enter feedback text. Then he can click on post and submit the feedback to website. The feedback forum is displayed.

Fig. 3.16 Activity Diagram for Feedback Activity

3.3 Sequence Diagrams

3.3.1 Users Login Sequence Diagram The user can login to his/her profile by providing username and password. If the combination is validated by interface, it is forwarded to database. If the combination is verified, it will display the home page otherwise error page is displayed. If it is not validated by interface, user is prompted to reenter the username and password. After logging in user can perform several functions it is intended for.

29 | P a g e

e-Gas Sewa

Fig. 3.17 Sequence Diagram Representing User Login

3.3.2 Take a Connection Diagram To take a connection user has to login and go to search dealer. For searching, a prompt to enter the locality is provided by the interface to the user. Now, interface forwards the locality to the database for searching .Search results are then forwarded to the interface .Then interface displays the result to the customer .Customer enter details and send request for connection .The interface forwards it to the dealer for acknowledgement .The dealer either accept the request or rejects it.

30 | P a g e

e-Gas Sewa

Fig. 3.18 Sequence Diagram Representing Connection

31 | P a g e

e-Gas Sewa
3.3.3 Lodge Complaint Sequence Diagram The interface prompts to customer to enter complaint text. Customer enters text. Text is forwarded to admin

and database. Database generates a complaintId which is displayed to the customer.

Fig. 3.19 Sequence Diagram for Lodging Complaint

3.3.4 Booking Sequence Diagram Customer has to login and go for booking. Interface shows the charges including delivery charges. Now customer books the cylinder. Customer may place request only after 22 days of last delivery, request is discarded. Thus, interface verifies it against 22 day policy either discarding request or accepting it. If accepted, customer can place the request which is then viewed by dealer. Dealer may accept, delay or reject the request. Customer is informed through a SMS. If discarded because of policy, customer is prompted with a warning message.

32 | P a g e

e-Gas Sewa

Fig .3.20 Sequence Diagram Representing Booking

33 | P a g e

e-Gas Sewa
3.3.5 Authentication of Privileged Users Sequence Diagram The user is prompted to enter details by interface. User enters details and send request for authentication. Request is forwarded to admin for verification. If verified successfully admin authenticate user otherwise request is rejected.

Fig. 3.21 Sequence Diagram for Authenticate User

34 | P a g e

e-Gas Sewa

4. Supporting Information 4.1 Index

A Abbreviations 5 Acronyms 5 Admin 12, 20 AJAX 5, 6 Analysis 3 B Booking Expenses 12
2

I Inception 3 Interface 8, 31, 33 Introduction 3 K Kiosk .23 Manager 12 KM 19, 13 M Methodology 3 O

S Scope 4 Sequence 30 Software 6 T Transition 4 Technologies 6

U Use-case 16 UML 6 W WASCE 5, 6

C Customer 7, 12 Connection 12 D Data Base 6 DB2 8, 9 Definitions 5 Development End 9 Drawbacks 7 Dealer 12 Design 14 E Elaboration 4 ER Diagram 10 Existing System 7 H Hardware 9 HTML 5 HTTP 5 HTTPS 10

Operating System 5, 8 Our Plan 7 Overall 8

P Product Perspective 8 Proposed System 7 Purpose 4 R RAD 6 References 6 Reports 12 Rational Unified Process 3

35 | P a g e

e-Gas Sewa

4.2 Special Thanks

We convey a special thanks to our department and to our college. We also convey a special thanks to all these softwares and websites, they have been helping a lot in doing the project.

36 | P a g e