Project Report

On
[Online RTO Management System]
MCA 406

Submitted To:

Submitted By:

Mr. Prabhakar Sharma

Ms. Apoorva Bhargava
(Asst. Prof., Dept. of MCA)

[Name
[Roll No
[Name
[Roll No
[Name
[Roll No

:
:
:
:
:
:

Role of Team members

Rohit Sahu]
0901CA131048]
Vikash Kushwah]
0901CA131056]
Vikash Shivhare]
0901CA131057]

1. [Rohit Sahu]

[System Analyze]

2. [Vikash Kushwah]

[Testing]

3. [Vikash Shivhare]

[System Design]

INDEX
1. Introduction

1.1 Brief Description of Project

1.1.1 Introduction
1.1.2 Purpose
1.1.3 Scope
1.1.4 Benefits
1.1.5 Functional Requirement
1.2 Component Description
1.3 System Requirement
1.4 Tools and Technology Used
2. System Analysis
2.1 Information Gathering
2.2 Existing System
2.3 Proposed System
2.4 SRS
2.4.1 Need for SRS
2.4.2 Software function Overview
2.5 Feasibility Study
2.5.1 Technical Feasibility
2.5.2 Operational Feasibility
2.5.3 Economic Feasibility
3. System Design
3.1 Logical Design
3.1.1 E R Diagram
3.1.2 Data Flow Diagram
3.1.3 Flow Chart
3.2 Database Design
4. System Testing and Implementation
4.1 Testing
4.2 Implementation
5. Bibliography

1. Introduction
1.1 Brief Description of Project

1.1.1 Introduction
The project RTO MANAGEMENT SYSTEM is proposed to install a system that shall
enable the proposed RTO SYSTEM interface with the existing system with maximum
accuracy .This project is very useful for those who are concern with the different
processes on RTO. During study phase, we have done a preliminary analysis
sufficient depth to permit a technical and economic evaluation of proposed system.
As a total manpower based system is currently running for the whole procedures,
designing a new system which makes the whole process online, demands a deep
knowledge about the existing system. Throughout the project we focus on presenting
information and commands in an easy and intelligible manner. The purpose of our
RTO management system is to provide a leading technological tool for the ease of
RTO functions such as Registration, Learners License, and Fitness etc...It will reduce
considerably the difficulties faced on existing system, with minimum error and
difficulties.

1.1.2 Purpose
RTO Office Administration is a government transport organization and the main
purpose of this office is to issue DL, vehicle registrations etc. in this document we
propose the computerized system of managing all the data works. It helps to bring the
smooth flow of work and also increase efficiency.
This document highlight the requirements and also give the guidelines that are
necessary for the development of the project work that is mentioned above. In also
give guidelines in brief about how to design the project.
This project is known to be a pilot project and helps to be prepared by the office of
RTO to maintain records of all the DL that is issued. At the same time it also jot down
the details for the registration of vehicles . When all these works will be started in a
computerized system then it will help to increase the employees efficiency. The scope
of this project is to maintain the records of the DL, registration of vehicles.
Windows XP is the most ideal operating system and Visual Basic 6.0 is used as the
development tool for this project. MS Access is the database that is used. Now the
works of registrations in the office are amended according to the manual system
which requires a lot of time and paperwork. It also decreases the work pressure and
the efficiency of the employees. With the modernization everything will become
computerized thus increasing the efficiency and smooth flow of work. The system
will also help to manage the daily operations quickly and easily.

1.1.3 Scope
This is a project prepared RTO office to maintain all the records like issuing the DL,
Vehicle registration. Once all these get computerized to work efficiency of the
employee will get increases. The RTO management system project consist of two
function module i.e. vehicle registration and license module.

1.1.4 Benefits

Save Energy

In using our system user do not need to waste energy to stand in a

row.
Easy to Access or user friendly
Our system is a very easy to access and user friendly because the
user that cant know about the online service can also be used this
project because it is according to this type of user, so we can say
that our project is user friendly.
24x7 Availability
The user can access our project from anywhere and any time. There
is no need to use project in office timing.
Save Time
Our software is very time consuming because in current time the
user wait for fill a form and wait for a appointment but in our
project the several user go online and do registration on a website
and fill the required field in a form and get appointment for the
license and vehicle registration.

1.1.5 Functional Requirement

Our system has mainly three modules, an administration module, an authorized user
module, and other user module. Various processes involved in these three modules
are:
License Application
Introduction: Any authorized user can upload a form for license application.
Input: Details provided by the users in the downloaded application form.
Process: The administrator will verify the entered data and proceeds it if it is
ok.
Output: User will get a mail regarding the license test.

Vehicle Registration
Introduction: Authorized user can register the vehicle by uploading the form
for vehicle registration.
Input: Details provided by the authorized user in the downloaded application
form.
Process: The administrator proceed it after verifying the details provided by
the user.
Output: User will get a mail regarding the license test.

Mail
Introduction: Administrator can send message to the authorized user regarding
the license renewal and all.
Input: The message sent by the administrator.
Process: The authorized user can read the message from his message box.
Output: The user can be get updated.

Search
Introduction: Administrator and authorized user can select a particular vehicle
and license holder by using license number, vehicle number, or color
Input: The vehicle number license number or the other information about the
vehicle
Process: By entering particular information about the vehicle or license can
retrieve all the
details about that vehicle
Output: The complete details of the vehicle will get.

1.2 Component Description

The system should be design in such a way that the authorized and unauthorized user
can access the project modules and the Administrator give the response of user.

1.3System Requirement
Hardware Requirements
Processor
RAM
Monitor
Keyboard
Mouse
Software Requirements
Operating System.
Developing Tool
Database

:
:
:

Pentium IV 2GHz and Above

2GB RAM
15 Color Monitor

:
:
:

Windows XP
Visual Basic 6.0
MS Access

1.4 Tools and Technology Used

Language
Front-end
Back-end

2. System Analysis

:
:
:

JAVA
HTML, JAVA Script
MY SQL

2.1 Information Gathering

Information gathering can be used for a variety of different reasons; however, the
main benefit with regards to your academic studies is that you will become aware of
more diverse sources, opinions and approaches which can only enhance your
academic work.

2.2 Existing System

A total manual system, which is running without any participation of a computer
definitely have its own disadvantages. We know that the production and use of
vehicles are increasing day by day. Hence the need of RTO is very important now
days. The complex functions such as Registration of vehicles etc. becomes very
difficult if we are using the existing system.
To know about the problems specifically, we have done a detailed study on the whole
procedure of the system which is currently running.
In the existing system of RTO office performs functions such as registration, license.
There are certain procedure and formalities required to perform these functions.
It is essential that the particulars of every vehicle and its owner should be available in
the concerned department or office of Government and that the vehicle should be
distinguishable from other vehicles by sight. The registration mark should be
displayed in specified places and in specified manner. In the registration section,
application for registration of a new vehicle shall be submitted before the Registering
Authority in whose jurisdiction the applicant is residing or having his business and the
vehicle is normally kept. The application for registration shall be made in Form,
within a period of 7 days from the date of delivery of such vehicle excluding the
period of journey.
Many people have craze on their vehicle registration numbers. Some of them want
fancy numbers while the others want numbers according to their belief in the
numerical astrology. Whatever it may, it will be interesting to know about the theory
of formation of vehicle registration numbers in the state, keeping it as a unique
identifier for each vehicle.
In the license section at the RTO, after the verification of the form your knowledge on
traffic rules and regulations as well as interpretation of symbols will be tested.
However, if the need arises, they may take a written test too.
After all this, a learners license will be issued. This license is valid for a period of 6
months and can be renewed for another 6 months just once though. The next time, a
fresh learners license will have to be made following the whole earlier procedure.

2.3 Proposed System

The proposed system is aimed to automate the major processes in the Regional
Transport Office.

 Decomposition of Proposed System

The basic modules in the total procedure are:
Administrator: Administrator is power user. He has the power to verify the
data entered by the user, processing of data and provide appropriate solutions.
Authorized user: Any person who have been authorized by the administrator.
An authorized user should have a user name and password to access detailed
information from the site excluding for accessing general information in
shared, public pages.
User: He is the person who gets the full benefits of this application.
Features of Proposed System

Proposed system is an online system: so any persons can browse the sit and
download & upload the application form.
Less time consuming.
Highly secure in data storing.
It is more users friendly: the sections such as, registration, license etc are
combined together in a single window.
Users can have knowledge about the new rules and regulations from the
informations &
awareness section.
In the online system the repetition of work & duplication of data can be
avoided.

2.4 SRS
Software requirement specification is a document in which completely describe
what the proposed system do it. The basic goal of the requirement phase is to
produce the SRS. Which describe the complete behavior of the proposed
software. SRS is also helpful for the user who use our software to understand thus
own need.

2.4.1 Need for SRS

User do not always know thus needs.

Must analyses and understand the potential.
The requirement process helps clarify needs.
Clear understanding about what is expected.
Requirement errors get manifested in final software.
To satisfy the quality objective must begin with high quality SRS.
SRS error are expensive to fix later.

2.4.2 Software function Overview

This is the software configuration in which the project was shaped. The programming
language used, tools used, etc are described here.
HTML and Java Script is used as front end
Microsoft SQL server is used as back end
Web technology used is ASP.net

2.5 Feasibility Study

Feasibility study is the detailed study expanded from the result of initial investigation.
This is done by investigating the existing system in the area under investigation or
generally ideas about a new system. It is the test of a system proposal according to its
work ability, impact on organization, ability to meet user needs and effective use of
resources. Objective of feasibility study is to acquire a sense of the scope of the
problem. It is carried out to select the best system that meets performance
requirements.

2.5.1 Technical Feasibility

Technical feasibility centers on existing system and to what extent it can support
proposed modifications. It involves financial enhancement.
This evaluation determines whether the technology needed for the proposed system is
available or not. This is concerned with specifying satisfy the user requirements. The
technical needs of the system may include front-end and back-end selection.
An important issue for the development of a project is the selection of suitable
frontend and back-end.
Based on some aspects, we select the most suitable platform that suits the needs of the
organization.

2.5.2 Operational Feasibility

The present system is easily understandable. The users are presented with friendly
user interface that helps them to understand the flow of the system more easily.
Maximum transparency has been provided. The new system is very much user
friendly andoperational cost is bearable. The maintenance and working of the new
system needs less human efforts. The proposed project is beneficial to the
organizational and is user friendly.
The system is directly used by the users and needs no other operators to coordinates
the system. So the system can be judged operationally feasible.

2.5.3 Economic Feasibility

Economic feasibility is used to determine the benefits and savings expected from the
candidate system and to compare them with costs incurred. If benefits outweigh cost,
then decision will be to design and implement system. Otherwise, alterations will
have to be made to the proposed system. The proposed system is economically
feasible.

3. System Design
System design typically focuses on the external interfaces of the modules and cannot
be extended to specify the internals. Detailed design is one way in which the design
can be communicated precisely and completely to whatever degree of detail desired
by the designer. The purpose of the Software Design Document is to provide a
description of the design of a system fully enough to allow for software development
to proceed with an understanding of what is to be built and how it is expected to built.
The Software Design Document provides information necessary to provide
description of the details for the software and system to be built. This Software Design
Document is for a base level system which will work as a proof of concept for the use
of building a quality control system that provides a base level of functionality to show
feasibility for large scale production use.

3.1 Logical Design

3.1.1 E R Diagram
The Entity Relationship Diagram (also known as an ERD or ER diagram) is a network
model that describes the stored data layout of a system at a high level of abstraction.
The ERD should represent the relationships between all the entities. Any two entities
must be connected to each other by some relationship set and type of relationship
should also be specified.
Components of an ERD
There are two major components of an ERD:
Entity:
It is defined as any object about which information is collected. It has different
attributes which describe it. It should be represented by a regular box as shown below:
Relationships:
Entities are connected to one another by relationships. a relationship represents a set
of connections between entities and represent by a diamond.
A relationship is a two-directional significant association.
There are three types of relationships
One-to-one relationships
One-to-many relationships
Many-to-many relationship

USER
Two
Wheeler

LMV

Four Wheeler

HMV

Apply for
Registrati
on

License

ISA

Four Wheeler

Two Wheeler

E_no.

C_no.

ISA

Color

C_no.

E_no.
M_no.

L_License

Color

U_id

P_License

U_id

M_no.

sex

sex
U_add

U_add

3.1.2 Data Flow Diagram

As the name suggests DFD is a representation of the data flow within the system. It
includes processes, data stores and external interfaces to the system. External
interfaces may be treated as external entities. DFDs can by explode to sub-processes.
Any two entities/data stores must be connected to each other by some process. The
processes cannot be directly connected to each other. The following are the four major
components of the DFD:
Process
External Entity
Data Store
Connector
The DFD is also known as the bubble chart. It is a simple graphical formalism that
can be used to represent a
system in terms of the input data to the system, various processing carried out in these
data and the output
data generated by the system. The main reason why this DFD technique is so popular
is probably because of
the facts that DFD is very simple formalism. It is simple to understand and use. A
DFD model uses a very
limited number of primitive symbols to represent the functions performed by a system
and the data flow
among these systems. Starting with a set of highlevel
functions that a system performance of DFD model in
hierarchically it represents various sub functions. The Data Flow Diagramming
technique also follows a
simple a simple set of intuitive concepts and rules.

0-Level DFD
Process
USER

ADMIN

Request

ISSUE & REJECT

Issue License
Response

Issue vehicle
Registration

License

Registration

1-Level DFD

3.1.3 Flow Chart

3.2 Database Design

A data base is a collection of related data. By data, we mean known facts that can be
recorded and that have implicit meaning. Defining a database involves specifying the
data types, structures, and constraints of the data to be stored in the database. The
general objective is to make database access easy, quick, inexpensive and flexible for
the users. Normalization is done to get internal consistency of data and to have
minimum redundancy and maximum stability. This ensures minimizing data storage
required and optimizing for updates.
The data in the system has to be stored and retrieved from database. Designing the
database is a part detailed designing. Data elements and data structures to be stored
have been identified in the analysis stage. They are structured and put together to
design the data storage and retrieval system.
MS SQL is the database of the system. It provide a secure, accurate and data
management.
The database of our project is designed using SQL and it comprise of 5 tables.
Admin Login
Signup
User Login
Vehicle Registration
License
1. Table Name : Admin Login
NAME
Description
Data Type
Size
Constraints
A_ID
Name of Admin
varchar
30
Primary key
A_Pass
Password
Varchar
30
2. Table Name : Signup
NAME
Description
ID
User ID
Name
Name of the user
Sex
Sex
DOB
Date of birth
Mob
Mobile number
Father name
Name of father
Add
Address
E-mail
Email ID
Path of Photo
Path of photo
Path of DOB
Path of dob
Path of add
Path of add

Data Type
Int
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar

Size
32
25
7
12
15
30
30
30
30
30
30

Constraints
Primary key

3. Table Name : User Login

NAME
Description
U_ID
Name of User
U_Pass
Password

Data Type
varchar
Varchar

Size
30
30

Constraints

4. Table Name : Vehicle Registration

NAME
Description
ID
ID of the vehicle
Dealer
Name of dealer
Class
4&2 wheeler
Manufactured
Name
of
the
manufacture
D_manufactured
Date
of
the
manufacture
H_P
Horse Power
Chassis_no.
Chassis number
Eng_no.
Engine number
Capacity
Capacity
Fuel
Fuel type
Color
Color of vehicle
Reg_no.
Registration number
5. Table Name : License
NAME
Description
U_ID
Name of U_id
D_apply
Date of apply
D_test
Date of test
T_test
Time of test
I_authority
Issue of authority
Result
Result of pass/fail
Type
Type of LMV/HMV

Data Type
varchar
Varchar
Varchar
Varchar

Size
32
25
32
Max

Varchar

32

Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar

25
50
50
30
40
30
30

Data Type
Int
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar

4. System Testing and Implementation

4.1 Testing

Size
30
20
20
10
30
10
10

Constraints
Primary key

Constraints
Primary key

System testing is actually a series of different whose primary purpose is to fully

exercise the computer based system. Software testing is critical element of software
quality assurance and represent the ultimate review of the specification, design and
coding. System testing makes a logical assumption that all the part of the system is
correct; the goal will be successfully achieved. Testing is the final verification and
validation activity within the organization itself. During testing the major activities
are concerned on the examinations and modification of the source code.
Testing is a process of executing a program with the intend of finding an error. A good
test is one that uncovers an as yet undiscovered error. Testing objectives are:
Unit testing
Unit testing enables a programmer to detect error in coding. A unit test focuses
verification of the smallest unit of software design. This testing was carried
out during the coding itself. In this testing step, each module going to be work
satisfactorily as the expected output from the module.
Project aspect:
The front end design consists of various forms. They were tested for data
acceptance. Similarly, the backend also tested for successful acceptance and
retrieval of data.
Integration testing
Through each program work individually, they should work after linking
together. This is referred to as interfacing. Data may be lost across the
interface; one module can have adverse effect on the other
subroutines after linking may not do the desired function expected by the main
routine. Integration testing is the systematic technique for constructing the
program structure while at the same time conducting test to uncover errors
associated with the interface. Using integrated test plan prepared in the design
phase of the system development as a guide, the integration test was carried
out. All the errors found in the system were corrected for the next testing step.
Project Aspect
After connecting the backend and the frontend as whole module, the data
entered in the front-end. Once submitted were successfully entered in the
Database. On request, data were successfully retrieved in to forms.
System testing
After performing the integration testing, the next step is output testing of the
proposed system. No
system could be useful if it doesnt produce the required output in a specified
format. The outputs generated are displayed by the user. Here the output
format is considered in to two ways. One in on screen and other in printed
format.
Project aspect:

The entire project was tested and found successful.

Validation testing
The user has to work with the system and check whether the project meets his
needs. In the validation
checking the user works with the beta version of the software.
Project aspect:
User enters the appropriate data and results was checked and validated.
User acceptance testing
User acceptance of a system is a key factor of the success of any system. The
system under consideration was tested for user acceptance by running a
prototype of the software.
Project aspect:
An Alfa version is demonstrated to the users. Their suggestions are recorded.

4.2 Implementation
Once the system was tested, the implementation phase started. Crucial phase in the
system development life cycle is successful implementation of new system design.

Implementation simply means converting new system design into operation. This is
the moment of truth the first question that strikes in everyones mind that whether the
system will be able to give all the desired result as accepted from system. Prior to
starting the project implementation process project must have successfully completed
the project evaluation process and the project has been approved for implementation.
The project evaluation process includes performing a needs analysis and architecture
review. The
implementation phase of the software design consists of different tasks to be done
sequentially for obtaining the desired result. Several distinct implementation projects
rather than one large implementation could limit risk and in scope and resource
management. So the project was implemented module wise.

5. Bibliography

http://www.mptransport.org

http://www.slideshare.net
https://www.scribd.com