TRAFFIC RULES MASTERY

1. Introduction

1.1 overview of Existing System

The traffic police officers used to send the CHALLAN’S to that individual person who breach the

rules are they collect money at that time only. The existing system can’t control the traffic once

the motorist cross the rule and pay the challan’s we can’t say again the particular motorist cannot

cross the rules.

1.1.1 Limitations in Existing System

There is no database regarding previously rules crossed by the motorist.

Some individuals can miss use the money from the vehicular.

1.2 Overview of Proposed System

This service has the excellent features and high security applications. Here we are providing

the card system of different types. They are issued according to the violations made by the

persons. Moreover the FINE amount should be paid as the DEMAND DRAFT (DD).And we

provide a database for vehicle details with previous rules crossed by the motorist for further step

to taken on them. The proposed system provides information about vehicle with fast and accurate

result. We provide an upadtion function for updating the rules crossed and any further information

is to be modify. Once the final card is issue to motorist the vehicle is to be sized.

1.2.2 Advantages over Existing System:

Free of charge

User friendly interface

Works on all Java enabled systems

Optimized searching method - results are returned quickly

Miss use of money by individual can over come and traffic problems can over come

1.3 System Scope

This service has the excellent feature to provide the details of the vehicles based on their input

(vehicle number).It has the feasibility to provide the rules crossed by the violator. Whenever

the user want see the status of the particular vehicle. When he opens the application it shows

the previous violations made by the violator. To view the present status of that vehicle we have

to do the updation of the database to get the current details of the violator. Based on the

database of vehicle is to be sized by this we can maximum avoid the traffic.

1.4 System Purpose

The main purpose of this project is to avoid the problems being faced by traffic police. Here we are going to store the database of the each and every vehicle. Where it helps us to find out the rules crossed by the person. It is a card system which is of four different formats and payment FINE should be done by DD(Demand Draft), hence there is no chance of misusing the acquired money by individual TRAFFIC POLICE officer as it will goes into the particular bank account.

The overview of the project is to search the vehicle data from the database and shows the what

action to be taken on particular violator after updating the current database of motorist .This

project is based on the card system so we give a particular card to the violator based on number

of times rules crossed by the motorist

1.5 System modules

The project traffic rules mastery consists of following modules.

1.5.1 User Interface Manager

Design GUI for traffic mastery

This module handles Creating user interface by using j2me technology. For the searching

the vehicle number there should arrange a text field and one update button so that for the

interface design we use classes

1.5.2 Collect vehicles database

When user enters the vehicle number in the text field that should be verifies the in .ddb

libraries. This module handles and maintains all the database files .these files are acting like a

database for the vehicular.

1.5.3 Implementing search method

This module handles search operations for the given vehicle number and displays all possible

data which are retrieved from the database libraries with the number as input, and from the

database files it searches the violations of the motorist.

2.  LITERATURE SURVEY

.

2.1 Project Description:

This application consists of three important functionalities which are used to design the

modules. First one is the designing functionality for user interface through system. Second

functionality is related to database for maintaining the database which consisting of vehicle data

such as vehicle number, Driver licenses, number of times rules crossed and type of vehicle, the

final functionality is that for implementing the search methodology for displaying the particular

vehicle database which entered in the text field and also consisting of update button for updating

the rules crossed, based on this rules it display which card is issue to the vehicle owner. It is an

optimized search which returns quickly and works on all java enabled system and also much

efficient and user friendly.

Through updation we can go for want action to be taken on particular person who breach the

rules. Once the vehicle is sized after a particular time the vehicle is going to dispatch to the

motorist. This period of time also store in database once the time is out it indicate the message

from database. The existing system has high security feature. In this we use back end language is

database sql and front end is java standard edition.

2.2 Overview of java

Java is very powerful and popular language that supports the development of system based

application and web based application. It provides a number of capabilities that complement

those provide by JavaScript.

What is java?

The rapid growth in the popularity of the java language is nothing short of a phenomenon. In

less than a year, java went from a relatively unknown alpha version to an incredibly successful

version 1.0 release. Every major computer hardware and software vendor has since endorsed

Java its remarkable success is summed up by fact that Microsoft, its chief rival, not only

supports java with Internet explorer, but also sells J++, a popular development environment. In

this section we'll explore various aspects of Java

Features of java

Java is platform-independent:

Java’s phenomenal success is due to the fact that it provides the capability of develop compiled

software that runs, without modification, on a large variety of operating systems platform-

including Microsoft windows, Apple Macintosh, IBM os/2, Linux, and several varieties of

UNIX. In addition, and perhaps more importantly, specially designed java programs known as

applets run in the context of java-enabled web browsers, such as Netscape navigator and

Microsoft Internet explorer.

The java virtual machine is the key to java’s platform-independence. The java virtual machine

(JVM) provides a machine-independent and operating system-independent platform for the

execution of java code. The JVM is a program that executes java programs that are compiled

into the JVM byte code

Java Is Object-Oriented

Java is an object-oriented language, and provides all of the benefits of object-oriented

programming: classification, inheritance, object composition, encapsulation, and polymorphism.

Java supports single Inheritance, but not multiple Inheritances; however, it provides the interface

construct, which can be used to obtain the benefits of multiple inheritance without having to deal

with any of its drawbacks.

Java Is Familiar

One of the most striking characteristics of java, at least from a programmer's perspective,

is its familiarity. Java is based on c++ and retains much of its syntax. This makes the language

very easy to learn for c++ programmers. Since JavaScript is also based on both c++ and Java,

Java's syntax will be easy for you to learn. However, since java is a full object-oriented language

(as opposed to an object-based language, like JavaScript), you will have to learn some additional

programming constructs.

Java Is Simpler and More Reliable

Although java is based on c++, it is simpler and easier to use. This is because the

designers of java eliminated many of the complex and dangerous

2.3 JAVA DATABASE CONNECTIVITY (JDBC)

JDBC OVERVIEW:

JDBC is a Java API for executing SQL statements. (JDBC is as trademark and is not an acronym; JDBC is often thought of as understanding for "Java Database Connectivity"). It consists of a set of classes and Interfaces written in the Java Programming Language. JDBC provides a standard API for tool/database developers and makes it possible to write database applications using a pure Java API.

Using JDBC it is easy to send SQL statements to virtually any relational database. In other words, with the JDBC API, it is not necessary to write one program to access a Sybase database, another program to access a Oracle database, another program to access a Informix database, and so on.

One can write a single program using the JDBC API, and with in ail application written in Java programming language, one also doesn't have to worry about writing different applications to run on different platforms. The combination of Java and JDBC lets a programmer to write it once run it anywhere.

Java, being robust, secure, easy to understand, and automatically downloaded on a network, is an excellent language basis for database application. What is needed is a way for Java applications to walk to a variety of different databases. JDBC is the mechanism for doing this.

The JDBC Structure

The JDBC is two-dimensional structure. The reasoning for the split is to separate the low-level programming from the high-level application interface. The low-level programming is the JDBC driver. The idea is that database vendors and third-party software vendors will supply pre-built drivers for connecting to different databases. JDBC drivers are quite flexible: They can be local data sources or remote database servers. The implementation of the actual connection to the data source/database is left entirely to the JDBC driver. The structure of the JDBC includes these key concepts:

The goal of the JDBC is a DBMS independent interface, a “generic SQL database access framework,” and a uniform interface to different data sources.

The programmer writes only one database interface; using JDBC, the program can access any data source without recoding. The JDBC is not only a specification for using data sources in Java applets and applications, but it also allows you to create and use low-level drivers to connect and “talk” with data sources. You have now explored the JDBC architecture and seen how the ODBC fits into the picture. The important concept to remember about the JDBC is that the modular design of the JDBC interface allows you to change between drivers—hence databases—without recoding your Java programs.

The architecture of JDBC

The Driver Manager class is used to open a connection to a database via a JDBC driver, which must register with the Driver Manager before the connection can be formed. When a connection is attempted, the Driver Manager chooses from a given list of available drivers to suit the explict

JAVA APPLICATION

JDBC DRIVER MANAGER

JDBC API

Jdbc driver Jdbc driver

DBMS DBMS

type of database Connection. After a connection is formed, the calls to query and fetch results are made directly with the JDBC driver. The JDBC driver must implement the classes to process these functions for the specific database, but the rigid specification of the JDBC ensures that the drivers will perform as expected. Essentially, the developer who has JDBC drivers for a certain database does not need to worry about changing the code for the Java program if a different type of database is used (assuming that the JDBC driver for the other database is available). This is especially useful in the scenario of distributed databases.

WHAT DOES JDBC DO?

Simply put, JDBC makes it possible to do three things:

1. Establish a connection with the database

2. Send SQL statements

3. Process the results

The following code fragments give a basic example of these three steps:

ConnectionCon = DriverManager.getconnection (“jdbc: odbc:”sn,”login”,”password”).

2.4 Overview of Uml

Unified modeling language is a popular language that has been using for modeling the object

oriented software. It is a language for visualizing, specifying, constructing and documentation of

software artifacts. Object Management Group (OMG) has first adopted in 1997 as a language for

Object-Oriented Analysis and Design. It uses graphical notations to articulate the software design

projects. UML is a very significant part of development processes. (Grady Booch & Jim

Rumbaing, 1994)

GOALS OF UML:

1. It offers the users to express visual modeling language and ready to use.

2. To extend the core concepts, various extensibility and specialization mechanisms are

provided.

3. Development processes and programming language which are in particular are made to be

independent by the UML design.

4. Necessary understanding of the language is provided formally.

5. Development concepts like components, frameworks, collaborations and patterns.

6. The market of the Object-Oriented tools growth must be encouraged.

2.5 Overview of Data flow diagrams

DATA DESIGN

The data design transforms the information domain model into the data structures that will be required to implement the software. The data objects and relationships defined in the entity relationship diagram and the detailed data content depict in the data dictionary provide the basis for the data design activity. Part of data design may occur in conjunction with the design of software architecture. More detailed data design of software architecture. More detailed data design occurs as each software component is design. Data design creates a model of data and information that is represented at the high level of abstraction. This data model is then refined into progressively more implementation. Specific representations that can be processed by the computer- based system. The structure of data has always been an important part of software design.

Architectural Design

Ever since has the first program was divided into modules, software systems has had architectures and programmers have been responsible for the interaction and programmers have been responsible for the interactions among the modules and architectures have been implicit accidents of implementation.

The software architecture of a program or computing system is the structure of structures of the system, which comprise software components, the relation ship among them. Three keys reasons that software architecture is important.

Representation of software architecture is an enabler for communication between all

parties interested in the development of a computer- based system. The architecture highlights of early design decisions that will have a profound impact on

all software engineering work that follows and as important. On the ultimate success of the system as an operational entity.

The architecture constitutes a relatively small, intellectually graspable model of how the system is structured and how its components work together.

USER INTERFACE DESIGN

Interface design focuses on three areas of concern.

The design of interfaces between software components. The design of interface between the software and other non-human producers and

consumers of information. The design of the interface between a human and the computer.

2.6 FEASIBILITY STUDY

Feasibility study, which the proposed system is subjected as discussed below. The objective is to

feasibility study is a high level capsule version of the entire system analysis and design process.

After problem is clearly understood and solutions are proposed the next step is to conduct the

feasibility study, which is the part of the system analysis as well as design process. The main

objective of the study is to determine whether the proposed system is feasible or not. Mainly there

are three types of determine quickly at a minimum expense how to solve a problem. The purpose

of feasibility is not to solve the problem but to determine if the problem is worth solving. The

system has been tested for feasibility in the following points.

Technical feasibility

Operational feasibility

Economical feasibility

Technical Feasibility:

As we are developing this Image Processor Application on Java 2 platform edition which is an

open source and free of cost. Once we started developing this application in Java 2 platform

edition then they is no need of purchasing any special software or application software for

support. Java it self provides all necessary functionalities and resources for developing j2me

application For Example like developing GUI can be developed by Java.

Operational Feasibility:

To determine the operational feasibility of the system we should take into consideration the

awareness level of the user and management. Every thing will be understood by user once he sees

the application. The proposed system offers greater levels of user’s friendliness combine with

greater processing speed. Therefore the cost of maintenance can be reduced.

Economic Feasibility:

To decide whether a project is economically feasible, or not we have to consider various factors

as:

Cost benefit analysis

Long-term returns

Maintenance costs

3. System Analysis

3.1 Software Requirement specification

Software requirement specification is clear documentation of sotware.srs is clear then project

is clear. Software Requirements used are Windows XP and any other latest editions. Java

Technologies and oracle.

3.1.1 Introduction

3.1.1.1 Document Conventions

Typing is done on the 12 point size letters for the running text, 14 point size for the sub-

headings and 16 point size for main headings/titles/chapter names/etc. The font type is TIMES

NEW ROMAN.

The layout margin to be provided is 4 cm on the left, 3 cm on the top and bottom, 1.5 cm on

the right. Fresh paragraph is commenced after 5 spaces.

3.1.2 Overall Description

3.1.2.1 Hard Requirements:

The hardware used for the development of project is:

512MB RAM

40GB hard disk

Pentium IV Processor

3.1.2.2 Software Requirements

Java 2 standard Edition

Oracle 8i

Java database connectivity

Microsoft windows or Linux or Mac any version

3.1.3 Nonfunctional Requirements

3.1.3.1 Software Quality Attributes

Reliability: The system is reliable and produces accurate resulting from implementation

of security measures. Security is provided using password protection, release when time

out etc., by using these technologies the system is made more secure and more authentic.

Maintainability: The system will be designed as a closed system. New methods can be

added easily with little or no changes in the existing architecture.

Portability: The system should be portable. It can be deployed on any windows platform

and used.

Security: The protection of computer based resources includes hardware, software, data,

procedures and people against unauthorized use or natural disaster is known as system

security.

3.2 System Analysis

The unified modeling language allows the software engineer to express an analysis model

using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules. A

UML system is represented using five different views that describe the system from distinctly

different perspective. Each view is defined by a set of diagram, which is as follows.

User Model View

This view represents the system from the user’s perspective.

The analysis representation describes a usage scenario from the end-users perspective.

Structural model view

In this model the data and functionality are arrived from inside the system.

This model view models the static structures.

Behavioral Model View

It represents the dynamic of behavioral as parts of the system, depicting the

interactions of collection between various structural elements described in the user

model and structural model view.

Implementation Model View

In this the structural and behavioral as parts of the system are represented as they are to

be built.

Environmental Model View

In this the structural and behavioral aspects of the environment in which the system is

to be implemented are represented.

3.2.1 Class Diagram:

Class diagrams are widely used to describe the types of objects in a system and their

relationships.  Class diagrams model class structure and contents using design elements such as

classes, packages and objects.  Class diagrams describe three different perspectives when

designing a system, conceptual, specification, and implementation.   These perspectives become

evident as the diagram is created and help solidify the design. Class diagram tell about the list of

classes with their attributes and methods which are used in each and every module.

3.2.2 Use Case Diagram:

Use case is a sequence of transactions performed by system which yields an observable result

of value for a particular actor.

A transaction consists of set of action, decision and message to other actor

To realize a software system and their requirements and relationship among actors and there

cases “use case diagrams” are very useful to understand all. A use case is a set of scenarios that

describing an interaction between a user and a system. A use case diagram displays the

relationship among actors and use cases.  The two main components of a use case diagram are use

cases and actors.

Here a user or a client is another system nothing but an “actor”, an actor will interact with the

system modeling.  A use case is an external view of the system that represents some action the

user might perform in order to complete a task. Use cases are used in almost every project.   They

are helpful in exposing requirements and planning the project.

Use case: USER

Here user is the main heart of our application and we are providing so many options to get all

meanings based on the words,

In this initially he should give the word to see the meaning for that user has search options,

whenever he giving a word that should be valid word. From the .ddb libraries checks all

information based on the user given data an that information will retrieve from .ddb. While user

viewing the data that should be show in the mobile

3.2.3 Sequence Diagram:

Sequence diagrams demonstrates the sequential flow of software architecture used in this

application .Sequence diagrams document the interactions between classes to achieve a result,

such as a use case. Because UML is designed for object oriented programming, this

communications between classes are known as messages. The sequence diagrams lists diagrams

lists objects horizontally, and time vertically, and models these messages over time

3.2.4 State machine

The behavior of an entity is not only a direct consequence of its input, but it also depends on its

preceding state. The history of an entity can best be modeled by a finite state diagram. State

Machine diagram can show the different states of an entity also how an entity responds to various

events by changing from one state to another.

State machine diagram specify state machines. This clause outlines the graphic element that may be shown in state machine diagram, and provides cross reference where detailed information about the semantics and concrete notation for each element can be found. It also furnishes examples that illustrate how the graphic elements can be assembled into diagrams

3.2.5 Data Flow Diagrams

The data flow diagram (DFD) is one of the most important modeling tools used by the system

analysis. DFD’s use a number of symbols to represents systems. There are four kinds of symbols

and are used to represent four kinds of system components namely process, data stores, data flows

and external entities. DFDs are used to illustrate how data flows and external entities. DFDs are

used to illustrate how data flows in a system.

Process Data Flow

External Entity Data Store

Process show what systems do. This describes how input data is converted output data. Each

process has a unique name and number. Each process has one or more inputs and produces one or

more outputs. Files or data stores are repository of data. It contains data that is retained in the

system. Process can enter data into a data or retrieve data from the data store. Each data store has

a unique name. External entities are outside the system but they either supply input data into

system or use the system output.

They are entities over which the designer has no control. External entities that supply data into

system are sometimes called source. External entities that use system data are sometimes called

sinks.

Data flows model the passage of data in the system. An arrow indicates the direction of the flow. Flows of data can be tack place between two processes from a data store to a process from a process to a process and from a process to a sink.

For describing the system by DFD’s common way is to model the whole system by one process, the DFD that does this is know as the context diagram. It shows the external entities that interact with the system and the data flow between these external entities and the system. This does not describe the system in detail. The DFD shows the major system processes is called the top level DFD. This shows the various processes that makeup the system; the DFD that describes the flow of physical data components between physical operations in a system is called physical DFD.

DFDs have a number of features, which can be used to ensure that they type are self explanatory, complete and unambiguous. The features are:

Absence of flowchart structures.

Conservation of data and

Good naming conservations

A good DFD should

Have no data flows that split up into a number of other data flows,

Have no crossing lines,

Not include flow chart loops of control elements and

Not include data flows that act as signals to active processes

4. System design

System design is transition from a user oriented document to programmers or data base personnel.

The design is a solution, how to approach to the creation of a new system. This is composed of

several steps. It provides the understanding and procedural details necessary for implementing the

system recommended in the feasibility study. Designing goes through logical and physical stages

of development, logical design reviews the present physical system, prepare input and output

specification, details of implementation plan and prepare a logical design walkthrough.

SOFTWARE DESIGN

In designing the software following principles are followed:

1. Modularity and partitioning: software is designed such that, each system should

consists of hierarchy of modules and serve to partition into separate function.

2. Coupling: modules should have little dependence on other modules of a system.

3. Cohesion: modules should carry out in a single processing function.

4. Shared use: avoid duplication by allowing a single module is called by other that need the

function it provides

4.1 Class diagrams

Motoristname = stringaddress = stringvehicle num = varchar

rulescrosed()

Userusername : string

update db()getdetails()

Databasename : string(15)vehiclenum : varchar(10)licencenum : varchar(10)addres : varchar(20)phone num : int(15)

update()add()delete()

Motoristname : stringaddres : varcharvehicle num : varcharname2 : type = initval

rules crossed()

4.2 Use case diagram

loging into the system

maintaing database

administrator

NewClass

enter vechile number

display details

4.3 Sequence diagram

user : NewClass

:Login :Enter the vehiclenumbere

:Database :Displaydetails

enter(username,password)

submit

enter vehicle numberrequest to database

response

display the detailsof vehicle

4.4 Tables

The basic units in SQL are tables, columns, and rows. So where does the “relational” model fit

into the SQL units

Strictly speaking, in terms of the relation model, the “relation” is mapped in the table: It provides

a way to relate the data contained within the table in a simple manner. A column represents a data

element present in a table, while a row represents an instance of a record, or entry, in a table. Each

row contains one specific value for each of the columns; a value can be blank or undefined and

still be considered valid. The table can be visualized, you guessed it, as a matrix, with the

columns being the vertical fields and the rows being the horizontal fields.

Attributes Constraint Data Type

Name Notnull Char(20)

Address Not null Varchar(20)

Vehicle number Primary key Varchar(15)

Rules crossed Notnull Int(10)

5. Implementation

5.1 Methodologies

Java Technology:

Initially the language was called as “oak” but it was renamed as “Java” in 1995. The

primary motivation of this language was the need for a platform-independent (i.e., architecture

neutral) language that could be used to create software to be embedded in various consumer

electronic devices.

Java is a programmer’s language.

Java is cohesive and consistent.

Except for those constraints imposed by the Internet environment, Java gives the

programmer, full control.

Finally, Java is to Internet programming where C was to system programming.

Importance of Java to the Internet:

Java has had a profound effect on the Internet. This is because; Java expands the Universe

of objects that can move about freely in Cyberspace. In a network, two categories of objects are

transmitted between the Server and the Personal computer. They are: Passive information and

Dynamic active programs. The Dynamic, Self-executing programs cause serious problems in the

areas of Security and probability. But, Java addresses those concerns and by doing so, has opened

the door to an exciting new form of program called the Applet.

Java can be used to create two types of programs:

Applications and Applets : An application is a program that runs on our Computer

under the operating system of that computer. It is more or less like one creating using C or C++.

Java’s ability to create Applets makes it important. An Applet is an application designed to be

transmitted over the Internet and executed by a Java –compatible web browser. An applet is

actually a tiny Java program, dynamically downloaded across the network, just like an image. But

the difference is, it is an intelligent program, not just a media file. It can react to the user input and

dynamically change.

Features of Java Security:

Every time you that you download a “normal” program, you are risking a viral infection.

Prior to Java, most users did not download executable programs frequently, and those who did

scan them for viruses prior to execution. Most users still worried about the possibility of infecting

their systems with a virus. In addition, another type of malicious program exists that must be

guarded against. This type of program can gather private information, such as credit card

numbers, bank account balances, and passwords. Java answers both these concerns by providing a

“firewall” between a network application and your computer.

When you use a Java-compatible Web browser, you can safely download Java applets without

fear of virus infection or malicious intent.

5.2 Sample Code

1. Coding with Output Screens

Import statements;

Public class Prof extends Frame implements ActionListener

{

Declaration of variables;

}

Prof ()

{

//constructor

//add buttons

}

Public void actionPerformed (ActionEvent ae)

{

//data base connection

//operations

}

Public void paint (Graphics g)

{

//displaying on frame

}

}

5.3 Screens

6. TESTING

Software Testing

Testing Software testing is a critical element of software quality assurance and represents the

ultimate review of specification, design and code generation.

6.1 TESTING OBJECTIVES

To ensure that during operation the system will perform as per specification.

TO make sure that system meets the user requirements during operation

To make sure that during the operation, incorrect input, processing and output will

be detected

To see that when correct inputs are fed to the system the outputs are correct

To verify that the controls incorporated in the same system as intended

Testing is a process of executing a program with the intent of finding an error

A good test case is one that has a high probability of finding an as yet

undiscovered error

The software developed has been tested successfully using the following testing strategies and

any errors that are encountered are corrected and again the part of the program or the procedure or

function is put to testing until all the errors are removed. A successful test is one that uncovers an

as yet undiscovered error.

Note that the result of the system testing will prove that the system is working correctly. It will

give confidence to system designer, users of the system, prevent frustration during

implementation process etc.,

6.2 TEST CASE DESIGN:

White box testing

White box testing is a testing case design method that uses the control structure of the procedure

design to derive test cases. All independents path in a module are exercised at least once, all

logical decisions are exercised at once, execute all loops at boundaries and within their

operational bounds exercise internal data structure to ensure their validity. Here the customer is

given three chances to enter a valid choice out of the given menu. After which the control exits

the current menu.

Black Box Testing

Black Box Testing attempts to find errors in following areas or categories, incorrect or missing

functions, interface error, errors in data structures, performance error and initialization and

termination error. Here all the input data must match the data type to become a valid entry.

The following are the different tests at various levels:

Unit Testing:

Unit testing is essentially for the verification of the code produced during the coding phase

and the goal is test the internal logic of the module/program. In the Generic code project, the

unit testing is done during coding phase of data entry forms whether the functions are

working properly or not. In this phase all the drivers are tested they are rightly connected or

not.

Integration Testing:

All the tested modules are combined into sub systems, which are then tested. The goal is to

see if the modules are properly integrated, and the emphasis being on the testing interfaces

between the modules. In the generic code integration testing is done mainly on table creation

module and insertion module.

Validation Testing

This testing concentrates on confirming that the software is error-free in all respects. All the

specified validations are verified and the software is subjected to hard-core testing. It also aims at

determining the degree of deviation that exists in the software designed from the specification;

they are listed out and are corrected.

System Testing

This testing is a series of different tests whose primary is to fully exercise the computer-based

system. This involves:

Implementing the system in a simulated production environment and testing it.

Introducing errors and testing for error handling.

Test Cases:

Test case 1: vehicle number verification Priority (H, L): High

Test Objective: user should be avail Traffic rules mastery software features in system

Test Description: get information from database

Requirements Verified: Yes

Test Environment: J2SE development environment

Test Setup/Pre-Conditions:

Actions Expected Results

User should give the word and get the information. Find the information through .ddb

Pass: Yes Conditions pass: Yes Fail: No

Problems / Issues: NIL

Notes: Successfully Executed

6.3 Screens for Failure Test Cases

7. Conclusion

The project gives the fast and efficient detail of a particular vehicle or motorist. So, by using

this we can know the present status of a motorist and when the vehicle is to be sized .This can

be done using update method .After certain period of time the vehicle is dispatched to vehicle

owner .By this we can control the traffic problems. And we can overcome the problem of miss

use of money by individuals.

When it comes to the conclusion part of our project where here we have the certain limitations

of crossing the rules after it goes into the vehicle seize situation. Moreover the fine amount

should be paid through demand draft where no third part can involve in it. Thus it helps us to

improve the security. By implementing through this project the traffic problems may limit

unto certain extent.

The proposed system has high security regarding to database and application it consist of

login and password through this particular authentication person can access it.

BIBLORAPHY

1. http://www.oracle.com/index.html

2. http://weblogs.sqlteam.com/jeffs/archive/2007/10/31/sql-server-2005-date-time-only-data-

types.aspx