RTO MANAGEMENT SYSTEM PROJECT REPORT

RTO MANAGEMENT SYSTEM PROJECT REPORT

PROJECT REPORT

RTO MANAGEMENT SYSTEM PROJECT REPORT

PROJECT SOURCE CODE

RTO MANAGEMENT SYSTEM PROJECT SOURCE CODE

OTHER PROJECT REPORT

ONLINE RTO OFFICE MANAGEMENT SYSTEM PROJECT REPORT

FREE DOWNLOAD ALL THE PROJECT REPORTS WITH SOURCE CODE FROM HERE

ABSTRACT

RTA Information System (RTA) is an online information source developed for Road Transport Authority to facilitate the users in applying for various licenses and registrations. This tool has been designed to facilitate the flow of information within the organization.RTA provides the facility of applying licenses online, issuance of permanent license, tax challans, and receiving payments against challans.

            In the Previous System It is not efficient in performing office work in RTO services, It includes much manual process and time consuming, It is not user friendly, Maintains local data base. It is not Generating Accurate Reports.

The Existing system of RTA services has been is usage for two years. The existing system is not giving accurate results while doing transactions. It doesn’t provide security, anyone enter into the system and can do their own transactions. It is not flexible in generating reports and many manual processes are made computerized.

To overcome problems in the existing System a new RTO services “Road Transport Authority Information System” is proposed after study of system. The objectives of proposed system are: Ensure data integrity and security, less manpower, Generate accurate reports, Accurate handling in multiple details.

RTA has the following modules

Application for learner license.

Issuance of permanent license.

Issuance of road tax challans for transport vehicles.

Receiving payments against challans.

                                                          

                                                       

                                  CONTENTS

1.                                           INTRODUCTION

                                          i.         PURPOSE OF PROJECT

                                         ii.         SCOPE OF PROJECT

                                        iii.         PROJECT OVERVIEW

2.                                            PROJECT ANALYSIS

                                          i.         EXISTING SYSTEM

                                         ii.         PROPOSED SYSTEM

                                        iii.         H/W and  S/W SPECIFICATIONS                  

3.                                            SYSTEM  DEVELOPMENT ENVIRONMENT

4.                                            PROJECT DESIGNING

                                          i.          DFD (Data Flow Diagrams)

                                         ii.          UML Diagrams

                                        iii.          ER Diagrams

                                       iv.          DB Design

                                        v.          Screens

5.                                           PROJECT TESTING

                                          i.          Performance Testing

                                         ii.          Unit Testing

                                        iii.          Integration Testing

6.                                           CONCLUSION

7.                                           FUTURE ENHANCEMENT

8.                                           BIBLIOGRAPHY

1. INTRODUCTION

2.1                                      Process Model

The System keeps track of the transactions in the RTO office. It maintains Renewal of learner’s License, Renewal of permanent license,Issue of learner’s license, Online LLR Form,Registration Form,Issue of perminent license,payment against challan and finally it produce printouts to payment of customers.

2.2        Purpose of the project

This project Deals with the transactions of RTO services office:-

F Renewal of learner’s license.

F Renewal of perminent license.

F Issue of learner’s license.

F Issue of perminent license.

F Registration Form

F Payment against challan.

F Online LLR Form

2.3 Problem in Existing System - RTO MANAGEMENT SYSTEM

The Existing system of RTO services has been is usage for two years.The existing system is not giving accurate results while doing transactions.It doesn’t provide security,anyone enter into the system and can do their own transactions.It is not flexible in generating reports.and many manual processes are made computerized.

The present system has following drawbacks:

Þ    It is not efficient in performing office work in RTO services.

Þ    It includes much manual process and time consuming.

Þ    It is not user friendly.

Þ    Maintains local data base.

Þ    It is not Generating Accurate Reports.

2.4                                      Solution of these Problems

To overcome problems in the existing System a new RTO services “Road Transport Authority Information System” is proposed after study of system. The objectives of proposed system are:

 Facilities ease of operation.

 Ensure data integrity and security.

 Less manpower.

 Generate accurate reports.

 Accurate handling in multiple details of multiple customers.

3. H/W AND S/W  SPECIFICATION

SOFTWARE CONFIGURATION

OPERATING PLATFORM        :           WINDOWS 2000/NT/XP

RDBMS                                         :           SQLSERVER 2000

SOFTWARE                        :         VS.NET 2003

FRONT END TOOL               :           ASP.NET

HARDWARE CONFIGURATION

RAM                                 :           128MB

HARD DISK                       :           MINIMUM 20 GB

                 

2. ANALYSIS

SYSTEM:

§  Designing and implementing the new links.

• Designing and implementing the users.
• Arranging new links as subject wise.

a.    Study of the System

 System analysis will be performed to determine if it is feasible to design information based on policies and plans of the organization and on user requirements and to eliminate the weaknesses of the present system.

Ø  The new system should be cost effective.

Ø  To augment management, improve productivity and services.

Ø  To enhance user / system interface.

Ø  To improve information qualify and usability.

Ø  To upgrade systems reliability, availability, flexibility and growth potential.

b.                            Feasibility Study - RTO MANAGEMENT SYSTEM 

3.1 Economic Feasibility

                      Economic feasibility attempts 2 weigh the costs of developing and implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the top management the economic justification for the new system.A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of  reference to compare actual costs as the project progresses. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, improvement in product quality better decision making timeliness of information, expediting activities, improved accuracy of operations, better documentation and record keeping, faster retrieval of information, better employee morale.

3.2 Operational Feasibility

 Proposed project is beneficial only if it can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are there major barriers to Implementation? Here are questions that will help test the operational feasibility of a project:

Is there sufficient support for the project from management from users? If the current system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.Are the current business methods acceptable to the user? If they are not, Users may welcome a change that will bring about a more operational and useful systems.

Have the user been involved in the planning and development of the project? Early involvement reduces the chances of resistance to the system and in general and increases the likelihood of successful project.

Since the proposed system was to help reduce the hardships encountered. In the existing manual system, the new system was considered to be operational feasible.  

3.3 Technical Feasibility

            Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, .at this point in time, not too many detailed design of the system, making it difficult to access issues like performance, costs on (on account of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a technical analysis.

Understand the different technologies involved in the proposed system before commencing the project we have to be very clear about what are the technologies that are to be required for the development of the new system. Find out whether the organization currently possesses the required technologies. Is the required technology available with the organization.

 5.1 DATA DICTIONARY - RTO MANAGEMENT SYSTEM 

Data dictionary consists of descriptions of all the data used in the system. It consists of logical characteristic of current systems data stores including name, description, aliases, contents and organization. Data dictionary serves as basis for identifying databases requirements during  requirements during system design. Data  dictionary is a  catalog a repository  of the elements in the system. The Data dictionary is used to manage the detail in large systems, to communicate a common meaning for all system elements, to document the features of the system elements, to document the feature of the system, to locate errors and omissions in the system.

                        Data dictionary contains two types of description for the data flowing through the system:   Data element and Data structure. Data Element are used to group together to make up the Data Structure. The  most fundamental level is the data  element. Data Structure is a set of data items  data related to one another and collectively describe a component in the system. The description of the data elements consists of data names, data description, aliases, and length and data values.

         5.1.1        Table Name: Challana details

Column Name	Type	Size
cno	nvarchar	50
name	varchar	50
amount	nvarchar	50
ianame	varchar	50
Ides	varchar	50
Vfrom	Varchar	50
Vto	Varchar	50

  

Table Name: Registration details

Column Name	Type	Size
regno	nvarchar	50
regdate	varchar	50
nameofapp	varchar	50
sdwof	varchar	50
age	varchar	50
Add1	varchar	50
Add2	varchar	50
city	varchar	50
state	varchar	50
phno	varchar	50
nameadd	varchar	50
typeofveh	varchar	50
date1	varchar	50
chassisno	varchar	50
engineno	varchar	50
Seatcap	varchar	50
Fuel	varchar	50

         5.1.2        Table Name: LLR details

Column Name	Type	Size
Img_pk	Int	4
Img_title	varchar	50
Img_stream	Image	16
Img_type	Varchar	50
llrno	Varchar	50
ldate	Varchar	50
name	Varchar	50
swd	Varchar	50
dob	Varchar	50
bg	Varchar	50
a1	Varchar	50
a2	Varchar	50
City	Varchar	50
State	Varchar	50
Phone	Varchar	50
Mark	Varchar	50
Vfrom	Varchar	50
Vto	Varchar	50
Type	Varchar	50

         5.1.3        Table Name: Admin

Column Name	Type	Size
Id	nvarchar	50
Password	nvarchar	50

         5.1.4        Table Name: LLR Exam

Column Name	Type	Size
Examno	Varchar	50
Ans1	Varchar	50
Ans2	Varchar	50
Ans3	Varchar	50
Ans4	Varchar	50
Ans5	Varchar	50
Ans6	Varchar	50
Ans7	Varchar	50
Ans8	Varchar	50
Ans9	Varchar	50
Ans10	Varchar	50
name	Varchar	50
Edate	Varchar	50
chalno	Varchar	50

         5.1.5        Table Name:Addemp

Column Name	Type	Size
Id	nvarchar	50
Password	nvarchar	50
Name	varchar	50
Address	varchar	50
phno	varchar	50

         5.1.6        Table Name: Renewal of LLR and PL

Column Name	Type	Size
llr	nvarchar	50
dateofiss	varchar	50
dateofren	varchar	50
typelicence	varchar	50
name	varchar	50
sdw	varchar	50
dob	varchar	50
bloodg	varchar	50
Add1	varchar	50
Add2	varchar	50
city	varchar	50
state	varchar	50
phno	varchar	50
Ident1	varchar	50
Ident2	varchar	50
vfrom	varchar	50
vto	varchar	50
chano	varchar	50
amount	varchar	50

         5.1.7        Table Name:Result

Column Name	Type	Size
aname	nvarchar	50
examno	nvarchar	50
cno	varchar	50
edate	varchar	50
marks	varchar	50
result	Varchar	50

 8.PROJECT TESTING - RTO MANAGEMENT SYSTEM 

Testing is the process of detecting errors.Testing performs a very critical role for quality assurance and for ensuring the reliability of software.The results of testing are used later on during maintainence also Psychology of Testing.

The aim of testing is often to demonstrate that a program works by showing that it has no errors.The basic purpose of testing phase is to detect the errors that may be present in the program.Hence one should not start testing with the intent of showing that a program works,but the intent should be to show that a  program doesn’t work.

Testing is the process of executing a program with the intent of finding errors.

Testing Objectives:

The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. Stating formally, we can say,

• Testing is a process of executing a program with the intent of finding an error.
• A successful test is one that uncovers an as yet undiscovered error.
• A good test case is one that has a high probability of finding error, if it exists.

• The tests are inadequate to detect possibly present errors.
• The software more or less confirms to the quality and reliable standards.

A series of testing is done for the proposed system before the system is ready for the user acceptance testing.

The steps involved in Testing are:

¨     Unit Testing:

Unit testing focuses verification efforts on the smallest unit of the software design, the module. This is also known as “Module Testing”. The modules are tested separately. This testing carried out during programming stage itself. In this testing each module is found to be working satisfactorily as regards to the expected output from the module.

¨     Integration Testing: 

            Data can be grossed across an interface; one module can have adverse efforts on another. Integration testing is systematic testing for construction the program structure while at the same time conducting tests to uncover errors associated with in the interface. The objective is to take unit tested modules and build a program structure. All the modules are combined and tested as a whole. Here correction is difficult because the isolation of cause is complicate by the vast expense of the entire program. Thus in the integration testing stop, all the errors uncovered are corrected for the text testing steps.

¨     System testing:

System testing is the stage of implementation that is aimed at ensuring that the system works accurately and efficiently for live operation commences. Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, then goal will be successfully achieved.

¨     Validation Testing:

            At the conclusion of integration testing software is completely assembled as a package, interfacing errors have been uncovered and corrected and a final series of software tests begins, validation test begins. Validation test can be defined in many ways.  But the simple definition is that validation succeeds when the software function in a

manner that can reasonably expected by the customer. After validation test has been conducted one of two possible conditions exists.

One is the function or performance characteristics confirm to specifications and are accepted and the other is deviation from specification is uncovered and a deficiency list is created. Proposed system under consideration has been tested by using validation testing and found to be working satisfactorily.

8.2     Output Testing:

            After performing validation testing, the next step is output testing of the proposed system since no system could be useful if it does not produce the required output in the specified format. Asking the users about the format required by them tests the outputs generated by the system under consideration. Here the output format is considered in two ways, one is on the screen and other is the printed format. The output format on the screen is found to be correct as the format was designed in the system designed phase according to the user needs. For the hard copy also the output comes as the specified requirements by the users. Hence output testing does not result any corrections in the system.

¨     User Acceptance Testing:

User acceptance of a system is the key factor of the success of any system. The system under study is tested for the user acceptance by constantly keeping in touch with the prospective system users at the time of developing and making changes wherever required.

¨     Test Data:

Taking various kinds of test data does the above testing. Preparation of test data plays a vital role in the system testing after preparing the test data the system under study is tested using the test data. While testing the system by using the test data errors are again uncovered and corrected by using above testing steps and corrections are also noted from the future use.

¨     Testing:

                   The testing done here was System Testing–checking whether the user requirements were satisfied. The code for the new system has been written completely using JSP as the coding language, HTML as the interface for front-end designing and Java Script for validating the client-side applications. The new system has been tested well with the help of the users and all the applications have been verified from every nook and corner of the user.

            Although some applications were found to be erroneous these applications have been corrected before being implemented. The flow of the forms has been found to be very much in accordance with the actual flow of data.

1.   CONCLUSION - RTO MANAGEMENT SYSTEM 

RTA provides the facility of applying licenses online, issuance of permanent license, tax challans, and receiving payments against challans.

ü  The project has been appreciated by all the users in the organization.

ü  It is easy to use, since it uses the GUI provided in the user dialog.

ü  User friendly screens are provided.

ü  The usage of software increases the efficiency, decreases the effort.

ü  It has been efficiently employed as a project management mechanism.