SYNOPSIS
PROJECT TITLE
E-RTO SYSTEM
Sant Gadge Baba Amravati University, Amravati
COLLEGE OF MANAGEMENT
AND COMPUTER SICNECE, YAVATMAL
SUBMITTED BY
Shubham Sherpurwar
BCA - III
2019-2020
SYNOPSIS
Project : PROJECT TITLE
E-RTO SYSTEM
MEMBER NAME: SHUBHAM SHERPURWAR
INTRODUCTION:
This project is an RTO office which maintain all the information like a issuing
the learning licence, permanent licence, vehicle registration, vehicle ownership transfer
etc. Once all these Gates computerized to work efficiency how the employee will get
increases.
"E-RTO System" will be designed to automate the process of registration of vehicle
and issuing driving licence process. System can make the daily activities efficient and
providing the fast response to store and retrieve information.
Online E-RTO system project will include the following information:
1. Issue of duplicate registration certificate.
2. Issue of learning licences.
3. Issue of regular driving licence.
4. Issue of a duplicate driving licence
5. Renewal of driving licences.
6. Issue of conductors licences.
7. Issue of Taxi/Maxi Cabs/Auto Rickshaw and private service vehicle permits.
EXISTING SYSTEM
There is no such computer management system which can perform the above
features online. We are making a project website which will able to perform all the
tasks related to the RTO services.
PROBLEMS IN EXISTING SYSTEM
There is no such computer management system which can perform the above
features online. We are making a project website which will able to perform all the
tasks related to the RTO services.
1. Manual Paperwork.
2. Time Consuming
3. Inefficient
PROPOSED SYSTEM
The proposed system will be able to carry out the following tasks.
1. Issue of duplicate registration certificate.
2. Issue of learning licences.
3. Issue of regular driving licence.
4. Issue of a duplicate driving licence
5. Renewal of driving licences.
6. Issue of conductors licences.
7. Issue of Taxi/Maxi Cabs/Auto Rickshaw and private service vehicle permits.
FEASIBILITY STUDY
A feasibility study is a short, which aims to answer a number of questions.
Does the system contribute to the overall objectives of the Organization?
Can the system be implemented using current technology and within given
cost and schedule constraints?
Can the system be integrated with systems which are already in place?
Feasibility study is an essential part for developing any software we study
present manual system, we calculation to cot required for maintaining various
record.
The space required for keeping the cost of manual staff and time required
for manual system was more.
A feasibility study is carried out to select the best system that must
performance requirement and its working ability in an organization. The feasibility
of the system has been done in Five types:
1. Operational feasibility study
2. Technical feasibility study
3. Schedule feasibility study
4. Economic feasibility study
5. Implementation feasibility study
OPERATIONAL FEASIBILITY:
The system must be evaluated from the technical point of view. The assessment
of this feasibility must be based on an outline design of the system requirement in the
terms of input, output, programs and procedures, Having identified an outline system,
the investigation must go on suggest the type of equipment, required method developing
the system, of running the system once it has been designed.
Technical issues raised during the investigation are:
Does the existing technology sufficient for the suggested once one?
Can the system expand if developed?
Considering various user for the application w have done operational feasibility
of the proposed operationally and easy to use by the users. The application must capable
of performing some automatic operation which helps the user for easy functionality
Operational feasibility measures how well the solution will work in the
organization and how will end-user & management feels about the system? Proposed
system as helpful for all the stakeholders associated with the organization. It will allow
the employees to have up-to-date information regarding all the aspects of their
respective departments. The decision-making process will also become faster with the
use of data integration, consolidation and computation power available at all the nodes
in the organization.
On studying the operational feasibility of the project, the following conclusions
could be derived.
Developed system will provide the adequate throughput and all necessary
information to end-users.
It will provide efficient and cost-effective access to up-to-date data.
If installed within suitable environment, system will do operations under
environment of limited resources.
Thus, it is operationally feasible to develop the propose system.
TECHNICAL FEASIBILITY:
Technical feasibility tries to answer the following questions to make the software
feasible to develop.
The software or tools necessary for building or running the application are
easily available or not?
The compatibility amongst software exists or not?
Are developers aware of these technologies?
What about the alternative of these chosen technologies?
SCHEDULE FEASIBILITY:
Projects are initiated with specific deadline. We need to evaluate whether the
deadlines are mandatory or desirable. Time is the one of the critical factor in the
development of any system but this kind of feasibility is hardly perfect in any system.
Hence, it is feasible to develop a system in predetermined time interval.
ECONOMICAL FEASIBILITY:
The developing system must be justified by cost and benefit. Criteria to ensure
that effort is concentrated on project, which will give best, return at the earliest. One of
the factors, which affect the development of a new system, is the cost it would require.
The following are the some of the important financial questions asked during
preliminary investigation:
The cost conducts a full system investigation.
The cost of the hardware and the software.
The benefits in the form of reduce costs or fewer costly errors.
Since the system is developed as part of project work, there is no manual cost
to spend for the purposed system. Also the resources are already available, it give an
indication of the system is economically possible for development.
Economic feasibility addresses to the following issues:
How much profit can be earned from the system by an organization?
Is the organization having the suitable budget to develop the proposed
system?
Would it be cost-effective to develop the system or it is worthwhile to
remain with current system?
IMPLEMENTATION FEASIBILITY:
Under the study of Implementation feasibility, we’ve got to draw the finger to the
certain issues, like
Is it possible to install the software within the given environment?
Will organization management and user support for the installation of the
software?
Will proposed system cause any harm to the operations of the organization?
SYSTEM REQUIREMENT:
Hardware
Pentium IV processor or any higher processor
512 MB RAM or more
2 GB Hard Disk or more
Software
Operating System
Windows XP or higher operating system
Development Tools
Microsoft Asp.NET
Database-Microsoft SQL Server
Documentation & Presentation Tools
Microsoft word 2007
Microsoft PowerPoint 2007
DFD’s
0 Level DFD
1 level DFD for Admin:
A level 0 DFD, also called a fundamental system model or context diagram
represents the entire software element as a single bubble with input and output data
indicated by incoming and outgoing arrows, respectively.
1 level DFD for User
(A) 2 level DFD
(B) 2 level DFD
E-R-DIAGRAM
MODULE DESCRIPTION
The application comprises the following two major modules:
1. Users
2. Admin
The admin will have total comtrol over the system and can perfrom all the
operations which the users can’t perfrom.
The user will have the following functionalities.
Functionalities:
Issue of Duplicate Registration Certificate.
Issue of Learning Licenses.
Issue of Regular Driving License.
Renewal of Driving Licenses.
Issue of a Duplicate Driving License.
Issue of Conductors Licenses.
Issue of Taxi/Maxi Cabs/Auto Rickshaw and Private Service Vehicle Permits.
INPUT FORMS:
1. USER LOGIN PAGE
2. ADMIN LOGIN PAGE
3. TEST PAGE
4. SIGN UP PAGE
5. FEEDBACK PAGE
6. CONTACT US PAGE
OUTPUT FORMS:
1. TEST RESULT PAGE
2. INFORMATION OF ISSUING OF LICENSE
3. INFORMATION OF TAXATION
4. INFORMATION OF PERMIT
5. INFORMATION OF OFFENCES AND PENALTIES
6. INFORMATION OF TRANSFER AND NOC
SYSTEM FLOW DIAGRAM:
USER YES LOGI NO
N
HOME PAGE INPUT VALID
USERNAME AND
PASSWORD
START USING THE LOGOUT
WEBSITE
EXIT
DATABASE DESIGN:
Admin Master Table
Sr.no. Field name Data type Constrain Size Description
1. Admin_id int Primary key - Id of admin master.
2. User_name Varchar Not null 50 Name of user
3. Password Varchar Not null 50 Password of user
4. F_name Varchar Not null 50 First name of user
5. L_name Varchar Not null 50 Last name of user
6. Address Varchar Not null 50 Address of user
7. City Varchar Not null 50 City of user
8. Mobile Decimal Not null 18 Mobile number of user
9. E-mail Varchar Not null 50 Email address of user
10. Seq_que Varchar Not null 50 Security question
11. Seq_ans Varchar Not null 50 Security answer
12. Status Varchar Not null 50 Status
Contact Us Table:
Sr.no. Field name Data type Constrain Size Description
1. Cont_id int Primary key - Id of contact us.
2. Name Varchar Not null 20 Name of user
3. Date Date time Not null 30 Date
4. Mobile Decimal Not null 18 Mobile number of
user
5. E-mail Varchar Not null 50 Email address of
user
6. Detail Varchar Not null 50 Detail about
Registration Table:
Sr.no. Field name Constrain Size Description
1. Reg_id Int Primary key - Id of registration.
2. User_name Varchar Not null 50 Name of user
3. Password Varchar Not null 50 Password of user
4. F_name Varchar Not null 50 First name of user
5. L_name Varchar Not null 50 Last name of user
6. Address Varchar Not null 50 Address of user
7. City Varchar Not null 50 City of user
8. Mobile Decimal Not null 18 Mobile number of user
9. E-mail Varchar Not null 50 Email address of user
10. Seq_que Varchar Not null 50 Security question
11. Seq_ans Varchar Not null 50 Security answer
12. Status Varchar Not null 50 Status
13. Temp Varchar Not null 50 Document
14. Photo Varchar Not null 50 Photos
Download Table:
Sr.no. Field name Data type Constrain Size Description
1. D_id int Primary key - Id of download
form
2. Title_eng Varchar Not null Max Name of English
form
3. File name Varchar Not null Max Name of English
eng file
4. Category Varchar Not null 50 Category of form
5. Detail Varchar Not null Max Detail about
6. Status Varchar Not null 50 Status
Feedback Table
Sr.no. Field name Data type Constrain Size Description
1. Feed_id int Primary - Id of feedback
key form.
2. Date Date time Not null 30 Date
3. Name Varchar Not null 50 Name of user
4. Mobile Decimal Not null 18 Mobile number of
user
5. E-mail Varchar Not null 10 e-mail address of
user
6. Comments Varchar Not null 50 Category of form
RTO Test Table
Sr no. Field name Data type. Constrain Size
Description
1. Que_id int Primary key - Question id.
2. Que_name Varchar Not null Max Question name.
3. Opt_1 Varchar Not null Max Option 1.
4. Opt_2 Varchar Not null Max Option 2.
5. Opt_3 Varchar Not null Max Option 3.
6. Ans Varchar Not null 1 Answer of question
7. Image Varchar Not null 50 Image
