R.T.O System

KALOL INSTITUTE OF TECHNOLOGY

& RESEARCH CENTRE

Candidate Declaration

I declare that 4th semester report entitled R.T.O. Management System is my own work conducted under the supervision of the guide

Faculty name.

I further declare that to the best of my knowledge the report for B.E. forth semester does not contain part of the work which has been submitted for the award of B.E. Degree either in this or any other university without proper citation.

Candidates sign:Signature of guide:

Candidates namePatel twinkal m

Er. No: 110260116047

KALOL INSTITUTE OF TECHNOLOGY

& RESEARCH CENTRE

Candidate Declaration

I declare that 4th semester report entitled R.T.O. Management System is my own work conducted under the supervision of the guide faculty name.

I further declare that to the best of my knowledge the report for B.E. forth semester does not contain part of the work which has been submitted for the award of B.E. Degree either in this or any other university without proper citation.

Candidates sign:Signature of guide:

Candidates name:

Nikki R. Patel

Er. No: 110260116025

CERTIFICATE

This is to certify that the project entitled R.T.O. Management System is a bonafide report of the work carried out by Ms. Trisha V. Patel under the guidance and supervision for the award of the degree of Bachelor of Information Technology at KALOL INSTITUTE OF TECHNOLOGY & RESEARCH CENTRE, Kalol, Gujarat.

To the best of my knowledge and belief, this work embodies the work of candidate himself/herself, has duly been completed, fulfills the requirement of the ordinance relating to the Bachelor Degree of The University and is up to the standard in respect of content, presentation and language of being referred to the examiner.

Asst. Prof. facultynameProf. Hitesh C. Patel

IT Department,Head of, IT Department,

Kalol Institute of TechnologyKalol Institute of Technology

& Research Centre, Kalol& Research Centre, Kalol

CERTIFICATE

This is to certify that the project entitled R.T.O. Management System is a bonafide report of the work carried out by Ms. Nikki R.

Patel under the guidance and supervision for the award of the degree of Bachelor of Information Technology at KALOL INSTITUTE OF TECHNOLOGY & RESEARCH CENTRE, Kalol, Gujarat.

To the best of my knowledge and belief, this work embodies the work of candidate himself/herself, has duly been completed, fulfills the requirement of the ordinance relating to the Bachelor Degree of The University and is up to the standard in respect of content, presentation and language of being referred to the examiner.

Asst. Prof. facultynameProf. Hitesh C. Patel

IT Department,Head of, IT Department,

Kalol Institute of TechnologyKalol Institute of Technology

& Research Centre, Kalol& Research Centre, Kalol

ACKNOWLEDGEMENT

With immense pleasure we would to present this report on our topic R.T.O. Management System. We are thankful to all that have

helped us a lot for successful completion of our project and providing us courage for completing the work.

We are thankful to our Head Of the Department Prof. Hitesh C. Patel, our internal faculty guide faculty name , for providing guidance throughout our work giving us their valuable time.

At last, we would like to thank our parents and friends who have directly or indirectly helped us in making the project work successfully.

Candidates Name Twinkal .m. Patel (110260116047)

ABSTRACT

This system is all about R.T.O. Management System. Now days we see faster & busier lives of everybody, so that busier person donthave any leisure time for extra work like getting license or other R.T.O.

related services. Hence this application provides a good solution for those busy people. And so we organize this great facility that is R.T.O. Management System. This application provides the sufficientinformation about works done at R.T.O for those people.

This type of project provides facility (getting license, registration

of new vehicle, transfer vehicle) to both the employees as well as to the citizens. people can do their work at their time and their convenience.

Graphical Notations

Class Diagram

Diagram:Description

:Class

:Association

:Generalization

:Association class

State Diagram

:State

Transition

:Entry

:Exit

Usecase Diagram

:System Boundary

:Usecase

:Uses

:Actor

Sequence Diagram

Object Lifeline

:Activation

:Message

:Constraint

Activity Diagram

:Action State

:Decision

:Entry

:Exit

:Control Flow

:Fork & Join Line

TABLE OF CONTENTS

TitlePage No.

Acknowledgement

Abstract

List of figures

Graphical notation

Chapter:1 Introduction1

1.1 Scope

Chapter:2 System Requirements.....2

2.1 Hardware Requirements

2.2 Software Requirements

Chapter:3 Diagrams.3

3.1. Class diagram

3.2 State diagram

3.2.1 State for License issue

3.2.2 State for Regitration of vehicle

3.2.3 State for Transfer of vehicle

3.3 Usecase diagram

3.3.1 Usecase for License issue

3.3.2 Usecase for Registration of vehicle

3.3.3 Usecase for Transfer the vehicle

3.4 Sequence diagram

3.4.1 Sequence for License issue

3.4.2 Sequence for Registration of vehicle

3.4.3 Sequence for Transfer the vehicle

3.5 Activity diagram

3.5.1 Activity for License issue

3.5.2 Activity for Registration of vehicle

3.5.3 Activity for Transfer the vehicle

Chapter:4 Data Dictionary...24

Chapter:5 Advantages & Limitations..30

Chapter:6 Future enhancement31

Chapter:7 Conclusion..32 Chapter:8 Referances...33

List of figures

NamePage No.

1. Class diagram..4

2. State diagram...5

1. For license issue.6

2. For registration of vehicle..7

3. For transfer of vehicle8

3. Usecase diagram..9

1. For license issue...10

2. For registration of vehicle11

3. For transfer of vehicle..12

4. Sequence diagram..13




5. Activity diagram20




RTO Management System 1

Chapter:1 Introduction

1.1 Scope

Nowadays life is becoming faster and faster so there is need to make all R.T.O. related processes like getting license, transfer the vehicle from one owner to another, registration of new vehicle stress less and less time consuming.

There is need of storage of data duplication free and retrieval efficiently. This system provide better interaction between all actors who take part in system.

Data related to vehicles, owner of vehicle, registration info can get easily from system.

Kalol Institute of Technology & Research Centre


Chapter:2 System Requirements

2.1 Hardware Requirements

Processor Intel(R) Core(TM) i3 M 330 @ 2.13GHz

1024MB RAM

Hard Disk 500GB

Keyboard

Touchpad

LED Display

2.2 Software Requirements

Microsoft Visio 2007

o For drawing diagrams

Adobe Photoshop CS6

o For other editions

Microsoft Office Word 2010

o For report file



Chapter:3 Diagrams

3.1 Class Diagram

A class is an association that describes properties important to application and ignores the rest background details.

An association is a description of a group of links with common structure and common semantics.

Generalization is the relationship between a class and one or more variations of the class. In this, superclass shares the features to the sub class in hierarchical relationship.





3.2 State Diagram

State model describes the aspects of an object in a system that change over a time. Change of state is a response to the event.

A transition is an instantaneous change from one state to another

state.

A guard condition is a Boolean expression that must be true in order for a transition to occur.

A state diagram is a graph whose nodes are states and directed arrow are transitions.



3.2.1 State diagram for License issue.



3.2.2 State diagram for Registration of vehicle.



3.2.3 State diagram for Transfer of vehicle.



3.3 Usecase Diagram

A usecase is coherent piece of functionality that a system can provide by interacting with actors.

An actor is a direct external user of a system an object or set of objects that communicates directly but that is not part of the system.

A system boundary is boundary that make separation between the system and the external user and other actor.



3.3.1 Usecase diagram for License issue.



3.3.2 Usecase diagram for Registration of vehicle.



3.3.3 Usecase diagram for Transfer of vehicle.



3.4 Sequence Diagram

Scenario is a sequence of events that occurs during one particular execution of a system such for a usecase.

A sequence diagram shows the participants in an interaction and the sequence of message among them.

Each actor as well as the system is represented by a vertical line called life line and each message by a horizontal arrow from the sender to the receiver.



3.4.1 Sequence diagram for License issue.

Scenario

Client pays fees to agent.

Agent or employee provides application form to client.

Client give filled application form to employee.

Client pay token fees to employee.

Employee give token to client.

Agent gives information to client.

Client submit documents to employee.

Employee rejects documents if its insufficient.

Otherwise employee accepts documents.

Client gives exam.

Employee gives result to client.

Client will be rejected if fail.

Otherwise client go for test drive.

Employee gives result to client.

Employee issuing license to client if pass test drive.

Client wishes to agent for service.





3.4.2 Sequence diagram for Registration of vehicle.

Scenario

Client check for availability of vehicle.

Employee displays available vehicles.

Client requests for vehicle to employee.

Employee gives application form.

Client fills application form and give to employee.

Client submits documents to employee.

Employee gives information if required.

Client pays deposit to employee.

Employee gives receipt to client.

Employee register new vehicle to system.

Employee takes confirmation no. from system.

Employee saves information to R.C book.

Employee pass vehicle.

Client get vehicle from employee.





3.4.3 Sequence diagram for Transfer of vehicle.

Scenario

Employee gives application form to the client.

Client pay fees for transformation to employee.

Client fills the form and submit to employee.

Client submits documents to the employee.

Employee gives verification to the client.

Employee gives information to client if required.

Employee ask for confirmation of transfer to client.

Client gives confirmation of transfer to employee.

Employee transfers vehicle to other client.





3.5 Activity Diagram

An activity diagram shows the sequence of steps that make up a complex process such as algorithm or workflow. It focus on operation rather than objects.

If there is more than one successor to an activity, each arrow may be labeled in square bracket that makes branches or also called decision.



3.5.1 Activity diagram for License issue.



3.5.2 Activity diagram for Registration of vehicle.



3.5.3 Activity diagram for Transfer of vehicle.



Chapter:4 Data Dictionary

Table Index

Table Name

Primary key

1

Person

unique_id,

IndexNameData_typeDescription

1f_namestring(15)Name of person

2l_namestring(15)Surname of person

3unique_idinteger(16)Unique id of person

4addressstring(150)Address of person

5genderstring(6)Gender of person

6date_of_birthdateBirthdate of person

7ageinteger(3)Age of person

8contact_nointeger(10)Contact for person

Table index

Table name

Primary key

2

Agent

agent_id

IndexNameData typeDescription

1agent_idinteger(10)Id of agent

2f_namestring(15)Name of agent

3l_namestring(15)Surname of agent

4salarylongSalary of agent

5ph_nointeger(10)Contact for agent

6agent_typestring(10)Type of field work



Table index

Table name

Primary key

3

Employee

job_id, employee_id


1job_idinteger(10)Job id of employee

2salarylongSalary of employee

3employee_idinteger(10)Employee id of employee

4join_datedateJoining date of job

5designationstring(15)Designation of employee

Table index

Table name

Primary key

4

Customer

Customer_id


1customer_idinteger(10)Id of customer

2license_idinteger(12)Id of license

3ele_bill_addstring(150)Address on electric bill

4pan_nointeger(15)Pan no. of customer

5voter_nointeger(10)Number on voter card

Table index

Table name

Primary key

5

License

license_id


1f_namestring(15)Name of holder

2l_namestring(15)Surname of holder

3date_of_birthdate(15)Birth date of holder

4addressstring(150)Address of holder


RTO Management System26

5ageinteger(3)Age of holder

6license_idinteger(12)Id no. of license

7genderstring(6)Gender of holder

8license_typestring(6)type of license

9emailstring(20)Email id of holder

10nationalitystring(15)Nationality of holder

11blood_groupstring(2)Blood group of holder

12vehicle_typestring(6)Vehicle type for license

Table index

Table name

Foreign_key

6

Crime_record

unique_id


1ipc_sectioninteger(3)Law Crime code

2finelongMoney to pay

3crime_typestring(20)Types of crime

4f_namestring(15)Name of criminal

5l_namestring(20)Name of criminal

6unique_idinteger(16)Unique id of criminal

Table index

Table name

Foreign_key

7

Registration

regi_no


1f_namestring(15)Name of owner

2l_namestring(15)Surname of owner

3unique_idinteger(16)Unique id of owner

4vehicle_typestring(10)Type of vehicle

5engine_nointeger(15)No of engine of vehicle

6model_nointeger(8)Model no of vehicle

7categorystring(15)Category of registration no



Table index

Table name

Foreign key

8

Vehicle

engine_no


1engine_nointeger(15)No. of engine of vehicle

2engine_typestring(5)Type of engine of vehicle

3rto_nointeger(4)Number of rto registry

4puc_idinteger(8)Id no. of PUC

5puc_due_datedateDate of PUC

6regi_nointeger(5)Number of regi

Table index

Table name

Foreign key

9

Transfer

unique_id


1unique_idinteger(16)Unique id of seller

2f_namestring(15)Name of seller

3l_namestring(15)Surname of seller

4rto_nostring(12)Number of rto registry

5transfer_typestring(15)Type of transfer vehicle

6new_unique_idinteger(16)Unique id of buyer

7trans_datedateDate of transfer



Table index

Table name

Primary key

10

Insurance

ins_no


1ins_nointeger(5)Number of insurance

2unique_idinteger(16)Number of client

3own_namestring(15)Name of client

4due_datedateDue date of insurance

5amountlongAmount of insurance

Table index

Table name

Foreign key

11

Expire

license_id


1validity_datedateDate of expire

2renew_datedateDate of renew

Table index

Table name

Primary key

12

Model

model_no


1vehicle_namestring(12)Name of vehicle

2company_namestring(12)Name of company

3model_nointeger(8)Number of model



Table index

Table name

Foreign key

13

Private_veh

unique_id


1f_namestring(15)Name of owner

2l_namestring(15)Name of owner

3unique_idintegerUnique id of owner


Table index

Table name

Primary key

14

Government_veh

batch-no


1batch_nointeger(4)No of batch




Chapter:5 Advantages & Limitations

Advantages

This system can remove complexity and make data storage more efficient and safe.

RTO system provide best functionality because it divides man power.

By this system, data duplication and redundancy problem can eliminate.

If any client lose its license then he/she can easily get new from RTO on the bases of old license data.

Data retrieval and manipulation becomes more efficient.

Limitations

RTO system takes time to proceed in license issuing, registration of vehicle, transfer of the vehicle.

People have to do more paper work like collect original copies and duplicate copies.

People have to come to RTO and go through all process of documentation to get new license, registration and transfer of vehicle.



Chapter:6 Future Enhancement

This system can reduce man power utilization.

Time taken by all processes can be reduce.

So time wastage of the people and employees can be reduce.

This system can make file system more efficient and less complex.

It can reduce paper work and new idea utilized.

It can make a new identity proof to reduce paper work and data processing from required information.



Chapter:7 Conclusion

By this system we concluded that to get license, register a new vehicle, and transfer the vehicle this system is best solution.

This system provides good facility to people who all are really busy with tight schedule and dont have time to spend behind all processes.

This system computerize the data processing system and make it easy.



Chapter:8 References

Object Oriented Modeling & Design with UML, Michel R Blaha and James R Rambaugh, Pearson.

Web links:

https://sarathi.nic.in


R.T.O System

Documents

Transcript of R.T.O System