CAB MANAGEMENT SYSTEM

A Project Report
Submitted in Partial fulfillment
of the Degree of
Bachelor of Computer Applications

Supervisor’s Name: DR. Manju Arora- Submitted By-:

Student Name: Prafful vats
Enrolment.NO: 120921093
Semester: 3

Jagannath University
Bahadurgarh (NCR)
(2021-24)
 Project Certificate

This is to certify that the project report entitled CAB MANAGEMENT SYSTEM

submitted to Jagan Nath University, Bahadurgarh in partial fulfillment of the requirement

for the award of the degree of BACHELOR OF COMPUTER APPLICATIONS ( BCA),

is an original work carried out by Mr / Ms. Prafful vats Enrolment No; 120921093 under

the guidance of Mr./Ms. Manju Arora. The matter embodied in this project is genuine work

done by the student and has not been submitted to this University or any other University /

Institute for the fulfillment of the requirement of any course of study.

Name of the student: Prafful vats Name of the Guide: Mrs. Manju Arora

Signature of the Student: Signature of the Guide:

Enrolment No:120921093 Date :

 ACKNOWLEDGEMENT

We would like to express our deepest appreciation to all those who provided us with the
possibility to complete this report. Special gratitude to our final year project mentor, DR.
Manju Arora, whose contribution in stimulating suggestions and encouragement, helped us to
coordinate and complete our project especially in writing this report.
Furthermore, we would also like to acknowledge with much appreciation, the crucial role of
the staff of JIMS, who permitted us to use all the resources and other necessary materials to
complete the project., CAB MANAGEMENT SYSTEM,
We shall also thank deep heartedly the course coordinator of BCA -IT, Mrs. Manisha Tripathi
who has invested her full effort in guiding the team in achieving the goal of concluding the
project on a satisfactory note.
 INDEX
SNO. TITLE P-NO.
1. Introduction 1-05

2. objectives

3. Tools/Environment

4. Analysis Document

5. Data flow Diagram

6. ER-Diagram/Data Dictionary

7. Project Code

8. Testing & Validation

9. Input-Output

10. Limitations of the Project

11. Future Applications

12. Bibliography
 Introduction of cab management

The proposed cab service management system is a web-based application that can handle
various branches and departmental works of a typical car agency. In the case of car rental
services, this sort of system stands out as trustworthy and reliable in the travel business.
This project aims at offering the best car services to clients in need. It has a fleet of cars
ranging from normal budget cabs to expensive luxury cars. The best thing about a web-based
system such as this is that it offers online cab hire for corporate houses. This makes the
overall car service work easily accessible and reliable.
Modules Overview and Functionality:
The cab management system is a five-module project where each module is assigned
different functionality, access, and permission. Here's a brief introduction to each module:
Admin: The administrator or admin has total control over the application. They can add
managers of any kind, set up their profiles, and add, delete, or modify manager records. They
can have an overview of all managers from different locations and directly communicate with
them. Admin is required to log in to the system with a unique user id consisting of a
username and password.
Finance: All work under this module is handled by the finance manager. They can modify
personal settings like passwords, update profiles, and update vehicle billing details in the
system database. Via the "vendor billing" form under this module, vendor and respective
payment details are updated in the database.
Human Resource: This module is handled by the human resource manager and is used for
managing employee-related tasks. The main forms in this module are:
• Employee details: add, modify, and delete employee details and
registration of employees.
• Shift scheduler: manage the everyday plan for employees.
• Batch information: employees are divided into batches and
routes.
Travel: This module is maintained by the travel manager, assigned with the task of looking
after routes, batches, and employees assigned to that route with details such as date and
timing. The main forms in this module are city (information or route and places), shift details
of each drive, and search. With the search form, users can search for different routes to
different places and find out the corresponding distance and cost.
Maintenance: The main function of this module is to look after vehicle maintenance such as
spare parts, vehicle allocation, etc. This module is handled by a maintenance manager and
they can perform tasks such as adding, modifying, and deleting vendor details and updating
these to the database. The manager can view details of the vehicle as well as the driver.
 Objectives
The main purpose of online cab booking software.

From the customer's point of view, demonstrate some objectives of the uber app.

 The uber app is more comfortable for customers.

 It is easy to book a taxicab.
 Uber app can schedule a benefit and offer while the customers reserve a
ride.
 It makes it easy to travel the journey.
 There is no tension or stress when riders can book a taxi.
 Uber app is a joining between riders and customers.
 .It has an easy option to pay the amount
 To help around the clock
 The customer can travel in a cab with a safe and protected.
 Uber app delivers customer satisfaction.

The project's objective is to automate vehicle rental and reservation so that customers do
not need to call and spend unnecessary time to reserve a vehicle.

They can go online and reserve any kind of vehicle they want that is available. Even
when a customer visits the booking center to hire a vehicle personally. Computers are
available for him to go online and perform his reservation. When he chooses to reserve
the vehicle speedily, issue him a reservation number.

The proposed update feature of OVRS is to allow the passenger’s associates to track the
journey's current status and evaluate the remaining duration until the passenger reaches
their destination. The passengers will be provided to log into the system and check the
status of the journey. The vehicle tracking feature is appreciated widely at times of
emergencies such as accidents, as at the time of accidents, the tracking device triggers an
emergency alarm that simultaneously informs the just cabs attendants as well as the
nearby hospital units or medical clinics about the incident and thereby asking for
immediate help.
 Tools/Environment
Hardware resources:
-(for code development purpose)
-OS: Windows 11
-Memory: 8GB
-storage: 512 GB
-Processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz 2.42 GHz

Software resources:
-(for code development purpose)
-the programming base functions and structure can be designed using code blocks/ dev c++.
-using c++ programming to log in to the code in the management system.
 ANALYSIS DOCUMENT

Analyzing documents helps researchers understand and categorize primary

sources or original accounts from people who had personal experiences with
the topic. When developing their studies, researchers use established sources
to gather ideas and evidence to support their claims. This process allows
researchers to evaluate the quality and purpose of the documents they use to
determine if the information they contain will benefit their studies. Learning
more about this process may help you better organize your resources and
perform research more effectively.
Uses of document analysis Providing context within research:-
• Introducing questions researchers may ask.
• Suggesting situations researchers should observe.
• Providing additional insights researchers may find valuable.
• Giving researchers a way to track the development of their studies.
 Testing & Validation

Till now the database design, user interface design, and implementation are complete. The
system now is tested for its functionality, validity, and performance. Test the system, and a
wide variety of tests are conducted to ensure that the system matches the identified
user requirements and concepts. This chapter focuses on testing the developed systems using
different test strategies to verify their correctness and user acceptance. Testing is the process
of executing a program to find an error. A good test case has a high probability of finding an
as-yet-undiscovered error. A successful test uncovers an as-yet-undiscovered error.

The development of software systems involves a series of production activities where

opportunities for the injection of human fallibility are enormous. Errors may begin to occur
at the very inception of the process where the objectives may be enormously or imperfectly
specified, as well as in later design and development stages. Because of the human ability
to perform and communicate with perfection, software development is accompanied by
quality assurance activity. Software testing is a critical element of software quality assurance
and represents the ultimate review of specification, design, and coding. And it needs to be
done in almost every phase of the product development life cycle not just before a product is
handed to a customer. The following are some attributes of a good test:
„h A good test has a high probability of f 
finding an error. To achieve this goal the tester must understand the software and attempt to
develop a mental picture of how the software may fail. Ideally, the classes of failure
are probed.
„h A good test is not redundant: testing time and resources are limited There is no point in
conducting a test that has the same purpose as another test. Every test should have a different
purpose.
„h A good test should be best of the breed. A group of tests with similar intent time and
resource limitations
may militate for executing only a subset of these tests. In such cases, the tester that has the
highest likelihood of uncovering a whole class of errors should be used.
„h A good test should be neither too simple nor too complex: although it is sometimes
possible to combine a series of tests into one test case, the possible side effects associated
with this approach may mask errors. In general, each test should be executed separately.

Unit Testing:
Unit testing focuses verification effort on the smallest unit software design- the module.
Using the procedural design description as a guide, important control paths are tested
to uncover errors within the boundary of the module. The module interface is tested to ensure
that information properly flows into and out of the program unit under test. The local data
structure is examined to ensure that data stored temporarily maintains its integrity during all
steps in algorithmic execution. Boundary conditions are tested to ensure that the module
operates properly at boundaries established to limit or restrict processing. All independent
paths (base paths) through the control structure are exercised to ensure that all elements in
a module have been executed at least once. And finally, all error-handling paths are tested.
The application interface of our system was unit tested at all levels of implementation, right
from the start of code writing, to integrating the code with other modules. Every module was
tested fully to check its syntax and logical correctness. Error handling was implemented into
relevant modules so that the code doesn’t crash on errors.
Integration Testing:
Integration testing is a systematic technique for constructing the program structures while
conducting tests to uncover errors associated with interfacing, the objective is to take unit-
tested modules and build a program structure that has been dictated by design. The user
interface of i-Admit was developed in modules. All of them were joined together to make the
complete running application. While integrating these modules, integration testing was
performed to verify that they meet interfacing requirements and pass relevant information
among themselves. In the end, the complete program structure was tested to ensure the
interoperability of all the modules.

System Testing:
Ultimately software is incorporated with other system elements (new hardware, information),
and a series of system, integration, and validation tests are conducted. It is a series of
different tests whose primary purpose is to fully exercise the computer-based system.
Although each test has a different purpose all work to verify that all system elements have
been properly integrated and perform allocated functions. System testing of this system was
performed at the development lab of this system by integrating the functional systems to
imitate the actual work environment. Since no special hardware was needed for this purpose,
the testing proceeded and succeeded with no errors.

Validation Testing:
At the culmination of integration testing software is completely assembled as a package:
interfacing errors have been uncovered and corrected and a final series of software tests
 – Validation Testing may begin. Validation can be defined in many ways, but a simple
definition is that validation succeeds when software functions in a manner that can be
reasonably expected by the customer. Software validation is achieved through a series of
Black Box tests that demonstrate conformity with requirements.