1.
Introduction
1.1 Introduction
An online vehicle rental system is a platform that allows bike owners to rent out their
bikes, cars, scooters to people who are looking for a temporary means of transportation.
This system includes three types of users: admin, vehicle owner, and renter. The owner
first registers their vehicle on the system by providing details such as the type of vehicle,
its condition, and rental price. Once the registration process is completed, the owner can
start receiving rental requests from the renters. On the other hand, the renter can browse
through the available vehicle and select the one that meets their requirements. The renter
can also specify the rental duration and complete the booking process by making the
payment. The admin plays a crucial role in validating the information provided by the
vehicle owner and reviewing the activities taking place on the platform. The admin also
handles any disputes between the owner and renter and ensures that the system is
functioning properly. renters alike. Proofs like license, citizenship and other essential
documents are compulsory so that no one could run taking the vehicle. Any customer
whose proofs are not uploaded and are not valid will not be allowed to take bike on rent.
1.2 Problem Statement
Some of the problems faced by existing rental system are as follows:
Traditional rental services can be time-consuming and inconvenient
Lack of transparency in rental policies and hidden fees.
There is a monopoly in the market.
Limited availability of vehicle options.
Tedious booking and confirmation processes.
No centralized database for vehicle availability
1
1.3 Objectives
The objectives of the system are:
To provide location-based service.
To support tourism and domestic mobility by offering accessible and
reliable transportation options.
To reduce the gap between vendor and customer.
To minimize manual errors and delays associated with traditional paper-
based booking systems.
To provide real-time access to available vehicles, pricing, and locations
through web and mobile applications.
2. Scope and Limitations
2.1 Scope
These are the scopes of my system:
Web-based and mobile-friendly application.
Vehicle listing with pictures, prices and details.
Booking and payment system (Cash on Delivery or Online Payment Integration)
Real-time vehicle availability checking.
User registration, login, and profile management.
Notification and support system (email/SMS)
Location-based vehicle searching.
2.2 Limitations
Initial version may be limited to a few cities.
Internet access and digital literacy may limit rural usage.
Payment integration depends on third-party APIs (eSewa, Khalti)
Compliance with local transport laws, rental regulations, and insurance
requirements might be complex.
No fixed pricing model across all providers.
3. Methodology
2
3.1. Requirement Identification
3.1.1. Study of the existing system
In Nepal, a few informal or small-scale websites and social media pages offer
rental services, but none offer a centralized digital platform for booking and
managing vehicle rentals. Existing services lack transparency, trust features,
and real-time booking. If we ignore the marketing issue and do research for
some similar platforms we can find [Link], sajilorental, etc. which is
expensive and only provide car rentals but not other type of vehicle.
3.1.2. Requirement collection
For the purpose of building a system according to what the customer wants,
the involvement of the end-users from the starting of the project would be
better. After defining the scope and making the application purpose crystal
clear, information collected by using a questionnaire can give realistic,
specific, and measurable requirements.
3.2. Feasibility Study
3.2.1. Technical Feasibility
As in no doubt, the solution is very practical. The use of cloud storage and
internet together with the information and delivery of service and high traffic
management is possible without any hassle.
3.2.2. Operational Feasibility
Our proposed system just requires minimalistic configuration on web
browsers and connectivity to the Internet. As these requirements can be easily
fulfilled, our proposed system is operationally feasible.
3.3. Tools
3
3.3.1. Analysis and Design Tools
[Link]. Data Flow Diagram
Fig1: 0 Level Data Flow diagram of Online Vehicle Rental System
Fig2: 1 Level Data Flow diagram of Online Vehicle Rental System
3.3.2. Implementation Tools (Frontend, Backend)
4
IDE: VS Code
Operating System: Linux or Windows
Browser: Chrome (Preferred)
Frontend: HTML, CSS, Javascript, Bootstrap
Backend: PHP or [Link]
Database: MySQL
4. Use case diagram
Fig3: Use case diagram
5. Expected Working Schedule
5
The estimated working schedule for the project is as shown in the chart below:
Weeks
1 2 3 4 5 6 7 8 9 10 11 12 13
Activities
System Analysis 1W
System Design 2W
Coding &
6W
Implementation
Testing 2W
Documentation 2W
Table: Expected working schedule
6. Expected Outcome
The users will be able to browse and book the vehicles in the system and the vehicle
renters will be able to rent out their vehicle as per the requirements submitted by the user.
6
References
[1] R. T. a. M. Chirstensen, The Project Manager's Guide to Software
Engineering's Best
Practices, IEEE Computer Society.
[2] A. H. Hofmann, Scientific Writing and Communication, Oxford University,
2016.
[3] [1] Department of Transport Management, Government of Nepal, “Vehicle
Registration and Licensing Policies” [Online].
Web References
[Link]
[Link]
m
