You are on page 1of 36

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

Web 2.0: It is commonly associated with web applications which facilitate interactive information sharing. operating systems. HTTP: Hyper Text Transfer Protocol. WSAD: WebSphere Studio Application Developer . XML: Extensible Markup Language. It is a database management system that provides a flexible and efficient database platform to raise a strong "on demand" business applications. both at the source and at the binary level. DB2: IBM Database 2. He also views the complaints of customers and takes necessary actions. AJAX: Asynchronous Java Script and XML. Acronyms and Abbreviations           HTML: Hyper Text Markup Language.It is a designer toolkit which is designed to develop more complex projects by providing a complete dynamic web service. Java language was designed to be small. It is a technique used in java script to create dynamic web pages. 4|Page . J2EE: Java 2 Enterprise Edition. belonging to the Java platform. simple. WASCE: WebSphere Application Server Community Edition. which is used for developing and running distributed java applications. It is used to create dynamic web content.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. 1. It is an application server that runs and supports the J2EE and the web service applications.4 Definitions. 1. It is a markup language that was designed to transport and store data. It is a programming platform. and portable across platforms. It is used to create static web pages. interoperability. JSP: Java Server Pages. user-centered design and collaboration on the World Wide Web. which means that Java programs (applet and application) can run on any machine that has the Java virtual machine (JVM) installed. It is a transaction oriented client/ server protocol between a web browser and a web server.e-Gas Sewa  Admin has the authority to add/delete users. grant permission to dealers.

0: Development tool. portals. JSP.6 Technologies Used         J2EE: (Servlet. It is IBM's supported distribution of Apache Geronimo that uses Tomcat for servlet container and Axis 2 for web services.Hindi. distributed.  Development tool–RAD IBM Rational Application Developer for WebSphere Software (RAD) is an integrated development environment (IDE).  Design tool – Rational Software Modeler IBM Rational Software Modeler. 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. Telugu. Marathi . Java Beans) Application architecture. is a Unified Modeling Language UML 2.0. (RSM) made by IBM's Rational Software division. JAVA: Application architecture.  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. made by IBM's Rational Software division. Bengali. based largely on modular components running on an application server. RAD 7. Over 15 WASCE developers are committers in the Apache Geronimo project. 1. and Java (J2EE) applications. Localization: 6 Languages . 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.0: RSS Feed 2. and deploying Web services. WASCE: (WebSphere Application Server Community Edition) Web Server DB2: IBM Database. for visually designing.0-based visual modeling and design tool. . JAXP. Ajax: Asynchronous Java Script and XML XML: Extension Markup Language.testing. thought-out applications and web services. Web 2. multi-tier Java software. Enterprise Edition or Java EE is a widely used platform for server programming in the java programming language. certified Java EE 5 server for building and managing Java applications. constructing .Tamil and English 5|Page .  Web server – WASCE WebSphere Application Server Community Edition (from now on WASCE) is a free.e-Gas Sewa  J2EE Java Platform.

1. IBM Red Books IBM TGMC Sample Synopsis. No online search and request of accessories.7 References          Software Engineering. Online search and request for accessories. Online application form for Dealership. Our Plan     Registration for users. 6|Page . Marathi and Tamil.sun. Bengali.J2EE – Keogh Object Oriented Modeling and Design with UML-Michael Blaha. Seventh Edition. Ian Sommerville. Remote area users and people who do not have knowledge of internet cannot use the system. James Rambaugh. Wikipedia .com. IBM-www. Overview Existing System           Registration for users Feedback forum Drawbacks No local language support. Online connection and booking facility. Local language support.ibm. Proposed System Registration for users. Telugu. Online maintenance of demand and delivery record. Local language support i.e. Complete Reference . Kiosk Managers .Navathe.in/developer works JAVA-www.com Database Management Systems . Hindi.www.help the customers who do not have knowledge of internet to use the system.wikipedia..e-Gas Sewa 1.8.

Guest user can view recent rates of LPG & security aspects etc. Server interacts with database. Search nearest LPG dealer center.Overall Description 2. Connection transfer facility to another location. Online application form for Dealership. Application server at the middle contains web container and messaging engine. 2.Client end requires browser and HTTP server to request the website. 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. Online search and request for accessories. Server listens for requests by client and maintain sessions. Online cancellation of booked LPG. Database is maintained in DB2.1 Product Perspective This application is based on 3-tier architecture.1 Product Perspective 7|Page .e-Gas Sewa        Online viewing delivery status for booked LPG.

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.e-Gas Sewa 2.5MB 8|Page . AJAX). Operating System (any) Development End RAD (J2EE. Servlets. Java Bean. Java. OS (Windows/Linux). Operating System (any) Web Server WASCE.2 Software Interface    Client on Internet Web Browser. HTML. DB2. XML. Operating System (any)   Data Base Server DB2. WebSphere (Web Server) 2. Operating System (any) Client on Intranet Web Browser.

4 ER.e-Gas Sewa MHz DB2 256MB 500MB 2.2 ER Diagram 9|Page .Diagram Fig.2.

This system is working for single server.5 Constraints    Login and password is used for the identification of user.3 Architecture Diagram 10 | P a g e .e-Gas Sewa 2. 2. Limited to HTTP/HTTPS.2.6 Architectural Diagram Application Layer Business Layer Database Layer Fig.

e. Customer can register complaints about connection to dealer and can also register complaint on any agency to admin. Hindi and Kannada. Kiosk Manager: Kiosk Manager views and manages the connections. daily delivered reports.7 Use Case Model Description Customer: Customer can register on portal and then login to search for agencies and make online connection request. Admin: Admin has the authority to add/delete users. Dealer: Dealers can give connections. performs day open and close activities and calculates his commission. 11 | P a g e . Tamil. They also can view their connection and delivery expenses. Dealers can view complaints of customers and can take actions accordingly. weekly and monthly reports for admin. Marathi. Customer is able to choose language i.e-Gas Sewa 2. Admin views reports and accordingly takes action . Dealer is able to generate daily. accept booking requests and can provide home delivery. They can also give feedback. security aspects about usability of LPG gas. Reports include daily order places report. Guest user can also see the procedure to be followed for getting a new LPG as connection. Admin authenticates and grant permission to dealers and kiosk manager. He also views the complaints of customers and takes necessary actions. He also sends reports to admin. Telugu. Admin is responsible for backup maintenance also. daily customer reports and monthly dealers and franchise report. daily cancelled order reports. Guest User: Guest user can see the recent rate of LPG gas cylinder declared by Indian Government.

8 Use case Model Diagram 12 | P a g e .2.e-Gas Sewa Fig.

8 Database Design Fig.2.5 Database Diagram 13 | P a g e .e-Gas Sewa 2.

6 Class Diagram 14 | P a g e .9 Class Diagram Fig.e-Gas Sewa 2.2.

The customer can apply request for removing connection The customer can apply request for booking LPG.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 can file complaint on agency to admin. Every registered customer has his/her own profile containing personal and professional details.1. The customer has option to withdraw his/her complaint.1 Use Case diagram for Customer 15 | P a g e .3. The customer can send private message to dealers and admin. Fig. The customer has the option to update his/her own profile. The customer can request for accessories. The customer can apply request to cancel booking.1 Use-case Report 3.Specific Requirements 3. The customer can search for the nearest LPG dealer center. The customers can give feedback to the admin. The customer can receive mail. The customer can apply request for connection.e-Gas Sewa 3. The customer can apply request for transfer connection to a new location (branch). The customer has to Login in order to start /begin his work. The customer can view delivery status for booked LPG. The customer can search for accessories.

3.2 Use Case diagram for Dealer 16 | P a g e . The dealer can choose any local language to view website.1. The dealer can accept requests of customers for booking. 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.e-Gas Sewa 3.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 can accept/rejects the request of customers for a connection. The dealer can search for a particular item in website by entering the keyword. The dealer can deliver cylinders to customers. Fig.

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 can see the current affairs. The guest user can see recent LPG rates decided by Indian Government. The guest user has to register for website services. The guest user can see the procedure to be followed for getting a new LPG connection.3.3 Use Case diagram for Guest User 17 | P a g e .e-Gas Sewa 3. Fig. The guest user can view information about the site. The guest user can see the security aspects about usage of LPG.1.

The KM can view the logs. The KM can search for a particular item in website by entering the keyword. The KM can receive mail. The KM can send report to admin.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 can send message.e-Gas Sewa 3. 3. The KM can charge commission from customers for using the facility of KIOSK . The KM should get approval from admin. Fig. The KM can choose any local language. The KM can manage the connections for customers. The KM has the option to update his/her own profile The KM can add new KIOSK.1.4 Use Case diagram for KIOSK Manager 18 | P a g e .

e-Gas Sewa 3.1. The admin views the report sent by kiosk manager.3. KMs and dealers. The admin can search for a particular item in website by entering the keyword. Fig. The admin can view the logs. Admin view his/her own profile containing personal and professional details. The admin can receive private messages from customers.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.5 Use Case diagram for Admin 19 | P a g e . 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.

If the username is not present then it checks for password and remaining mandatory fields. the User name is verified. Once they click submit. then the user is again taken back. then they are again taken back. then the user is informed to enter the correct values. Once the user clicks submit. so that they can change the username. If the username is already present.1 User Registration Activity Initially user is made to fill all mandatory fields filled in registration form. If any of the mandatory field is left empty or filled incorrect.2. If the username is not present then it checks for password and remaining mandatory fields. then the registration is done. Once all these verifications are succeeded. If any of the mandatory field is left empty or filled incorrect.e-Gas Sewa 3. Fig.3. then they are informed to enter the correct 20 | P a g e .6 Activity Diagram for Representing User Registration 3.2. so that he can change the username. the username is verified.2 Activity Diagrams 3.2 Dealer and Kiosk Manager Registration Activity The dealer and KM needs to fill all mandatory fields filled in registration form. If the username is already present.

Fig. These details are sent to admin for verification and the admin verifies the data and approves registration and grants privileges.e-Gas Sewa values.3.7 Activity Diagram for Representing Dealer & KM Registration 21 | P a g e .

KIOSK ID has to be entered.3 User Login Activity User is prompt to enter the username and password. then the user is logged in and assigned the respective privileges.e-Gas Sewa 3.2. then entered values are verified. If it is a valid username and password. Kiosk Manager and Administrator is made to enter the username and password. privileged user is provided with its profile page from where it can perform various tasks. entered values are verified. 22 | P a g e . or else they are asked to retry by entering the correct values. or else they are asked to re enter the correct values.8 Activity Diagram for User Login 3. then the user is logged in. 3. If it is a valid username and password.2.4 Privileged User Login Activity Privileged User such as Dealer. Fig. if he is signing in through KIOSK. After logging in.

2. the customer will search for a dealer using search option.5 Take Connection Activity Customer first creates an account in portal. 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. 23 | P a g e .3. After logging in the portal.9 Activity Diagram for Privileged User Login 3. Then he can either reject the request or can approve it by sending an appropriate message to customer.e-Gas Sewa Fig.

e-Gas Sewa Fig. the customer will receive an acceptance email and a message or else he will receive a failure email and message. If request for booking is accepted by the dealer. customer can book the cylinder. 24 | P a g e .2. He will come to know the total charges (LPG cost + delivery charges etc). Then customer will click on booking option. Request is validated against last request for 22 days policy.3.6 Booking LPG cylinder The customer will have to login.10 Activity Diagram for Taking Connection 3. If valid. Then he will request for booking cylinder.

He will have to enter new records and details. Then customer will go to opt for transfer connection. Then he will enter the type of connection and request for transfer connection.7 Transfer Connection The customer will have to login. 25 | P a g e . The customer will search for nearest dealer and select the suitable dealer.11 Activity Diagram for Booking LPG 3. If the request is approved he will receive a confirmation message or else he will receive a failure message.e-Gas Sewa Fig 3.2.

e-Gas Sewa Fig.12 Activity Diagram for Transfer Connection 26 | P a g e .3.

Customer is prompted to enter text.13 Activity Diagram for LPG Delivery 3. customer can go for making complaint. 27 | P a g e .8 LPG Delivery Activity The dealer will view all requests by customer.2.2. The dealer will either accept the request than deliver the cylinder to the customer or delays it for a certain period.3. Fig.9 Lodging a Complaint Activity After logging in. 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.e-Gas Sewa 3.

14 Activity Diagram for Lodging Complaint 3.e-Gas Sewa Fig.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 .3.

If the combination is verified. If it is not validated by interface. If the combination is validated by interface. Fig. Then he can click on post and submit the feedback to website. 29 | P a g e . After logging in user can perform several functions it is intended for.11 Feedback Activity The customer will have to go for feedback and enter feedback text. it will display the home page otherwise error page is displayed. 3. The feedback forum is displayed. it is forwarded to database. user is prompted to reenter the username and password.16 Activity Diagram for Feedback Activity 3.2.3 Sequence Diagrams 3.e-Gas Sewa 3.3.1 Users Login Sequence Diagram The user can login to his/her profile by providing username and password.

For searching.The interface forwards it to the dealer for acknowledgement .2 Take a Connection Diagram To take a connection user has to login and go to search dealer. 30 | P a g e . Now.17 Sequence Diagram Representing User Login 3. 3.e-Gas Sewa Fig. interface forwards the locality to the database for searching .Customer enter details and send request for connection .3.Search results are then forwarded to the interface .The dealer either accept the request or rejects it. a prompt to enter the locality is provided by the interface to the user.Then interface displays the result to the customer .

18 Sequence Diagram Representing Connection 31 | P a g e .e-Gas Sewa Fig. 3.

3. request is discarded. customer can place the request which is then viewed by dealer. Interface shows the charges including delivery charges. Database generates a complaintId which is displayed to the customer. delay or reject the request. Thus. Customer may place request only after 22 days of last delivery. Text is forwarded to admin and database. If accepted. Now customer books the cylinder.3. If discarded because of policy. Dealer may accept.e-Gas Sewa 3.3 Lodge Complaint Sequence Diagram The interface prompts to customer to enter complaint text.19 Sequence Diagram for Lodging Complaint 3. customer is prompted with a warning message.4 Booking Sequence Diagram Customer has to login and go for booking. Customer is informed through a SMS. Customer enters text.3. Fig. 32 | P a g e . interface verifies it against 22 day policy either discarding request or accepting it.

e-Gas Sewa Fig .3.20 Sequence Diagram Representing Booking 33 | P a g e .

21 Sequence Diagram for Authenticate User 34 | P a g e .5 Authentication of Privileged Users Sequence Diagram The user is prompted to enter details by interface. If verified successfully admin authenticate user otherwise request is rejected. Request is forwarded to admin for verification. User enters details and send request for authentication.3. 3. Fig.e-Gas Sewa 3.

20 AJAX · 5. 6 Analysis · 3 B Booking Expenses ·12 2 I Inception · 3 Interface · 8. 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. Supporting Information 4. 31.e-Gas Sewa 4. 33 Introduction · 3 K Kiosk . 6 C Customer · 7. 12 Connection · 12 D Data Base · 6 DB2 · 8. 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 .1 Index A Abbreviations · 5 Acronyms · 5 Admin · 12. 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.23 Manager· 12 KM· 19.

2 Special Thanks We convey a special thanks to our department and to our college. they have been helping a lot in doing the project. 36 | P a g e .e-Gas Sewa 4. We also convey a special thanks to all these software’s and websites.