Vehicle Report Changed

1
CHAPTER
1:
INTRODUCTION
In the fast changing world, information technology and information management are going to
play an important role. We are living in the computer age during past some year .The computer
has gaining popularity. Computer revolution found its way into almost every aspect of human
life and living. A computer is admirably suited to handle any information and hence is an
information processor that is, it can receive data, perform some basic operations on that data
and produces results according to a predetermined program.
is a web based application in which the whole records of the passenger in the vehicle
would be manage the details about different students which have received the books would be
kept. The students would be able to know the books availability status on the basis of proper
login which would be provided to them. The management would be able to know the whole
library status on a single click and customized reports would be generated.
1.1ABOUT THE PROJECT

In the background of Vehical Sanagement System all the manual and paper work which
was done in the past would be removed by the use the web technology different huge size
register were use to maintain. The records of books and details about books issues etc. All
these things would be software based and customize report would be generated paper work
would be lesser. This project of “VEHICLE MANAGEMENT SYSTEM” of gives us
the complete information about the library. We can enter the record of new books and
retrieve the details of books available in the library. We can issue the books to the students
and maintain their records and can also check how many books are issued and stock available
in the library. In this project we can maintain the late fine of students who returns the issued
books after the due date. Throughout the project the focus has been on presenting
2
information and comments in an easy and intelligible manner. The project is very useful for
those who want to know about VEHICLE MANAGEMENT SYSTEM.
1.1.1 System Objective
Today’s world is computer world because most of work is doing with the help of
computer. Dependency on computer is behind the few reasons. We cannot easily manage
to store large number of data or information single handle. If we will be need some
information or data in urgency then we cannot manage in manually these works are very
difficult if we cannot use computer.
1.1.2 System Context:

This section clearly depicts the environment and boundaries of the LMS and the entities with
which it interacts. it helps us see how the system fits into the existing scheme of things. What the
system will do by itself and what it expects other entities to do is clearly delineated.
1.1.1 Functional Requirement
In the background of Vehicle Management System was all the manual and paper work
which was done in the past would be removed by the use the web technology different huge
size register were use to maintain. The records of books and details about books issues etc.
All these things would be software based and customize report would be generated paper
work would be lesser. This project of “VEHICLE MANAGEMENT SYSTEM” of gives us
the complete information about the Vehicle. We can enter the record of new books and
retrieve the details of books available in the library. We can issue the books to the students
and maintain their records and can also check how many books are issued and stock available
in the library. In this project we can maintain the late fine of students who returns the issued
books after the due date. Throughout the project the focus has been on presenting
information and comments in an easy and intelligible manner. The project is very useful for
those who want to know about Vehicle Management System.
3
1.1.2 Non-Functional Requirement

These are quality requirement that stipulate the performance levels required of the system for
various kind of activate. Numerical lower and upper limits set conditions on the response times,
access times etc of the system. Sometimes tradeoffs are necessary among various non-functional
requirements.
1.1.3 Future Requirement

These are the specifications which are not provided for now in the current version of
LMS but which could be incorporated into future versions. Some of these need advanced
technologies and interface with other system. The LMS could be designed in future to
enhance the existing capabilities or add entirely new ones.
1.2 OBJECTIVES
Today’s world is computer world because most of work is doing with the help of computer.
Dependency on computer is behind the few reasons. We cannot easily manage to store large
number of data or information single handily. If we will be need some information or data in
urgency then we cannot manage in manually these works are very difficult if we cannot use
computer.
So the objective of this project is to overcome the limitation of the manual approach.
This project is started towards systematically automating all the work that is done manually at
present. Their aim is to focus following aspects:
o The main objective is to automate non computer environment

o To save manpower.
o It will speed the processing of data and transaction.
o It will provide all the error reporting and handling features, so that the user is warned and
made aware of any foreseen errors. Thus it will reduce the error rate.
o It will provide various ways through which we generate various types of report.
o It will provide best security features such as provisions of passwords.
4
o of the available notepad Feature.

5
6
CHAP TER 2 :
PROBLEM DEFINATION AND FEASIBILITY ANALYSIS
PROBLEM SPECIFICATION
The definition of our problem lies in manual system and a fully automated system.
Manual System
The system is very time consuming and lazy. This system is more prone to error and sometimes
the approach to various problems is unstructured.
Technical System
With the advent of latest technology if we do not update our system then our business result in
losses gradually with time. The technical system contains the tools of latest trend i.e. computers,
printers, FAX, Internet etc the system with the technology are very fast, accurate, user friendly
and reliable.
Need of Vehicle Management System Software

A Vehicle Management System is a person or a company who can texting and
formating data are distinguished from ordinary mail services by features such as speed,
security, tracking, signature, specialization and individualization of express services, and
swift bidding times, which are optional for most everyday auction services. As a
premium service, library are usually more expensive than usual mail services, and their
use is typically restricted to issuing where one or more of these features are considered
important enough to warrant the cost.
Existing System
The Existing system comprises of a system in which details are to be manually handled this is
not use friend.
The Proposed Vehicle Management System S/w

It will be able to manage inforrmation about writing data in more user friendly way. This system
7
will manage text and Return result at various colleges.. Various reports based on the data entered
by employee at branches are generated at Main Branch or Head office. These report are helpful
in Manpower Management Decision.
Introduction
Problem introduction or problem starting is the starting point of the software development
activity. The objective of this statement is to answer: Exactly what must the system do? The
software project is initiated by the client’s need. In the beginning, these needs are on the minds
of various people in the client’s organization. The analyst has to identify the requirements by
talking to the people and understanding to their needs. It goes without saying that an accurate
and through understanding of software requirement are essentials to the success of software
development effort. All further development like system analysis. System design and coding will
depends on how accurate and well understood the requirements are poorly analyzed and
specified software will disappoint the user and will bring brief to the developer. No matter how
well designed and well appearances are often deceiving. Chances of misinterpretation are very
high, ambiguity is probable and communication gap between customer and developer is bound to
bring confusions. Requirements understanding begin with a clear and concise heading stating in
sentence the task to be performed. Then requirements are describe in a technical manner precise
statement.
2.1Feasibility study
All projects are feasible given unlimited resources and infinite time! Unfortunately, the
development of computer based system is more likely to be plagued by a scarcity of resources
and difficult delivery dates. It is both necessary and prudent to evaluate the feasibility of the
project at the earliest possible time. Months or years of effort, Money loss and untold
professional embarrassment can be averted I few better understand the project at its study time.
This type of study determines if an application can and should be developed. Once it has
been determining that, application is feasible. After that analyst can go ahead and prepares the
project specification, which finalizes project requirements. Feasibility studies are undertaken
within tight time constraints.
8
1. Technical Feasibility
2. Operational Feasibility
3. Economic Feasibility
4. Legal Feasibility
2.2 Technical Feasibility

As we know the technical feasibility is concerned with specifying equipment and software
that will successfully satisfy the user requirement. The technical needs of the system may vary
considerably, but might include:
 The facility to produce outputs of advertisements, shopping and mailing in a given time for
ease of use.
 Response time under certain condition is minimal.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distinct location.
In examining the technical feasibility, configuration of the system is given more importance
than the actual make of hardware. The configuration should give the complete picture about the
system’s requirements- how many workstations are required, how these units are interconnected
so that they could operate and communicate smoothly.
2.3 Operational Feasibility

Proposed projects are beneficial only if they can be turned into information system that will
meet the financial management requirements of the business/organization. This test of feasibility
asks if the system will work when it developed and installed. Are there major barriers to
implementation?
Some of the important questions that are useful to test the operational feasibility of a project are
given below:
9
 Is there sufficient support for the project from the implementation? From user? If the present
system is well liked and used to the extent that persons will not be able to see reasons for
change, there may be resistance.
 Are current business methods acceptable to the user? If they are not, user may welcome a
change that will bring about a more operational and useful system
 Have the user been involved in the planning and development of the Project? If they are
involved at the earliest stage of project development, the chances of resistance can be possibly
reduced.
 Will the proposed system cause harm? Will it produce poorer result in any case or area?
 Will the performance of staff member fall down after implementation? Issue that
 Appears to be quite minor at the early stage can grow into major problem after
Implementation.
2. 4 Economical Feasibility
Economic analysis is the most frequently used technique for evaluating the effectiveness of
the proposed system. More commonly known as cost/benefits analysis, the procedure is to
determine the benefits and savings that are expected from the purposed system and compared
with costs.
If benefits outweigh cost, a decision is taken to design and implement the system. Otherwise,
further justification or alternative of the proposed system will have to be made if it has a chance
of being approved. This is an ongoing effort that improves in accuracy at each phase of the
system life cycle. The analysis part also clears the doubt of economic problems which could be
possible in developing the system. As already mentioned that the company has to just pay the
developed software cost and not other investment is needed at the time of implementation of the
new system as the preliminary requirements already exist in the company.
2.5 Legal Feasibility

In the legal feasibility is necessary to check that the software we are going to develop is legally
correct which means that the ideas which we have taken for the proposed system will be legally
implemented or not so , it is also an important step in feasibility study.
1
0
1
1
CHAPTER 3
SOFTWARE REQUIREMENT SPECIFICATIONS
System and their relationships within and outside of the system. Here the key question is- what
all problems exist in the present system? What must be done to solve the problem? Analysis
begins when a user or manager begins a study of the System Analysis is a detailed study of the
various operations performed by a program using existing system.
During analysis, data collected on the various files, decision points and
transactions handled by the present system. The success of the system depends largely on how
clearly the problem is defined, thoroughly investigated and properly carried out through the
choice of solution. A good analysis model should provide not only the mechanisms of problem
understanding but also the frame work of the solution. Thus it should be studied thoroughly by
collecting data about the system. Then the proposed system should be analyzed thoroughly in
accordance with the needs
1.3 PURPOSE
The purpose of this application is to keep the record of text in the editor properly and the
different text which is issues to the activities. The availability of content can be easily
managed and tex thaving different system of library .
1.4 SCOPE
The scope of this project is to enhance the facilities available in the current notepad
system and different security measures would be applicable in the future for the student point
of view and management point of view. The application would be fruitful.
The different areas where we can use this application are:

1
2
3.1 OVERVIEW A SYSTEM

Collection of component, which are interconnected, and work together to realize some objective,
from a system. There are three components in every system, namely input, processing and output
Input Processing Output
3.1.1 GENERAL DESCRYPTION OF SYSTEM

The Systems development life cycle (SDLC), or Software development process in systems
engineering, information systems and software engineering, is a process of creating or altering
information systems, and the models and methodologies that people use to develop these
systems. In software engineering, the SDLC concept underpins many kinds of software
development methodologies. These methodologies form the framework for planning and
controlling the creation of an information system the software development process.
Broadly, following are the different activities to be considered while defining the system
development life cycle for the said project:
 Problem Definition
 System Analysis
 Study of existing system
 Drawback of the existing system
 Proposed system
10
 System Requirement study

 Data flow analysis
 Feasibility study
 System design
 Input Design (Database & Forms)
 Updating
 Report design
 Administration
 Testing
 Implementation
 Maintenance
3.1.2 PRODUCT DESCRIPRION

Systems analysis is the study of sets of interacting entities, including computer systems analysis.
This field is closely related to requirements analysis or operations research. It is also "an explicit
formal inquiry carried out to help someone (referred to as the decision maker) identify a better
course of action and make a better decision than he might otherwise have made.
System development can generally be thought of having two major components: systems
analysis and systems design. In System Analysis more emphasis is given to understanding the
details of an existing system or a proposed one and then deciding whether the proposed system is
desirable or not and whether the existing system needs improvements. Thus, system analysis is
the process of investigating a system, identifying problems, and using the information to
recommend improvements to the system.
11
3.1.3 USER CHARACTERISTICS
Systems design is the process of defining the architecture, components, modules, interfaces, and
data for a system to satisfy specified requirements. One could see it as the application of systems
theory to product development. There is some overlap with the disciplines of systems analysis,
systems architecture and systems engineering. If the broader topic of product development
"blends the perspective of marketing, design, and manufacturing into a single approach to
product development," then design is the act of taking the marketing information and creating the
design of the product to be manufactured. Systems design is therefore the process of defining and
developing systems to satisfy specified requirements of the user. Until the 1990s systems design
had a crucial and respected role in the data processing industry. In the 1990s standardization of
hardware and software resulted in the ability to build modular systems. The increasing
importance of software running on generic platforms has enhanced the discipline of software
engineering.
Object-oriented analysis and design methods are becoming the most widely used methods for
computer systems design. The UML has become the standard language in object-oriented
analysis and design. It is widely used for modeling software systems and is increasingly used for
high designing non-software systems and organizations
3.2 Reports Generated By the System
1) List of Total Passenger detail

2) A lot Car different type
3) Tour and Trip
4) Travelling pass
5) Fare per K/m
12
CHAPTER 6
SYSTEM SPECIFICATION
The purpose of system requirement specification is to produce the specification

analysis of the task and also to establish complete information about the requirement,
behavior and other constraints such as functional performance and so on. The goal of
system requirement specification is to completely specify the technical requirements for
the product in a concise and unambiguous manner.
6.1 HARDWARE REQUIREMENTS
 System : Pentium IV 2.4 GHz.

 Hard Disk : 40 GB.
 Floppy Drive : 1.44 Mb.
 Monitor : 15 VGA Colour.
 Mouse : Logitech.
 Ram : 512 Mb.
6.2 SOFTWARE REQUIREMENTS
 Operating system : Windows XP/7.

 Coding Language : ASPNS2, C#NS2
 Tool : Visual Studio 2010
 Database : SQL SERVER 2008
13
CHAPTER 9
OBJECT ORIENTED DESIGN
ARCHITECTURE:
DATA FLOW DIAGRAM:
1. The DFD is also called as bubble chart. It is a simple graphical formalism that can be
used to represent a system in terms of input data to the system, various processing carried
out on this data, and the output data is generated by this system.
ER DIAGRAM
Logo Fu
ut Oil
Vehic el change
le
Detai
Booki
Driver Admin ngs
Detail Section n
luxury Vehic
Edi le
Vehicle
User Section Car Trip
Managem
Map
ent
Booking
excuti detail
ve Econo Stat
my Starting us
Ho point
me Ending
point
Hel
View p
Help
About
Company Welcome
home
14
Context Le ve l Diagram
Admin User
Vehicle
Managem
ent
Vehicle Travelli
ng
15
First Level Data Flow Diagram
Home
Vehicle Tour & Trip
Passenger
VMS
Fare
Per K/M
Driver
16
Vehicle Management System Connected My SQL Server online:-
Booking Tables:
Column Name Data Type Allow Null
Boooking Id (primary Key) varchar(15) Not Null
User Id(Primary Key) archar(20) Not Null
b_name varchar(20) Allow Null
u_Name varchar(20) Allow Null
v_name varchar(50) Allow Null
s_date varchar(50) Allow Null
e_date varchar(50) Allow Null
Km varchar(50) Allow Null
Status varchar(50) Allow Null
No of seat varchar(50) AllowNull
Node varchar(50) AllowNull
17
Admin User

id (primary Key) nchar(15) Not Null
u_name varchar(20) Allow Null
u_pass varchar(20) Allow Null
Login Nchar(20) Allow Null
Logout Nchar(20) Allow Null
Driver Details

Name varchar(20) Allow Null
Address varchar(40) Allow Null
Image varchar(50) Allow Null
City varchar(20) Allow Null
lic_no Varchar(30) Not Null
Experience Int[4] Allow Null
18
Fuel Detail:

F_ id (primary Key) nchar(15) Not Null
v_Name varchar(20) Allow Null
d_name varchar(40) Allow Null
Date number(20) Allow Null
F_type varchar(20) Allow Null
Qty varchar(30) Not Null
Note varchar(30) Allow Null
Oil Details:-

d_name varchar(40) Allow Null
o_type varchar(20) Allow Null
Odometer varchar(30) Not Null
19
Repair Details:-

g_name varchar(40) Allow Null
g_name varchar(20) Allow Null
o_type varchar(20) Allow Null
Oodometer varchar(30) Not Null
User Details:-

Name varchar(20) Allow Null
Pass varchar(40) Allow Null
add1 varchar(20) Allow Null
City varchar(20) Allow Null
State varchar(30) Allow Null
Mobile varchar(30) Allow Null
Email varchar(30) Allow Null
20
Vmast Details:-

v_ name varchar(20) Allow Null
v_no number(20) Allow Null
Make varchar(20) Allow Null
fuel_type varchar(20) Allow Null
Kmr double(30) Allow Null
Avg number(30) Allow Null
Cost number(30) Allow Null
Image varchar(30) Allow Null
Insurer varchar(30) Allow Null
Company varchar(30) Allow Null
exp_date number(20) Allow Null
Driver varchar(30) Allow Null
20
3.3 Choice of Tools and Technology
Introduction:-
The Vehicle Management System ES bundle service-enables SAP Vehicle Management for
Automotive, which is run by automotive importers and distribution centers. Using the services in this ES
bundle, importers and distribution centers can provide a composite application for their dealers to enable
them to search for available vehicles and order vehicles that match a customer's specifications.
From Dealer Stock to Custom Orders:-
Because of many interrelated factors, today's automotive markets face increasing competition
and slowing demand. Chiefly, the Internet has made customers far more astute by greatly
increasing market transparency. This transparency has armed customers with the means to seek
out dealers that can sell them the makes and models of vehicles of their choice with a wide array
of personalized specifications, at prices they have negotiated. Given this market climate, dealers
and manufacturers alike know that without the ability to respond rapidly to customer
requirements, the odds of success will remain stacked against them. The made-to-stock model by
which they once operated is no longer satisfactory. Instead, to generate and maintain competitive
advantage, businesses have adopted sophisticated order-to-delivery models and are now taking
steps to streamline them such that the time from order to delivery is greatly expedited.
In short, sales representatives at dealerships must be able to search for and locate vehicles whose
configurations meet the demands of inquiring customers, at will. If the desired vehicle has not
yet been manufactured, the dealer must be able to create an order for its manufacture and
delivery in a manner that both manufacturers and distributors can accommodate, as well.
Whatthe Vehicle Management System ES Bundle Does
Figure 1 shows the parties involved in this interaction. The OEM manufactures the vehicles, the
importer or distribution center orders vehicles from the OEM, and dealers then sell the vehicles
to the public. The Vehicle Management System ES bundle service- enables the interaction
between the dealers and SAP Vehicle Management for Automotive, which importers and
distribution centers run.
21
Deploying the services in this ES bundle, dealers using a composite applicat ion or dealer portal
can:
 Create and modify vehicle configurations in SAP Vehicle Management for Automotive
 Find and read information about existing vehicles in SAP Vehicle Management for Automotive
 Vehicles can be located and accessed using configuration dataand other elements such as
customer data, reference numbers, and vehicle batch IDs
 Create, modify, find, and read sales orders for vehicles in SAP Vehicle Management for
Automotive
 Generate detailed estimates for specific vehicleconfigurations
The VMS ES bundle leverages enterprise SOA by service-enabling SAP Vehicle Management for
Automotive.
Audience
Importers and distribution centers that want to extend the functionality of SAP Vehicle
Management for Automotive to their dealers will find the Vehicle Management System ES
bundle especially helpful.
The roles in these industries that can use this bundle include:
 System administrators
 Sales and importer representatives
 Dealers
How to Use This ES Bundle

Until recently, the model upon which the automotive industry based most of its production and
stock methods was "make-to-stock." Each year manufacturers used past sales patterns to
determine production for the immediate future. They produced a given number of vehicles
according to a given set of configurations and then shipped those vehicles to market, where they
were kept in stock as available for purchase.
Within this context, SAP developed SAP Vehicle Management for Automotive. SAP Vehicle
Management for Automotive provides OEMs, importers and distributors with a single,
centralized tool for procuring, configuring, managing, selling and tracking vehicles in either the
make-to-stock model or in some cases a make-to-order scenario. In this latter case, make-to-
order primarily has allowed customers purchasing high-end vehicles to configure the vehicle to
their particular tastes.
22
Today, however, the automotive industry is going through a transition that reflects greater
demand by all customers--not just those purchasing high-end vehicles--to order vehicles
configured to meet their particular needs. In response, the automotive industry is seeking ways to
efficiently and cost effectively meet customer expectations.
Underlying successful implementation of this newer model is the ability to reduce the order-to-
delivery time by providing a smooth and seamless process for the search and/or order of a
vehicle configured to the customer's needs.
The Vehicle Management System ES bundle extends the functionality of SAP Vehicle
Management for Automotive to the associated dealers of vehicle importers and distributors. This
means that through a composite application or portal based on these services, a dealer's sales
representative is able to search for a vehicle matching the customer's desired configuration or, if
necessary, initiate the process to order a matching vehicle from an OEM.
For example, an importer in the US acts as a distribution point for vehicles manufactured by
Toyota. This importer will use SAP Vehicle Management for Automotive to manage, configur e,
order, and sell vehicles. The dealer portal provided by the importer to its associated dealers will
allow dealers to access SAP Vehicle Management for Automotive. The enterprise services
contained in this bundle will enable dealers to search for vehicles in stock or on order from
Toyota as well as create sales orders for those vehicles. If no vehicle matching the customer's
configuration is in stock or on order, the dealer can submit a sales order to SAP Vehicle
Management for Automotive, which in turn triggers the importer to place a sales order with
Toyota indicating the specifications of the vehicle in question.
This section will explore a series of use cases for the Vehicle Management System ES bundle.
Each scenario will show how different outcomes can be achieved by using the enterprise services
in different combinations. While these examples illustrate a few of the ways that this ES bundle
could be used, the intention is to show the flexibility and reusability of these business objects and
enterprise service operations so that you will have a clearer understanding of how to best deploy
them in your own environment. This wiki is also a space for you to share knowledge and
collaborate with others who are implementing the Vehicle Management System ES bundle.
Use Case 1: Searching for and purchasing an existing vehicle
In this use case, a customer has entered a car dealership with the intent to purchase a new car.
Before arriving, however, she has researched the various possible configurations that are
available for the make and model she is interested in, including body color, upholstery type and
color, audio, tire rims, and so forth, and made a definite decision about what she wants. In this
scenario the customer will test drive a similar vehicle, search for the availability of a vehicle
matching a particular configuration, read through a search list of vehicles, negotiate a price, and
the sales representative will create a sales order.
23
Finding a Vehiclethat Matches a Specified Configuration
After the customer has test driven the make and model of her choice, she wants to know whether
she can buy her customized version of it. To determine if such a vehicle is available, the sales
representative can enter all of the options she has chosen into the dealer portal UI. This gives the
dealer access to the importer's or distributor's database as well as visibility to backend systems.
The dealer can then select the search option and enter the search criteria for the vehicle. When
the search is initiated the application invokes the Find Automotive Vehicle Basic Data by
Elements service operation, which uses the Automotive Vehicle business object. This service
will search within SAP Vehicle Management for Automotive by vehicle configuration and
related elements and return a list of cars that match the specified search terms with each vehicle's
ID number.
Readingthe Details of a Vehicle
A list appears on the dealer's UI from which the customer can select and view the details of a
vehicle. Clicking on the link to a vehicle invokes the Read Automotive Vehicle enterprise
service, which presents the details of that particular car. The application uses the vehicle ID as
the input for the read service. The business object used is Automotive Vehicle.
Generatinga List Price for a Vehicle
The customer is satisfied with the car and its projected delivery date, but she needs to know how
much it will cost as configured. To find out the list price, the sales representative selects an
option that invokes the Check Sales Order Creation service operation, which uses the Sales
Order business object.
Creatinga Sales Order for a Vehicle
After negotiating a price with the customer, the sales representative can create a sales order for
the vehicle. To complete the sale, the dealer adds the customer's information such as name,
contact information, payment type, and so on, and submits the order to the importer or distributor
by selecting an option in the UI that invokes the Create Sales Order service operation. This
enterprise service is actually a standard SAP Sales and Distribution service and is run with the
data returned from the read service, such as the batch number (ID), configuration data,
manufacturing plant, equipment number, usage code, initial registration date, counter reading,
price, current location, production date and time, and planned date and delivery and time.
Essentially, the composite application forwards the information from the Read Automotive
Vehicle service to the Create Sales Order service seamlessly.
Step 1: A sales representative searches for a vehicle

Find Automotive Vehicle Basic Data
that matches
by Elements
a customer's configuration specifications
Step 2: The sales rep selects a matching vehicle from
the search results, Read Automotive Vehicle
which passes the vehicle's batch ID to the read service
24
Step 3: The customer is interested in purchasing the

vehicle but first
wants to know its price. The sales representative Check Sales Order Creation
generates a list price
based on the specified configuration
Step 4: The customer wishes to purchase the vehicle,
so the
Create Sales Order
sales representative creates the sales order in
SAP Vehicle Management for Automotive
Use Case 2: Ordering a New Vehicle with a Custom Configuration
In use case 1, the dealer was able to help the customer find and order a vehicle that met her
specifications. Frequently, though, a new vehicle may need to be made to fill the customer's
order.
The customer knows what she wants, and the sales rep at the dealership enters all of the options
she has chosen into the dealer portal UI, which invokes the Find Automotive Vehicle Basic
Data by Elements service operation, which uses the Automotive Vehicle business object. This
service will search SAP Vehicle Management for Automotive by vehicle configuration and
related elements and return a list of cars that match the specified search terms with each vehicle's
ID number.
Unlike in the previous use case, no available vehicles match the search criteria. As a result, the
dealer will create a sales order that includes all of the configuration details. The customer
naturally wants to know how much that vehicle will cost as configured before committing to buy
it, so the sales rep invokes Check Sales Order Creation, which checks all the data in the sales
order, including a price.
The customer, experiencing a bit of sticker shock, attempts to negotiate the price downward. The
dealer makes some adjustments, but also tells the customer that removing the most costly options
will also bring down the price. The dealer changes the order accordingly and invokes Check
Sales Order Creation again. The price is now acceptable to the customer, so the dealer invokes
Create Sales Order, which sends the sales order to SAP Vehicle Management for Automotive.
Note that the car itself has not been configured; the importer will handle this step.
The Importer Receives the Sales Order:-
The importer receives the sales order and uses the configuration details to order the car in SAP
Vehicle Management for Automotive.
The Customer Changes Her Mind and the Sales Rep Updates the Configuration
The customer goes away from the dealership and thinks about the options she turned down. She
puts the additional cost in perspective versus the monthly payment amount and decides to call
the sales rep back to request the reinstatement of these options. The dealer then returns to the
25
portal and invokes the Find Sales Order Basic Data by Elements enterprise service operation.
He selects the customer's sales order from a list, which invokes Read Sales Order. The sales rep
can see that the importer has already created the vehicle (the batch ID is now listed on the sales
order), so he clicks on the batch ID which invokes the Find Automotive Vehicle by Batch ID
enterprise service operation followed by the Read Automotive Vehicle enterprise service
operation. The sales representative sees that there is still time to change the configuration, so he
invokes the Update Sales Order enterprise service operation to change the sales order to reflect
the new configuration. This will in turn update the vehicle in the backend system.
Step 1: A sales representative searches for a vehicle that Find Automotive Vehicle by
matches a customer's configuration specifications Property Valuation and Elements
(no enterprise service operation is
Step 2: The search produces no matching results
invoked during this step)
Step 3: The customer explains the options she wants and
the sales rep enters them.
Check Sales Order Creation
The sales rep simulates a sales order to get a price.
The sales rep modifies the order and runs the service again
Step 4: The customer wishes to purchase the vehicle, so the
sales representative creates
Create Sales Order
the sales order in SAP Vehicle Management for
Automotive
Step 5: The importer receives the sales order and creates a (no enterprise service operation is
vehicle in SAP Vehicle Management for Automotive invoked during this step)
Step 6 The customer calls back and the sales rep looks up Find Sales Order Basic Data by
the sales order Elements
Step 7: The sales rep reviews the sales order Read Sales Order
Find Automotive Vehicle by Batch
Step 8: The sales rep sees that a vehicle has been created
ID
for this order and looks it up
Read Automotive Vehicle
Step 9: The sales rep makes the changes the customer
Update Sales Order
requested
Use Case 3: Customer Calls to Check on Order:-
The customer is now so excited about the new car that she calls the sales rep every few days to
find out about the progress of the order. The sales rep uses the Find Sales Order Basic Data by
Elements enterprise service to find the sales order and Read Sales Order to see the details.
Clicking on the Batch ID for the vehicle invokes the Read Automotive Vehicle enterprise
service operation and the dealer can update the customer with information about how her new
car is progressing and the latest information about when she can expect delivery.
Step 1: A sales representative searches for the customer's Find Sales Order Basic Data by
sales order Elements
Step 2: The sales rep drills down into the batch ID Find Automotive Vehicle by Batch
that identifies the car, ID
26
which invokes a service to search for the car by its ID

Step 3: The sales rep reviews the details about the new car
and
lets the customer know any updated information about the Read Automotive Vehicle
progress
of her order
Future Directions
Future directions for the Vehicle Management System ES bundle may include additional service-
enablement of SAP Vehicle Management for Automotive and Warranty Management. In
addition, SAP's dealer portal will be service-enabled using the enterprise services in this ES
bundle (at this time, the dealer portal is integrated using BAPIs). Support for additional
accounting documents such as purchase orders, delivery documents, and goods receipts may also
be included in a future release.
27
CHAP TER 4
Testing and Implementation
Objective of Testing
Software testing is an investigation conducted to provide stakeholders with information about

the quality of the product or service under test. Software testing can also provide an objective,
independent view of the software to allow the business to appreciate and understand the risks of
software implementation. Test techniques include, but are not limited to, the process of executing
a program or application with the intent of finding software bugs (errors or other defects).
Software testing can be stated as the process of validating and verifying that a software
program/application/product:
1. meets the requirements that guided its design and development;

2. works as expected; and
3. can be implemented with the same characteristics.
Software testing, depending on the testing method employed, can be implemented at any time in
the development process. However, most of the test effort traditionally occurs after the
requirements have been defined and the coding process has been completed having been shown
that fixing a bug is less expensive when found earlier in the development process. Although in
the Agile approaches most of the test effort is, conversely, on-going. As such, the methodology
of the test is governed by the software development methodology adopted.
Different software development models will focus the test effort at different points in the
development process. Newer development models, such as Agile, often employ test driven
development and place an increased portion of the testing in the hands of the developer, before it
reaches a formal team of testers. In a more traditional model, most of the test execution occurs
after the requirements have been defined and the coding process has been completed. Testing can
28
never completely identify all the defects within software. Instead, it furnishes a criticism or
comparison that compares the state and behavior of the product against oracles—principles or
mechanisms by which someone might recognize a problem. These oracles may include (but are
not limited to) specifications, contracts,[3] comparable products, past versions of the same
product, inferences about intended or expected purpose, user or customer expectations, relevant
standards, applicable laws, or other criteria.
Every software product has a target audience. For example, the audience for video game
software is completely different from banking software. Therefore, when an organization
develops or otherwise invests in a software product, it can assess whether the software product
will be acceptable to its end users, its target audience, its purchasers, and other stakeholders.
Software testing is the process of attempting to make this assessment.
4.2Types of Testing
4.2.1 Black Box Testing
Black-box testing treats the software as a "black box"—without any knowledge of internal
implementation. Black-box testing methods include: equivalence partitioning, boundary value
analysis, all-pairs testing, fuzz testing, model-based testing, exploratory testing and specification-
based testing.
 Specification-based testing: Specification-based testing aims to test the

functionality of software according to the applicable requirements. Thus, the
tester inputs data into, and only sees the output from, the test object. This level of
testing usually requires thorough test cases to be provided to the tester, who then
can simply verify that for a given input, the output value (or behavior), either "is"
or "is not" the same as the expected value specified in the test case.
Specification-based testing is necessary, but it is insufficient to guard against certain
risks.
 Advantages and disadvantages: The black-box tester has no "bonds" with the
code, and a tester's perception is very simple: a code must have bugs. Using the
principle, "Ask and you shall receive," black-box testers find bugs where
29
programmers do not. On the other hand, black-box testing has been said to be
"like a walk in a dark labyrinth without a flashlight," because the tester doesn't
know how the software being tested was actually constructed. As a result, there
are situations when (1) a tester writes many test cases to check something that
could have been tested by only one test case, and/or (2) some parts of the back-
end are not tested at all.
Therefore, black-box testing has the advantage of "an unaffiliated opinion", on the one hand, and
the disadvantage of "blind exploring", on the other
4.2.2 White Box Testing
White-box testing is when the tester has access to the internal data structures and algorithms
including the code that implements these.
Types of white-box testing

The following types of white-box testing exist:
 API testing (application programming interface) - testing of the application using

public and private APIs
 Code coverage - creating tests to satisfy some criteria of code coverage (e.g., the
test designer can create tests to cause all statements in the program to be executed
at least once)
 Fault injection methods - improving the coverage of a test by introducing faults to
test code paths
 Mutation testing methods
 Static testing - All types
Test coverage
White-box testing methods can also be used to evaluate the completeness of a test suite
that was created with black-box testing methods. This allows the software team to
examine parts of a system that are rarely tested and ensures that the most important
function points have been tested.[21]
30
Two common forms of code coverage are:
 Function coverage, which reports on functions executed

 Statement coverage, which reports on the number of lines executed to complete
the test
They both return a code coverage metric, measured as a percentage.
4.2.3 Functional Testing
Functional testing refers to activities that verify a specific action or function of the code. These
are usually found in the code requirements documentation, although some development
methodologies work from use cases or user stories. Functional tests tend to answer the question
of "can the user do this" or "does this particular feature work."
Non-functional testing refers to aspects of the software that may not be related to a specific
function or user action, such as scalability or other performance, behavior under certain
constraints, or security. Testing will determine the flake point, the point at which extremes of
scalability or performance leads to unstable execution. Non-functional requirements tend to be
those that reflect the quality of the product, particularly in the context of the suitability
perspective of its users.
4.2.4 System Testing
System testing of software or hardware is testing conducted on a complete, integrated system to

evaluate the system's compliance with its specified requirements. System testing falls within the
scope of black box testing, and as such, should require no knowledge of the inner design of the
code or logic.
As a rule, system testing takes, as its input, all of the "integrated" software components that have
successfully passed integration testing and also the software system itself integrated with any
applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies
between the software units that are integrated together (called assemblages) or between any of
31
the assemblages and the hardware. System testing is a more limited type of testing; it seeks to
detect defects both within the "inter-assemblages" and also within the system as a whole.
4.3 Various level Of Testing

Before implementation the system is tested at two levels:
Level 1
Level 2
4.3.1 Level 1 Testing (Alpha Testing)

Alpha testing is simulated or actual operational testing by potential users/customers or an
independent test team at the developers' site. Alpha testing is often employed for off-the-shelf
software as a form of internal acceptance testing, before the software goes to beta testing.
4.3.2 Level 2 Testing (Beta testing)

Beta testing comes after alpha testing and can be considered a form of external user acceptance
testing. Versions of the software, known as beta versions, are released to a limited audience
outside of the programming team. The software is released to groups of people so that further
testing can ensure the product has few faults or bugs. Sometimes, beta versions are made
available to the open public to increase the feedback field to a maximal number of future users.
4.3.3 Recovery and Security
A forced system failure is induced to test a backup recovery procedure for file integrity.
Inaccurate data are entered to see how the system responds in terms of error detection and
protection. Related to file integrity is a test to demonstrate that data and programs are secure
from unauthorized access.
4.3.4 Usability Documentation and Procedure:
The usability test verifies the user-friendly nature of the system. This relates to normal operating
and error-handling procedures.
32
4.4Quality Assurance
Though controversial, software testing is a part of the software quality assurance (SQA) process.
In SQA, software process specialists and auditors are concerned for the software development
process rather than just the artifacts such as documentation, code and systems. They examine and
change the software engineering process itself to reduce the number of faults that end up in the
delivered software: the so-called defect rate.
What constitutes an "acceptable defect rate" depends on the nature of the software; A flight
simulator video game would have much higher defect tolerance than software for an actual
airplane.
Although there are close links with SQA, testing departments often exist independently, and
there may be no SQA function in some companies.
Software testing is a task intended to detect defects in software by contrasting a computer

program's expected results with its actual results for a given set of inputs. By contrast, QA
(quality assurance) is the implementation of policies and procedures intended to prevent defects
from occurring in the first place.
4.5System Implementation
During the implementation stage the system in physically created. Necessary programs are
coded, debugged and documented. A new hardware is selected, ordered and installed.
4.6System Specification
Every computer system consists of three major elements.
1. The Hardware
2. Application software such as visual studio
3. Operating system
For successful operation of the package following must be kept in mind:

33
Too many packages should not be used, as very few system may have all those packages
installed due to memory problem. Thus, the compatibility of the system development will get
reduced.
34
4.7Installation
The application installation script have to be generated from the current server where the
application source code saved and installed in the main server from where the application is to be
run. This was done using a special code, which generates all SQL-Statements to insert preliminary
data (like menu entries, code in code directories etc) at server and the operational modules of the
application made available to the end user successfully.
4.8Implementation
The system is still under construction few report are yet to me made after that this system will be
implanted at client side. Users will be given a training to use the package and special work shop is
conducted by the courier for the purpose and according to their feedback the change implanted in
the software.
35
Snapshort:-
Using Technology JSP source code (java server pages) in advanced java:-
Index.jsp
<html>
<head>
<title>Vehicle Mgmt System</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859- 1">
<link href="include/admin.css" rel="stylesheet" type="text/css">
<link href="include/menu.css" rel="stylesheet" type="text/css">
<link href="include/main.css" rel="stylesheet" type="text/css">
<link rel="STYLESHEET" type="text/css" href="include/calendar.css">
<script language="JavaScript" type="text/javascript" src="include/simplecalendar.js"></script>
<style type="text/css">

</style>
</head>
<body>
<div class="">
<table width="1000" border="0" align="center" cellpadding="0" cellspacing="1"
class="graybox">
<tr>
<td colspan="2">
<%@ include file="include/header.jsp" %>
</td>
</tr>
36
<tr>
37
<td colspan="2" bgcolor="#D22929" style="height:30px;"><span

class="style1">
<marquee truespeed="truespeed">
<span class="style2">Vehicle Management System </span>
</marquee></span></td>
</tr>
<tr>
<td width="20%" valign="top" bgcolor="#EED9A8" class="navArea"><p> </p>
<%@ include file="include/umenu.jsp" %>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
</td>
<td width="80%" valign="top" class="contentArea"><table width="100%" border="0"

cellspacing="0" cellpadding="20">
<tr>
<td>
<%
String conPage=(String)session.getAttribute("content_page"); System.out.print("conPage ==>
"+conPage);
if(conPage!=null){
%>
<jsp:include page="<%=conPage%>"/>
<%
}
else {
%>
<jsp:include page="ucontent.jsp"/>
<%
}
%></td>
</tr>
</table></td>
</tr>
</table></div>
<p> </p>
<div class="white">
38
<p align="center">Copyright 2002 - 2009 - <b>Vehicle- Management.com</b> - All Rights

Reserved <br>
<br>
<strong>Home</strong><strong> |
</strong><strong>Profile</strong><strong> | </strong><strong>Site Map</strong><strong> |
</strong><strong>Services</strong><strong> |
</strong><strong>Terms &
Conditions</strong><strong> |
</strong><strong>Disclaimer</strong><strong>|
</strong><strong>Partners</strong><strong> | </strong><strong>Contact us</strong></p>
</body>
</html>
Admin.Jsp:-
<%@ page contentType="text/html; charset=iso-8859-1" language="java" import="java.sql.*"

errorPage="" %>
<%
String op=""; Connection
c=null;
String uname = request.getParameter("Username"); String upass =
request.getParameter("Password"); if(uname != null && upass !=
null) {
try{
Class.forName("com.mysql.jdbc.Driver"); c =
DriverManager.getConnection("jdbc:mysql://localhost:3307/vdb","root"," abdul");
String sql = "select uname, upass from admin_user where uname='"+uname+"' and upass
= '"+upass+"'";
Statement st = c.createStatement();
ResultSet rs= st.executeQuery(sql);
if(rs.next()){
op="YES";
session.setAttribute("content_page","content.jsp");
response.sendRedirect("template.jsp");
}else {
op="NO";
}
39
c.close();
}catch(Exception e){ System.out.println(e);
}//catch
}//if
%>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859- 1" />
<title>Vehicle Management System</title>
<style>
html,body{
height: 100%;
text-align: center;
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif; font-size: small;
color:#FA0;
}
.style1 {
#D22929;
text-decoration:underline;
}
.style3 {
#D22929;
text-decoration:blink;
}
.myBox {
margin: 0.5in auto; color:
#fff; width: 600px;
padding: 20px;
text-align: left;
background-color: #EED9A8;
40
border: 3px solid #fff;
/* Do rounding (native in Firefox and Safari) */

-webkit-border-radius: 20px;
-moz-border-radius: 20px;
}
.style5 {color: #D22929}
.style6 {color: #D22929; font-weight: bold; }
</style>
<script type="text/JavaScript">

</script>
</head>
50
<body>
<div class="myBox">
<table width="" border="0" align="center" style="
background:#EED9A8">
<tr>
<th width="45" scope="col"> </th>
</tr>
<tr>
<th colspan="3" bgcolor="#D22929" scope="col"><div align="center"><span
class="style3"><span class="style4"><marquee>Vehicle Management
System</marquee></span></span> </div></th>
</tr>
<tr>
<td> </td>
<td><form id="form1" name="form1" method="post" action="">
<table width="100%" border="0" align="center">
<tr>
<th colspan="3" scope="col">
<%
if(op.equals("NO")){
%>
<h3><font color="#000000">Login Failed. Re-Login Again</font></h3>
<%
}
%>
</th>
</tr>
<tr>
<td width="46%" rowspan="8"><img src="images/car.jpg" width="213"
height="193" /></td>
<td colspan="2"> </td>
</tr>
<tr>
<td colspan="2"><div align="center"><span class="style1">Admin Login Panel
</span> </div></td>
</tr>
<tr>
</tr>
<tr>
<td width="22%"><span class="style6">User Name :</span>
51
<span class="style5">
<label></label>
</span></td>
<td width="32%"><label>
<input name="Username" type="text" id="Username" />
</label></td>
</tr>
<tr>
<td><span class="style6"> Password :
<label> </label>
</span>
<span class="style5">
<label></label>
</span></td>
<td><label>
<input name="Password" type="password" id="Password" />
</label></td>
</tr>
<tr>
</tr>
<tr>
<td colspan="2">
<div align="center">
<input name="Submit2" type="submit" class="redButton"
onclick="MM_validateForm('Username','','R','Password','','R');return
document.MM_returnValue" value=" Log In "/>
</div></td>
</tr>
<tr>
<td colspan="2"><label>
</label></td>
</tr>
<tr>
</tr>
</table>
</form> </td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
</tr>
52
</table>
</div>
</body>
</html>
Register.jsp:-

</script>
<h3>If you want to Book any of the Vehicle then please register ypur self.<br/>
After Registration You can Login-In and Book any of the Vehicle From this site.<br/>
If You already Register with us then please <a href="do?MOD=BOK&ACT=Login">Login
In</a> to Book the vehicle for your Trips.</h3>
<form id="form1" name="form1" method="post"
action="do?MOD=BOK&ACT=doReg">
<table width="70%" border="0" align="center" cellpadding="5" cellspacing="2">
<tr>
<th colspan="5" scope="col"><div class="header">User Registration</div></th>
</tr>
<tr>
<%= "Hello" %>
<td width="20%"> </td>
</tr>
<tr>
<td> </td>
<td>Name</td>
<td>:</td>
<td><label>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Password</td>
<td>:</td>
<td><input name="Password" type="password" id="Password" /></td>
<td> </td>
</tr>
54
<tr>
<td> </td>
<td>Address</td>
<td>:</td>
<td><textarea name="Address" id="Address"></textarea></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>City</td>
<td>:</td>
<td><input name="City" type="text" id="City" /></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>State</td>
<td>:</td>
<td><input name="State" type="text" id="State" /></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Mobile No. </td>
<td>:</td>
<td><input name="MobileNo" type="text" id="MobileNo" /></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>E-mail</td>
<td>:</td>
<td><input name="Email" type="text" id="Email" /></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td> </td>
<td><label>
<div align="right">
55
<input type="reset" name="Submit2" value="Reset" />

</div>
</label></td>
<td> </td>
<td><label>
<input name="Submit" type="submit"
onclick="MM_validateForm('Username','','R','Password','','R','City',''
,'R','State','','R','MobileNo','','R','Email','','RisEmail','Address', '','R');return
document.MM_returnValue" value="Register Now" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td colspan="5"><div class="header"> </div></td>
</tr>
</table>
</form>
Driver.jsp:-

</script>
<form id="form1" name="form1" method="post" action="do?MOD=MTN&ACT=AddDriver" >

<tr>
<th colspan="5" scope="col"><div class="header">
<div align="left">Add Driver Details </div>
</div></th>
</tr>
<tr>
</tr>
<tr>
<td> </td>
<td>Driver First Name </td>
<td>:</td>
<td><label>
<input name="FirstName" type="text" id="FirstName" size="30"
/>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Driver Last Name </td>
57
<td>:</td>
<td><label>
<input name="LastName" type="text" id="LastName" size="30" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Address</td>
<td>:</td>
<td><label>
<input name="Address" type="text" id="Address" size="40" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>City </td>
<td>:</td>
<td><label>
<input name="City" type="text" id="City" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>State. </td>
<td>:</td>
<td><label>
<input name="State" type="text" id="State" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>:</td>
<td><label>
<input name="MobileNo" type="text" id="MobileNo" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>License No. </td>
<td>:</td>
58
<td><label>
<input name="LicenseNo" type="text" id="LicenseNo" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Expiry Date </td>
<td>:</td>
<td><label>
<input type="text" name="doe" readonly="true"/>
<a href="javascript: void(0);" onMouseOver="if (timeoutId)
clearTimeout(timeoutId);window.status='Show Calendar';return true;" onMouseOut="if
(timeoutDelay) calendarTimeout();window.status='';"
onClick="g_Calendar.show(event,'form1.doe',true,'yyyy-mm-dd'); return false;"><img
src="include/calendar.gif" name="imgCalendar" width="34" height="21" border="0" alt=""
></a></label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Year of Experiacne </td>
<td>:</td>
<td><label>
<input type="text" name="Experiance" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Note</td>
<td>:</td>
<td><label>
<textarea name="Note" cols="30" rows="5" id="Note"></textarea>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
59
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td> </td>
<td><label>
<div align="right">
<input type="reset" name="Submit2" value="Reset" class="redButton"/>
</div>
</label></td>
<td> </td>
<td><label>
<input name="Submit" type="submit" class="redButton"
onclick="MM_validateForm('FirstName','','R','LastName','','R','Address
','','R','City','','R','State','','R','MobileNo','','R','LicenseNo',''
,'R','Experiance','','RisNum');returndocument.MM_returnValue" value="Add Driver" />
</label></td>
<td> </td>
</tr>
</table>
</form>
<hr width="600px" style="background:#D22929; border:#D22929 solid
2px;"/>
Fuel.jsp
<%@ page import="java.sql.*,java.util.*,net.vehicle.VehicleCommon"%>
<%
ArrayList al=VehicleCommon.getDrivers(); ArrayList
al1=VehicleCommon.getVehicles();
%>

</script>
<form id="form1" name="form1" method="post" action="do?MOD=MTN&ACT=AddFuel">

<tr>
<div align="left">Add Fuel Expences Details </div>
</div></th>
</tr>
<tr>
</tr>
<tr>
<td> </td>
<td>Vehicle Name </td>
61
<td>:</td>
<td><label>
<select name="VehicleName">
<%
for(int i=0;i<al1.size();i++){
%>
<option value="<%=(String)al1.get(i)%>"><%=(String)al1.get(i)%></option>
<% } %>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Driver Name </td>
<td>:</td>
<td><label>
<select name="DriverName">
<%
for(int i=0;i<al.size();i++){
%>
<option value="<%=(String)al.get(i)%>"><%=(String)al.get(i)%></option>
<% } %>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Fuel Date </td>
<td>:</td>
<td><label>
<input name="fdate" type="text" id="fdate" readonly="true"/>
<a href="javascript: void(0);" onmouseover="if (timeoutId)
clearTimeout(timeoutId);window.status='Show Calendar';return true;" onmouseout="if
onclick="g_Calendar.show(event,'form1.fdate',true,'yyyy-mm-dd'); return false;"><img
src="include/calendar.gif" alt="" name="imgCalendar" width="34" height="21" border="0"
id="imgCalendar"></a></label></td>
<td> </td>
</tr>
<tr>
<td> </td>
62
<td>Fuel Type </td>

<td>:</td>
<td><label>
<select name="ftype">
<optionvalue="Pertol"> Pertol </option>
<optionvalue="Diesel"> Diesel </option>
<optionvalue="Gas"> Gas </option>
<optionvalue="Hybrid"> Hybrid </option>
<optionvalue="Electricity"> Electricity </option>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Fuel Quantity</td>
<td>:</td>
<td><label>
<input name="Quantity" type="text" id="Quantity" size="10" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Total Cost . </td>
<td>:</td>
<td><label>
<input name="Cost" type="text" id="Cost" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Note</td>
<td>:</td>
<td><label>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
63
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td> </td>
<td><label>
<div align="right">
</div>
</label></td>
<td> </td>
<td><label>
onclick="MM_validateForm('VehicleName','','R','DriverName','','R','Qua
ntity','','R','Cost','','R');returndocument.MM_returnValue" value="Add Fuel Details" />
</label></td>
<td> </td>
</tr>
</table>
</form>
2px;"/>
Addvehicle.jsp:-

<%
ArrayList al=VehicleCommon.getDrivers();
%>

</script>
<form id="form1" name="form1" method="post" action="do?MOD=MTN&ACT=AddVehicle"

enctype="multipart/form-data">
<tr>
<div align="left">Add Vehicle Details </div>
</div></th>
</tr>
<tr>
65
</tr>
<tr>
<td> </td>
<td>:</td>
<td><label>
<input name="VehicleName" type="text" id="VehicleName" size="30" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Vehicle No. </td>
<td>:</td>
<td><label>
<input name="VehicleNo" type="text" id="VehicleNo" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Make</td>
<td>:</td>
<td><label>
<input name="Make" type="text" id="Make" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Fuel Type </td>
<td>:</td>
<td><label>
<select name="ftype">
<optionvalue="Pertol"> Pertol </option>
<optionvalue="Diesel"> Diesel </option>
<optionvalue="Gas"> Gas </option>
<optionvalue="Hybrid"> Hybrid </option>
<optionvalue="Electricity"> Electricity </option>
</select>
</label></td>
<td> </td>
</tr>
<tr>
66
<td> </td>
<td>Rs / K.m. </td>
<td>:</td>
<td><label>
<input name="Rs" type="text" id="Rs" size="10" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Average</td>
<td>:</td>
<td><label>
<input name="Average" type="text" id="Average" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Cost</td>
<td>:</td>
<td><label>
<input name="Cost" type="text" id="Cost" size="10" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Image</td>
<td>:</td>
<td><label>
<input name="Image" type="file" id="Image" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Vehicle Type </td>
<td>:</td>
<td><label>
<select name="vtype">
<option value="Luxury Cars"> Luxury Cars</option>
<option value="Executive Cars "> Executive Cars
</option>
<option value="MUVs & SUVs"> MUVs & SUVs</option>
<option value="Economy Cars"> Economy Cars</option>
67
<option value="Mini Vans & Large Coaches"> Mini Vans & Large

Coaches</option>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td colspan="5"><div class="header">Insurance Details</div></td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Insurer Name </td>
<td>:</td>
<td><label>
<input name="InsurerName" type="text" id="InsurerName" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Company Name </td>
<td>:</td>
<td><label>
<input name="CompanyName" type="text" id="CompanyName" size="30" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Date Of. Insurance </td>
<td>:</td>
68
<td><label>
<input name="doi" type="text" id="doi" readonly="true" />
onClick="g_Calendar.show(event,'form1.doi',true,'yyyy-mm-dd'); return false;"><img
></a></label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Date of Expiry </td>
<td>:</td>
<td><label>
<input type="text" name="doe" readonly="true" /><a href="javascript: void(0);"
onMouseOver="if (timeoutId) clearTimeout(timeoutId);window.status='Show Calendar';return
true;" onMouseOut="if (timeoutDelay) calendarTimeout();window.status='';"
onClick="g_Calendar.show(event,'form1.doe',true,'yyyy-mm-dd'); return false;"><img
></a>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>:</td>
<td><label>
<select name="dname" id="dname">
<%
%>
<option value="<%=(String)al.get(i)%>"><%=(String)al.get(i)%></option>
<% } %>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
69
<td> </td>
</tr>
<tr>
<td> </td>
<td><div align="right">
<input type="reset" name="Submit2" value="Reset" class="redButton" />
</div></td>
<td> </td>
<td><label>
onclick="MM_validateForm('VehicleName','','R','VehicleNo','','R','Make
','','R','Rs','','R','Average','','R','Cost','','R','InsurerName','','
R','CompanyName','','R');return document.MM_returnValue" value="Add Vehicle" />
</label></td>
<td> </td>
</tr>
</table>
</form>
2px;"/>
Book User.jsp:-
<%@ page contentType="text/html; charset=iso-8859-1" language="java" import="java.sql.*,
java.util.*,
net.vehicle.*" errorPage="" %>

<%
int id = Integer.parseInt((String)session.getAttribute("u_id")); ArrayList all =
VehicleCommon.viewBookingByID(id);
int size = all.size();
%>

</style>
70
<div class="header">View Your Booking Status</div>

<h3>View Your Previous Booking status Here.<br/>If you want to book a vehicle then please <a
href="do?MOD=BOK&ACT=View&v=lux">click here</a></h3>
<br/>
<table width="95%" align="center" style="border:#D22929 solid
2px;padding:10px;" border="0">
<tr>
<th bgcolor="#D22929" scope="col"><span class="style10">Vehicle Name
</span></th>
<th bgcolor="#D22929" scope="col"><span class="style10">Driver
Name </span></th>
<th bgcolor="#D22929" scope="col"><span class="style10">Start Date</span></th>
<th bgcolor="#D22929" scope="col"><span class="style10">End Date
</span></th>
<th bgcolor="#D22929" scope="col"><span class="style10">Kilometer</span></th>
<th bgcolor="#D22929" scope="col"><span
class="style10">Status  </span></th>
</tr>
<%
for(int i=0;i<size;i++){
ArrayList one=(ArrayList)all.get(i);
%>
<tr style="height:30px; padding:4px;">
<td><divalign="center"><%=(String)one.get(0)%></div></td>
<td><div align="center"><%=(String)one.get(4)%> Km.</div></td>
</tr>
<% } %>
</table>
Edit Vehicle:-
java.util.*,

<%
int vid = Integer.parseInt((String)session.getAttribute( "vid"));
71
//out.println("<h3>Vehicle ID :"+vid);
ArrayList all = VehicleCommon.viewVehiclesByID(vid); ArrayList
al=VehicleCommon.getDrivers();
int size = all.size();
for(int i=0;i<size;i++){
ArrayList one=(ArrayList)all.get(i);
%>

</script>
<div class="header">Vehicle Edit </div>

<h3>Following are the Vehicle Details.You can Edit the Details </h3>
<br/>
72
<form id="form1" name="form1" method="post" action="do?MOD=BOK&ACT=doBok">

<table width="90%" align="center" style="border:#D22929 solid
2px;padding:5px;" border="0" >
<tr>
<divalign="left">  <%=(String)one.get(1)%></div>
</div></th>
</tr>
<tr>
<td><strong>Number : </strong> <%=(String)one.get(2)%></td>
<td><strong>Rupees Per Kilometer :
</strong><%=(String)one.get(6)%></td>
<td width="21%" rowspan="9"><img src="<%=(String)one.get(8)%>" width="220"
height="120" /></td>
</tr>
<tr>
<td colspan="2"><strong>Make</strong> :
<%=(String)one.get(3)%></td>
</tr>
<tr>
<td width="36%"><strong>Fuel Type:</strong>
<%=(String)one.get(4)%></td>
<td width="43%"><strong>Cost :
</strong><%=one.get(7)%> Rs.</td>
</tr>
<tr>
<td colspan="2"><strong>Vehicle Type:
</strong><%=one.get(9)%></td>
</tr>
<tr>
<td><strong>Insurer :</strong> <%=one.get(10)%></td>
<td><strong>Company :</strong> <%=one.get(11)%></td>
</tr>
<tr>
<td colspan="2"><hr width="400px" align="left"
style="border:#990000 solid 2px;"/></td>
</tr>
<tr>
<td colspan="2"><div align="center"><a href="#"><strong>Edit Vehicle
Details</strong> </a></div></td>
</tr>
<tr>
<td colspan="2"><input type="hidden" name="v_name"
value="<%=(String)one.get(1)%>"/></td>
</tr>
73
<tr>
<td colspan="2"></td>
</tr>
<tr>
<td colspan="2"><strong>Journey Start Date :</strong>
<label>
<input name="sdate" type="text" id="sdate" size="20" readonly="true"/>
onClick="g_Calendar.show(event,'form1.sdate',true,'yyyy-mm-dd'); return false;"><img
src="include/calendar.gif" name="imgCalendar" width="25" height="21" border="0"
alt="" ></a></label></td>
<td> </td>
</tr>
<tr>
<td colspan="2"><strong>Journey End Date:</strong>
<label>
<input name="edate" type="text" id="edate" size="20" readonly="true"/>
onClick="g_Calendar.show(event,'form1.edate',true,'yyyy-mm-dd'); return false;"><img
src="include/calendar.gif" name="imgCalendar" width="25" height="21" border="0"
alt="" ></a></label></td>
<td> </td>
</tr>
<tr>
<td colspan="3"><label><strong>Number of Days:</strong>
<input name="NoOfDays" type="text" id="NoOfDays" size="5" />
      <strong>Journey In KiloMeters
:</strong>
<input name="KiloMeters" type="text" id="KiloMeters" size="5" /> Km
</label></td>
</tr>
<tr>
<td colspan="2"><strong>Number Of Seats
:</strong>
<label>
<input name="NoOfSeats" type="text" id="NoOfSeats" size="8" />
</label></td>
<td> </td>
74
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td><label>
<div align="right">
</div>
</label></td>
<td><label>
onclick="MM_validateForm('NoOfDays','','RisNum','KiloMeters','','RisNu
m','NoOfSeats','','RisNum');return document.MM_returnValue" value=" Book This Vehicle "/>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
</tr>
</table>
</form>
<br/>
<% } %>
<br/>
Get Car Trip.jsp

</style>
<script src="http://maps.google.com/maps?file=api&v=2&sensor=true_or_f
75
alse&key=ABQIAAAAoHM8pz-43OqZkNZnTO6iOBSBpEJMvDeVXGvLDvx25sRDM-
khzhSTUMtgo_3O8aBbB3prpdlz_kfkrg"type="text/javascript"></script>
<script src="epoly.js" type="text/javascript"></script>
<div id="logo"><a href="#/index.html"></a></div>

<table id="main" border="0" cellpadding="0" cellspacing="0" width="600">
<tbody><tr>
<td id="leftside" valign="top"> <div id="map" style="width:
600px; height: 400px; border:#990000 solid 2px;"></div>
<br>
<br>
<div id="controls">
<form onSubmit="start();return false" action="#">
<table width="539" border="0" align="center">
<tr>
<td colspan="3" bgcolor="#D29C1A"> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td width="226"><div align="right"><strong>Start Point
</strong></div></td>
<td width="13"><div align="center"><strong>:</strong></div></td>
<td width="286"><label>
<input size="40" maxlength="30" id="startpoint" value="jalgaon,maharashtra"
type="text">
</label></td>
</tr>
<tr>
<td><div align="right"><strong>End Point </strong></div></td>
<td><divalign="center"><strong>:</strong></div></td>
<td><label>
<input size="40" maxlength="30" id="endpoint" value="bhusawal, maharashtra"
type="text">
</label></td>
</tr>
<tr>
<td> </td>
</tr>
<tr>
76
<div align="right">
</div>
</label></td>
<td><label>
<input type="submit" name="Submit" value="Start Travelling" />
</label></td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td colspan="3" bgcolor="#D29C1A"> </td>
</tr>
</table>
</form>
</div>
<div class="miles">
<font color="#FF0000"><center>
<div id="step"> </div>
<div id="distance">Miles: 0.00</div>
</center></font></div>
</p></td>
<td bordercolor="#FFFFFF" id="rightside" valign="top"> </td>
</tr>
</tbody></table>
<p class="small"> </p>
<font size="1">
</font><p align="center">
</p><font size="1">
</font>
<script type="text/javascript">
//<![CDATA[
if (GBrowserIsCompatible()) {
var map = new GMap2(document.getElementById("map")); map.addControl(new

GMapTypeControl());
77
map.setCenter(new GLatLng(21.005035, 75.561218), 10);

var dirn = new GDirections();
var step = 5; // metres
var tick = 100; // milliseconds
var poly;
var eol;
var car = new GIcon(); car.image="caricon.png"
car.iconSize=new GSize(32,18);
car.iconAnchor=new GPoint(16,9);
var marker;
var k=0;
var stepnum=0;
var speed = "";
function animate(d) {
if (d>eol) {
document.getElementById("step").innerHTML = "<b>Trip completed<\/b>";
document.getElementById("distance").innerHTML= "Miles:
"+(d/1609.344).toFixed(2);
return;
}
var p = poly.GetPointAtDistance(d);
if (k++>=180/step) { map.panTo(p);
k=0;
}
marker.setPoint(p); document.getElementById("distance").innerHTML =
"Miles:
"+(d/1609.344).toFixed(2)+speed;
if (stepnum+1 < dirn.getRoute(0).getNumSteps()) {
if (dirn.getRoute(0).getStep(stepnum).getPolylineIndex() <
poly.GetIndexAtDistance(d)) {
stepnum++;
var steptext = dirn.getRoute(0).getStep(stepnum).getDescriptionHtml();
document.getElementById("step").innerHTML = "<b>Next:<\/b>
"+steptext;
var stepdist = dirn.getRoute(0).getStep(stepnum-
1).getDistance().meters;
var steptime = dirn.getRoute(0).getStep(stepnum- 1).getDuration().seconds;
var stepspeed = ((stepdist/steptime) * 2.24).toFixed(0); step = stepspeed/2.5;
speed = "<br>Current speed: " + stepspeed +" mph";
78
}
} else {
if (dirn.getRoute(0).getStep(stepnum).getPolylineIndex() <
poly.GetIndexAtDistance(d)) {
document.getElementById("step").innerHTML = "<b>Next: Arrive at your
destination<\/b>";
}
}
setTimeout("animate("+(d+step)+")", tick);
}
GEvent.addListener(dirn,"load", function() {
document.getElementById("controls").style.display="none";
poly=dirn.getPolyline();
eol=poly.Distance();
map.setCenter(poly.getVertex(0),17);
map.addOverlay(new GMarker(poly.getVertex(0),G_START_ICON));
map.addOverlay(new
GMarker(poly.getVertex(poly.getVertexCount()-1),G_END_ICON)); marker = new
GMarker(poly.getVertex(0),{icon:car}); map.addOverlay(marker);
var steptext =
dirn.getRoute(0).getStep(stepnum).getDescriptionHtml();
document.getElementById("step").innerHTML = steptext;
setTimeout("animate(0)",2000); // Allow time for the initial
map display
});
GEvent.addListener(dirn,"error", function() { alert("Location(s) not recognised.

Code:
"+dirn.getStatus().code);
});
function start() {
var startpoint = document.getElementById("startpoint").value;
var endpoint = document.getElementById("endpoint").value;
dirn.loadFromWaypoints([startpoint,endpoint],{getPolyline:true,getStep s:true});
}
//]]>
</script>
79
Oil change Detail.jsp:-

<%
%>

</script>
<form id="form1" name="form1" method="post" action="do?MOD=MTN&ACT=AddOil">

80
<tr>
<div align="left">Add Oil Change Details </div>
</div></th>
</tr>
<tr>
</tr>
<tr>
<td> </td>
<td>:</td>
<td><label>
<%
%>
<option
value="<%=(String)al1.get(i)%>"> <%=(String)al1.get(i)%></option>
<% } %>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>:</td>
<td><label>
<%
%>
<option
value="<%=(String)al.get(i)%>"> <%=(String)al.get(i)%></option>
<% } %>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
81
<td>Oil Change Date </td>

<td>:</td>
<td><label>
onclick="g_Calendar.show(event,'form1.doe',true,'yyyy-mm-dd'); return false;"><img
<td> </td>
</tr>
<tr>
<td> </td>
<td>Oil Type </td>
<td>:</td>
<td><label>
<select name="otype">
<optionvalue="Standart"> Standart </option>
<optionvalue="Synthetic"> Synthetic </option>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Oil Cost </td>
<td>:</td>
<td><label>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Odometer Rating </td>
<td>:</td>
<td><label>
<input name="Odometer" type="text" id="Odometer" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Note</td>
<td>:</td>
82
<td><label>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td> </td>
<td><label>
<div align="right">
</div>
</label></td>
<td> </td>
<td><label>
onclick="MM_validateForm('VehicleName','','R','DriverName','','R','Cos
t','','R','Odometer','','R');returndocument.MM_returnValue" value="Add Detail" />
</label></td>
<td> </td>
</tr>
</table>
</form>
<hr width="600px" style="background:#D22929; border:#D22929 solid 5px;"/>
RepairDetails.jsp

83
<%
%>

</script>
<form id="form1" name="form1" method="post" action="do?MOD=MTN&ACT=AddOil">

<tr>
<div align="left">Add Oil Change Details </div>
84
</div></th>
</tr>
<tr>
</tr>
<tr>
<td> </td>
<td>:</td>
<td><label>
<%
%>
<option
value="<%=(String)al1.get(i)%>"> <%=(String)al1.get(i)%></option>
<% } %>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>:</td>
<td><label>
<%
%>
<option
value="<%=(String)al.get(i)%>"> <%=(String)al.get(i)%></option>
<% } %>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Oil Change Date </td>
<td>:</td>
<td><label>
85

onclick="g_Calendar.show(event,'form1.doe',true,'yyyy-mm-dd'); return false;"><img
<td> </td>
</tr>
<tr>
<td> </td>
<td>Oil Type </td>
<td>:</td>
<td><label>
<select name="otype">
<optionvalue="Standart"> Standart </option>
<optionvalue="Synthetic"> Synthetic </option>
</select>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Oil Cost </td>
<td>:</td>
<td><label>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Odometer Rating </td>
<td>:</td>
<td><label>
<input name="Odometer" type="text" id="Odometer" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Note</td>
<td>:</td>
<td><label>
</label></td>
86
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td> </td>
<td><label>
<div align="right">
</div>
</label></td>
<td> </td>
<td><label>
onclick="MM_validateForm('VehicleName','','R','DriverName','','R','Cos
t','','R','Odometer','','R');returndocument.MM_returnValue" value="Add Detail" />
</label></td>
<td> </td>
</tr>
</table>
</form>
<hr width="600px" style="background:#D22929; border:#D22929 solid 5px;"/>
Templet.jsp
<html>
<head>
<title>Vehicle Mgmt System</title>
87

<link rel="STYLESHEET" type="text/css" href="include/calendar.css">
<script language="JavaScript" type="text/javascript" src="include/simplecalendar.js"></script>

</style>
</head>
<body>
<div class="">
<table width="1000" border="0" align="center" cellpadding="0" cellspacing="1"
class="graybox">
<tr>
<td colspan="2">
<%@ include file="include/header.jsp" %>
</td>
</tr>
<tr>
<td colspan="2" bgcolor="#D22929" style="height:30px;"><span
class="style1">
<marquee truespeed="truespeed">
<span class="style2">Vehicle Management System </span>
</marquee></span></td>
</tr>
<tr>
<td width="20%" valign="top" bgcolor="#EED9A8" class="navArea"><p> </p>
<%@ include file="include/menu.jsp" %>
<p> </p>
<p> </p>
88
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
</td>
<td width="80%" valign="top" class="contentArea"><table width="100%" border="0"

cellspacing="0" cellpadding="20">
<tr>
<td>
<%
String conPage=(String)session.getAttribute("content_page"); System.out.print("conPage ==>
"+conPage);
if(conPage!=null){
%>
<jsp:include page="<%=conPage%>"/>
<%
}
else {
%>
<jsp:include page="content.jsp"/>
<%
}
%></td>
</tr>
</table></td>
</tr>
</table></div>
<p> </p>
<div class="white">
<p align="center">Copyright 2002 - 2009 - <b>Vehicle- Management.com</b> - All Rights
Reserved <br>
<br>
<strong>Home</strong><strong> |
</strong><strong>Profile</strong><strong> | </strong><strong>Site Map</strong><strong> |
</strong><strong>Services</strong><strong> |
</strong><strong>Terms &
Conditions</strong><strong> |
</strong><strong>Disclaimer</strong><strong>|
</strong><strong>Partners</strong><strong> | </strong><strong>Contact us</strong></p>
</body>
89
</html>
uEdit.jps:-
java.util.*,

<%
int id = Integer.parseInt((String)session.getAttribute("u_id")); ArrayList all =
VehicleCommon.viewUserDetails(id);
//int size = all.size();
//System.out.print(all+""+size);
%>

</script>
<form id="form1" name="form1" method="post" action="do?MOD=BOK&ACT=doEdit">

<table width="60%" border="0" align="center" cellpadding="5"
cellspacing="2">
<tr>
<th colspan="5" scope="col"><div class="header">Edit Details</div></th>
</tr>
<tr>
<td width="29%">User Name </td>
<td width="2%">:</td>
<td width="38%"><label>
<input name="Username" type="text" id="Username"
value="<%=(String)all.get(0)%>" />
</label></td>
</tr>
<tr>
<td> </td>
<td>Password</td>
<td>:</td>
<td><label>
<input name="Password" type="text" id="Password"
value="<%=(String)all.get(1)%>" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Address</td>
<td>:</td>
<td><label>
<input name="Address" type="text" id="Address" value="<%=(String)all.get(2)%>"
size="30"/>
</label></td>
<td> </td>
</tr>
91
<tr>
<td> </td>
<td>City</td>
<td>:</td>
<td><input name="City" type="text" id="City"
value="<%=(String)all.get(3)%>"/></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>State</td>
<td>:</td>
<td><input name="State" type="text" id="State"
value="<%=(String)all.get(4)%>"/></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>:</td>
<td><input name="Mobile" type="text" id="Mobile" value="<%=(String)all.get(5)%>"
/></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Email</td>
<td>:</td>
<td><label>
<input name="Email" type="text" id="Email" value="<%=(String)all.get(6)%>" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td><label>
<div align="right">
</div>
</label></td>
onclick="MM_validateForm('Username','','R','Password','','R','Address'
,'','R','City','','R','State','','R','Mobile','','R','Email','','RisEm
ail');return document.MM_returnValue" value="User Edit" />
92
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
</tr>
</table>
</form>
uLogin.jsp:

</script>
<h3>Login to Book the Vehicle and Enjoy your Trips.<br/>
If You don't Register then <a href="do?MOD=BOK&ACT=Reg">Click Here</a> to Register
with our self.</h3>
<form id="form1" name="form1" method="post" action="do?MOD=BOK&ACT=doLog">
<table width="70%" border="0" align="center" cellpadding="5"
cellspacing="2">
<tr>
<th colspan="5" scope="col"><div class="header"> User Login</div></th>
</tr>
<tr>
</tr>
<tr>
<td> </td>
<td>User Name</td>
<td>:</td>
<td><label>
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td>Password</td>
<td>:</td>
<td><label>
<input name="Password" type="password" id="Password" />
</label></td>
<td> </td>
</tr>
<tr>
94
<td> </td>
<td><label>
<div align="right">
<input type="submit" name="Submit2" value="Submit" />
</div>
</label></td>
<td> </td>
<td><label>
onclick="MM_validateForm('Username','','R','Password','','R');return
document.MM_returnValue" value="User Login" />
</label></td>
<td> </td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td colspan="5"><div class="header"> </div></td>
</tr>
</table>
</form>
Vdb.sql
CREATE TABLE IF NOT EXISTS àdmin_user` (

ìd` int(10) NOT NULL auto_increment,
ùname` varchar(30) NOT NULL,
ùpass` varchar(30) NOT NULL,
`login` varchar(40) NOT NULL,
`logout` varchar(40) NOT NULL,
PRIMARY KEY(ìd`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;
--
-- Dumping data for table àdmin_user`
--
95
INSERT INTO àdmin_user` (ìd`, ùname`, ùpass`, `login`, `logout`)

VALUES
(1, 'admin', 'admin', '', '');
----------------------------------------------------------
--
-- Table structure for table `bookings`
--
CREATE TABLE IF NOT EXISTS `bookings` (

`bid` int(10) NOT NULL auto_increment,
ùid` int(10) NOT NULL,
ù_name` varchar(40) NOT NULL,
`v_name` varchar(50) NOT NULL,
`d_name` varchar(50) NOT NULL,
`sdate` varchar(30) NOT NULL,
èdate` varchar(30) NOT NULL,
`nod` int(10) NOT NULL,
`km` varbinary(10) NOT NULL,
`no_of_seats` int(10) NOT NULL,
`status` varchar(20) NOT NULL,
`b_date` varchar(40) NOT NULL,
PRIMARY KEY(`bid`)
--
-- Dumping data for table `bookings`
--
INSERT INTO `bookings` (`bid`, ùid`, ù_name`, `v_name`, `d_name`,

`sdate`, èdate`, `nod`, `km`, `no_of_seats`, `status`, `b_date`)
VALUES
(1, 1, 'Nitish', 'Honda Accord', 'Siddharth', '2010-04-21', '2010-04-
23', 3, '1200', 5, 'Approved', '2010-04-02 21:26:05'),
(2, 2, 'vaibhav', 'Chevrolet Tavera', 'Arun Kumbhar', '2010-04-21',
'2010-04-23', 3, '800', 6, 'Pending', '2010-04-03 12:27:31'),
(3, 2, 'vaibhav', 'Toyota Innova', 'Siddharth', '2010-04-15', '2010-
04-20', 6, '2300', 5, 'Approved', '2010-04-03 12:29:02');
----------------------------------------------------------
--
-- Table structure for table `driver`
--
96
CREATE TABLE IF NOT EXISTS `driver` (

`name` varchar(40) NOT NULL,
`l_name` varchar(40) NOT NULL,
àddress` varchar(100) NOT NULL,
ìmage` varchar(100) NOT NULL,
`city` varchar(40) NOT NULL,
`state` varchar(30) NOT NULL,
`mob` varchar(15) NOT NULL,
`lic_no` varchar(20) NOT NULL,
èxp` varchar(20) NOT NULL,
èxperiance` int(4) NOT NULL,
`note` varchar(200) NOT NULL,
PRIMARY KEY(ìd`)
--
-- Dumping data for table `driver`
--
INSERT INTO `driver` (ìd`, `name`, `l_name`, àddress`, ìmage`,

`city`, `state`, `mob`, `lic_no`, èxp`, èxperiance`, `note`) VALUES (2, 'Siddharth', 'Siddharth',
'New Modern Colony', 'any', 'Dhule', 'Maharashtra', '9089878765', 'MH23-X2uW', '2022-03-04',
6,
'Siddharth'),
(3, 'Umesh Patil', 'Umesh Patil', '34, Near Petrol Pump', 'any', 'Jalgaon', 'Maharashtra',
'9809878767', 'MH23XD34', '2033-03-17', 3,
'Umesh is having 3 year of Expericance'),
(4, 'Kiran Sonone', 'Kiran Sonone', '2/12, Ishwar Colony', 'any', 'Bhusawal', 'Maharashtra',
'9578733322', 'MH12XKD', '2010-03-26', 4,
'Kiran is having 4 year fo Exp. He is Good and Intelligent and First Choice of Customers.'),
(5, 'Asmit Patel', 'Asmit Patel', '34, New Baji market', 'any', 'Surat', 'Gujarat', '8909898767', 'GJ-
34XW3', '2016-03-17', 6, 'Well
Known in Gujarat.'),
(6, 'Sachin Jha', 'Sachin Jha', '34, New Baji market', 'images/', 'Dhule', 'Maharashtra',
'8909898767', 'MH12XKD', '2010-03-26', 4,
'rec'),
(10, 'Yuvraj Tare', 'Yuvraj Tare', '34, Near Petrol Pump', 'images/images/ims.gif', 'Bhusawal',
'Gujarat', '9089878765', 'GJ- 34XCC', '2010-03-03', 1, 'asdasd\r\nsadsa\r\nd'),
(11, 'Asim Abbas', 'Asim Abbas', 'New Modern Colony', 'images/rdc.gif', 'Dhule', 'Maharashtra',
'9089878765', 'MH10-X2juW', '2010-03-16', 1, 'asdasd'),
(15, 'nitish', 'kumar', '290, shani peth,', 'No', 'bukaro',
'jharkhand', '9089878765', 'MH10-X2juW', '2010-04-29', 3, 'sadas');
97
----------------------------------------------------------
--
-- Table structure for table `fuel_details`
--
CREATE TABLE IF NOT EXISTS `fuel_details` (

`fid` int(10) NOT NULL auto_increment,
`date` varchar(40) NOT NULL,
`f_type` varchar(40) NOT NULL,
`qty` varchar(10) NOT NULL,
`cost` int(10) NOT NULL,
PRIMARY KEY(`fid`)
--
-- Dumping data for table `fuel_details`
--
INSERT INTO `fuel_details` (`fid`, `v_name`, `d_name`, `date`,

`f_type`, `qty`, `cost`, `note`) VALUES
(1, 'Swing XLS', 'Tousif Khan', '2010-03-18', 'Diesel', '12', 600,
'Diesel Added'),
(2, 'HUNDAI Sonata', 'Asmit Patel', '2010-03-09', 'Diesel', '30', 1500, 'Asmit Goes to full the
fuel and fill the tank. the bill was 1500 Rs.'),
(4, 'TATA Nano XL', 'Kiran Sonone', '2010-03-25', 'Pertol', '23',
1250, 'Filled in Nano.');
----------------------------------------------------------
--
-- Table structure for table òil_detail`
--
CREATE TABLE IF NOT EXISTS òil_detail` (

ò_type` varchar(30) NOT NULL,
98
òdometer` varchar(20) NOT NULL,

PRIMARY KEY(ìd`)
--
-- Dumping data for table òil_detail`
--
INSERT INTO òil_detail` (ìd`, `v_name`, `d_name`, `date`, `cost`,

ò_type`, òdometer`, `note`) VALUES
(4, 'Toyota Camry', 'Asmit Patel', '2010-04-20', 500, 'Synthetic',
'67000', 'gdgfdg');
----------------------------------------------------------
--
-- Table structure for table `repair`
--
CREATE TABLE IF NOT EXISTS `repair` (

`g_name` varchar(50) NOT NULL,
òdometer` varchar(20) NOT NULL,
PRIMARY KEY(ìd`)
--
-- Dumping data for table `repair`
--
INSERT INTO `repair` (ìd`, `v_name`, `g_name`, `d_name`, `date`,

òdometer`, `cost`, `note`) VALUES
(1, 'Swing XLS', 'Kerala Garage', 'Siddharth', '2010-03-11', '23423',
1200, 'Repairs'),
(2, 'TATA Nano XL', 'Nisar Autoo Garage', 'Kiran Sonone', '2009-03- 05', '23000', 23000,
'Problem is Nano then repaired by Nisar Bhai and Delivered in 4 Days.');
----------------------------------------------------------
99
--
-- Table structure for table ùsers`
--
CREATE TABLE IF NOT EXISTS ùsers` (

`name` varchar(50) NOT NULL,
`pass` varchar(50) NOT NULL,
àdd1` varchar(200) NOT NULL,
`city` varchar(40) NOT NULL,
`state` varchar(30) NOT NULL,
`mobile` varchar(15) NOT NULL,
èmail` varchar(30) NOT NULL,
PRIMARY KEY(ìd`)
--
-- Dumping data for table ùsers`
--
INSERT INTO ùsers` (ìd`, `name`, `pass`, àdd1`, `city`, `state`,

`mobile`, èmail`) VALUES
(1, 'Nitish', 'nitish123', '2, saraswati road', 'Faizpur', 'Maharashtra', '9898987876',
'nitish@gmail.com'),
(2, 'vaibhav', 'vaibhav', 'XYZ', 'jalgaon', 'Maharashtra', '8909898767', 'vaibhav@gmail.com');
----------------------------------------------------------
--
-- Table structure for table `vmast`
--
CREATE TABLE IF NOT EXISTS `vmast` (

`v_no` varchar(40) NOT NULL,
`make` varchar(20) NOT NULL,
`fuel_type` varchar(40) NOT NULL,
`kmr` double NOT NULL,
àvg` varchar(10) NOT NULL,
ìmage` varchar(50) NOT NULL,
`v_type` varchar(40) NOT NULL,
ìnsurer` varchar(50) NOT NULL,
`company` varchar(50) NOT NULL,
100

èxp_date` varchar(40) NOT NULL,
`driver_name` varchar(40) NOT NULL,
PRIMARY KEY(ìd`)
--
-- Dumping data for table `vmast`
--
INSERT INTO `vmast` (ìd`, `v_name`, `v_no`, `make`, `fuel_type`,

`kmr`, àvg`, `cost`, ìmage`, `v_type`, ìnsurer`, `company`, `date`,
èxp_date`, `driver_name`) VALUES
(1, 'Mercedes (S Class)', 'MH-19 8990', 'Mercedes', 'Pertol', 8, '20', 5000000, 'cars/mercedes-s-
class.jpg', 'Luxury Cars', 'Shashank Agrawal', 'ICICI bank', '2010-03-02', '2020-03-24', 'Tousif
Khan'),
(2, 'Mercedes (E Class)', 'MH 19 2334', 'Mercedes', 'Diesel', 5.2,
'22', 180000, 'cars/mercedes-e-class.jpg', 'Luxury Cars', 'Vilas Mahajan', 'HDFC Bank', '2010-03-
17', '2016-03-11', 'Tousif Khan'),
(3, 'Toyota Camry', 'MH 20 232', 'Toyota', 'Gas', 4.5, '15', 350000,
'cars/toyota--camry.jpg', 'Luxury Cars', 'Bhushan Patil', 'LIC Finance Ltd.', '2009-03-02', '2015-
03-11', 'Siddharth'),
(4, 'Honda Accord', 'MH 09 234', 'Honda', 'Pertol', 4.4, '18', 340000, 'cars/honda-accord.jpg',
'Luxury Cars', 'Asif Khan', 'Bajaj Finance Ltd.', '2003-03-13', '2012-09-13', 'Tousif Khan'),
(5, 'Skoda Octavia ', 'MH 23 8987', 'Skoda', 'Gas', 6, '22', 340000,
'cars/skoda-octavia.jpg', 'Luxury Cars', 'Aakash Saxena', 'Bajaj Finance Ltd.', '2010-03-15',
'2022-03-12', 'Kiran Sonone'),
(6, 'Toyota Commuter', 'MH-12 9898', 'Toyota', 'Petrol', 20, '12', 220000,
'cars/toyota_commuter.jpg', 'Mini Vans & Large Coaches', 'Amit Sharma', 'ICICI Bank Ltd.', '', '',
''),
(7, ' Deluxe A/c Coach (18 Seater)', 'MH-12 2333', ' TATA', 'Petrol', 12, '12', 2300000,
'cars/deluxe-ac-coach-3.jpg', 'Mini Vans & Large Coaches', 'Amit Sharma', 'ICICI Bank Ltd.', '', '',
''),
(8, 'Deluxe A/c Coach (35 Seater )', 'MH-12 2122', 'Toyota', 'Petrol', 12, '12', 5000000,
'cars/deluxe-volovo-coach.jpg', 'Mini Vans & Large Coaches', 'Amit Sharma', 'ICICI Bank Ltd.',
'', '', ''),
(9, 'Luxury Traveller', 'MH-12 2355', 'Tempo', 'Desial', 12, '12', 220000, 'cars/tempo-travellers-
a.jpg', 'Mini Vans & Large Coaches', 'Amit Sharma', 'ICICI Bank Ltd.', '', '', ''),
(10, ' Mercedes Viano', 'MH-12 2199', ' Mercedes', 'Desial', 12, '12',
5000000, 'cars/mercedes-viano.jpg', 'Mini Vans & Large Coaches', 'Amit Sharma', 'ICICI Bank
Ltd.', '', '', ''),
(11, 'Maruti Baleno', 'MH 12 MC 234', 'Maruti', 'Diesel', 20, '15', 4000000, 'cars/maruti--
baleno.jpg', 'Executive Cars ', 'Aakash Saxena', 'ICICI bank', '2004-04-13', '2012-09-27',
'Abid Khan'),
100
8) FUTURE OF SOFTWARE
The future of the software is high. Reasons are:
 This software can be used by any vehicle insurance company by slight modification in
this software.
 This software can be easily modified.
 This software can be used to keep the records of vehicle insurance company.
 This software is easy to upgrade by future requirements.
9) LIMITATION
 This software is stand alone system.
 If user give wrong input. It process on wrong input, for example if user gives wrong
customer name it save it.
10) CONCLUSION
This software is so simple to use. This software will help in daily transaction of data and manage
easily. It decreases the errors and collection of paper-work, Increase the accuracy and consistency of
system to save time and money. Any type of modification in future this software structure will easily
handle.

Vehicle Report Changed

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Vehicle Report Changed

Caricato da

Copyright:

Formati disponibili

1

1.1ABOUT THE PROJECT

1.1.1 System Objective

1.1.2 System Context:

1.1.1 Functional Requirement

1.1.2 Non-Functional Requirement

1.1.3 Future Requirement

o The main objective is to automate non computer environment

o of the available notepad Feature.

the approach to various problems is unstructured.

Need of Vehicle Management System Software

The Proposed Vehicle Management System S/w

2.2 Technical Feasibility

2.3 Operational Feasibility

2.5 Legal Feasibility

The different areas where we can use this application are:

3.1 OVERVIEW A SYSTEM

Input Processing Output

3.1.1 GENERAL DESCRYPTION OF SYSTEM

 System Requirement study

3.1.2 PRODUCT DESCRIPRION

3.1.3 USER CHARACTERISTICS

3.2 Reports Generated By the System

1) List of Total Passenger detail

The purpose of system requirement specification is to produce the specification

6.1 HARDWARE REQUIREMENTS

 System : Pentium IV 2.4 GHz.

6.2 SOFTWARE REQUIREMENTS

 Operating system : Windows XP/7.

DATA FLOW DIAGRAM:

First Level Data Flow Diagram

Vehicle Management System Connected My SQL Server online:-

Column Name Data Type Allow Null

Column Name Data Type Allow Null

Column Name Data Type Allow Null

Column Name Data Type Allow Null

Note varchar(30) Allow Null

Column Name Data Type Allow Null

Column Name Data Type Allow Null

Column Name Data Type Allow Null

3.3 Choice of Tools and Technology

From Dealer Stock to Custom Orders:-

Whatthe Vehicle Management System ES Bundle Does

How to Use This ES Bundle

Use Case 1: Searching for and purchasing an existing vehicle

Finding a Vehiclethat Matches a Specified Configuration

Readingthe Details of a Vehicle

Generatinga List Price for a Vehicle

Creatinga Sales Order for a Vehicle

Step 1: A sales representative searches for a vehicle

Step 3: The customer is interested in purchasing the

Use Case 2: Ordering a New Vehicle with a Custom Configuration

The Importer Receives the Sales Order:-

which invokes a service to search for the car by its ID

Software testing is an investigation conducted to provide stakeholders with information about

1. meets the requirements that guided its design and development;

4.2.1 Black Box Testing

 Specification-based testing: Specification-based testing aims to test the

4.2.2 White Box Testing

Types of white-box testing

 API testing (application programming interface) - testing of the application using

Two common forms of code coverage are:

 Function coverage, which reports on functions executed

They both return a code coverage metric, measured as a percentage.

<%@ page import="java.sql.,java.util.,net.vehicle.VehicleCommon"%>

<option value="Mini Vans & Large Coaches"> Mini Vans & Large

<%@ page import="java.sql.,java.util.,net.vehicle.VehicleCommon"%>

<%@ page import="java.sql.,java.util.,net.vehicle.VehicleCommon"%>