SOFTWARE REQUIREMENT

SPECIFICATION
 SOFTWARE REQUIREMENT SPECIFICATION

2.1 INTRODUCTION
Software requirement and specification is a complete description about the behaviour of
the system to be developed. It includes a set of use cases that describes all the
interactions that the users will have with the software. In addition to use case, the SRS
also contain non-functional requirement which impose constraints on the design or
implementation.

E.RTO (Electronical Regional Transport Office Management System) is one of the web
application for users to apply for their driving licence. It contains information about the
different type of licence, the fee charged, and the procedure to apply for the same.

2.1.1 Purpose
This project aim is to develop an online RTO system for the users (E.RTO). This project
is to create an E-information about the users, vehicles and the RTO that are useful.
Through this application the public (user) can register them self. By providing all the
required information and documents, the user can also apply for licence and register
their vehicles.

The application takes care of different modules and their associated reports, which are
produced as per the applicable strategies and standards that are put forwarded by the
administrative staff.

2.1.2 Scope
The scope of RTO system is to provide all the services online, which are provided in
RTO office. The services provided are LL, DL, International driving license, all India
permit, conductor license, vehicle registration, transfer of vehicle, renewal of license
and online fine payment
2.1.3 Definition, Acronyms, Abbreviations
Terms Meaning
DFD Data Flow Diagram
ER Diagram Entity Relation Diagram
SRS Software Requirements Specification
ASP Active Server Pages
DB Data Base
RTO Regional Transport Office
CFD Control Flow Diagram
SQL Structured Query Language
GUI Graphics User Interface

2.1.4 References
 Books
J. B. Dixit, Raj Kumar, Structured System Analysis and Design, Laxmi Publications,
2008.
Pankaj Jalote, An Integrated Approach to Software Engineering, 2nd
Edition, Narosa Publishing House, 2004
Dr. K.V.K.K. Prasad, Software Testing tools, Dreamtech Press.

 Websites
• http://transport.karnataka.gov.in
• https://www.scribd.com/doc/132098581/ONLINE-RTO-MANAGEMENTSYSTEM
• https://www.youtube.com/watch?v=Wmnq0OOt024
• http://www.enggroom.com/Asp/Free%20Project%20Download%20Online%2
0E-RTO%20System%20in%20Asp.Net.html

2.1.5 Overview
The developer is responsible for the development of the underlying database structure
that shall serve as online registration of licence and vehicles. The developer is also
responsible for development of both the user and RTO interface for the system that shall
both make use of the underlying database structure. The developer will also train the
RTO staff to use the interface and show sample data entry and deletion. The client must
then build the database.

2.2 OVERALL DESCRIPTION

2.2.1 Product perspective

This product is an entirely new product. It is not a component of the whole system. The
E.RTO is an RTO management system. In this system, the user or the RTO staff
interacts with the E.RTO and its databases.

RTO
Admin, User
management Database
and RTO staff
system

2.2.2 Product functions

The following list of function descriptions explains the major features of the E.RT O Regional
Transport Office management System.

a) Account registration
The registration function shall allow users to create secure accounts. The account
will track the user’s name, mobile number, email id and password. Rationale:
This provides security to the account member by setting up an account that is
password protected. This also offers convenience so the user only has to enter
the information listed above once and then it is stored in the account.

b) Account login
The login function shall allow account members to enter their user name and
password. Once verified, users will be able to access account history and update
their account information.
Rationale: this provides a method by which the users can access the restricted
operations.
 c) Apply for licence
This function will allow the user to apply for the different types of licence by providing
the required information.

d) Vehicle registration
This function will allow the user to register their vehicle by providing the details.

e) View vehicle details

This function will allow the traffic police to view the various cases registered to a
particular vehicle.

f) View violation report

This function will allow the user to view his/her violations details on their vehicle with
the help of their vehicle licence plate number.

g) Account log out

The account logout function shall allow account members to exit their account for
security purposes.
Rationale: This allows account members to exit their accounts, and prevent others from
accessing it.

2.2.3 User characteristics

Users of the website must possess a minimal educational level which conforms
to online RTO management system (E.RTO) entrance standards. Users of the
website must know how to navigate in a website.

2.2.4 Assumptions and Dependencies

Assumption

Since the Regional Transport Office management, system (E.RTO) is only

accessible through the Internet. It is assumed that the end user has a connection
 to the Internet. In addition, that the user has a web browser able to display the
website. (I.E. Microsoft Internet Explorer 9+ or compatible browser)
Dependencies

The number of users and services on the E.RTO depends on various factors like

• Power source.

• Systems (User system/Servers).

• Communication mediums (Wired/Wireless).

• Internet connections.

2.3 SPECIFIC REQIREMENTS

2.3.1 External Interface Requirements

2.3.1.1 User interfaces

The system will provide the ability for the users and the RTO staff to store
information via the internet. There will be three different user interface that will
accompany this website: one for the public, second for the RTO staff and finally
for the administrators.

• User: The public (user) will be allowed to lodge complaints without having to
login, however they must login in order to perform any other operations. These
operations will include applying for license, uploading of documents, updating
their profile and fee payment.

• RTO Staff: The RTO staff also will be given with login through which they can
access the data and use it for the verification of the documents. In addition,
approve the same to the user and allot the user with the date to appear to the
driving test, the staff will be able to search for the details of the vehicles.

• Admin: Administrators will be required to login at all times. However, they will
have limit access via the web-interface only being able to pull predefined reports.
 The administrators will have to logon to a host machine inside the RTO system
in order to manage users, build reports and ensure the backup is running.

2.3.1.2 Hardware Interfaces

Processor 133-MHz Intel Pentium-class Processor
or higher

Hard disk 200GB recommended or higher

Memory 4GB of RAM or higher
Display Standard Output display
Keyboard Standard Qwerty Keyboard for Interface
Mouse Standard mouse
Printer Inkjet/Laser color printer provides at
least 1000 Dpi

Modem 1Mbps

2.3.1.3 Software Interfaces

Operating System Windows XP and Above

Other technologies ASP.net, C#, HTML5 , AJAX

Front End/IDE Microsoft Visual Studio 2013
Back End Microsoft SQL Server
Web Browser Internet explorer9 and above, Google
chrome, opera, Firefox

2.3.1.4 Communication Interfaces

This is a web-based system and communication is done through internet and internet
protocols (TCP/TP).

2.4 FUNCTIONAL REQUIREMENTS

a) Register

• The system shall allow a non-registered user to create a secure account.

 • The system shall require the following information from the user: Name, mobile
no, email id, password.
• The system shall ask the user for a username and password.
• The system shall confirm the username and password are acceptable.
• The system shall store the information in the database.
b) Login

• The system shall allow a registered user to log-in to their account. The
system shall require a username and password from the user.
• The system will verify the username and password, and the user will be
considered “logged-in”.
c) Home
• This is the main page for all the pages.
• The home page will allow the users to search the particular vehicle which they
required.
• In this page we also have organised tips, fee policy, privacy policy investors,
RTO agreement, how to book, our team, our gallery and reach us. The
customer can go through it before booking.

d) LL/DL/VEHICLE REGISTRATION

• In this user can view and add details like photos and other related information
required for t he application forms.

• In this user will upload various documents like marks cards, voter id,
ADHAAR card.

• In this user can view the various payment types to pay the required fee for the
respective applications.

e) RTO staff

• Here the RTO staff will be able to validate and verify whether the documents
produced by the user is correct or not.

• Here the RTO staff will be able to check whether the payment has been done
by the user or not.

• In this the RTO Staff is able to trace a particular vehicle with the help of
vehicle number and view various violations of the particular vehicle.
 • In this the staff is able to allot a particular day and time to the user to present
himself for the written text and also the driving test.

• Here the staff is able to notify the user whether they have passed the tests
and also when and how they will receive their respective license.

f) Administrator
• The system shall allow the administrator to do the manipulation in
the system such as adding and removing of users and RTO staff from
the database.

• As a higher authority of the system he is able to view various reports

generated by the system with the help of this module.

• The admin has the ability to take backup of the database and also
restore it whenever needed. Administrator is the super user who is
having more powers.

2.5 PERFORMANCE REQUIREMENTS

The performance requirements are as follows:
• System login/logout shall take less than 5 seconds.
• Searches and provides you required information within 10 seconds.
• Response taken by the system is very less with the minimum internet speed.
• System shall support 5,000 simultaneous users.

2.6 DESIGN CONSTRAINTS

The Regional Transport Office Management System (E.RTO) conform to the following design
constraints:
• Able to support PC, Mac, other platforms.
• System logs out user after a twenty-minute inactivity period.
• System supports all web browsers (i.e. graphical, non-graphical).
2.7 SYSTEM ATTRIBUTES
a) Reliability

The average time to failure shall be 30 days. In the event that a server does crash, a
backup server will be up and running within the hour.

b) Availability

The Regional Transport Office Management System (E.RTO) shall be available

to users 24 hours a day, 7 days a week, with the exception of being down for
maintenance no more than one hour a week. If the system crashes, it should be
back up within one hour.

c) Security

Users will be able to access only their own personal information and not that of
other users. The other process will also be handled through a secure server to
ensure the protection of user’s credit card and personal information.

d) Maintainability

Any updates or defect fixes shall be able to be made on server-side computers only
without any patches required by the user.

e) Portability

Nothing required

2.8 OTHER REQUIREMENTS

Required Nothing