Vehicle Insurance management system project(OOAD)
Sneha19
anish.pdf
Online Vehicle Rent System
Rivier University
Course:CS552AH1 Object-Oriented System Analysis & Design
Semester: Fall 2019
Instructor: Prof. Vladimir Riabov
Project Submitted by
SUNIL KRISHNA CHENNA
ABHISHEK REDDY PENTAREDDY
THARAKA PRASANNA REDDY PALLETI VENKATA
Executive Summary
Online vehicle rent system is a web application. The main functionalities of this application is
user can create account in this application. After user login and enter the desired location for
vehicle search. Regarding that location, the administrator will check the any vehicles are
available for that location or not. If vehicles are available, the customer select the desired vehicle
and reserve that vehicle for rent ad ride. This application manager can login into system and
verify the vehicle rent customers details and rent vehicles details. Check the customer’s bill
payment information. The employee of this application login into system and verify the customer
bill payments and process that bill payments. If bill payment is success generate the printed bill
details to customers and send to customer. Customer can access the payment details. This is total
functionality of the system.
Actually this application is implemented in architecture is model, view and controller
architecture. The technologies used in this application is java language is used for front end
development and for backend database storage purpose using MySQL database server.
Table of Contents
Executive Summary ........................................................................................................................ 1
Introduction ..................................................................................................................................... 3
Problem statement ....................................................................................................................... 3
Project objective .......................................................................................................................... 3
Project Plan ..................................................................................................................................... 3
Functional Specifications ................................................................................................................ 5
Use Case Diagram ....................................................................................................................... 5
Users/Actors/Roles ...................................................................................................................... 5
Use cases ..................................................................................................................................... 6
Business Rules............................................................................................................................. 7
Functional Tests Plan ...................................................................................................................... 7
System Design Specifications ......................................................................................................... 7
System Integration Tests Plan ......................................................................................................... 8
Issues to Future Studies .................................................................................................................. 8
Conclusion ...................................................................................................................................... 8
Class Diagram ............................................................................................................................. 9
Object Diagram ......................................................................................................................... 10
Sequence Diagram..................................................................................................................... 10
Collaboration or Communication Diagram ............................................................................... 11
State chart Diagram ................................................................................................................... 12
Functional Tests Plan .................................................................................................................... 12
System Design Specifications ....................................................................................................... 14
Architecture diagram ................................................................................................................. 14
Client server approach/deployment diagram............................................................................. 14
Package Diagram....................................................................................................................... 15
Window Navigation Diagram ................................................................................................... 16
User Interfaces........................................................................................................................... 16
Output Report Forms ................................................................................................................. 18
Data Flow Diagram ................................................................................................................... 21
Entity-Relational diagram ......................................................................................................... 22
Database Tables......................................................................................................................... 22
System Integration Tests Plan ....................................................................................................... 30
Issues to Future Studies ................................................................................................................ 31
Conclusion .................................................................................................................................... 32
References……………………………………………………………………………………..... 32
Introduction
In recent days’ technology improved a lot and many users are preferred to use the online
application. So for vehicle rent the people are physically search for the vehicle rent offices.
Physically go to that rental office and ask for available vehicles. If vehicles are available give
payment for rent of vehicle manually and book the car and go for ride. But this process is time
taking process. It is long process.
Problem statement
The main problem of present existing vehicle rent system is time taking process. People are
required to manually go to offices and paid money for vehicle reservation. So these present
system problems are overcome by introducing new online vehicle rent system. The office
manager also has taking long time to check the reports. The employee given normal paper bill
for payment confirmation. But it is not safe. Data inconsistency problems in management of
vehicle rental offices. These are different types of problems in vehicle rent system.
Project objective
The main objective of this project is to people search for the vehicle online and select the
particular vehicle for rent and book that vehicle. In booking of vehicle process people required to
paid money though online using credit card or internet banking. This process is very easy and
time saving process. The existing system problems are overcome by using this proposed
application.
Project Plan
Task Name 12/09/19 19/09/19 26/09/19 03/10/19 10/10/19 14/10/19 17/10/2019
Online Vehicle Rent
Project goals and
plan Start End
Deliverables
definition Start End
Gather requirements
Phase Start End
System Analysis
Phase Start End
Functional
Specification Phase Start End
Risk assessment Start End
System Design
Phase Start End
Design of all
diagrams Start End
System
implementation
phase Start End
Develop coding for
project Start End
System Testing
phase Start End
Unit testing Start End
Integration testing Start End
Project Deployment
Phase Start End
Functional Specifications
Use Case Diagram
Figure 1: Use case Diagram
Users/Actors/Roles
Use case diagram users
The above diagram has total 3 actors or users. There are
1. Customer: Customer is login into this application and search for vehicle. After search select the vehicle and reserve vehicle with payment.
2. Manager: Manager managed the total vehicles and customers reports information. 3. Employee: Employee is always checking the payment details of customers. If once
done the payment the employee generates the bill and send that report to
corresponding customer.
4. Driver: The driver is assigned for reserve of vehicle based on type of vehicle. Manager will check the driver licensing information and assigned for vehicle driving
service.
The total actors of the system are
1. Customer: This actor is client for this application. 2. Manager: This actor is managed the total application. He is like head of application. 3. Employee: The worker of application is employee actor. 4. Driver: The vehicle drives by driver actor in this application. 5. Distributed System: This system is used for process the client request and details are
stored in database server or get from data base server. After processing server
generated response is send back to client system.
6. Payment/ credit card center: This actor is used for payment gateway. The customer enters the cad details and complete payment. But in background process this
application is integrated with credit card payment gateway process and complete
payment successfully.
Use cases
Use cases of customer is
Login. This use case has extension is Signup
Select vehicle. This use case includes search vehicle and reserve vehicle. This reserve vehicle
use case have extension payment use case and it includes drive service use case.
Reserve vehicle.
Use cases of Manager is
Login
Maintain Reports. This use case has extension use case maintain customers and vehicle reports.
Verify the vehicle rental reports of customer.
Use cases of Employee is
Login
Generate Reports
Use cases of Driver is
Login
Drive service
Use cases of Distributed system is
Maintain reports
Business Rules
The above use case diagram has following business rules. There are following business rules.
Customer select vehicle business rule
Customer reserve vehicle business rule
Class Diagram
Object Diagram
Sequence Diagrams
Collaboration or Communication Diagram
State chart Diagram
Functional Tests Plan
System Design Specifications
Architectural diagram
Use case Number: 1
Use case Name: Customer select vehicle
Description: The customer actor wants to search vehicle.
Actors: Customer
Use-case relationships: This use case have included relationship with search vehicle
and another includes relationship with reserve vehicle.
Pre-conditions: Must be login into system.
Basic –flow: Customer first login into system. After that go to search vehicle and
search for the vehicle based on required input data. After that if any results that are
visible to customer. The customer need to select the vehicle from list. It includes
reserve vehicle facility also.
Post-conditions: Select the vehicle for reservation or booking.
Alternative flows: No alternative flow
Notes: Customer must be register in application with create new account.
Use case Number: 2
Use case Name: Customer reserve vehicle
Description: The customer actor wants to reserve the vehicle for driving or ride.
Actors: Customer
Use-case relationships: This use case have included relationship with drive service
use case and it have extension use case relationship with payment use case.
Pre-conditions: Must be login into system and select vehicle for rent.
Basic –flow: Customer first login into system. After that go to search vehicle and
search for the vehicle based on required input data. After that if any results that are
visible to customer. The customer need to select the vehicle from list. Customer
reserve the vehicle for rent with payment.
Post-conditions: Select the vehicle for reservation or booking.
Alternative flows: No alternative flow
Notes: Customer must be register in application with create new account.
Design Scheme - Client-Server approach
Manager maintain reports use case business rule
Package Diagram
Window Navigation Diagrams
Drafts of User Interfaces
Data Flow Diagram
Entity-Relational diagram
Database Tables
System Integration Tests Plan
Issues to Future Studies
Conclusion
Use case Number: 3
Use case Name: Manager maintain reports use case.
Description: Manager maintain the reports and verify the vehicle rental system
reports.
Actors: Manager, Distributed system
Use-case relationships: This use case have extended relationship with maintain
customers use case and verify reports use case.
Pre-conditions: The manager must be login into system.
Basic –flow: The manager login into system and go for reports. Check reports
regarding rent and approve that requests. Next verify the customers and vehicle
rental bill reports details. All the details are maintained by distributed system is web
server and database for storage purpose.
Post-conditions: Manager Login into system.
Alternative flows: No alternative flow
Notes: Manager must be login in application with create new account.
Class Diagram
Object Diagram
Sequence Diagram
Collaboration or Communication Diagram
State chart Diagram
Functional Tests Plan
Functional test plan
The functional test plan of online vehicle rent system is
Test case ID : 1
Test case Name : Customer registration
Input : Customer information like name, contact and address
Process : After click on register button request processed by web server and details
stored in vehicle database. Display success message to customer
Output : Redirect to login page of online vehicle rent system.
Test case ID : 2
Test case Name : Customer login
Input : Customer information like username and password
Process : After click on login button request processed by web server and details
check with vehicle database.
Output : If login success go to customer home page. If fail redirect to login page.
Test case ID : 3
Test case Name : Customer vehicle search
Input : location
Process : After click on search button if any vehicles available display vehicle
details.
Output : display list of available vehicles.
Test case ID : 4
Test case Name : Reserve Vehicle
Input : selected vehicle
Process : After click on reserve button reserve selected vehicle and details stored
in database.
Output : display success message to user
Test case ID : 5
Test case Name : pay bill
Input : Customer pay type
Process : Based on pay type click on pay if pay success details stored in database
and generate bill.
Output : If success Generated online bill receipt for confirmation. If fail display
corresponding message to user.
System Design Specifications
Architecture diagram
Client server approach/deployment diagram
Package Diagram
Window Navigation Diagram
User Interfaces
My project is vehicle rent system. The user interface specifications of this project is
New user registration page
Login page
Guest login page
Vehicle Reservation page
Vehicle Search and selection page
Vehicle reservation page
Vehicle reservation confirmation page
New user registration page:
This page is used for user signup. This page has user input fields are first name, last
name, phone number, email id, password and confirm password and finally register
button.
Login page:
This page is used for user login. This page has user input fields login email id and
password details. Click on login button for user login process action.
Guest login page:
This page is used for guest login. This page has first name, middle name, last name,
phone number and email id are input fields. After enter all details for action this page has
login as guest button. Click on that button perform guest login action process.
Vehicle Search and selection page:
This page has used for vehicle reservation purpose. This page has input fields like vehicle
category id, pick up date and return date. User enter all details and before reservation
check the vehicle is available or not. For this click on look up vehicle availability button
and search vehicle.
Vehicle Reservation page:
The available vehicle details displayed in this page like vehicle category, pick date and
return date. The rental cost if everything ok for user he enters the input like driver
information like license id, first name, last name and click on reserve vehicle button.
Vehicle reservation confirmation page:
This page shows the vehicle reservation confirmation information.
The above all pages have common design specifications are
UI Font Color Size
Background
Image
Times New Roman Background
Image
auto
Header tag Times New Roman white 16
Body of
register
form
Times New Roman Black (default) 12
Output Report Forms
Login page
New customer register page
Guest User page
Admin pickup confirmation
User vehicle lookup
Vehicle reservation
Data Flow Diagram
Entity-Relational diagram
Database Tables
The following are database tables
Category table
Customer table
Driver table
Employee table
Manager table
Payment table
Rental table
Reserve vehicle
User table
Vehicle table
The scripts for create of above all tables are
--
-- Create schema onlinevehiclerent
--
CREATE DATABASE /*!32312 IF NOT EXISTS*/ onlinevehiclerent;
USE onlinevehiclerent;
DROP TABLE IF EXISTS `category`;
CREATE TABLE `category` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`type` varchar(45) NOT NULL DEFAULT '',
`availablestatus` tinyint(1) NOT NULL DEFAULT '0',
`rentalpayment` float NOT NULL DEFAULT '0',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS `customer`;
CREATE TABLE `customer` (
`customerid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`regdate` varchar(45) NOT NULL DEFAULT '',
PRIMARY KEY (`customerid`),
CONSTRAINT `FK_Customer_1` FOREIGN KEY (`customerid`) REFERENCES `user`
(`userid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS `driver`;
CREATE TABLE `driver` (
`driverid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`licenseno` varchar(45) NOT NULL DEFAULT '',
PRIMARY KEY (`driverid`),
CONSTRAINT `FK_driver_1` FOREIGN KEY (`driverid`) REFERENCES `user` (`userid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS `employee`;
CREATE TABLE `employee` (
`employeeid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`joindate` date NOT NULL DEFAULT '0000-00-00',
PRIMARY KEY (`employeeid`),
CONSTRAINT `FK_employee_1` FOREIGN KEY (`employeeid`) REFERENCES `user`
(`userid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS `manager`;
CREATE TABLE `manager` (
`managerid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`joinDate` date NOT NULL DEFAULT '0000-00-00',
PRIMARY KEY (`managerid`),
CONSTRAINT `FK_manager_1` FOREIGN KEY (`managerid`) REFERENCES `user`
(`userid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS `payment`;
CREATE TABLE `payment` (
`paymentid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`reserveid` int(10) unsigned NOT NULL DEFAULT '0',
PRIMARY KEY (`paymentid`),
KEY `FK_payment_1` (`reserveid`),
CONSTRAINT `FK_payment_1` FOREIGN KEY (`reserveid`) REFERENCES
`reservevehicle` (`reserveid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS `rental`;
CREATE TABLE `rental` (
`rentalid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`reserveid` int(10) unsigned NOT NULL DEFAULT '0',
`expiredate` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`overdueprice` float NOT NULL DEFAULT '0',
`payamount` float NOT NULL DEFAULT '0',
PRIMARY KEY (`rentalid`),
KEY `FK_rental_1` (`reserveid`),
CONSTRAINT `FK_rental_1` FOREIGN KEY (`reserveid`) REFERENCES `reservevehicle`
(`reserveid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS `reservevehicle`;
CREATE TABLE `reservevehicle` (
`reserveid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`customerid` int(10) unsigned NOT NULL DEFAULT '0',
`driverid` int(10) unsigned NOT NULL DEFAULT '0',
`vehcleid` int(10) unsigned NOT NULL DEFAULT '0',
`pickup` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`return` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`price` float NOT NULL DEFAULT '0',
PRIMARY KEY (`reserveid`),
KEY `FK_reservevehicle_1` (`customerid`),
KEY `FK_reservevehicle_2` (`driverid`),
KEY `FK_reservevehicle_3` (`vehcleid`),
CONSTRAINT `FK_reservevehicle_1` FOREIGN KEY (`customerid`) REFERENCES
`customer` (`customerid`),
CONSTRAINT `FK_reservevehicle_2` FOREIGN KEY (`driverid`) REFERENCES `driver`
(`driverid`),
CONSTRAINT `FK_reservevehicle_3` FOREIGN KEY (`vehcleid`) REFERENCES `vehicle`
(`vehicleid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS `user`;
CREATE TABLE `user` (
`userid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(45) NOT NULL DEFAULT '',
`email` varchar(45) NOT NULL DEFAULT '',
`password` varchar(45) NOT NULL DEFAULT '',
`address` varchar(45) NOT NULL DEFAULT '',
`contact` varchar(45) NOT NULL DEFAULT '',
PRIMARY KEY (`userid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS `vehicle`;
CREATE TABLE `vehicle` (
`vehicleid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(45) NOT NULL DEFAULT '',
`plateno` varchar(45) NOT NULL DEFAULT '',
`modelname` varchar(45) NOT NULL DEFAULT '',
`categoryid` int(10) unsigned NOT NULL DEFAULT '0',
PRIMARY KEY (`vehicleid`),
KEY `FK_vehicle_1` (`categoryid`),
CONSTRAINT `FK_vehicle_1` FOREIGN KEY (`categoryid`) REFERENCES `category`
(`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
System Integration Tests Plan
Test plan for system integration
Test case ID : 1
Objective : Customer registration with database interaction
Description : Check the database connection between user registrations to database
server connection link.
Expected result : After click on register button get database connection. If
connection success details stored in database otherwise display database related error
message.
Test case ID : 2
Objective : Customer login with database interaction
Description : Check the database connection between user login to database server
connection link.
Expected result : After click on login button get database connection. If connection
success details get from database otherwise display database related error message.
Test case ID : 3
Objective : Vehicle search with database and application server
Description : Check the database connection in vehicle search and the application
server connection process
Expected result : After click on look up vehicle button get connected with
application server and server to database connection and verify user input with database
data process query and get result.
Test case ID : 4
Objective : Vehicle reservation with database and application server
Description : Check the database connection in vehicle search and the application
server connection process
Expected result : After click on reservation vehicle button get connected with application
server and server to database connection and stored data in database and again response
back to client and display reservation status information.
Issues to Future Studies
In this application developed I faced many issues like development of user interface with java
source code like java server pages’ language. I faced issues in coding executing and database
connection management. I followed online tutorials and with help for online sources I fixed all
issues.
Conclusion
Online vehicle rent system a good and efficient web application. Using this web application
people are easy to search vehicle for rent and book vehicle in online. This application save
people time and provide more efficiency in application.
References
https://www.careerride.com/oops-elements.aspx
https://www.lifecyclestep.com/open/410.0ANALYSISPHASE.htm
https://www.geeksforgeeks.org/unified-modeling-language-uml-introduction/
