Rto Management System

SYSTEM REQUIREMENT SPECIFICATION ON “RTO MANAGEMENT SYSTEM”

SUBMITTED TO:-

SUBMITTED BY:-

VIJAY MOHAN SHRIMAL

RAKESH YADAV

(Assistant Professor)

(CS-A/2ndyear)

(CSE Deptt.)

2

Index S.NO.

PARTICULAR

PAGE NO.

1.

Project introduction

4

1.1 1.2 1.3 1.4

4-5 5 5 6-7

2.

3.

4.

Purpose Scope Benefits Functional requirement

General Description

7

2.1 System requirement 2.2 Tools and Technology used

7 7

System Analysis

8

3.1 Information Gathering 3.2 Existing System 3.3 Proposed System 3.4 SRS 3.4.1 Need for SRS 3.4.2 Software function Overview 3.5 Feasibility Study 3.5.1 Technical Feasibility 3.5.2 Operational Feasibility 3.5.3 Economic Feasibility

8 8-9 9-10 10 10 11 11 11 12 12

System Design

13

4.1 Logical Design 4.1.1 E R Diagram 4.1.2 Data Flow Diagram 4.1.3 Flow Chart 4.2 Database Design

13 13-14 15-18 19 20-22

3

S.NO.

PARTICULAR

PAGE NO.

5.

System Testing and Implementation

23

5.1 Testing 5.2 Implementation

23-24 25

System Specification

26

6.1 Software Specification 6.2 Hardware Specification

26

6.

26-27

7.

System Maintanance

28-29

8.

System Security

30-32

9.

Reference & Appendices

33

10.

Conclusion

33

4

RTO MANAGEMENT SYSTEM 1.Project Introduction The project RTO MANAGEMENT SYSTEM is proposed to install a system that shall enable the proposed RTOSYSTEM 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 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 employee’s 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

5 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.2 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.3 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 can’t 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.4 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.

6 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.

2.General Description

7 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. 2.1 System Requirement Hardware Requirements Processor

:

Pentium IV 2GHz and Above

RAM

:

2GB RAM

Monitor

:

15” Color Monitor

Operating System.

:

Windows XP

Developing Tool

:

Visual Basic 6.0

Database

:

MS Access

Keyboard Mouse Software Requirements

2.2 Tools and Technology Used Language

:

JAVA

Front-end

:

HTML, JAVA Script

Back-end

:

MY SQL

8

3. System Analysis 3.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. 3.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.

9 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 learner’s 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 learner’s license will have to be made following the whole earlier procedure.

3.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.

10 

Users can have knowledge about the new rules and regulations from the

 

information’s & awareness section. In the online system the repetition of work & duplication of data can be avoided.

3.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. 3.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.

3.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 3.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 isthe test of a system proposal according to its work ability, impact on organization, ability to meet user

11 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. 3.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 backend selection. An important issue for the development of a project is the selection of suitable front end and back-end. Based on some aspects, we select the most suitable platform that suits the needs of the organization.

3.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 and operational costis 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.

3.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,

12 alterations will have to be made to the proposed system. The proposed system is economically feasible.

4.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. 4.1 Logical Design 4.1.1E 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

13 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 Wheele r

LMV

Four Wheeler

Ap ply for

Registratio n

License

IS A Two Wheeler

E_no

.

HMV

IS A Four Wheeler

L_License

P_License

14

C_no

.

C_no

Color

E_no M_n o.

Color

. .

U_i d

U_i d

M_n o.

sex

U_ad d

sex

4.1.2 Data Flow Diagram U_ad within the system. As the name suggests DFD is a representation of the data flow d

It includes processes, data stores and external interfaces to the system. External interfaces may be treated as external entities. DFD’ scan by explode to subprocesses. 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 high level 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

15

Request Process ISSUE & REJECT

USER Response

Issue vehicle

Registration management

Vehicle management

Driving licence management

License

Registration

ADMIN

0-Level DFD

Issue License

Customer management RTO Vehicle Registrat ion system

Login management

System User management

Registration

16

1-Level DFD

Vehicle management

Generate Vehicle Report

Customer management

Generate Customer Report

Driving licence management Registration management

RTO Vehicle Registration system

Generate Driving Licence Report

Login management

Generate Registration Report Report Check User Login Details

System User management

Generate System User Report

17

RTO OFFICER

I NAM E

I ID I NO

CATEGOR CATEGOR Y Y OFFE RS

Create s

VERI FY R TYPE R EXP

R NO. R DATE

BELO NGS TO

FINE

LICENCE/RENEWAL LICENCE/RENEWAL

F TYPE

4.1.3 Flow Chart E DURATION

TRAFFIC EDUCATIO N

E STAGES

T NO

ENROL LED

L NO.

L EXPIRE

F NO

FINE FINE TRANSECTI TRANSECTI ONN ONN

T BAN K T AMT

PA YS

L TYPE SHOUL D HAVE

LICENC E

DRIVER U ID

GE TS U_ADDRESS

U VEHICLE VEHICLE

NAME

U_PHONE

U CONTACT V REG

V V NO. NO. V TYPE

V CHASIS V COL

U_ USERNAME

18

4.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, in expensive 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 A_ID A_Pass

Description Data Type Name of Admin varchar Password Varchar

Size 30 30

Constraints Primary key

Size 32 25

Constraints Primary key

2. Table Name : Signup NAME ID Name

Description Data Type User ID Int Name of the Varchar

19

Sex DOB Mob Father name Add E-mail Path of Photo Path of DOB Path of add

user Sex Date of birth Mobile number Name of father Address Email ID Path of photo Path of dob Path of add

Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar

7 12 15 30 30 30 30 30 30

Data Type varchar Varchar

Size 30 30

3. Table Name : User Login NAME U_ID U_Pass

Description Name of User Password

Constraints

4. Table Name : Vehicle Registration NAME ID

Description Data Type ID of the varchar

Size 32

Dealer Class Manufactured

vehicle Name of dealer Varchar 4&2 wheeler Varchar Name of the Varchar

25 32 Max

D_manufactured

manufacture Date of the Varchar

32

H_P Chassis_no.

manufacture Horse Power Chassis

Varchar Varchar

25 50

Eng_no. Capacity Fuel Color

number Engine number Capacity Fuel type Color of

Varchar Varchar Varchar Varchar

50 30 40 30

Reg_no.

vehicle Registration

Varchar

30

number

Constraints Primary key

20

5. Table Name : License NAME U_ID D_apply D_test T_test I_authority

Description Name of U_id Date of apply Date of test Time of test Issue of

Data Type Int Varchar Varchar Varchar Varchar

Size 30 20 20 10 30

Result

authority Result

of Varchar

10

Type

pass/fail Type

of Varchar

10

Constraints Primary key

LMV/HMV

5. System Testing and Implementation 5.1 Testing 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.

21 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 doesn’t produce the required output in a specified format. The outputs generated are displayed by the user. Here the

22 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.

5.2 Implementation Once the system was tested, the implementation phase started. Crucial phase in the system development lifecycle 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 everyone’s 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.

23

6.System Specification 6.1 SOFTWARE SPECIFICATION A major element in building a system is the selection of compatible software since the software in the market is experiencing a geometric progression Selected software in the market is experiencing a geometric progression Selected software should be acceptable by the firm and one users as well as it should be feasible for the system. Front End Tool Tools Backend Operating System

: ASP.NET with C#.NET : Ajax.net, Crystal reports : Microsoft SQL Server 2005 : Windows NT/2000 Server/ XP/ 2003/ Longhorn (with

IIS) Client Side

: HTML, Java Script, Photoshop

The purpose of having a software requirement specification document is to have an understandable, unambiguous and complete specifications documentation requirement for the project. 6.2 HARDWARE SPECIFICATION The section of hardware configuration is a important task related to the software development Insufficient Random Access Memory may affect adversely on the speed and efficiency of the entire system The process should be powerful to handle the entire operations The hard disk should have sufficient capacity to store the file and applications. Processor : Pentium IV and above Processor speed : 1.4 GHz Onwards System Memory : 128 Mb Minimum 256 Mb Recommended Display : Graphics Card Capable of Produce 1024,768 Resolution Cache Size : 512 KB RAM : 512 MB (Minimum)

24 Network Card

: Any Card Can Provide a 100 Mbps Speed

Network Connection Printer Hard disk Monitor Mouse Keyboard Modem

: UTP or Coaxial Cable Connection : Inkjet/Laser Color Printer Provides At Least 1000 Dpi : 80 GB : SVGA Color 15” : 104 Keys US Key Board Serial, USB or PS/2 : 104 Keys : 56.6 Kbps

7. System Maintanance Management is “the process of designing and maintaining an environment in which individuals, working together in groups, accomplish efficiently selected aims” . In the case of maintenance the key aim is to provide cost-effective support to a software system during its entire lifespan. Management is concerned with quality and productivity, that imply effectiveness and efficiency. management consists of five separate functions The functions are: planning, organizing, staffing, leading (sometimes also called directing), and controlling. Planning consists of selecting missions and objectives and predetermining a course of

25 actions for accomplishing them. Commitment of human and material resources and scheduling of actions are among the most critical activities in this function. Organizing is the management function that establishes an intentional structure of roles for people to fill in an organization. This entails arranging the relationships among roles and granting the responsibilities and needed authority. Staffing involves filling the positions in the organization by selecting and training people. Two key activities of this function are evaluating and appraising project personnel and providing for general development, i.e. improvement of knowledge, attitudes, and skills. Leading is creating a working environment and an atmosphere that will assist and motivate people so that they will contribute to the achievement of organization and group goals. Controlling measures actual performances against planned goals and, in case of deviations, devises corrective actions. This entails rewarding and disciplining project personnel. software maintenance organizations can be designed and set up with three

structures: functional, project, or matrix

Functional organizations are hierarchical in nature. The maintenance organization is broken down into different functional units, such as software modification, testing, documentation, quality assurance, etc. Functional organizations present the advantage of a centralized organization of similar specialized resources. The main weakness is that interface problems may be difficult to solve: whenever a functional department is involved in more than a project conflicts may arise over the relative priorities of these projects in the competition for resources. In addition, the lack of a central point of complete responsibility and authority for the project may entails that a functional department places more emphasis on its own specialty than on the goal of the project. Project organizations are the opposite of the functional organizations (see figure 14). In this case a manager is given the full responsibility and authority for conducting the project; all the resources needed for accomplishing the project goals are separated from the regular functional structure and organized into an autonomous, self-contained team. The project manager may possibly acquire additional resources from outside the overall organization. Advantages of this type of organization are a full control over the project, quick decision making, and a high motivation of project

26 personnel. Weaknesses include the fact that there is a start-up time for forming the team, and there may be an inefficient use of resources. Matrix organizations are a composition of functional and project organizations with the objective of maximizing the strengths and minimizing the weaknesses of both types of organizations.

Maintenance is still perceived by many organizations as a non

strategic issue, and this explain why it is staffed with students and new hired people. To compound the problem there is the fact that most Universities do not teach software maintenance, and maintenance is very rarely though in corporate training and education programs, too. The lack of appraisal of maintenance personnel generates other managerial problems, primarily high turnover and low morale

8. System Security Security can have varying levels of difficulty for implementation. One factor in determining the difficulty is the number and distribution of the systems. When only individual systems need to be protected, such as one computer with all files residing locally and with no need to connect to any outside resources, security is not as complex as with distributed systems. With distributed systems architecture, there are different nodes and resources. One major issue with distributed systems is application security. There is the question of how security is handled in distributed applications, and how the client handles applications coming from an unknown source. Establishing security policy The security policy consists of those procedures and regulations intended to maintain the desired level of system security. The security policy for the Teradata RDBMS should include two essential implementation elements:

27  

System-enforced security features Personnel-enforced security features ( via the administrator, operator, and

end users) System-enforced security is relatively easy to implement. It defines how to use the Teradata security features and the rules. Implementing those rules is responsible by the security administrator. The primary consideration for establishing a security policy includes:  Identification of security needs.  Identification of policies and procedures to meet those needs. Identifying Security needs and security levels The first step to establish a security policy is to identify security needs, which will involve the following:  Identifying the business importance of the data and its associated 

processing system. Assigning a security priority to the data, based on the business case



evaluation. Identifying the classes of users requiring access to the Teradata RDBMS



and the data under its control. Identifying the system resources requiring protection to ensure continued availability to all valid Teradata users.

The security requirements should be based on the business value of the data processed on the system. A system that stores and processes highly sensitive data probably has a greater need for security than one that does not. There are three levels of data security, including minimal, moderate, and high. Each level will have its advantages and disadvantages:  Minimal security Anyone who has successfully logged on to the system has unrestricted access to all data and Teradata RDBMS resources. No security-related auditing is done, and there is no formal security policy. The only security-related access restriction is that a user must first gain access to a client system that is capable of communicating with the Teradata RDBMS. All these make sharing information is extremely simple, and the system performance is enhanced by the lack of security enforcement activities. On the other hand, obviously, the data is subject to destroy or corrupt due to the luck of the system security control.

28 

Moderate security In this class, users are grouped according to their needs and trustworthiness. Under moderate security, unlimited access is reserved for a small, privileged subgroup. Only occasional auditing of security-related events is performed, and no formal security policy exists for the users. In this class, security-related events that have a little or no effect on system performance, and users are subject to little or no demand for additional effort to perform their work, but the disadvantage is that it's possible that serious violation attempt can go undetected for extended



periods. High security At this level, a security administrator is identified and charged with establishing and maintaining Teradata RDBMS security. Physical access to processors, disk storage units, and system consoles is carefully controlled. Security-related events are audited regularly. Random security audits of individual users are performed. In this class, data and processing resources are afforded a high level of protection. If an unauthorized access is attempted, the auditing policy is designed to both detect the attempt and permit corrective measures to be implemented. The disadvantage is that shared data requires additional effort on the part of owner, as they must define who is authorized to access the owned information. Also, based on the frequency and scope of the audit, system performance can be negatively affected by the demands of auditing

security-related events. Formulating Security Policy Once the security needs of the system have been defined, a security policy can be formulated. The security documents should cover:  Extent of the need for security  Benefits to be derived form a secure system  A defined management policy when a user is discovered attempting to    

violate security Password protection Granting access to data Computer room staff Contacting the security administrator

29

9.Reference & Appendices  www.google.com

10.Conclusion RTO OFFICE MANAGEMENT SYSTEM is a web application, which is very useful for RTO works completion online. Here we are developing such types of the module which help to reduce the RTO work manually and it helps to save the time of the user. Considerably reduce the corruption in the transport department. Keep the license documents safely.

30