Online Rto Management System

ONLINE RTO MANAGEMENT SYSTEM
MAIN PROJECT REPORT

Submitted in partial fulfillment of the requirements For the award of the degree of
B.Sc. COMPUTER SCIENCE MAHATHMA GANDHI UNIVERSITY KOTTAYAM
Presented by, KRISHNALAL.K.J (SBAD10186520) DEPARTMENT OF COMPUTER SCIENCE Sree Narayan Arts and Science College Kedamangalam , N.Paravur 2011-2013
S.N.ARTS AND SCIENCE COLLEGE
KEDAMANGALAM
CERTIFICATE
This is to certify that the report entitled ONLINE RTO MANAGEMENT SYSTEM is submitted by Krishnalal.k.j in partial fulfillment of requirement of Bachelor Of
Computer Science of S.N Arts & Science College Kedamagalam affililated to Mahatma Gandhi University Kottayam during their 6th semester.
Internal Guide (ANITHA C.R )
Head Of the Department (SWAPNA SUMAN)
External Guide
KEDAMANGALAM
DECLARATION
We here by declare that the project entitled ONLINE RTO MANAGEMENT SYSTEM has been carried out as a group project. The project has been submitted to Sree Narayana Arts and Science College, Kedamangalam for the partial fulfillment of the requirements for the award of the degree Bsc Computer Science under Mahatma Gandhi University.
KRISHNALAL.K.J Place :. Date :.
KEDAMANGALAM
ACKNOWLEDGEMENT
We are so glad to present our project report on ONLINE RTO MANAGEMENT SYSTEM, which is prepared as a part of our fifth semester project in BSc Computer
Science. This project work is the outcome of guidance provided by dedicated and experienced personal of SREE NARAYANA ARTS AND SCIENCE COLLEGE, KEDAMANGALAM. We thank God and our parents for helping us start off with good education. With profound sense of indebtedness, we use this opportunity to express our sincere thanks to our beloved principal, P.M.SURESH for providing all sorts of support and necessary facilities throughout the course and for the inspiration to complete my project. We express our sincere gratitude to Mrs. Swapna Suman Head of BSc. Computer Science Department for inspiration and permission to carry out our project. We wish to extend our thanks to our project guide ANITHA C.R Lecturer, Department of BSc. Computer Science, JISH JOHN Lecturer, Department of BSc. Computer Science and NIMI V.P, Lecturer, Department of BSc. Computer Science and JISHA DEEPU Lecturer , Department of BSc. Computer Science for their keen interest, valuable guidance and support rendered throughout our project. Last but not the least; we extend our sincere thanks to all our seniors and classmates for their help and support. And also we would like to extend our deep sense of gratitude to all those who have assisted us in the successful completion of this project.
KEDAMANGALAM
CONTENTS CONTENTS PA GE NO : 7 8 10 10 12 13 14 15 17 18 `18 20 21 21 22 24 30 31 36
1. INTRODUCTION 1.1 OVERVIEW OF THE SYSTEM 1.2 OBJECTIVE OF THE PROJECT 1.3 MODULES 2. SYSTEM ANALYSIS 2.1 EXISTING SYSTEM 2.2 PROPOSED SYSTEM 2.3 FEASIBLTY ANALYSIS 3. SYSTEM SPECIFICATION 3.1 SOFTWARE SPECIFICATION 3.2 HARDWARE SPECIFICATION 4. SYSTEM DESIGN 4.1 INPUT DESIGN 4.2 OUTPUT DESIGN 4.3 DATA FLOW DIAGRAM 5. SOFTWARE DEVELOPMENT 5.1 PLATFORM OVERVIEW 6. SOURCE CODE
KEDAMANGALAM
7. SYSTEM TESTING & IMPLEMENTATION 7.1 SYSTEM TESTING 7.2 SYSTEM IMPLEMENTATION 7.3 SYSTEM MAINTANCE 7.4 SYSTEM SECURITY 8. CONCLUSION 9. FUTURE ENHANCEMENT 10. APPENDIX 10.1 SCREEN SHOTS 10.2 BIBLIOGRAPHY
56 57 60 64 65 69 71 73 74 85
KEDAMANGALAM
INTRODUCTION
KEDAMANGALAM
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.1OVERVIEW
Administrator is power user. He has the power to verify the data entered by the user, processing of data and provide appropriate solutions. 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 is the person who gets the full benefits of this application.By introducing the new system we have been organized some striking felicities.Registration of vehicle through online. Fancy number selection of vehicles through online. Issue of informations about license, which include application forms, demo of leaners license test and other informations. It helps traffic police for tracing particular vehicles. It helps for public awareness.Separate account for the license holders and police. Provide mail alerts for users about license expiry.And also register Complaint.
S.N.ARTS AND SCIENCE COLLEGE KEDAMANGALAM
2.2.2 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. Can avoid intermediate persons & institutions. Helpful in traffic issues: authorized users can trace the vehicle in the
accident cases using their register number. It is more users friendly: the sections such as, registration, license etc are Demo questions of learners license test will help the users in their license
combined together in a single window.
test. 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
RTO Management System has been designed to automate the process of registration of vehicle and issuing driving license process. System can make the daily activities efficient and providing the fast response to store and retrieve information.
Type - Web Front End ASP.NET
Back End - SQL Server Others Itext Sharp
KEDAMANGALAM
10
1.2 OBJECTIVES OF RTO MANAGEMENT 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.3MODULES
User Management Including Login management of different users. User Creation of different users. Provide change Password option for users.
Learning License Learning license module includes the learners registration and the license expire details. Also includes the online license test.
Permanent License The module includes permanent license registration. Also Renewal License feature. And also provides facility for Duplicate License.
Vehicle Registration The module includes new registration of vehicles. And Getting Duplicate Registration,
11
Reports Corresponding to each operation report generation in PDF format will be available for future reference.
KEDAMANGALAM
12
SYSTEM ANALYSIS
KEDAMANGALAM
13
2.1 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, and fitness. 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.
KEDAMANGALAM
14
2.2 Proposed System

The proposed system is aimed to automate the major processes in the Regional Transport Office.
2.2.1 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.
By introducing the new system we have been organized some striking felicities: Registration of vehicle through online. Fancy number selection of vehicles through online. Issue of informations about license, which include application forms, demo of
leaners license test and other informations. It helps traffic police for tracing particular vehicles. It helps for public awareness. Separate account for the license holders and police. Provide mail alerts for users about license expiry. Complaint registration.
KEDAMANGALAM
15
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. Can avoid intermediate persons & institutions. Helpful in traffic issues: authorized users can trace the vehicle in the accident
cases using their register number. It is more users friendly: the sections such as, registration, license etc are
combined together in a single window. test. Users can have knowledge about the new rules and regulations from the Demo questions of learners license test will help the users in their license
informations & awareness section.
2.3 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. Feasibility analysis involves the following steps:

Form a project and appoint a project leader Prepare system flowcharts Weigh system performance Prepare and report final project directive to management
KEDAMANGALAM
16
There are three key considerations involved in feasibility analysis namely: Economic feasibility Technical feasibility Operational feasibility
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. 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. 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 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.
KEDAMANGALAM
17
SYSTEM SPECIFICATION
KEDAMANGALAM
18
3.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 Client Side : ASP.NET with C#.NET : Ajax.net, Crystal reports : Microsoft SQL Server 2005 : Windows NT/2000 Server/ XP/ 2003/ Longhorn (with IIS) : 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.
3.2 HAERDWARE 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 Processor speed System Memory Display Cache Size : Pentium IV and above : 1.4 GHz Onwards : 128 Mb Minimum 256 Mb Recommended : Graphics Card Capable of Produce 1024,768 Resolution : 512 KB
KEDAMANGALAM
19
RAM Network Card
: 512 MB (Minimum) : Any Card Can Provide a 100 Mbps Speed
Network Connection : UTP or Coaxial Cable Connection Printer Hard disk Monitor Mouse Keyboard Modem : 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
KEDAMANGALAM
20
SYSTEM DESIGN
KEDAMANGALAM
21
4.1 INPUT DESIGN
Input design is the process of converting a user-oriented description of the inputs to a computer based business system into a programmer-oriented specification. Inaccurate input data is the most common cause of processing errors. Effective input design minimizes errors made by data entry operators. The input design is the link that ties information system into the world of its users. Input design consists of developing specific procedures for data preparations, steps necessary to put the transaction data in the form that is usable for computer processing. The data entry operator need to know the space allocated for each field, the field
sequence which must match with the source document and the format in which the data is entered. Our project Online R T O Management System has got several inputs taken from the user. They are:

Details of vehicles and license holders. Complaints by the user.
The system is provided with C# pages for the user to input abovedetails. Only the administrator and registered user are able to upload data. So their details are the major inputs to the system.
4.2 OUTPUT DESIGN
Outputs form computer systems are required primarily to communicate the processing to the end users. The output of the system designed in such a way that it provides, opportunities, problem or warnings, trigger an action and confirm an action. The userfriendly interfaces provide a clear output to the system. The output of this software system is a website. This system consists of online vehicle registration, fancy number selection, informations about License, helps traffic police for tracing particular vehicles, and complaint registration.
22
In this system the output that can be viewed by the end user is the website. It provides an opportunity to get public awareness, online registration for vehicles, selection of fancy number, license application form downloading and uploading, and complaint registration, automatic e mail for the registered user about license renewal etc.
4.3 DATABASE DESIGN

Tables Table Name: Login
Column Name Username Password status
Column Description Name of the user password Status
Data Type
Width/Size Constraints
Varchar Varchar Int
30 30 32
Primary key
Screen Label Name Username Password status
Table. Name:QuestionBank
Column Name Qid Question Choice1 Choice2 Choice3 Rightanswer
Column Description Id of the question Question Choice Choice Choice Answer
Data Type Int Varchar Varchar Varchar Varchar int
Width/Size 32 Max 50 50 50 32
Constraints Primary key
Screen Label Name Qid Question Choice1 Choice2 Choice3 Rightanswer
Table Name: SignUp
Column Name
Column Description
Data Type
Width/Size Constraints
Screen Label Name
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM Id Name Sex Dob mobile username User id Name of the user Sex Date of birth Mobile no username Int Varchar Varchar Varchar Varchar Varchar 32 25 7 12 15 25 Primary key Id Name Sex Dob mobile username
23
Primary key
Table Name: Download
Column Name id Name Category Fname Status dte
Column Description Id of the download Name of download Category of download First Name Status of download Date of download
Data Type Int Varchar Varchar Varchar Int Varchar
Width/Size Constraints 32 50 50 50 32 50 Primary key
Screen Label Name id Name Category Fname Status dte
Table Name: FileUpload Column Name id Userid Category Filename Status dte Column Description Id of the file Id of the user Category of file Name of the file status date Data Type Int Varchar Varchar Varchar Int Varchar Width/Size Constraints 32 50 50 50 32 50 Primary key Foreign key Screen Label Name id Userid Category Filename Status dte
KEDAMANGALAM
24
Table Name: License Column Name Id Authority Name Sex Paddress Caddress Dob Edu_qual Mobileno Dte Id_mark Blood Email Expdate Status Column Description Id of licence Name of authority Name of the user Sex Permanent address Communication address Date of birth Educational qualification Contact no Date Identification mark Blood group E mail address Licence expiry date status Data Type Int Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar int Width/Size Constraints Screen Label Name 32 Primary key Id 50 Authority 25 7 max max 12 max 15 50 max 8 50 50 32 Foreign key Name Sex Paddress Caddress Dob Edu_qual Mobileno Dte Id_mark Blood Email Expdate Status
Table Name: License photo
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM Column Name id Licenseno Filename Column Description Id of license holder License number Name of the file Data Type int varchar varchar Width/Size Constraints Screen Name 32 Primary key id 50 50
25
Label
Licenseno Filename
Table Name: VehicleReg Column Name Id Name Age Paddress Column Description Id of the vehicle Name of user Age of the user Permanent address Caddress Communication address Dealer Name of dealer class Class of the vehicle Body Type of body Vehicle Name of vehicle Manuname Name of manufacturer Dateofmanu Date of manufacturing Hp Horse power Chassisno Chassis number Engno Engine number Capacity Capacity Fuel Fuel type Colour Colour of vehicle Length Length of vehicle Width Width of vehicle Height Height of vehicle
Data Type Int Varchar Int Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Float Varchar Varchar Float Float Float
Width/Size Constraints Screen Label Name 32 Primary key Id 25 Name 32 Age max Paddress Max 50 50 50 50 50 50 50 50 50 50 50 Caddress Dealer class Body Vehicle Manuname Dateofmanu Hp Chassisno Engno Capacity Fuel Colour Length Width Height
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM Regno Registration number Varchar 50 Foreign key Regno
26
Table Name: Fancy Number Column Name id Fancynumber status Column Description Id of the fancy number Fancy number status Data Type int varchar int Width/Size Constraints Screen Name 32 Primary key id 50 32 Label
Fancynumber status
Table Name: Info Column Name id info Column Description Information id information Data Type int varchar Width/Size Constraints 32 max Primary key Screen Label Name id info
Table Name: Mail Column Description Mail id Name of sender Name of recipient Subject of mail Contents of the mail Data Type int varchar varchar varchar varchar Width/Size Constraints Screen Name 32 Primary key id 20 From1 20 25 max To1 subject body Label
Column Name id From1 To1 subject body
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM dte status date status varchar int 30 32 dte status
27
Table Name: OfficialReg Column Name id name designation department address ContactNo mobile Username status Column Description Registration id Name of official Designation Department name Address of official Contact number Mobile number Name of the user status Data Type int varchar varchar varchar varchar varchar varchar varchar int Width/Size Constraints Screen Name 32 Primary key id 25 name 30 30 max 15 15 25 32 Label
designation department address ContactNo mobile Username status
4.4 Data Flow Diagram (DFD)
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
28
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 .
Level 0
KEDAMANGALAM
29
Level 1
KEDAMANGALAM
30
SOFTWARE DEVELOPMENT
KEDAMANGALAM
31
5. SOFTWARE DEVELOPMENT 5.1 PLATFORM OVERVIEW

ASP.NET ASP.NET is more than the next version of Active Server Pages (ASP); it is a unified Web development platform that provides the services necessary for developers to build enterprise-class Web applications. While ASP.NET is largely syntax compatible with ASP, it also provides a new programming model and infrastructure for more secure, scalable, and stable applications. ASP.NET is an entirely new technology. ASP.NET is a part of the Microsoft .NET framework, and a powerful tool for creating dynamic and interactive web pages. ASP.NET is a server side scripting technology that enables scripts (embedded in web pages) to be executed by an Internet server. Microsoft's Internet Information Services (IIS) Web server is by far the most common platform for ASP.NET websites it supports code written in compiled languages such as Visual Basic, C#, this technology can be very beneficial in today's broadband era where web applications play a very significant role.Asp.Net is Compiled one rather than interpreted. Asp.net provides the developer with several controls to perform basic as well as advanced operations. Controls provided in Asp.net falls under HTML Controls, HTML Server Controls. HTML SERVER CONTROLS: HTML Server Controls looks exactly like the HTML Controls with one difference that they are executed on the server rather than the client. Just add a run at server attribute to indicate that element should be treated as a server control. HTML server controls must be within a <form> tag with the runat="server" attribute. WEB SERVER CONTROLS: Web Server Controls are the most advanced controls in Asp.net. Each control comes with tons of features that allows the developer to complete the task in less time. Web Server
KEDAMANGALAM
32
Controls are executed on the Server. Web Server Controls include datagrid control, datalist control, calendar control and many many more. ASP.NET ARCHITECTURE
As the illustration shows, all Web Administrators communicate with ASP.NET applications through IIS. IIS deciphers and optionally authenticates the request. If Anonymous is turned on, no authentication occurs. IIS also finds the requested resource (such as an ASP.NET application), and, if the client is authorized returns the appropriate resource. MICROSOFT .NET FRAMEWORK
The .NET Framework is an environment for building, deploying, and running Web applications and Web Services. Microsoft's first server technology ASP (Active Server Pages), was a powerful and flexible "programming language". But it was too code oriented. It was not an application framework and not an enterprise development tool. The Microsoft .NET Framework was developed to solve this problem. The .NET Framework is the infrastructure for the new Microsoft .NET Platform. And it is a common environment for building, deploying, and running Web applications and Web Services. The .NET Framework contains a common language runtime and common class libraries - like ADO .NET, ASP .NET and Windows Forms - to provide advanced standard services that can be integrated into a variety of computer systems. The .NET Framework provides a feature-rich application environment, simplified development and easy integration between a numbers of different development languages. The .NET Framework is language neutral. Currently it supports C++, C#, Visual Basic, and Jscript.
33
Microsoft's Visual Studio.NET is a common development environment for the new .NET Framework.
THE .NET FRAMEWORK CONSISTS OF 3 MAIN PARTS: Programming languages:

C# (Pronounced C sharp) Visual Basic (VB .NET) J# (Pronounced J sharp) Server technologies and client technologies:
ASP .NET (Active Server Pages) Windows Forms (Windows desktop solutions) Compact Framework (PDA / Mobile solutions) .NET FRAMEWORKS FEATURES
Easier and quicker programming Reduced amount of code Declarative programming model Richer server control hierarchy with events Larger class library Better support for development tools Increased Performance Greater scalability C# LANGUAGE Microsoft C# (pronounced C sharp) is a new programming language designed for building a wide range of enterprise applications that run on the .NET Framework. An evolution of Microsoft C and Microsoft C++, C# is simple, modern, type safe, and object oriented. C# code is compiled as managed code, which means it benefits from the
KEDAMANGALAM
34
services of the common language runtime. These services include language interoperability, garbage collection, enhanced security, and improved versioning support. C# is introduced as Visual C# in the Visual Studio .NET suite. Support for Visual C# includes project templates, designers, property pages, code wizards, an object model, and other features of the development environment. The library for Visual C# programming is the .NET Framework. MICROSOFT SQL SERVER 2005 Microsoft SQL Server is a relational database management system (RDBMS). Users of small to medium databases appreciate the system, in part because it supports Transact - Structured Query Language (T- SQL). Lately users of large enterprise databases have started taking advantage of its features as well. If you'd like to find out more, check out the tutorials in this section With the lowest implementation and maintenance costs in the industry, SQL Server 2005 delivers rapid return on your data management investment. SQL Server 2005 supports the rapid development of enterprise-class business applications that can give your company a critical competitive advantage. Benchmarked for scalability, speed, and performance, SQL Server 2005 is a fully enterprise-class database product, providing core support for Extensible Markup Language (XML) and Internet queries. Microsoft SQL Server 2005 includes a complete set of graphical tools and command line utilities that allow users, programmers, and administrators to increase their productivity. SQL Server is a Relational database where data is stored and retrieved very efficiently.SQL Server Express is a free, easy to use, redistributable version of SQL Server 2005 designed for building simple data-driven applications. Developers can design schemas, add data, and query local databases, and perform most of the features supported by SQL Server 2005. SQL Server 2005 supports Windows and Server authentication modes and is closely integrated with it. In Windows Authentication mode, specific Windows user and group accounts are trusted to log in to SQL Server. no passwords are passed across the network during the authentication process. In Mixed Mode Authentication, both Windows
KEDAMANGALAM
35
accounts and SQL Server-specific accounts (known as SQL logins) are permitted. When SQL logins are used, SQL login passwords are passed across the network for authentication
KEDAMANGALAM
36
SOURCE CODE
KEDAMANGALAM
37
SqlHelper.cs
using System; using System.Data; using System.Configuration; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; using System.Data; /// <summary> /// Summary description for database /// </summary> public class database { Sql Connection con =new SqlConnection(ConfigurationManager.ConnectionStrings["ConnectionString"].Connectio nString); public int nonquery(string s) { int n = 0; try { con.Open();
ONLINE RTO MANAGEMENT SYSTEM SqlCommand com = new SqlCommand(s, con); n = com.ExecuteNonQuery(); } catch { } finally { con.Close(); } return n; } public string scalar(string s) { string n = ""; try { con.Open(); SqlCommand com = new SqlCommand(s, con); n = com.ExecuteScalar().ToString(); } catch { } finally { con.Close(); } return n; } public DataTable table(String s) {
38
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM DataTable n = new DataTable(); try { con.Open(); SqlCommand cmd = new SqlCommand(s, con); SqlDataAdapter da = new SqlDataAdapter(cmd); da.Fill(n); } catch { } finally { con.Close(); } return n; }
39
/*License Application*/
using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls;
ONLINE RTO MANAGEMENT SYSTEM using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.IO; public partial class usercontrol_License : System.Web.UI.UserControl { database db=new database(); protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { int i=0; string cnt = ""; try { cnt = db.scalar("select max(id) from LicensePhoto"); } catch { } int id = 0; if (cnt != "") { id = int.Parse(cnt) + 1; } else { id = 1; } string ft = FileUpload1.PostedFile.FileName; string fname = Path.GetFileName(ft); string str = (id.ToString()) + fname;
40
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM i = db.nonquery("insert into License values('" + TextBox1.Text + "','" +
41
TextBox2.Text + "','" + DropDownList1.SelectedItem.ToString() + "','" + TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox7.Text + "','" + TextBox8.Text + "','"+TextBox12.Text+"','" + TextBox9.Text + "','" + TextBox10.Text + "','" + TextBox11.Text + "','" + TextBox13.Text + "','"+TextBox14.Text+"','1')"); if (i > 0) { Label1.Text = "Saved"; TextBox1.Text = ""; TextBox2.Text = ""; TextBox4.Text = ""; TextBox5.Text = ""; TextBox6.Text = ""; TextBox7.Text = ""; TextBox8.Text = ""; TextBox9.Text = ""; TextBox10.Text = ""; TextBox11.Text = ""; TextBox12.Text = ""; TextBox13.Text = ""; string str1 = ""; try { str1 = db.scalar("select Licenseno from LicensePhoto where Licenseno='" + TextBox14.Text + "'"); } catch { } if (str1 != "") { } else { int g = 0;
42
g = db.nonquery("insert into LicensePhoto values('" + TextBox14.Text + "','" + str + "')"); if (g > 0) { FileUpload1.SaveAs(Server.MapPath("~") + @"\\License\" + str); Label1.Text = "success"; } else { Label1.Text = "Not success"; } } } else { Label1.Text = "Not Saved"; } } }
Use: To apply for a licence for registered users.
/*Vehicle Registration*/
using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security;
ONLINE RTO MANAGEMENT SYSTEM using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class usercontrol_VehicleReg : System.Web.UI.UserControl { database db = new database(); protected void Page_Load(object sender, EventArgs e) { } protected void TextBox8_TextChanged(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { int i = 0; i = db.nonquery("insert into VehicleReg values('" + TextBox1.Text + "','" +
43
TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox7.Text + "','" + TextBox8.Text + "','" + TextBox9.Text + "','" + TextBox10.Text + "','" + TextBox11.Text + "','" + TextBox12.Text + "','" + TextBox13.Text + "','" + TextBox14.Text + "','" + TextBox15.Text + "','" + TextBox16.Text + "','" + TextBox17.Text + "','" + TextBox18.Text + "','" + TextBox19.Text + "','" + TextBox20.Text + "')"); if (i > 0) { Label1.Text = "Saved"; TextBox1.Text = ""; TextBox2.Text = ""; TextBox3.Text = ""; TextBox4.Text = "";
ONLINE RTO MANAGEMENT SYSTEM TextBox5.Text = ""; TextBox6.Text = ""; TextBox7.Text = ""; TextBox8.Text = ""; TextBox9.Text = ""; TextBox10.Text = ""; TextBox11.Text = ""; TextBox12.Text = ""; TextBox13.Text = ""; TextBox14.Text = ""; TextBox15.Text = ""; TextBox16.Text = ""; TextBox17.Text = ""; TextBox18.Text = ""; TextBox19.Text = ""; TextBox20.Text = ""; } else { Label1.Text = "Not Saved"; } } }
44
Use: To apply for vehicle registration.
/*Complaint Module*/
using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq;
ONLINE RTO MANAGEMENT SYSTEM using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class usercontrol_Complaint : System.Web.UI.UserControl { database db = new database(); public static string uid = ""; protected void Page_Load(object sender, EventArgs e) { if (!IsPostBack) { uid = Session["UID"].ToString(); } } protected void Button1_Click(object sender, EventArgs e) { int i = 0; i = db.nonquery("insert into
45
Complaint
values('"+uid+"','"+TextBox1.Text+"','"+TextBox2.Text+"','"+DateTime.Now.ToString() +"','1')"); if (i > 0) { Label1.Text = "Complaint Send Succesfully"; TextBox1.Text = ""; TextBox2.Text = ""; } else {
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM Label1.Text = "Not Send"; } } }
46
Use: For registering a complaint.
/*Fancy Number Selection*/
using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class usercontrol_FancyNumber : System.Web.UI.UserControl { database db = new database(); protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { string str = ""; try {
ONLINE RTO MANAGEMENT SYSTEM str = db.scalar("select FancyNumber from FancyNumber where FancyNumber='"+TextBox1.Text+"'"); if (str != "") { Label2.Text = "FancyNumber Already used"; TextBox1.Text = ""; } else { int i = 0;
47
i = db.nonquery("insert into FancyNumber values('" + TextBox1.Text + "','1')"); if (i > 0) { Label2.Text = "Success"; TextBox1.Text = ""; } else { Label2.Text = "Not Saved"; //TextBox1.Text = ""; } } } catch { } } }
Use: To select a fancy number from the available list.
/*Vehicle Search*/
using System; using System.Collections;
ONLINE RTO MANAGEMENT SYSTEM using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class usercontrol_VehicleSearch : System.Web.UI.UserControl { database db = new database(); protected void Page_Load(object sender, EventArgs e) { }
48
protected void RadioButtonList1_SelectedIndexChanged(object sender, EventArgs e) { CheckBox3.Visible = false; CheckBox4.Visible = false; } protected void CheckBox3_CheckedChanged(object sender, EventArgs e) { RadioButtonList1.Visible = false; } protected void CheckBox4_CheckedChanged(object sender, EventArgs e) { RadioButtonList1.Visible = false; } int r = 0; public static int cnt = 0;
ONLINE RTO MANAGEMENT SYSTEM protected void Button1_Click(object sender, EventArgs e) { if (RadioButtonList1.SelectedIndex == 1) { Label3.Visible = true; TextBox2.Visible = true; Label2.Visible = false; TextBox1.Visible = false; Button2.Visible = true; cnt = 1; } else if (RadioButtonList1.SelectedIndex == 0) { Label2.Visible = true; TextBox1.Visible = true; Label3.Visible = false; TextBox2.Visible =false; Button2.Visible = true; cnt = 2; } else if (CheckBox3.Checked == true && CheckBox4.Checked == true) { r = 1; Label4.Visible = true; Button2.Visible = true; TextBox3.Visible = true; RadioButtonList1.Visible = false; Label5.Visible = true; TextBox4.Visible = true; Label2.Visible = false; TextBox1.Visible = false; Label3.Visible = false;
49
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM TextBox2.Visible = false; cnt = 3; } if (CheckBox3.Checked == true) { if (r == 0) { Button2.Visible = true; Label4.Visible = true; TextBox3.Visible = true; RadioButtonList1.Visible = false; Label5.Visible = false; TextBox4.Visible = false; Label2.Visible = false; TextBox1.Visible = false; Label3.Visible = false; TextBox2.Visible = false; cnt = 4; } } if (CheckBox4.Checked == true) { if (r == 0) { Button2.Visible = true; Label5.Visible = true; TextBox4.Visible = true; RadioButtonList1.Visible = false; Label4.Visible = false; TextBox3.Visible = false; Label2.Visible = false; TextBox1.Visible = false;
50
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM Label3.Visible = false; TextBox2.Visible = false; cnt = 5; } } } protected void Button2_Click(object sender, EventArgs e) { if (cnt == 1) { DataTable dt = new DataTable();
51
dt = db.table("SELECT name AS NAMEOFOWNER,age AS AGE,caddress AS CONTADDRESS,dealer AS DEALERNAME,class AS CLASS, body AS BODY,vehicle AS VEHICLENAME, manuname AS MANUNAME, dateofmanu AS DATEOFMANU, hp AS HP, chassisno AS CHASSISNO, engno AS ENGNO,capacity AS CAPACITY, fuel AS FUEL, color AS COLOUR, length AS LENGTH, width AS WIDTH, height AS HEIGHT, regno AS REGNO FROM VehicleReg where chassisno like '%"+TextBox2.Text+"%'"); if (dt.Rows.Count > 0) { GridView1.DataSource = dt; GridView1.DataBind(); } else { Label6.Text = "No Records"; } } else if (cnt == 2) {
DataTable dt = new DataTable();
KEDAMANGALAM
52
dt = db.table("SELECT name AS NAMEOFOWNER,age AS AGE,caddress AS CONTADDRESS,dealer AS DEALERNAME,class AS CLASS, body AS BODY,vehicle AS VEHICLENAME, manuname AS MANUNAME, dateofmanu AS DATEOFMANU, hp AS HP, chassisno AS CHASSISNO, engno AS ENGNO,capacity AS CAPACITY, fuel AS FUEL, color AS COLOUR, length AS LENGTH, width AS WIDTH, height AS HEIGHT, regno AS REGNO FROM VehicleReg where regno like '%" + TextBox1.Text + "%'"); if (dt.Rows.Count > 0) { GridView1.DataSource = dt; GridView1.DataBind(); } else { Label6.Text = "No Records"; } } else if (cnt == 3) { DataTable dt = new DataTable(); dt = db.table("SELECT name AS NAMEOFOWNER,age AS AGE,caddress AS CONTADDRESS,dealer AS DEALERNAME,class AS CLASS, body AS BODY,vehicle AS VEHICLENAME, manuname AS MANUNAME, dateofmanu AS DATEOFMANU, hp AS HP, chassisno AS CHASSISNO, engno AS ENGNO,capacity AS CAPACITY, fuel AS FUEL, color AS COLOUR, length AS LENGTH, width AS WIDTH, height AS HEIGHT, regno AS REGNO FROM VehicleReg where vehicle like '%" + TextBox3.Text + "%' and color like'%"+TextBox4.Text+"%'"); if (dt.Rows.Count > 0) { GridView1.DataSource = dt; GridView1.DataBind(); } else
ONLINE RTO MANAGEMENT SYSTEM { Label6.Text = "No Records"; } } else if (cnt == 4) { DataTable dt = new DataTable();
53
dt = db.table("SELECT name AS NAMEOFOWNER,age AS AGE,caddress AS CONTADDRESS,dealer AS DEALERNAME,class AS CLASS, body AS BODY,vehicle AS VEHICLENAME, manuname AS MANUNAME, dateofmanu AS DATEOFMANU, hp AS HP, chassisno AS CHASSISNO, engno AS ENGNO,capacity AS CAPACITY, fuel AS FUEL, color AS COLOUR, length AS LENGTH, width AS WIDTH, height AS HEIGHT, regno AS REGNO FROM VehicleReg where vehicle like '%" + TextBox3.Text + "%'"); if (dt.Rows.Count > 0) { GridView1.DataSource = dt; GridView1.DataBind(); } else { Label6.Text = "No Records"; } } else if (cnt == 5) { DataTable dt = new DataTable(); dt = db.table("SELECT name AS NAMEOFOWNER,age AS AGE,caddress AS CONTADDRESS,dealer AS DEALERNAME,class AS CLASS, body AS BODY,vehicle AS VEHICLENAME, manuname AS MANUNAME, dateofmanu AS DATEOFMANU, hp AS HP, chassisno AS CHASSISNO, engno AS ENGNO,capacity AS CAPACITY, fuel AS FUEL, color AS COLOUR, length AS LENGTH, width AS WIDTH, height AS
KEDAMANGALAM
54
HEIGHT, regno AS REGNO FROM VehicleReg where color like '%" + TextBox4.Text + "%'"); if (dt.Rows.Count > 0) { GridView1.DataSource = dt; GridView1.DataBind(); } else { Label6.Text = "No Records"; } } } }
Use: To search for a vehicle using some key.
/*Message*/
using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; public partial class usercontrol_Messages : System.Web.UI.UserControl {
ONLINE RTO MANAGEMENT SYSTEM database db = new database(); protected void Page_Load(object sender, EventArgs e) { if (!IsPostBack) { DataTable dt = new DataTable(); string id=""; id=Session["UID"].ToString();
55
dt = db.table("select id,From1,Subject from Mail where Status='1' and To1='" + id + "' order by dte desc"); if (dt.Rows.Count > 0) { GridView1.DataSource = dt; GridView1.DataBind(); } } } protected void GridView1_SelectedIndexChanging(object sender, GridViewSelectEventArgs e) { int d = e.NewSelectedIndex; Session["inbox"] = GridView1.Rows[d].Cells[1].Text; Response.Redirect("InboxRead.aspx"); } } Use: To send informative mails to registered users.
KEDAMANGALAM
56
SYSTEMTESTING & IMPLEMENTATION
KEDAMANGALAM
57
7. SYSTEM TESTING & IMPLEMENTATION 7.1 SYSTEM 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. 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 Integration testing System testing Validation testing User acceptance testing
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 back-end also tested for successful acceptance and retrieval of data.
KEDAMANGALAM
58
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 back-end and the front-end 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.
KEDAMANGALAM
59
Test Case Design Methods The primary objective of test case design methods is to derive a set of test that has of highest likelihood of uncovering the defects. To accomplish this objective, two categories of test case design techniques are used Black box testing and white box testing. 1) White box testing White box testing is a set case design method that uses the control structure of the procedural design to derive test cases. Using white box testing methods, we can derive test cases that Guarantee that all independent paths within a module have been exercised
at least once Exercise all logical decisions on their true and false sides Execute all loops at their boundaries and within their operational bounds Exercise internal data structures to ensure their validity
2) Black box testing Black box testing methods focus on the functional requirements in the software. That is, black box testing enables us to derive sets of input conditions that will fully exercise All functional requirements of the program Black box testing attempts to find errors in the following categories: Incorrect or missing function Interface errors Errors in data structure or external job access Performance errors Initialization and termination errors.
KEDAMANGALAM
60
7.2.SYSTEM 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. Implementation Methodology An implementation methodology is a collection of practices, procedures and rules that must be applied to perform a specific operation to provide deliverables at the end of each stage. The eight principles listed below is built from a collection of procedures to establish an effective implementation methodology framework. This framework provides flexibility to react and adapt to the unique requirements of every project, incorporating the principles of: 1. Project Management & Planning 2. Scope & Requirements Specification 3. Risk & Issues Management 4. Communication & Training 5. Quality Management 6. Post-Implementation Review 7. Documentation G 8. Experience Project Management & Planning
KEDAMANGALAM
61
Project management is the art and science of communicating between individuals with different responsibilities, perspectives, and expectations so that the project team and the sponsoring organization perceive value and quality in the end product The implementation process should be driven by solid project management principles and the concept of people working in tandem. The project manager drives the collaborative process so team members work together to accomplish agreed goals. Scope & Requirements Specification The implementation approach should have an outcomes-based focus. This means that the process emphasizes on identifying the business requirements that target an organizations specific goals and objectives. This is achieved through a systematic manner which sets out a solution roadmap that transforms goals and objectives into functional requirements (critical success factors, csfs). Risk Management Risk is associated with almost everything we do and is definitely associated with software implementation projects. A risk is something that may happen, implying a probability of less than 100%, and if it does transpire, will have an adverse impact on the project. If it has a probability of 100%, in other words, it occurs then it becomes an issue. Such an issue is handled differently to a risk. Risk management An effective methodology approach addresses risk management in four stages: Stage 1: Identification Stage 2: Quantification Stage 3: Response Stage 4: Control Issue management Issues are really problems. To solve the problem, an action must be assigned to someone who has to do something by a due date. Issues should be tracked by type, status and priority. The methodology should encapsulate the following steps when managing issues: 1. Define what an issue is.
62
2. Keep log of issues that is easily accessible to everyone on the project. 3. Prioritize issues in terms of risk to project completion. 4. Assign an owner to the issue. 5. Most importantly, regularly monitor and report on the status of issues. Communication & Training Communication Communicate formally, informally and frequently. Keep people informed so that they will support the outcome of the project, understand what they need to do and the implications, and alert the project team to issues. Communication should be targeted at two key groups stakeholders such as staff, management, regulators, contractors and the project team. Training Training is essential for the uptake of the system by users. Some key considerations are: Scheduling training Too early and all will be forgotten; The audience involved The training strategy for management will be different for staff who are required to use the system as part of their day-to-day activities; The training content e.g. Exclude report writing skills for users who are only ever going to capture data. Quality Management Quality management ensures that the system meets or exceeds the customer expectations. It is a method for ensuring that all the activities, procedures and documentation required to implement a project are effective and efficient with respect to the system and its performance. The focus is not only on the product but also on how to achieve it. Post-Implementation Review This stage instigates learning from mistakes and identifying areas for improvement. In the context of quality management, this is the review stage. At project sign-off, a project close-out meeting should be held with all members of the project team, including stakeholders. Usually held as a workshop scenario, project team members and stakeholders discuss and document project lessons learned in the form of project outcomes, significant issues, benefits and risks. A project close-out report is a summary of these issues. For many projects, this is where the implementation ends. However, after a suitable period of time, a comprehensive
63
model will determine the overall success of a project by measuring and reviewing the client kpis in terms of the project and organizational objectives. Project learnings should also feedback into the implementation methodology itself in the form of continual improvement initiatives. Documentation An implementation methodology must be well documented. The documentation should be content and audience-specific and usually comes in the form of: Procedure An overview of the methodology, its phases, milestones and deliverables. This type of documentation also includes templates that help promote efficiencies and streamline the implementation process. This type of documentation is aimed at the project team. Technical Describes the technical & installation requirements for the information system. This type of documentation is aimed at a technical audience. End-User Refers to manuals for the end-user, system administrator and support staff. They include resources such as training manuals, training aides (such as powerpoint slides) and automated training material (such as animations). Experience Experience is a valuable commodity and vital ingredient for improving the success of any project. Leveraging the knowledge, talent and skills acquired through years of operational experience drives the development of a proven deployment methodology. It is not possible to sustain a quality model without continual improvement initiatives. A software providers implementation consultants should have extensive actual experience in addressing the day-to-day issues with which their clients are confronted. They must be able to advise, instruct, apply creative solutions, resolve process issues and leverage organizational resources. In this way, they also help develop the methodology through refinements and application of best practices. Implementation Plan Our project is designed by strictly following the rules and regulations of the Kerala Motor Vehicle act. So this can implement in any Regional Transport Office in Kerala.
KEDAMANGALAM
64
7,3 SYSTEM MAINTANANCE

Management is the process of designing and maintaining an environment in which individuals, working together in groups, accomplish efficiently selected aims . In thecase of maintenance the key aim is to provide cost-effective support to a software systemduring its entire lifespan. Management is concerned with quality and productivity, that implyeffectiveness 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 actionsfor 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 motivatepeople 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 differentorganizational structures: functional, project, or matrix Functional organizations are hierarchical in nature.The maintenanceorganization is broken down into different functional units, such as software modification,testing, documentation, quality assurance, etc. Functional organizations present the advantageof a centralized organization of similar specialized resources. The main weakness is that interface problems may be difficult to solve: whenever a functional department is
KEDAMANGALAM
65
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 thiscase 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 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 theobjective of maximizing the strengths and minimizing the weaknesses of both types oforganizations. 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 theproblem there is the fact that most Universities do not teach software maintenance, andmaintenance is very rarely though in corporate training and education programs, too. Thelack of appraisal of maintenancepersonnel generates other managerial problems, primarily high turnover and low morale
7.4 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.
66
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:

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.
67
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.
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.
KEDAMANGALAM
68
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
KEDAMANGALAM
69
CONCLUSION
KEDAMANGALAM
70
7CONCLUSION
The application is designed in such a way that any further enhancements can be done with ease. The system has the capability for easy integration with other systems. New modules can be added to the existing system with less effort. The system has six classes. Each of these classes has various procedures and functions. In future a new function or procedure can be easily added in the system through these classes. Or even a new class can be added. The system generates only a limited number of reports. If more detailed reports are required the system can be directed. Even though the system has well communication facility, it's not enough. The mail service can be enhanced with features bcc, cc etc. the system has full security but the account information for the customer credit information. Thus by adding this module the system transaction will be improved.
KEDAMANGALAM
71
FUTURE ENHANCEMENT
KEDAMANGALAM
72
9. FUTURE ENHANCEMENTS
This application can be easily implemented under various situations. We can add new features as and when we require. Reusability ispossible as and when require in this application. There is flexibilityin all the modules.
SOFTWARE SCOPE:
Extensibility:
This software is extendable in ways that its originaldevelopers may not expect. The following principles enhances extensibility like hide data structure, avoid traversing multiplelinks or methods, avoid case statements on object type anddistinguish public and private operations
Reusability:
Reusability is possible as and when require in thisapplication. We can update it next version. Reusable softwarereduces design, coding and testing cost by amortizing effortover several designs. Reducing the amount of code alsosimplifies understanding, which increases the likelihood thatthe code is correct. We follow up both types of reusability:Sharing of newly written code within a project and reuse ofpreviously written code on new projects.
KEDAMANGALAM
73
APPENDIX
KEDAMANGALAM
74
10 . APPENDIX 10.1 SCREENSHOT

login
admin Home
KEDAMANGALAM
75
ViewRegisteredUsers
Add maker
KEDAMANGALAM
ONLINE RTO MANAGEMENT SYSTEM add question
76
Add Vehicle Descriptio
KEDAMANGALAM
77
View Duplicate Licence Requests
View Duplicate Vehicle Registration Requests
KEDAMANGALAM
78
View Learning Licence Requests
View Licence Request.
KEDAMANGALAM
79
View Renew Licence Requests
View Renew Registration Requests
View Vehicle Registrstion Requests

80
Userlogin
KEDAMANGALAM
81
RequestLearningLicence
RequestDrivingLicence
KEDAMANGALAM
82
RequestVehicleRegistration
KEDAMANGALAM
83
RequestRenewLicence
RequestDuplicateLicence
KEDAMANGALAM
84
RequestDuplicateRegistration
RequestRenewRegistration
KEDAMANGALAM
85
BIBLIOGRAPHY
KEDAMANGALAM
86
11.

BIBLIOGRAPHY
Professional VB. NET - Bill Evjen, Billy Hollis, Rockford Lhotka An Introduction To Database Systems -Bipin.C.Desai Software Engineering -Roger S. -Marvin Gore -Silberschatze
Elements Of System Analysis Database system concept
Designing Visual Basic.NET Applications -David Vitter Mastering ASP.NET with VB.NET -A Russell Jones
KEDAMANGALAM
87
KEDAMANGALAM

Online Rto Management System

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Online Rto Management System

Hochgeladen von

Copyright:

Verfügbare Formate

ONLINE RTO MANAGEMENT SYSTEM

MAIN PROJECT REPORT