Introduction: Journey became part and parcel of a human

being’s life. Without moving around, people cannot communicate and share the moments with others.

This becomes easy with E-Wheelz software which helps in obtaining reservations of seats in a bus well before and take the tickets also online by staying at home.

On the other hand, the administrator of this system will be able to add new routes, add pick up points for the existing routes and cancel existing routes. Also he can add new travel, add bus details for the travels and can remove an existing travel company’s name from the list.

EWheelz software is a globally deployable, integrated, workflow based end-to-end system starting from searching bus routes to book them online. This is a complete application for travelers as well as venders. Vendors provide the information like, available routes, timings, price, etc. Customers can book a ticket which is a five step process that includes Search Bus, Select Bus, Select Seats, Provide Customer Information and Make Payment. This application also provides facility to cancel a booked ticket online. There is also scope to measure the user satisfaction regarding the entire booking process. He can express his views or grievances through testimonial option in the application so that it reflects the goodwill of the travel company and helps other users to have trust in the company.

Technologies Used: J2SE, Servlets, JSP, JDBC and Java Script

Objectives:- To research, from the literature, the techniques

used in generating web based e-wheels Schedules.

Understanding of the Key techniques for developing , and solving the problems in the project.

To implement/test/evaluate an interactive system for generating the “web-based ewheelz” project using suitable constraint library in Java.

OOPS: Object Oriented Programming Structures Class Object Data Abstraction Data Encapsulation Polymorphism Inheritance Message Passing Class:- A class is a group name that contains similar types of objects. Ex: Flower is a class, and rose is a object of flower class. Object:- Object is any thing that is really exists in the world.

SYSTEM ANALYSIS Definition and reason for Condition Analysis System analysis will be performed to determine if it is feasible to

design an information based on policies and plans of the organization and on user requirements and to eliminate the weaknesses of the present system.

General requirements The new system should be cost effective. To augment management, improve productivity and services. To enhance User/System interface. To improve information qualify and usability. To upgrade system’s reliability, availability, flexibility and growth

potential.

Identification of Need Existing System Here the existing system is a manual one. When a customer wants a

book a ticket for his journey then he needs to go to any booking branch office physically and book the ticket. In this case the branch people needs to check the available seats by making a call to main office and then only these people can book ticket which leads to improper synchronization between the branches. We can maintain all the booking details in a record at very branch but finally checking the availability and allotting the seats may cause some human errors. It is very difficult to maintain the booking details of each bus and their status manually.

Disadvantages: Difficulty in co-coordinating different branches and allotting the seats Customer has to come and book the ticket physically which gives

competitors to grab the market Difficulty of maintaining each bus booking details in record. Difficulty in generating the reports Difficulty in canceling the ticket. Difficulty in providing user-friendly information to the customer

The eWheelz is to replace the existing manual system with a online software solution using which provides lot of flexibilities for the customers from online. Customer can book ticket according to his requirement by viewing different different buses information and their seat arrangements on the console very easily. It fills the gap between different branches and provides effective synchronization between them. It allows the customers to post their feedback which will be displayed as testimonial.

The proposed system has one administrator to manage the routes, buses and their schedules. He can have the permission to control the overall activities of this application

Merits of This System Faster processing when compared to existing one. Centralized system Provides convenient way for the customer to book required seat as per their

convenience and cancel the ticket also. Providing good co-ordination between different branches. Administrator can view reports any bused at any point of time. Easy maintenance of booked, blocked and vacant details info Avoids human errors Provides the facility to print the ticket.

Feasibility Study: An initial investigation culminates in a proposal that determines

whether an alternative system is feasible than the present candidate system. To do feasible study we have to do the Technical, Financial feasible studies.

Technical Feasibility: - The system is self-explanatory and does not need any extra

sophisticated training. As the system has been built by concentrating on the Graphical User Interface Concepts, the application can also be handled very easily with a novice User. The overall time that is required to train the users upon the system is less than half an hour.

The System has been added with features of menu-driven and button interaction methods, which makes the user the master as he starts working through the environment. The net time the customer should concentrate is on the installation time.

Financial Feasibility: - i) Time Based: Contrast to the manual system management can generate

any report just by single click. In manual system it is too difficult to maintain historical data which become easier in this system. Time consumed to add new records or to view the reports is very less compared to manual system. So this project is feasible in this point of view

ii) Cost Based: No special investment need to manage the tool. No specific training is required for employees to use the tool. Investment requires only once at the time of installation. The software used in this project is freeware so the cost of developing the tool is minimal and hence the overall cost.

TECHNICAL FEASIBLITY Required Hardware Pentium IV processes architecture 512 MB RAM. 40 GB Hard Disk Space Ethernet card with an Internet or Internet zero. Required Software Database : MySQL 5.0 Server : Apache Tomcat 5.51 Front end : JSP / Servlets, J2SDK 1.4, HTML, DHTML, Java Script Editor : Edit plus

OPERATIONAL FEASIBILITY User-friendly Customer will use the forms for their various transactions i.e. for adding new

routes, viewing the routes details. Also the Customer wants the reports to view the various transactions based on the constraints. Theses forms and reports are generated as user-friendly to the Client.

Reliability The package wills pick-up current transactions on line. Regarding the old

transactions, User will enter them in to the system. Security The web server and database server should be protected from hacking,

virus etc Portability The application will be developed using standard open source software

(Except Oracle) like Java, tomcat web server, Internet Explorer Browser etc these software will work both on Windows and Linux o/s. Hence portability problems will not arise.

Availability This software will be available always.

Maintainability

The system called the ewheelz uses the 2-tier architecture. The 1st tier is the GUI, which is said to be front-end and the 2nd tier is the database, which uses My-Sql, which is the back-end.

The front-end can be run on different systems (clients). The database will be running at the server. Users access these forms by using the user-ids and the passwords.

ECONOMICAL FEASIBILITY The computerized system takes care of the present existing system’s data

flow and procedures completely and should generate all the reports of the manual system besides a host of other management reports.

It should be built as a web based application with separate web server and database server. This is required as the activities are spread through out the organization customer wants a centralized database. Further some of the linked transactions take place in different locations.

Open source software like TOMCAT, JAVA, Mysql and Linux is used to minimize the cost for the Customer.

Requirements Specification Document Introduction According to Roger Pressman in Software Engineering: A

Practitioner's Approach (McGraw-Hill Publications) [SEPA–1997], the requirement specification document is produced at the end of Analysis of the system. This document is a very comprehensive document & contains all the User requirements & Analysis diagrams. The Requirements are broadly divided into two groups:

1. Functional requirements 2. Non-functional requirements Functional Requirements The main purpose of functional requirements within the requirement

specification document is to define all the activities or operations that take place in the system. These are derived through interactions with the users of the system. Since the Requirements Specification is a comprehensive document & contains a lot of data, it has been broken down into different Chapters in this report. The depiction of the Design of the System in UML is presented in a separate chapter. The Data Dictionary is presented in the Appendix of the system.

But the general Functional Requirements arrived at the end of the interaction with the Users are listed below. A more detailed discussion is presented in the Chapters, which talk about the Analysis & Design of the system.

1. The System holds all the details of the routes and travels.

2. It holds the details of all the users. 3. It holds the details of all the buses and the

passenger’s details. 4. The system allows the users to log into their accounts

and perform their tasks. 5. It allows the normal users to search for the buses and

tickets availability status. 6. The system allows the normal users to reserve their

tickets for their journey.

7. The system holds the information regarding the buses which are available in the corresponding travels.

8. It holds the information regarding the buses, adding and removing the buses.

9. Once the new travel is added then it will display in the travels list and the normal user can view the details of all the travels.

10. Once the user has reserve the ticket then he can take out the print and he can pay the amount through the cards.

11. It allows the users to provide the testimonials. 12. It allows the users to reserve or cancel the tickets. Non-Functional Requirements The non-functional requirements consist of 1. Analysis, Design & Data requirements (Use-case diagrams,

textual analysis, sequence diagrams, data dictionary etc.) 2. Constraints. 3. Guidelines.

ER- Diagrams

Introduction An Overview of UML The UML is a language for Visualizing Specifying Constructing Documenting These are the artifacts of a software-intensive system. A conceptual model of UML: The three major elements of UML are The UML’s basic building blocks The rules that dictate how those building blocks may be put together. Some common mechanisms that apply throughout the UML.

Basic building blocks of the UML The vocabulary of UML encompasses three kinds of building blocks: Things Relationships Diagrams Things are the abstractions that are first-class citizens in a model; Relationships tie these things together; Diagrams group the interesting collection of things. Things in UML: There are four kind of things in the UML Structural things Behavioral things. Grouping things Annotational things These things are the basic object oriented building blocks of the

UML. They are used to write well-formed models.

1. STRUCTURAL THINGS Structural things are the nouns of the UML models.

These are mostly static parts of the model, representing elements that are either conceptual or physical. In all, there are seven kinds of Structural things.

Class: A class is a description of a set of objects that share the

same attributes, operations, relationships, and semantics. A class implements one or more interfaces.

Graphically a class is rendered as a rectangle, usually including its name, attributes and operations.

Interface: An interface is a collection of operations that specify a

service of a class or component. An interface describes the externally visible behavior of that element.

Graphically the interface is rendered as a circle together with its name.

Collaboration: Collaboration defines an interaction and is a society of

roles and other elements that work together to provide some cooperative behavior that’s bigger than the sum of all the elements.

Graphically , a collavoration is rendered as an ellipse with dashed lines, usually including only its name.