A

PROJECT REPORT
ON
RTO management system

Towards partial fulfilment of the requirement in

2nd Semester BCA/B.Sc. IT/IMCA 2021-22
Submitted By: -
210510113078 Parekh Kuldeep Vineshbhai
210510113086 Patel Deep Alpeshkumar
210510113109 Saini Amit Omprakash

Submitted To: -

Parul Institute of Computer Application,

Parul University.
Under the Guidance of
Prof. Shraddha Shah
 Acknowledgement
The success and final outcome of this project required a lot of guidance and assistance from
many people and we are extremely privileged to have got this all along the completion of our
project. All that we have done is only due to such supervision and assistance and we would
not forget to thank them.

I respect and thank Dr. Priya Swaminarayan, Dean, and FITCS for providing us an
opportunity to do the project work in BCA and giving us all support and guidance, which
made us complete the project duly. We are extremely thankful to Mam for providing her
support and guidance, although she had busy schedule managing the academic affairs.

We would not forget to remember Prof. Hina Chokshi, HOD, BCA department for her
encouragement and more over for her timely support and guidance till the completion of our
project work.

We owe our deep gratitude to our project guide Prof.Sradhdha Shah, who took keen interest
on our project work and guided us all along, till the completion of our project work by
providing all the necessary information for developing a good system.

I am thankful to and fortunate enough to get constant encouragement, support and guidance
from our Parents, all Teaching staffs of BCA Department which helped us in successfully
completing our project work. Also, we would like to extend our sincere esteems to all staff in
laboratory for their timely support.

[Parekh Kuldeep] [210510113078]

[Patel Deep] [210510113086]

[Saini Amit] [210510113109]

 PARUL INSTITUTE OF COMPUTER APPLICATION

CERTIFICATE

This is to certify that Kuldeep , Deep , Amit the student(s) of Parul Institute of
Computer Application, has/have satisfactorily completed the project entitled
“RTO Management System” as a part of course curriculum in BCA/B.Sc.
IT/IMCA semester-II for the academic year 2021-2022 under guidance of Dr.
/Prof. Shraddha Shah .

Enrolment Number: 210510113078

Enrolment Number: 210510113086

Enrolment Number: 210510113109

Quality of work Grade Sign of Internal

guide
Poor / Average / B /B+ / A / A+
Good /
Excellent

Date of submission:

HOD, Principal,

Prof. Hina Chokshi Dr. Priya Swaminarayan

 INDEX
Content Page No.
1. Introduction to Project System 6

2. System Requirement Specification 8

2.1 Introduction to SRS 8

2.2 Hardware Requirement 8

2.3 Software Requirement 8

2.4 System Users 9

2.5 Description of User Role 9

2.6 System Modules 9

2.7 Description of Modules 9

2.8 Timeline Chart 10

3. System Flow Diagram 13

4. Data Flow Diagram (All Levels of DFDs) 13

5. Use Case Diagram 18

6. Data Dictionary 20

7. Screenshots of Development Phase -1 23

8. Screenshots of Development Phase -2 25

9. Screenshots of Development Phase -3 28

10. Conclusion 34

11. Future Enhancement 35

12. References 36
 ABSTRACT

 RTO Information System (RTO) is an online information source developed for

Road Transport Authority to facilitate the users in applying for various licenses
and registrations. This tool has been designed to facilitate the flow of information
within the organization. RTO provides the facility of applying licenses online,
issuance of permanent license, tax challans, and receiving payments against
challans.
 The Existing system of RTO services has been is usage for two years. The
existing system is not giving accurate results while doing transactions. It doesn’t
provide security, anyone enter into the system and can do their own transactions.
It is not flexible in generating reports and many manual processes are made
computerized.

 In this System It is not efficient in performing office work in RTO services, It includes
much manual process and time consuming, It is not user friendly, Maintains local data
base. It is not Generating Accurate Reports. To overcome problems in the existing
System a new RTO services “Road Transport Authority Information System” is
proposed after study of system. The objectives of proposed system are: Ensure data
integrity and security, less manpower, Generate accurate reports, Accurate handling in
multiple details.
1. Intorduction to project system

Research may be very broadly defined as systematic gathering of data and information and
its analysis for advancement of knowledge in any subject. Research attempts to find
answer intellectual and practical questions through application of systematic methods.

a. Surveys:

Surveys involve collecting information, usually from fairly large groups of people, by
means of questionnaires but other techniques such as interviews or telephoning may
also be used. There are different types of survey.

b. Case Studies:

Case studies usually involve the detailed study of a particular case (a person or small
group). Various methods of data collection and analysis are used but this typically
includes observation and interviews and may involve consulting other people and
personal or public records.

c. Experiment:

People who take part in research involving experiments might be asked to complete
various tests to measure their cognitive abilities (e.g., word recall, attention,
concentration, reasoning ability etc.) usually verbally, on paper or by computer.

d. Interviews:

Interviews are usually carried out in person i.e., face-to-face but can also be
administered by telephone or using more advance computer technology such as Skype.
Sometimes they are held in the interviewee’s home, sometimes at a more neutral place.
RTO management

1.2 Feasibility Study:

Feasibility is the measure of how beneficial or practical the development of information

system will be to an organization. Feasibility study is a process to check possibilities of
system development. It is a method to check various different requirements and availability
of financial & technical resources There are three aspects in the feasibility study portion of
the preliminary investigation.

1) Technical Feasibility
2) Economical Feasibility

3) Operational Feasibility.

1.3. Technical Feasibility:

Evaluating the technical feasibility is the trickiest part of a feasibility study. This is
because, .at this point in time, not too many detailed designs of the system, making it
difficult to access issues like performance, costs on (on account of the kind of
technology to be deployed) etc. A number of issues have to be considered while doing a
technical analysis. Understand the different technologies involved in the proposed
system before commencing the project we have to be very clear about what are the
technologies that are to be required for the development of the new system. Find out
whether the organization currently possesses the required technologies. Is the required
technology available with the organization.
Frontend: HTML, CSS, PHP, JavaScript.
Backend: MySQL

1.4 Economical Feasibility:

Economic feasibility attempts 2 weigh the costs of developing and implementing a new
system, against the benefits that would accrue from having the new system in place.
This feasibility study gives the top management the economic justification for the new
system. A simple economic analysis which gives the actual comparison of costs and
benefits are much more meaningful in this case. In addition, this proves to be a useful
point of reference to compare actual costs as the project progresses. There could be
various types of intangible benefits on account of automation. These could include
increased customer satisfaction, improvement in product quality better decision-making
timeliness of information, expediting activities, improved accuracy of operations, better
documentation and record keeping, faster retrieval of information, better employee
morale.
RTO management

2. System Requirements Specification:

2.1. Introduction of SRS:

A software requirements specification (SRS) is a description of a software system to be

developed. It lays out functional and non-functional requirements, and may include a
set of use cases that describe user interactions that the software must provide.

Need of SRS?
In order to fully understand one’s project, it is very important that they come up with a
SRS listing out their requirements, how are they going to meet it and how will they
complete the project. It helps the team to save upon their time as they are able to
comprehend how are going to go about the project. Doing this also enables the team to
find out about the limitations and risks early on.

2.2 Hardware Requirement

Hardware Components Specification

Processor Intel core I3,/I5
RAM 4GB/8GB
Hard disk 512GB/1TB
Monitor 15.6 colour monitor or advance
Device Keyboard, Mouse

2.3 Software Requirement

Name of component Specification

Operating System WindowsXP,windows10
Control Panel Xampp Control Panel/Wamp
Control Panel
Software development kit Google Chrome, Internet Explorer,
Mozilla Firefox ( any appropriate
or suitable browser)
Programming Language PHP, HTML, JAVASCRIPT

Server Apache Web Server

Database MySQL
RTO management

2.4 System user

2.5 Description of User Role
 Admin
 Citizen
 Government

2.6 Modules

 Admin
 User

2.7 Description of Module:

2.7.1: Admin Module:

 Admin can update the act and rules.

 Admin can manage the user information.
 Admin can cancel the user registration.
 Admin can manage the user account.
 Admin can update the news.
 Admin can manage learner’s license
 Admin can manage driving license
 Admin view the complaints/query

2.7.2: User Module:

 User can see the information section.

 User can registration.
 User can login.
 User can change the password.
 User can apply for leaner’s license.
 User can apply for driving license.
 User can view the test detail.
 User can submit the complaints.
RTO management

2.8 Timeline Chat:

Development 75 Days Duration

phase N
(days)
0to10 11to20 21to30 31to40 41to50 51to75
days Days days days days Days

Requirement 07
Gathering

Analysis 09

Design 10

Development 13
Phase 1

Development 13
Phase 2

Development 13
Phase 3

Documentation 10

Total time 75
(Days)
RTO management

2.9 Technology Description:

1. PHP:

Hypertext Pre-processor (PHP). is a general-purpose scripting language especially

suited to web development. [It was originally created by Danish-
Canadian programmer Ramus in 1994. The PHP reference implementation is now
produced by The PHP Group. PHP originally stood for Personal Home Page. but it now
stands for the recursive initialise PHP: Hypertext Pre-processor.

2. HTML:

Hypertext Mark-up Language (HTML) is the standard mark-up language for

documents designed to be displayed in a web browser. It can be assisted by
technologies such as Cascading Style Sheets (CSS) and scripting languages such
as JavaScript. Web browsers receive HTML documents from a web server or from
local storage and render the documents into multimedia web pages. HTML describes
the structure of a web page semantically and originally included cues for the
appearance of the document.

3. CSS:

Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a mark-up language such as HTML. CSS is a
cornerstone technology of the World Wide Web, alongside HTML and JavaScript. CSS
is designed to enable the separation of presentation and content,
including layout, colours, and fonts. This separation can improve content accessibility,
provide more flexibility and control in the specification of presentation characteristics,
enable multiple web pages to share formatting by specifying the relevant CSS in a
separate .CSS file which reduces complexity and repetition in the structural content as
well as enabling the .CSS file to be cached to improve the page load speed between the
pages that share the file and its formatting.

2.10 Features and limitation:

4.1.1 Advantages:

 Facilities ease of operation.

 Ensure data integrity and security.
 Less manpower.
 Accurate handing in multiple details of multiple customers.
RTO management

4.1.2 Disadvantages:

 It is not efficient in performing office work in RTO services.

 It is not user friendly.
 Maintains local data base.
It includes much manual process and time consuming
RTO management

4. Data Flow Diagram:

4.1. Context Level DFD’s:

Figure 1: context level DFD’s

RTO management

4.2. Level 1 DFD’s:

4.2.1. Admin side level 1 DFD’s:

Figure 2: admin side level 1 DFD’s

RTO management

4.2.2. User side level 1 DFD’s:

Figure 3: user side level 1 DFD’s

RTO management

4.3. Level 2 DFD’s:

4.3.1. Admin side level 2 DFD’s:

Figure 4: admin side level 2 DFD’s

RTO management

4.3.2. User side level 2 DFD’s:

Figure 5: user side level 2 DFD’s

RTO management

5. Use Case Diagram:

5.1. Admin side:

Figure 6: admin side use case diagram

RTO management

5.2 User side:

Figure 7: user side use case diagram.

RTO management

6. Data Dictionary:

i) Citizen: -user information form

Sr. No Name Data Type Size Constraint Description
1 First_Name VARCHAR 30 PK First Name
2 Middle_Name VARCHAR 30 Not Null Middle Name
3 Last_Name VARCHAR 30 Not Null Last Name
4 Aadhar CHAR 12 Not Null Aadhar
5 Gender CHAR 1 Not Null Gender
6 DOB DATE Not Null Date of birth
7 Phone_no CHAR 10 Not Null Phone number
8 Mail_ID VARCHAR 50 Not Null E-mail

ii) Address: - user address table

Sr. No Name Data Type Size Constraint Description

1 Aadhar CHAR 12 PK, FK Aadhar
2 Street VARCHAR 100 Not Null Street
3 City VARCHAR 30 Not Null City
4 State VARCHAR 20 Not Null State

iii) Offices: -RTO office address

S.NO Name Data Type Size Constraint Description

1 District VARCHAR 30 PK District
2 Rto_Address VARCHAR 200 Not Null RTO address

iv) Inspector: -admin can login.

S.NO Name Data Type Size Constraint Description

1 ID INT 10 PK Id
2 Username VARCHAR 50 Not Null Username
3 Password VARCHAR 100 Not Null Password
4 Privilege VARCHAR 5 Not Null Privilege
RTO management

v) LLR: -user learner’s license registration

S.NO Name Date Type Size Constraint Description

1 Aadhar CHAR 20 FK Aadhar
2 Name VARCHAR 20 Not Null Name
3 Cov VARCHAR 20 Not Null Cov
4 Edate DATE Not Null End date
5 E id VARCHAR 10 Not Null Id
6 Llr id INT 10 PK LLR id
7 E pwd CHAR 10 Not Null password
8 Password VARCHAR 50 Not Null Password
9 Mail_ID VARCHAR 50 Not Null e-mail
10 Llr_status INT 10 Not Null Llr status
11 Llr_issue_date DATE Not Null LLR issue date

vi) Reg: -user registration form.

S. No Name Data Type Size User Description

1 Aadhar CHAR 12 FK Aadhar

2 Name VARCHAR 30 Not Null Name
3 Cov VARCHAR 30 Not Null Cov
4 Model VARCHAR 20 Not Null Model
5 Company VARCHAR 20 Not Null Company
6 Reg. Date DATE Not Null Date
7 Reg. Id INT 10 PK Id
8 Password VARCHAR 30 Not Null Password
9 Mail_ID VARCHAR 50 Not Null Email
10 Reg. Status INT 10 Not Null Status
11 Reg. Issue date DATE Not Null Date
12 Vehicle no. VARCHAR 20 Not Null Number
13 Reg. Expiry date DATE Not Null Exp. date
RTO management

vii) DL :- driving license registration.

S.NO Name Data Type Size Constraint Description
1 Aadhar CHAR 12 FK Aadhar
2 Name VARCHAR 30 Not Null Name
3 Cov VARCHAR 20 Not Null Cov
4 E date DATE Not Null Date
5 E id VARCHAR 10 Not Null Id
6 DL id INT 10 PK Id
7 Password VARCHAR 50 Not Null Password
8 Mail_ID VARCHAR 50 Not Null Email
9 Dl_status INT 10 Not Null Status
10 Dl-Issue date DATE Not Null Date

viii) License :- view the license detail

S.NO Name Data Type Size Constraint Description

1 Id INT 10 PK ID
2 Aadhar CHAR 12 FK Aadhar
3 Name VARCHAR 30 Not Null Name
4 License_no VARCHAR 20 Not Null Number
5 Cov VARCHAR 20 Not Null Cov
6 License_Issue_date DATE Not Null Issue Date
7 License_Exp. Date DATE Not Null Exp. Date
8 Mail_ID VARCHAR 50 Not Null Mail

ix) Complaint :- user complaints submit.

S.NO Name Data Type Size Constraint Description
1 Aadhar CHAR 12 FK Aadhar
2 C date DATE Not Null Date
3 C desc TEXT Not Null Description
4 C id INT 10 PK Id
RTO management

7. Screenshots of Development Phase -1

7.1. Home page:

Screenshot:1 Home page of RTO management system.

This the home page for RTO management system. user can see the LLR, DLR, vehicle
Registration. And user can also see the LLR and DLR status check.
RTO management

7.2. Admin login page:

Screenshot 2: admin login page

Admin login page only admin can login the page. Admin can login for valid id and
password. Admin can login successfully the see the admin panel.
RTO management

8. Screenshots of Development Phase -2

7.3. New Vehicle registration page:

Screenshot 3: new vehicle registration

This section is for the citizens to register their newly bought vehicles. The citizen will
be asked to apply through their Aadhaar number and a password to be used for
authentication. The citizen will be asked to submit the details of the vehicle such as the
category of vehicle, vehicle company and the vehicle model. After the details are
entered, the system will generate an appropriate date for the documents verification at
the nearest RTO office.
RTO management
RTO management
RTO management

9. Screenshots of Development Phase -3

RTO management

ss
RTO management
RTO management
RTO management
RTO management
RTO management

10. Conclusion:

RTO OFFICE MANAGEMENT SYSTEM is a web application, which is very useful for
RTO works completion online. Here we are developing such types of the module which
help to reduce the RTO work manually and it helps to save the time of the user.
Considerably reduce the corruption in the transport department.
RTO management

11. Future Enhancement:

This system is also helpful for Traffic police also. The traffic police to be more
effective in controlling repeat violators of traffic rules. Traffic Police have the database
of registration numbers as well as the history of driving license holders. When a traffic
policeman would enter the details of any vehicle caught violating traffic rules, it would
give the complete details of that particular vehicle including the name and address of
the owner and the make, model and other details of the vehicle. Not only this, the
details of the driving license holder would also be available. Therefore, enhanced
penalties would be imposed for repetition of violation of traffic rules. Fake registration
plates, if any, would be detected immediately.

RTO OFFICE MANAGEMENT SYSTEM is a web application, which is very useful

for RTO works completion online. Here we are developing such types of the module
which help to reduce the RTO work manually and it helps to save the time of the user.
Considerably reduce the corruption in the transport department. Keep the license
documents safely.
RTO management

12. References & Bibliography:

1] https://www.studentprojectguide.com/java-projects/rto-management-system/amp/

2]https://www.ijarnd.com/manuscripts/v2i3/V2I3-1157.pdf

3]https://youtu.be/aIsu9SPcGbU

4] Xiao sheng Yu, Yichang, China CAI Yi, "Design and Implementation of the Website
Based on PHP & MYSQL", in E-Product E-Service and E- Entertainment (ICEEE), pp.
[1 – 4]