Professional Documents
Culture Documents
Candidate Declaration
I declare that 4 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.
th
Candidates sign:
Signature of guide:
Candidates sign:
Signature of guide:
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. facultyname IT Department, Kalol Institute of Technology & Research Centre, Kalol
Prof. Hitesh C. Patel Head of, IT Department, Kalol Institute of Technology & 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. facultyname IT Department, Kalol Institute of Technology & Research Centre, Kalol
Prof. Hitesh C. Patel Head of, IT Department, Kalol Institute of Technology & 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.
ABSTRACT
This system is all about R.T.O. Management System. Now days we see faster & busier lives of everybody, so that busier person dont have 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 sufficient information 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 clas s
State Diagram
:
:
State Transition
: :
Entry Exit
Usecase Diagram
Sy stem Boundary
: :
Usecase Uses
Actor
Sequence Diagram
Object Lifeline
: :
Activation Message
Constraint
Activity Diagram
: Action State
Decision
: : :
:
TABLE OF CONTENTS
Title Page 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
Name
1. 2.
Page No.
3.
4.
5.
Class diagram..4 State diagram...5 1. For license issue.6 2. For registration of vehicle..7 3. For transfer of vehicle8 Usecase diagram..9 1. For license issue...10 2. For registration of vehicle11 3. For transfer of vehicle..12 Sequence diagram..13 1. For license issue...15 2. For registration of vehicle17 3. For transfer of vehicle..19 Activity diagram20 1. For license issue...21 2. For registration of vehicle22 3. For transfer of vehicle..23
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.
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.
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.
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.
10
11
12
13
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.
14
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.
15
16
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.
17
18
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.
19
20
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.
21
22
23
24
2 Agent agent_id
Index
1 2 3 4 5 6
Name
agent_id f_name l_name salary ph_no agent_type
Data type
integer(10) string(15) string(15) long integer(10) string(10)
Description
Id of agent Name of agent Surname of agent Salary of agent Contact for agent Type of field work
25
3 Employee job_id, employee_id Data type integer(10) long integer(10) date string(15) Description Job id of employee Salary of employee Employee id of employee Joining date of job Designation of employee
4 Customer Customer_id Data type integer(10) integer(12) string(150) integer(15) integer(10) Description Id of customer Id of license Address on electric bill Pan no. of customer Number on voter card
Description Name of holder Surname of holder Birth date of holder Address of holder
26
5 6 7 8 9 10 11 12
Age of holder Id no. of license Gender of holder type of license Email id of holder Nationality of holder Blood group of holder Vehicle type for license
6 Crime_record unique_id Data type integer(3) long string(20) string(15) string(20) integer(16) Description Law Crime code Money to pay Types of crime Name of criminal Name of criminal Unique id of criminal
7 Registration regi_no Data type string(15) string(15) integer(16) string(10) integer(15) integer(8) string(15) Description Name of owner Surname of owner Unique id of owner Type of vehicle No of engine of vehicle Model no of vehicle Category of registration no
27
8 Vehicle engine_no Data type integer(15) string(5) integer(4) integer(8) date integer(5) Description No. of engine of vehicle Type of engine of vehicle Number of rto registry Id no. of PUC Date of PUC Number of regi
9 Transfer unique_id Data type integer(16) string(15) string(15) string(12) string(15) integer(16) date Description Unique id of seller Name of seller Surname of seller Number of rto registry Type of transfer vehicle Unique id of buyer Date of transfer
28
10 Insurance ins_no Data type integer(5) integer(16) string(15) date long Description Number of insurance Number of client Name of client Due date of insurance Amount of insurance
29
13 Private_veh unique_id Data type string(15) string(15) integer string(12) Description Name of owner Name of owner Unique id of owner Type of vehicle
14 Government_veh batch-no Data type integer(4) string(12) Description No of batch Type of vehicle
30
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.
31
32
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.
33
Chapter:8 References
Object Oriented Modeling & Design with UML, Michel R Blaha and James R Rambaugh, Pearson. Web links: https://sarathi.nic.in