1843

Balujalabs Contact us at 9313565406, 9212002599
A Project for MCA
(Dynamic Site using ASP.NET ,C# and SQL Server)
Prepared By:
PINKY (Enrollment No. : 050185527)

Email : pinky.tyagi@gmail.com
Ph.: 9910024208
-1-

ONLINE VEHICLE TRACKING SYSTEM
Under Supervision of: G.S.BALUJA
Submitted By:
Name : PINKY
Enrolment No. : 050185527
Address : WZ-A/93, Vidhya Vihar, Hastsal
Road, New Delhi-59
Phone : 9910024208
Email : pinky.tyagi@gmail.com
Programme Code : MCA
Course Code : MSCP-60
Subject Title : PROJECT REPORT
Project Title : ONLINE VEHICLE TRACKING SYSTEM
Name of the Study : MAHARAJ SURAJMAL INSTITUTE,

Centre JANAK PURI, N.D.-59
Date : ___________________
(Signature)
-2-

ACKNOWLEDGEMENT
With Candor and Pleasure I take opportunity to express my sincere thanks and
obligation to my esteemed guide Mr.G.S.Baluja. It is because of his able and mature
guidance and co-operation without which it would not have been possible for me to
complete my project.
It is my pleasant duty to thank all the staff member of the computer center who never
hesitated me from time during the project.
Finally, I gratefully acknowledge the support, encouragement & patience of my

family, and as always, nothing in my life would be possible without God, Thank You!
(Pinky)
-3-

DECLARATION
I hereby declare that this project work titled “ONLINE VEHICLE TRACKING
SYSTEM” is my original work and no part of it has been submitted for any other
degree purpose or published in any other from till date.
(Pinky)
-4-

TABLE OF CONTENT
1. Preface
2. System Study
2.1. Introduction
2.2. Feasibility Study
2.3. System Overview
3. System Analysis
3.1. Importance of Computerized Educational System or a WebSite
3.2. About the Project
3.3. Functional Requirements
4. System Design
4.1. System Development Cycle
4.2. DFD
4.3. Search Process
5. Data Dictionary
5.1. Physical Design
5.2. Source Code
6. Testing
6.1. Testing Phases
6.2. Verification & Validation
6.3. Reports
-5-

7. System Implementation
8. Post Implementation Maintenance and Review
9. User’s Manual
7.1. Operational instruction for the User
7.2. Introduction to various operations
10. Bibliography
-6-

INTRODUCTION
This is a Project work is undertaken in context of partial fulfillment of the MCA.
Since Online Vehicles Tracking System is associated with the lives of common
people mainly who are going to purchase a used vehicle and they want to inquire
about it ,to check whether it is involved in any crime .So I decided to work on this
project.
The manual handling of the record is time consuming and highly prone to error. The
purpose of this project is to automate the process of day to day activities like records
of accidental vehicles, theft vehicles, vehicles which are in police records, car theft
information, challans and jump records, Daily updatations and Modification by the
administrator etc.
The complete set of rules & procedures related to vehicles day to day activities and
generating report is called “ONLINE VEHICLES TRACKING SYSTEM”. My project
gives a brief idea regarding automated searching activities.
I have tried my best to make the complicated process of ONLINE VEHICLES

REPORT TRACING SYSTEM as simple as possible using Structured & Modular
technique & Menu oriented interface. I have tried to design the software in such a
way that user may not have any difficulty in using this package & further expansion is
possible without much effort. Even though I cannot claim that this work to be entirely
exhaustive, the main purpose of my exercise is to perform each activity in
computerized online way rather than manually which is time consuming.
I am confident that this software package can be readily used by non-programming

personal avoiding human handled chance of error. This project is used by two types
of users
-7-

i. Online Users.
ii. Administrator (management of the company).
Online users can check criminal background of the vehicle, if it has any.
Administrator can maintain l records of accidental vehicles, theft vehicles, vehicles

which are in police records, car theft information, challans and jump records, Daily
updations and Modifications etc. Administrator is must be an authorized user. He
can further change the password. There is the facility for password recovery, logout
etc.
-8-

OBJECTIVES OF THE PROJECT
• Maintain records of the all vehicles.
• Generate reports for the vehicles.
• Generate reports for the details about the accidental vehicles.
• Deletion of data of Vehicles and users from the table.
• Updating data in the tables to enter data of new clients and companies.
• Searching of records according to users requirements.
• Administrator Module to generate following reports
i. Accidental Vehicles
ii. Theft Vehicles
iii. Challans & jumps
ii. Vehicle Details
iii. Vehicles having pollution checking certificate.
iv. Users
• Collecting Feedbacks from the users.
• Report Generation.
-9-

DRAWBACKS OF CURRENT MANUAL- SYSTEM
• The current manual system has a lot of paper work and it does not deal with
old and new car purchase and sale.
• To maintain the records of sale and service manually, is a Time-consuming
job.
• With the increase in database, it will become a massive job to maintain the
database.
• Requires large quantities of file cabinets, which are huge and require quite a
bit of space in the office, which can be used
for storing records of previously sale vehicles.
• The retrieval of records of previously sold vehicle will be a tedious job.
• Lack of security for the records, anyone disarrange the records of your
system.
• If someone wants to check the details of the available vehicle for his/her
satisfaction (like the details of the owner of the vehicle) the previous system
does not provide any necessary detail of this type.
- 10 -

ESTABLISH THE NEED OF NEW SYSTEM
1. Problem of Reliability: Current system is not reliable. It seems to vary in quality

from one month to the next. Some times it gives good output, but some times the
output is worst.
2. Problem of Accuracy: There are too many mistakes in reports.
3. Problem of timeliness: In the current system the reports and output produced is
mostly late and in most of the cases it is useless because it is not on time.
4. Problem of Validity: The output and reports mostly contains misleading

information. The customer's information is sometimes not valid.
5. Problem of Economy: The current system is very costly. We have to spend lots
of money to keep the system up and going, but still not get the desired results.
6. Problem of Capacity: The current system is suffering from problem of capacity

also. The staff for organization is very less and the workload is too much. Few
peoples cannot handle all the work.
- 11 -

PROPOSED SYSTEM
1. Vehicle Details: The new proposed system stores and maintains all the
vehicles details.
2. Calculations: The new proposed system updates tables and other

information automatically and it is very fast and accurate.
3. Registers: There is no need of keeping and maintaining salary and

information manually. It remembers each and every record and we can get
any report at any time.
4. Speed: The new proposed system is very fast with 100% accuracy and
saves time.
5. Manpower: The new proposed system needs less manpower. Less people
can do the large work.
6. Efficiency: The new proposed systems complete the work of many people
in less time.
7. Past details: The new proposed system contains the details of every past
vehicle for future assistance.
8. Reduces redundancy: The most important benefit of this system is that it

reduces the redundancy of data within the data.
9. Work load: Reduces the work load of the data store by helping in easy
updates of the products and providing them with the necessary details
together with financial transactions management.
10. Easy statements: Month-end and day-end statement easily taken

out without getting headaches on browsing through the day end
statements.
- 12 -

1.1 NEED:
I have designed the given proposed system in the ASP.NET to automate the process
of vehicle crime report information system. This project is useful for the authorities
who keep track of all the vehicles registered in a particular state .The authority can
add vehicle details whether it has any accidental details or not, adding theft or stolen
details of the vehicles, add challan details of the vehicles, add owner details of the
vehicles.
The following steps that give the detailed information of the need of proposed system
are:
• Performance: During past several decades, the records are supposed to
be manually handled for all activities. The manual handling of the record is
time consuming and highly prone to error. To improve the performance of
the Company system, the computerized system is to be undertaken. The
computerized project is fully computerized and user friendly even that any
of the members can see the report and status of the company.
• Efficiency: The basic need of this website is efficiency. The website

should be efficient so that whenever a new user submits his/her details the
website is updated automatically. This record will be useful for other users
instantly.
• Control: The complete control of the project is under the hands of

authorized person who has the password to access this project and illegal
access is not supposed to deal with. All the control is under the
administrator and the other members have the rights to just see the
records not to change any transaction or entry.
- 13 -

• Security: Security is the main criteria for the proposed system. Since
illegal access may corrupt the database. So security has to be given in this
project.
SOFTWARE & HARDWARE REQUIREMENTS
“Client-Server approach with XML / ASP.NET”
The need of today’s software development is competence in a GUI based front-end

tool, which can connect to Relational Database engines. This gives the programmer
the opportunity to develop client server based commercial applications.
FRONT END
.NET programming tools are complete programming environments. It allows

programmers to build a GUI program using the various on-screen controls such as
buttons, text, menus, boxes etc. These controls are placed on a form and then the
processing details related with each control are filled in.
In the business world, competitive strategies have become the order of the day to
improve quality, cut costs and provide a high response customer service base. Most
organizations today need to be market driven and do a lot of value addition to their
products and services. This naturally calls for rational decision making, which
requires information. Information Technology or IT provides that effective channel to
support and implement this strategy. Client/Server is the technology that empowers
the desktop, thus setting a trend for the way successful organizations will use
technology in the next decade.
- 14 -

INTRODUCTION TO .NET
What is .NET?
• A vision of how information technology will evolve
• A platform that supports the vision
• A business model of software as a service
1. A Vision.
• Web sites will be joined by Web services
• New smart devices will join the PC
• User interfaces will become more adaptable and customizable
• Enabled by Web standards
2. A Platform.
• The .NET Framework
• Visual Studio.NET
• .NET Enterprise Servers
o Database, Messaging, Integration, Commerce, Proxy, Security,
Mobility, Orchestration, Content Management
• .NET Building Block Services
o Passport
o .NET My Services (“Appin”)
• Goal: make it incredibility easy to build powerful Web applications and Web
services
3. A business model.
• Software as a service
- 15 -

• Subscription-based services
• Application hosting, e.g. bCentral
Interoperability: Web languages and protocols must be compatible with one

another independent of hardware and software.
Evolution: The Web must be able to accommodate future technologies.

Encourages simplicity, modularity and extensibility.
Decentralization: Facilitates Scalability and Robustness.
Web Services
• A programmable application component accessible via standard Web
protocols
• The center of the .NET architecture
• Exposes functionality over the Web
• Built on existing and emerging standards are HTTP, XML, SOAP, UDDI,
WSDL, …
The .NET Framework
- 16 -

What is the .NET Framework?

• A set of technologies for developing and using components to create:
o Web Forms
o Web Services
o Windows Applications
• Supports the software lifecycle
o Development
o Debugging
o Deployment
o Maintenance
• Application Architectures
o The Different types of Applications may vary from single-tier desktop
applications (applications that follow the single-tier architecture) to
multi-tier applications (applications that follow the two-, three, or n-tier
architecture)
o Single-tier architecture
− A single executable file handles all functions relating to the user,
business, and data service layers.
o Two-tier architecture
− Divides an application into the following two components:
Client
Server
o Three-tier architecture
− All the three service layers reside separately, either on the same
machine or on different machines.
o n-tier architecture
− Uses business objects for handling business rules and data
access.
− Has multiple servers handling business services.
The .NET Initiative

• The introduction of the Internet and its rapid growth in the recent past has led
to the development of a number of new Technologies.
- 17 -

• One of the most important requirements of such applications is the ability to

interchange information across platforms and to benefit from the functionality
provided by other applications.
• In the current scenario, although applications serve organization-specific
requirements, they are not interoperable. Microsoft has introduced the .NET
initiative with the intention of bridging the gap in interoperability between
applications.
• The .NET initiative offers a complete suite for developing and deploying
applications, which consists of the following:
o NET products: Microsoft has already introduced Visual Studio .NET,
which is a tool for developing NET applications by using programming
languages such as Visual Basic, C#, and Visual C++.
o NET services: Microsoft is coming up with its own set of Web services,
known as My Services. These services are based on the Microsoft
Passport Authentication service, the same service that is used in
Hotmail.
Explanation of the .NET Framework

• Is a collection of services and classes?
• Exists as a layer between .NET applications and the underlying operating
system.
• Encapsulates much of the functionality, such as debugging and security
services.
• The following figure depicts the components of the .NET Framework:
The .NET Framework Base Classes or the .NET Class Framework
• Consists of a class library that works with any .NET language, such as Visual
Basic .NET and C#.
- 18 -

• Provides classes that can be used in the code to accomplish a range of

common programming tasks.
• Comprises
o Namespaces: Namespaces help you to create logical groups of
related classes and interfaces that can be used by any language
targeting the .NET Framework.
o Assembly: An assembly is a single deployable unit that contains all
the information about the implementation of classes, structures, and
interfaces.
• The Common Language Runtime
o Provides functionality such as exception handling, security, debugging,
and versioning support to any language that targets it.
o Can host a variety of languages and offer a common set of tools across
these languages, ensuring interoperability between the codes.
• Provides the following features:

o Automatic memory management
o Standard type system
o Language interoperability
o Platform independence
o Security management
o Type safety
Advantages of the .NET Framework
• Some advantages of the .NET Framework are:

o Consistent programming model
o Multi-platform applications
o Multi-language integration
o Automatic resource management
o Ease of deployment
ADO.NET
- 19 -

• Is a model used by Visual Basic .NET applications to communicate with a

database for retrieving, accessing, and updating data?
• Uses a structured process flow to interact with a database.
ADO .NET Data Access
Most applications need data access at one point of time making it a crucial
component when working with applications. Data access is making the application
interact with a database, where all the data is stored. Different applications have
different requirements for database access. VB.NET uses ADO.NET (Active X Data
Object) as it's data access and manipulation protocol, which also enables us to work
with data on the Internet. Let's take a look why ADO.NET came into picture replacing
ADO.
Evolution of ADO.NET
The first data access model, DAO (data access model) was created for local
databases with the built-in Jet engine which had performance and functionality
issues. Next came RDO (Remote Data Object) and ADO (Active Data Object) which
were designed for Client Server architectures but soon ADO took over RDO. ADO
was a good architecture but as the language changes so is the technology within it.
With ADO, all the data is contained in a record set object which had problems when
implemented on the network (Internet) and penetrating firewalls. ADO was a
connected data access which means that when a connection to the database is
established the connection remains open until the application is closed, which raises
concerns about database security and network traffic. And also as databases are
becoming increasingly important and as they are serving more people a connected
data access model makes us think about its use. For example, an application with
connected data access may do well when connected to two clients, the same may
do poorly when connected to 10 and might be unusable when connected to 100 or
more. Also, open database connections use system resources to a maximum extent
making the system performance less effective.
- 20 -

Why ADO.NET?
To cope up with some of the problems mentioned above, ADO.NET came into
existence. ADO.NET addresses the above mentioned problems by maintaining a
disconnected database access model which means that when an application
interacts with the database the connection is opened to serve the request of the
application and is closed as soon as the request is completed. Likewise if a database
is updated, the connection is opened long enough to complete the Update operation
and is closed. By keeping connections open for only a minimum period of time
ADO.NET conserves system resources and provides maximum security for
databases and also has less impact on system performance. Also, ADO.NET when
interacting with database uses XML by converting all the data into XML and using it
for database related operations making them more efficient.
Features of ADO.NET
• Disconnected data architecture — Applications connect to the database only
while retrieving and updating data.
• Data cached in datasets — ADO.NET is based on a disconnected data
structure. Therefore, the data is retrieved and stored in datasets.
• Data transfer in XML format — ADO.NET uses XML for transferring
information from a database into a dataset and from the dataset to another
component.
• Interaction with the database is done through data commands.
ADO.NET Object Model

Key Components of the ADO.NET Model
• Data Provider
o Is used for connecting to a database, retrieving data, and storing the
data.
• Is of two types:
o OLE DB data provider
o SQL Server data provider
- 21 -

Components of a Data Provider

• Connection
o Used to establish a connection with a data source
o Some commonly used properties and methods:
ConnectionString property
Open()method
Close()method
State property
• Data adapter
o Creates a dataset and updates the database.
o Handles data transfer between the database and the dataset through
its properties and methods.
o Displays the data through the process of table mapping.
o Are of two types:
SqlDataAdapter
OleDbDataAdapter
• Data command
o Is a SQL statement or a stored procedure that is used to retrieve,

insert, delete, or modify data from a data source.
o Is an object of the OleDbCommand or SQLCommand class.
• Data reader
o Is used to retrieve data from a data source in a read-only and forward-

only mode.
o Stores a single row at a time in the memory.
o Commonly used methods:
Read()
Close()
NextResult()
• Dataset
- 22 -

o Is a disconnected, cached set of records that are retrieved from a

database.
o Is present as a DataSet class in the System.Data namespace.
o Has its own object model.
- 23 -

- 24 -

PRELIMINARY INVESTIGATION
System development, a process consisting of two major steps of system analysis
and design, start when management or sometimes system development personnel
feel that a new system or an improvement in the existing system is required. The
system development life cycle is classically thought of as the set of activities that
analysts, designers and users carry out to develop and implement an information
system. The system development life cycle consists of the following activities:
Preliminary investigation
Determination of system requirements
Design of system
Development of software
System testing
Implementation, evaluation, and maintenance
A request to take assistance from information system can be made for many
reasons, but in each case someone in the organization initiates the request is
made, the first system activity the preliminary investigation begins. This activity
has three parts:
1) Request clarification
2) Feasibility study
3) Request approval
Request clarification: Many requests from employees and users in the

organizations are not clearly defined, therefore it becomes necessary that
project request must be examined and clarified properly before considering
systems investigation.
- 25 -

SYSTEM DEVELOPMENT LIFE CYCLE

Systems are created to solve problems. One can think of the systems approach as
an organized way of dealing with a problem. In this dynamic world, the subject
System Analysis and Design (SAD), mainly deals with the software development
activities.
DEFINING A SYSTEM
A collection of components that work together to realize some objective forms a

system. Basically there are three major components in every system, namely input,
processing and output.
In a system the different components are connected with each other and they are
interdependent. For example, human body represents a complete natural system.
We are also bound by many national systems such as political system, economic
system, educational system and so forth. The objective of the system demands that
some output is produced as a result of processing the suitable inputs.
SYSTEM LIFE CYCLE

System life cycle is an organizational process of developing and maintaining
systems. It helps in establishing a system project plan, because it gives overall list
of processes and sub-processes required for developing a system.
System development life cycle means combination of various activities. In other
words we can say that various activities put together are referred as system
development life cycle. In the System Analysis and Design terminology, the system
development life cycle means software development life cycle.
Following are the different phases of software development cycle:
System study
Feasibility study
System analysis
- 26 -

System design
Coding
Testing
Implementation
Maintenance
The Different Phases Of Software Development

Life Cycle Are Shown Below.
- 27 -

PRELIMINARY
INVESTIGATION
REVIEW RUNNING DETERMINATION OF

SYSTEM AND SYSTEM REQUIREMENTS
MAINTENANCE
DEVELOPMENT OF
PROTOTYPE SYSTEM
SYSTEM DESIGN OF SYSTEM

IMPLEMENTATION
DEVELOPMENT OF
SYSTEM TESTING SOFTWARE AND CODING
SYSTEM
ANALYSIS
50%
DESIGN
DESIGN
OF
SYSTE
M
30%
CODING
FIG: SHOWING GENERAL LIFE CYCLE PROCESS AND

PERCENTAGE OF TIME DEVOTED
- 28 -

A system analysis is a separation of a substance into parts for study and their
implementation and detailed examination.
Before designing any system it is important that the nature of the business and the
way it currently operates are clearly understood. The detailed examination provides
the specific data required during designing in order to ensure that all the client's
requirements are fulfilled. The investigation or the study conducted during the
analysis phase is largely based on the feasibility study. Rather it would not be
wrong to say that the analysis and feasibility phases overlap. High-level analysis
begins during the feasibility study. Though analysis is represented as one phase of
the system development life cycle (SDLC), this is not true. Analysis begins with
system initialization and continues until its maintenance. Even after successful
implementation of the system, analysis may play its role for periodic maintenance
and up gradation of the system.
One of the main causes of project failures is inadequate understanding, and one of
the main causes of inadequate understanding of the requirements is the poor
planning of system analysis.
Analysis requires us to recall the objectives of the project and consider following
three questions:
What type of information is required?
What are the constraints on the investigation?
What are the potential problems that may make the task more
difficult?
- 29 -

- 30 -

IMPORTANCE OF COMPUTERIZED
VEHICLE CRIME REPORT INFORMATION SYSTEM
There are several attributes in which the computer based information works.
Broadly the working of computer system is divided into two main groups:
♦ Transaction System
♦ Decision Support System
Transaction System:
A transaction is a record of some well-defined single and usually small

occurrence in a system. Transactions are input into the computer to update the
database files. It checks the entering data for its accuracy. This means that
numeric data appears in numeric field and character data in character field. Once
all the checks are made, transaction is used to update the database. Transaction
can be inputted in on-line mode or batch mode. In on-line mode, transactions are
entered and updated into the database almost instantaneously. In batch mode,
transactions are collected into batches, which may be held for a while and
inputted later.
Decision Support System:

It assists the user to make analytical decision. It shows the various data in
organized way called analysis. This analysis can be made to syrdy preferences
and help in making decisions.
Computer system works out best with record maintenance. It will tell you which
customer would get how much pending/reports statements. It will also help to
search the information about a particular person by simply entering his telephone
number. User can store information as per requirement, which can be used for
comparison with other reports.
- 31 -

PRINCIPLES OF SYSTEM ANALYSIS
Principles:
1. Understand the problem before you begin to create the analysis model.
2. Develop prototypes that enable a user to understand how human machine
interaction will occur.
3. Record the origin of and the reason for every requirement.
4. Use multiple views of requirements like building data, function and behavioral
models.
5. Work to eliminate ambiguity.
A Complete Structure:
The limited time and resources have restricted us to incorporate, in this project, only
the main activities that are performed in news sites, but utmost care has been taken
to make the system efficient and user friendly.
For the optimum use of practical time it is necessary that every session is planned.
Planning of this project will include the following things:
• Topic Understanding.
• Modular Break – Up of the System.
• Processor Logic for Each Module.
• Database Requirements.
Topic Understanding:
It is vital that the field of application as introduced in the project may be totally a new
field. So as soon as the project was allocated to me, I carefully went through the
project to identify the requirements of the project.
Modular Break –Up of the System:
Identify The Various Modules In The System.

- 32 -

List Them In The Right Hierarchy.

Identify Their Priority Of Development
Description Of The Modules:
MODULES
MODULE 1: PASSWORD MODULE

In this module, this website is for multiple users. If a User enters a password and the
software checks its validity. If the password is valid then option is given to change
the password, otherwise “Invalid User/Password” message is displayed. There is an
option for password recovery, log out, login, new users sign in. The Administrator
can also update changes in the site after login.
MODULE 2: CREATING NEW ENTITIES (Users, Vehicles, Theft Vehicles, Stolen

Vehicles, Owner of the Vehicles, Challans, Administrator)
In this module, whenever a new entity is required to be added the corresponding
forms are opened and the database is manipulated to check whether the data is
already existing or not. If it already exists, then it prompts that “Entry already
existing” and if not than the data is entered with the various validation checks.
MODULE 3: MODIFYING / UPDATING EXISTING ENTITIES

In this module, whenever an existing entity is required to be modified the
corresponding forms are opened and the database is manipulated and the data is
fetched. Now the administrator can made the required changes and then
accordingly, he updates the data. Again, the checks are followed in case there is any
invalid entry.
MODULE 4: SEARCHING
In this module, whenever an existing entity is required to be searched the
corresponding forms are opened and the database is manipulated and the data is
fetched. Again, the checks are followed in case there is any invalid entry.
MODULE 5: ACCIDENTAL
- 33 -

In this module, accidental details of all the vehicles are stored in the database. This
database will be uploaded so that, if a user or dealer who wants to purchase a
vehicle can check the accidental history of the vehicle.
MODULE 6: STOLEN
In this module, details of all the theft or stolen vehicles are stored in the database.
This database will be uploaded so that, if a user or dealer who wants to purchase a
vehicle can check the history of the vehicle.
MODULE 7: CHALLANS
In this module, details of all the vehicles challans are stored in the database. This
vehicle can check the challan history of the vehicle.
MODULE 8: OWNERS
In this module, owner details of all the vehicles are stored in the database. This
vehicle and he/she can check the owner details of the vehicle.
MODULE 9: VALIDATION OF DATA ENTERED BY THE USER & ERROR

HANDLING
In this module, the validity of data entered by the user during the various business
processes is checked through various validation checks. For example, there should
not be any characters entered in the numeric fields, likewise if there is any error
occurs than it should handle that particular error and give the required messages.
Module 10: Feedback

This module keeps track of all the feedbacks given by the users for future
records.
Module 11: Transactions

This module keeps track of all the transactions done by the company for
future records and income tax purposes.
- 34 -

PROCESS LOGIC FOR EACH MODULE:
In the first module, validity of password is checked against a particular user.
In the second module, whenever a new entity is entered it should be checked for
the duplicate data.
In the third and fourth module, just like the first module it should have the proper
checks for every entity being modified or updated.
In the fifth and sixth module, again the validation checks are made and the
different reports are generated to ease the business processes and decision making.
DATA STRUCTURE REQUIREMENTS ACCORDING TO THE

MODULES:
Identify The Various Tables Required.
Fields for These Tables.
The Various Key Fields (for example Primary key and foreign key).
Identify The Various Constraints like Not Null, Unique etc.
NUMBER OF FUNCTIONS USED IN THIS PROJECT
1. Function Password ()
This is the function used for password authentication for users and administrator.
2. Function New_Vehicle ()
This is the function used to add new vehicle details in the database. The owner
details are also stored in the database.
- 35 -

3. Function DISPLAY_RECORD ()
This function is used to display all the transaction regarding any user, vehicle,
owner etc. This is a global report to display all the transaction records in the
screen.
4. Functions Accident ()
This function is used store accidental details of all the vehicles. This database
will be uploaded so that, if a user or dealer who wants to purchase a vehicle can
check the accidental history of the vehicle.
5. Function Stolen ()
This function is used to store details of all the theft or stolen vehicles in the database.
vehicle can check the history of the vehicle.
6. Functions Challan ()
This function is used to store details of all the vehicles challans in the database.
vehicle can check the challan history of the vehicle.
7. Functions Authorized_Dealers ()
This function is used to store details of all the authorized dealers in the database.
This database will be uploaded so that, if a user wants to purchase a vehicle can
check the details of the dealer.
8. Functions Search ()
This function is used to search records regarding any vehicle, user etc.
9. Functions Reports ()
This function is used to generate reports by the administrator for
i. Users
ii. Accidental Reports
iii. Challan Reports
iv. Stolen or Theft Reports
v. Any General Information
- 36 -

TOOLS / PLATFORM, HARDWARE AND SOFTWARE

REQUIREMENT SPECIFICATION
HARDWARE
Processor : Pentium 2.4 GHz or above
Memory : 256 MB RAM or above
Cache Memory : 128 KB or above
Hard Disk : 3 GB or above [at least 3 MB free space required]
Floppy Disk Drive : 3.5” [At least one drive labeled a: required]
Printer : Dot Matrix / DeskJet connected to LPT port
SOFTWARE
Operating System : Windows XP (Professional).
Font-End Tool : ASP .NET, C#
Back-End : SQL SERVER 2000
- 37 -

VEHICLE CRIME REPORT INFORMATION SYSTEM

DATA FLOW DIAGRAM
CONTEXT LEVEL DFD
Theft Vehicle
News Accident
(World, India)
Online
Vehicle
tracking
Challan System Fitness/ Renewal
Online Training/
Rules Traffic Symbol
Insurances
- 38 -

DFD for ONLINE VEHICLE TRACKING SYSTEM
CUSTOMER 1.1 Receive

customer D4: Fitness
Registration
request
Fitness /
Renewal
Customer request
Apply for Fitness
Certificate
D5:
Insurance
1.2 Generate Transport
New Dept
Registration Insurance
Number Online
Vehicle
Tracking Calcul
System ate
Premi
um
D1: Vehicle
1.6
Insurance
Report Calculation
Accident/ Theft Module
FIR NO
1.3 online 1.4 Traffic

THEFT Crime Rule
report Module
Module
D2: THEFT
Challan
Fir no Inform Police Report Violation
D6: Challan
Traffic rule
ACCIDENT
VIOLATION
D3: ACCIDENT
- 39 -

DFD for the ACCIDENT
Accident
Accident 1. Report to
online
Vehicle
tracking
system
2. Area
Police
Station
Report
3. Online
Vehicle
tracking
system
D3: Accident
- 40 -

DFD for the FITNESS
Fitness
FITNESS 1.
Fitness
Renewal
Module
Request
Fitness request
2.
Transport
3. Online Dept
Vehicle Module
tracking
System
D4: vehicle Fitness
- 41 -

DFD for THEFT
1. Report to
on line
THEFT Theft Information Vehicle
tracking
system
FIR
FIR No.
2. Area
Police
Station
Report
3. On Line
Vehicle
Tracking
System
D2: Theft
- 42 -

DFD for the NEW Registration
1. New
CUSTOMER Registration Registration
Request Request
Registration Registration
Number Generation
2. On Line
Vehicle
Tracking
System
D1: Registration
- 43 -

DFD For Login of User
Read User
User Id & Data Base
Password
Authenticate
User & Login
Output
- 44 -

E-R diagram
Registrati
Customer Customer on
Name Address Chassis Make
Date No.
Customer Vehicle Color
ID No.
PIN
Price
Purchases Vehicle
City
Customer
Locatio
Date
n
of
Theft
Insuranc Tim
e e
Amount
Insuran Vehicle
Crime
THEFT
ce date Type of
Insuranc
e Date of
Locatio
Accide
Insurance n
nt
Time
Panel
No.
Accident
- 45 -

DATA MODELING
PASSWORD TABLE
FIELDS TYPE
USERNAME CHAR(20)
PASSWORD CHAR(20)
E-MAIL CHAR(30)
SECURITY QUESTION CHAR(60)
ANSWER CHAR(60)
VEHICLE TABLE
FIELDS TYPE
MODEL CHAR(20)
NAME CHAR(20)
VEHICLE NUMBER INT(20)
DESCRIPTION CHAR(60)
ACCIDENTAL_VEHICLE
FIELDS TYPE
VEHICLE NAME CHAR(20)
CUSTOMER NAME CHAR(20)
ADDRESS CHAR(50)
POLICY DATE DATE
ACCIDENTAL DETAILS CHAR(20)
INSURANCE_FROM DATE
TO DATE
STOLEN_VEHICLE
FIELDS TYPE
VEHICLE NAME CHAR(20)
CUSTOMER NAME CHAR(20)
ADDRESS CHAR(50)
ACCIDENTAL DETAILS CHAR(20)
FROM DATE
TO DATE
- 46 -

CUSTOMER TABLE
FIELDS TYPE
NAME CHAR(15)
ADDRESS CHAR(35)
E-MAIL CHAR(30)
PHONE CHAR(20)
VEHICLE NO CHAR(30)
FEEDBACK TABLE
FIELDS TYPE
NAME CHAR(15)
ADDRESS CHAR(35)
E-MAIL CHAR(30)
PHONE CHAR(20)
REMARK CHAR(90)
DEALER TABLE
FIELDS TYPE
NAME CHAR(15)
ADDRESS CHAR(35)
E-MAIL CHAR(30)
PHONE CHAR(20)
DESCRIPTION CHAR(30)
- 47 -

SYSTEM DESIGN
The design document that we will develop during this phase is the blueprint of the
software. It describes how the solution to the customer problem is to be built. Since
solution to complex problems isn’t usually found in the first try, iterations are most
likely required. This is true for software design as well. For this reason, any design
strategy, design method, or design language must be flexible and must easily
accommodate changes due to iterations in the design. Any technique or design
needs to support and guide the partitioning process in such a way that the resulting
sub-problems are as independent as possible from each other and can be combined
easily for the solution to the overall problem. Sub-problem independence and easy
combination of their solutions reduces the complexity of the problem. This is the
objective of the partitioning process. Partitioning or decomposition during design
involves three types of decisions: -
Define the boundaries along which to break;
Determine into how money pieces to break; and
Identify the proper level of detail when design should stop and implementation
should start.
Basic design principles that enable the software engineer to navigate the design
process suggest a set of principles for software design, which have been adapted
and extended in the following list:
Free from the suffer from "tunnel vision." A good designer should consider alternative
approaches, judging each based on the requirements of the problem, the resources
available to do the job.
The design should be traceable to the analysis model. Because a single element of
the design model often traces to multiple requirements, it is necessary to have a
means for tracking how requirements have been satisfied by the design model.
- 48 -

The design should not repeat the same thing. Systems are constructed using a set of
design patterns, many of which have likely been encountered before. These patterns
should always be chosen as an alternative to reinvention. Time is short and
resources are limited! Design time should be invested in representing truly new ideas
and integrating those patterns that already exist.
The design should "minimize the intellectual distance" between the software and the
problem as it exists in the real world. That is, the structure of the software design
should (whenever possible) mimic the structure of the problem domain.
The design should exhibit uniformity and integration. A design is uniform if it appears
that one person developed the entire thing. Rules of style and format should be
defined for a design team before design work begins. A design is integrated if care is
taken in defining interfaces between design components.
The design activity begins when the requirements document for the software to be
developed is available. This may be the SRS for the complete system, as is the case
if the waterfall model is being followed or the requirements for the next "iteration" if
the iterative enhancement is being followed or the requirements for the prototype if
the prototyping is being followed. While the requirements specification activity is
entirely in the problem domain, design is the first step in moving from the problem
domain toward the solution domain. Design is essentially the bridge between
requirements specification and the final solution for satisfying the requirements.
The design of a system is essentially a blueprint or a plan for a solution for the
system. We consider a system to be a set of components with clearly defined
behavior that interacts with each other in a fixed defined manner to produce some
behavior or services for its environment. A component of a system can be
considered a system, with its own components. In a software system, a component
is a software module.
- 49 -

The design process for software systems, often, has two levels. At the first level, the
focus is on deciding which modules are needed for the system, the specifications of
these modules, and how the modules should be interconnected. This is what is
called the system design or top-level design. In the second level, the internal design
of the modules, or how the specifications of the module can be satisfied, is decided.
This design level is often called detailed design or logic design. Detailed design
essentially expands the system design to contain a more detailed description of the
processing logic and data structures so that the design is sufficiently complete for
coding.
Because the detailed design is an extension of system design, the system design
controls the major structural characteristics of the system. The system design has a
major impact on the testability and modifiability of a system, and it impacts its
efficiency. Much of the design effort for designing software is spent creating the
system design.
The input to the design phase is the specifications for the system to be designed.
Hence, reasonable entry criteria can be that the specifications are stable and have
been approved, hoping that the approval mechanism will ensure that the
specifications are complete, consistent, unambiguous, etc. The output of the top-
level design phase is the architectural design or the system design for the software
system to be built. This can be produced with or without using a design
methodology. Reasonable exit criteria for the phase could be that the design has
been verified against the input specifications and has been evaluated and approved
for quality.
A design can be object-oriented or function-oriented. In function-oriented design, the

design consists of module definitions, with each module supporting a functional
abstraction. In object-oriented design, the modules in the design represent data
abstraction (these abstractions are discussed in more detail later). In the function-
oriented methods for design and describe one particular methodology the structured
design methodology in some detail. In a function- oriented design approach, a
system is viewed as a transformation function, transforming the inputs to the desired
- 50 -

outputs. The purpose of the design phase is to specify the components for this
transformation function, so that each component is also a transformation function.
Hence, the basic output of the system design phase, when a function oriented
design approach is being followed, is the definition of all the major data structures in
the system, all the major modules of the system, and how the modules interact with
each other.
Once the designer is satisfied with the design he has produced, the design is
to be precisely specified in the form of a document. To specify the design,
specification languages are used. Producing the design specification is the ultimate
objective of the design phase. The purpose of this design document is quite different
from that of the design notation. Whereas a design represented using the design
notation is largely to be used by the designer, a design specification has to be so
precise and complete that it can be used as a basis of further development by other
programmers. Generally, design specification uses textual structures, with design
notation helping in understanding.
- 51 -

SCHEDULING
Scheduling of a software project does not differ greatly from scheduling of any multi-
task engineering effort. Therefore, generalized project scheduling tools and
techniques can be applied with little modification to software projects.
Program evaluation and review technique (PERT) and critical path method (CPM)
are two project scheduling methods that can be applied to software development.
Both techniques are driven by information already developed in earlier project
planning activities.
Estimates of Effort
A decomposition of the product function.
The selection of the appropriate process model and task set.
Decomposition of tasks.
Interdependencies among tasks may be defined using a task network. Tasks,

sometimes called the project Work Breakdown Structure (WBS) are defined for the
product as a whole or for individual functions.
Both PERT and CPM provide quantitative tools that allow the software planner to (1)
determine the critical path-the chain of tasks that determines the duration of the
project; (2) establish "most likely" time estimates for individual tasks by applying
statistical models; and (3) calculate "boundary times" that define a time window" for a
particular task.
Boundary time calculations can be very useful in software project scheduling.

Slippage in the design of one function, for example, can retard further development
of other functions. It describes important boundary times that may be discerned from
a PERT or CPM network: (I) the earliest time that a task can begin when preceding
tasks are completed in the shortest possible time, (2) the latest time for task initiation
before the minimum project completion time is delayed, (3) the earliest finish-the
- 52 -

sum of the earliest start and the task duration, (4) the latest finish- the latest start
time added to task duration, and (5) the total float-the amount of surplus time or
leeway allowed in scheduling tasks so that the network critical path maintained on
schedule. Boundary time calculations lead to a determination of critical path and
provide the manager with a quantitative method for evaluating progress as tasks are
completed.
Both PERT and CPM have been implemented in a wide variety of automated tools
that are available for the personal computer. Such tools are easy to use and take the
scheduling methods described previously available to every software project
manager.
- 53 -

- 54 -

HOME.ASPX
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="home.aspx.cs"

Inherits="_Default" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >

<head runat="server">
<title>Untitled Page</title>
<link href="stylesheet.css" rel="stylesheet" type="text/css" />
<script language="javascript" type="text/javascript">
// <!CDATA[
// ]]>
</script>
</head>
<body>
<form id="form1" runat="server">
<div id="header" style="font-size: 18pt; color: white; background-
color: red;" >

 
 
- 55 -

ONLINE VEHICLE CRIME REPORT

INFORMATION SYSTEM 
</div>
<div id="sidebar" style="height: 721px; width: 160px;" >
 
 

<asp:HyperLink ID="HyperLink1" runat="server" Font-Bold="True"
Font-Underline="True"
ForeColor="#FF8000"
NavigateUrl="~/home.aspx">HOME</asp:HyperLink> 
 
 
<asp:HyperLink ID="HyperLink2" runat="server"
Font-Bold="True" Font-Underline="True"
ForeColor="#FF8000" NavigateUrl="~/aboutus1.aspx">ABOUT
US</asp:HyperLink> 
 
 
Font-Bold="True" Font-Underline="True"
ForeColor="#FF8000" NavigateUrl="~/contactus1.aspx">CONTACT
 

 

ForeColor="#FF8000" NavigateUrl="~/aboutus1.aspx">AUTHORIZED
DEALERS</asp:HyperLink> 
 
 

ForeColor="#FF8000" NavigateUrl="~/aboutus1.aspx">VEHICLE
DETAILS</asp:HyperLink> 
 
 

ForeColor="#FF8000" NavigateUrl="~/aboutus1.aspx">CHALLAN
 
 

ForeColor="#FF8000" NavigateUrl="~/aboutus1.aspx">ACCIDENT
 
 

ForeColor="#FF8000" NavigateUrl="~/aboutus1.aspx">LICENSE
AUTHORITY</asp:HyperLink> 
 
- 56 -

 

ForeColor="#FF8000"
NavigateUrl="~/administrator.aspx">ADMINISTRATOR FORM</asp:HyperLink></div>
<div style="text-align: justify" id="branding2">
<div id="brandingboxtext">
<h2>
<table>
<tr>
<td style="width: 594px"><marquee>

 WELCOME TO
OUR
WEBSITE </marquee> </td>
</tr>
</table>

 </h2>
<h2>

Providing information and

 

resources for people working 

to aware of vehicle crime </h2>
</div>
</div>
<table id="TABLE1" onclick="return TABLE1_onclick()">

<tr >
<td style="color:red; width: 278px; height: 1px; ">
<marquee
direction="UP">

LOG IN TO VIEW AUTHORIZED DEALERS VIEW VEHICLE DETAILS KNOW
ABOUT
US</marquee></td>
</tr>
</table>


 

ForeColor="Red" NavigateUrl="~/login.aspx">Log In</asp:HyperLink>
- 57 -








<asp:LinkButton
ID="LinkButton1" runat="server" Font-Bold="False" Font-
Underline="True" PostBackUrl="~/aboutus1.aspx">license
authority</asp:LinkButton>
<asp:LinkButton ID="LinkButton2" runat="server"
PostBackUrl="~/aboutus1.aspx">about us</asp:LinkButton>
PostBackUrl="~/contactus1.aspx">contact us</asp:LinkButton>
PostBackUrl="~/aboutus1.aspx">view authorized dealers</asp:LinkButton>
PostBackUrl="~/aboutus1.aspx">view vehicle details</asp:LinkButton>
PostBackUrl="~/aboutus1.aspx">accidental details</asp:LinkButton>

PostBackUrl="~/aboutus1.aspx">challan details</asp:LinkButton>



 
</form>
</body>
</html>
- 58 -

ABOUT US. ASPX
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Aboutus.aspx.cs"



<title>About Us</title>
<link href ="stylesheet.css" rel="stylesheet" type="text/css" />
</head>
<body>


INFORMATION SYSTEM 
<div id="header"> <marquee>
<img style="WIDTH: 129px"
- 59 -

src="image/thumb.jpg"
/> &
nbsp; &nbs
p;<IMG
style="WIDTH: 182px; HEIGHT: 90px" src="image/Audi_A6-Avant-2004[1].jpg"
/> &
nbsp; &nbs
p;
<img style="WIDTH: 165px; HEIGHT: 92px"
src="image/320-2007-Chevrolet-Impala-SS-Car-of-Tomorrow-NASCAR-Side-Angle-
Top[1].jpg"
/> &
nbsp;
<img src="image/main[7].jpg" /></marquee></div>
<div id="sidebar" style="height: 1526px; width: 161px;">
 
 

ForeColor="#C04000"
 

 

ForeColor="#C04000"
NavigateUrl="~/Aboutus.aspx">ABOUT US</asp:HyperLink> 
 
 
 <asp:HyperLink ID="HyperLink3"
runat="server" Font-Bold="True" ForeColor="#C04000"
NavigateUrl="~/Contactus.aspx">CONTACT
US</asp:HyperLink> 
 

 
Font-Bold="True" ForeColor="#C04000"
NavigateUrl="~/Displaydealers.aspx">AUTHORIZED
DEALERS</asp:HyperLink> 
 
 
<asp:HyperLink ID="HyperLink5" runat="server" Font-
Bold="True" ForeColor="#C04000"
NavigateUrl="~/Displayvehicle.aspx">VEHICLE
 
 

ForeColor="#C04000" NavigateUrl="~/displaychallan.aspx">CHALLAN
 
 

- 60 -

ForeColor="#C04000"
NavigateUrl="~/displayaccident.aspx">ACCIDENT DETAILS</asp:HyperLink> 
 
 

ForeColor="#C04000" NavigateUrl="~/displaylicense.aspx">LICENSE
AUTHORITY</asp:HyperLink></div>
<div style="text-align: left">


 
 WELCOME
<asp:LoginName ID="LoginName1" runat="server" Font-Bold="True"
Font-Italic="True"
ForeColor="RoyalBlue" />


 <asp:LoginStatus ID="LoginStatus1" runat="server"
LogoutAction="RedirectToLoginPage" />



 INTRODUCTION<?xml namespace="" ns="urn:schemas-microsoft-
com:office:office"
prefix="o"
?><o:p></o:p>


<o:p> </o:p>




 This is a Project
work is undertaken in context of partial fulfillment of the
AMIETE.
- 61 -


<?xml namespace="" ns="urn:schemas-microsoft-com:office:office"
prefix="o" ?><o:p> </o:p>
 


Since Online Vehicles Crime Report Information System is
associated with the lives
of common people mainly who are going
to purchase a used vehicle and they want to inquire about
it ,to check whether it
is involved in any crime .So I decided
to work on this project.<o:p></o:p>

The manual handling of the
record is time consuming
and highly prone to error. The purpose of this project is
to automate the process
of day to day activities like records of accidental
vehicles, theft vehicles, vehicles
which are in police records, car theft information,
challans and jump records, Daily
updations and 
Modification by the administrator etc. 

The complete set of rules & procedures related to
vehicles day to day activities
and generating report is called “ONLINE VEHICLES CRIME
REPORT INFORMATION SYSTEM”.
My project gives a brief idea regarding automated searching
activities.<o:p></o:p>
I have tried my best to make the complicated process of
ONLINE VEHICLES CRIME REPORT
INFORMATION SYSTEM as simple as possible using Structured
& Modular technique
& Menu oriented interface. I have tried to design the
software in such a way
that user may not have any difficulty in using this package
& further expansion
is possible without much effort. Even though I cannot claim
that this work to be
entirely exhaustive, the main purpose of my exercise is to
perform each activity
in computerized online way rather than
- 62 -

manually which is time

consuming.<o:p></o:p>
150%">
I am confident that this
software package can be readily used by non-programming
personal avoiding human handled chance of error. This
project is used by two types
of users



i.

 
Online Users.



ii.

 
Administrator (management
of the company).
150%">
Online users can check
criminal background of the
vehicle, if it has any.
150%">
Administrator can maintain l
records of accidental
vehicles, theft vehicles, vehicles which are in police
records, car theft information,
challans and jump records, Daily updations and
Modifications etc. Administrator is
must be an authorized user. He can further change the
password. There is the facility
for password recovery, logout etc.
<o:p></o:p>
 

 

- 63 -






Objectives of
the Project<o:p></o:p>


The objectives of the project are to: 
<o:p></o:p>




12.0pt">

 i.

Develop a functional &
usable Online Vehicles Crime Information
System.<o:p></o:p>
lfo2">
12.0pt">

ii.

This Website is
useful
for the user who mainly wants to purchase a
used vehicle as well as for the
dealer who is in the sale purchase of
the vehicles.<o:p></o:p>
lfo2">
- 64 -


12.0pt">

 iii.

This
Website is useful for users as follows: 
<o:p></o:p>


tab-stops: list .75in; mso-list: l0 level1 lfo1; text-align:
justify;">


·

200%">
To check vehicle details whether it has any
accidental details or not .<o:p></o:p>
justify;">
Ignore">

·

Check Theft or stolen details of the vehicles.
- 65 -


Ignore">
·


Check Challan details of the vehicles.
Ignore">

·

Check Owner details of the vehicles.
Ignore">
 ·


To
give their feed backs
12.0pt">

iv.

 This
Website is useful
for
Administers
as follows: 
<o:p></o:p>





 ·

To add vehicle details whether it has any
accidental details or not .
font-size: 12.0pt;

·

Add theft or stolen details of the vehicles.
font-size: 12.0pt;

- 67 -


Add
Challan details of the vehicles.
font-size: 12.0pt;


Add Owner details of the vehicles.
font-size: 12.0pt;


Collecting Feedbacks
from the users.<o:p></o:p>
justify;">
font-size: 12.0pt;


- 68 -

Report Generation
text-align: justify; tab-stops: list 1.0in; mso-list: l1 level2
lfo2">


lfo2">

lfo2">



</div>
</form>
</body>
</html>
LOG IN.ASPX
- 69 -

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="login.aspx.cs"



<title>Log In</title>
<Link href="stylesheet.css" rel="stylesheet" type="text/css" />
</head>
<body>

ONLINE VEHICLE CRIME
REPORT INFORMATION SYSTEM 
<div id="header" style="background-color: white">
<marquee><img src="image/thumb.jpg" />

- 70 -


<div id="sidebar" style="height: 517px; width: 160px;"> 

ForeColor="#C04000"
 

ForeColor="#C04000" NavigateUrl="~/aboutus1.aspx">ABOUT
 

ForeColor="#C04000" NavigateUrl="~/contactus1.aspx">CONTACT
 

ForeColor="#C04000" NavigateUrl="~/aboutus1.aspx">AUTHORIZED
 
Bold="True" Font-Underline="True"
ForeColor="#C04000" NavigateUrl="~/aboutus1.aspx">VEHICLE
 
ForeColor="#C04000" NavigateUrl="~/aboutus1.aspx">CHALLAN
 

ForeColor="#C04000" NavigateUrl="~/aboutus1.aspx">ACCIDENT
 

ForeColor="#C04000" NavigateUrl="~/aboutus1.aspx">LICENSE
<div>

<asp:Login ID="Login1" runat="server"
DestinationPageUrl="~/Aboutus.aspx">
</asp:Login>

- 71 -



 

 

Font-Italic="True"
Font-Underline="True" ForeColor="Red"
NavigateUrl="~/newlog.aspx">NEW USER SIGN IN</asp:HyperLink> 
 
To change Password or Recover
Password <asp:HyperLink
ID="HyperLink2" runat="server"
NavigateUrl="~/changepassword.aspx" Font-Bold="True" Font-Italic="True"
Font-Underline="True" ForeColor="Red">CLICK HERE</asp:HyperLink> 


 
 
 
 
 
 
 
 
 
<asp:LinkButton
ID="LinkButton1" runat="server"
PostBackUrl="~/home.aspx">home</asp:LinkButton>
PostBackUrl="~/aboutus1.aspx">view authorized dealers</asp:LinkButton>
PostBackUrl="~/aboutus1.aspx">accidenal
details</asp:LinkButton></div></form></body></html>
NEW USER LOG IN.ASPX
- 72 -

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="newlog.aspx.cs"



</head>
<body>

#ff0000">ONLINE VEHICLE
CRIME REPORT INFORMATION SYSTEM 
<div id="header" style="background-color: white">
<marquee direction="forward"><IMG
src="image/main[7].jpg"/> &n
bsp; &nbsp
; &n
bsp; <IMG
- 73 -

/> &
nbsp; &nbs
p; <IMG
style="WIDTH: 159px; HEIGHT: 99px"
Top[1].jpg"
/>
</marquee></div>
 
 

ForeColor="#C04000"
 

 
runat="server" Font-Bold="True" Font-Underline="True"
 

 

 

 

DETAILS</asp:HyperLink></div>
<div>
</div>

<asp:CreateUserWizard ID="CreateUserWizard1" runat="server"
ContinueDestinationPageUrl="~/login.aspx"
OnCreatedUser="CreateUserWizard1_CreatedUser">
<WizardSteps>
<asp:CreateUserWizardStep runat="server">
</asp:CreateUserWizardStep>
- 74 -

<asp:CompleteWizardStep runat="server">
</asp:CompleteWizardStep>
</WizardSteps>
</asp:CreateUserWizard>
 
 
 
 
 
 
 

PostBackUrl="~/aboutus1.aspx">view authorized
dealers</asp:LinkButton>
PostBackUrl="~/aboutus1.aspx">accidental details</asp:LinkButton>


</form>
</body>
</html>
CHANGEPASSWORD.ASPX
- 75 -

<%@ Page Language="C#" AutoEventWireup="true"

CodeFile="changepassword.aspx.cs" Inherits="_Default" %>


<title>Change Password</title>
</head>
<body>

REPORT INFORMATION SYSTEM 
<div id="header" style="background-color:
white"> <marquee> &nbsp
;
<IMG style="WIDTH: 196px; HEIGHT: 94px"
Top[1].jpg"
- 76 -

/> &
nbsp;
<IMG style="WIDTH: 188px; HEIGHT: 108px" src="image/Audi_A6-Avant-
2004[1].jpg"
/> &
nbsp;
<IMG src="image/main[7].jpg" /></marquee></div>
 
 

ForeColor="#C04000"
NavigateUrl="~/home.aspx">HOME</asp:HyperLink>
 
 
 

 
 

 
 

DEALERS</asp:HyperLink>
 
 
 

 
 
 
 

DETAILS</asp:HyperLink></div>
<div>
 
- 77 -

 
<asp:Wizard ID="Wizard1" runat="server"
CancelDestinationPageUrl="~/login.aspx"
FinishDestinationPageUrl="~/login.aspx"
OnFinishButtonClick="Wizard1_FinishButtonClick" ActiveStepIndex="0">
<WizardSteps>
<asp:WizardStep runat="server" Title="CHANGE PASSWORD">
<asp:ChangePassword ID="ChangePassword1" runat="server"
CancelDestinationPageUrl="~/login.aspx"
ContinueDestinationPageUrl="~/login.aspx">
</asp:ChangePassword>
</asp:WizardStep>
<asp:WizardStep ID="WizardStep1" runat="server"
Title="RECOVER PASSWORD">
<asp:PasswordRecovery ID="PasswordRecovery1"
runat="server">
</asp:PasswordRecovery>
</asp:WizardStep>
</WizardSteps>
</asp:Wizard>
 
 
 
 
 
 
 
PostBackUrl="~/aboutus1.aspx">view authorized
PostBackUrl="~/aboutus1.aspx">accident details</asp:LinkButton>
PostBackUrl="~/aboutus1.aspx">challan details</asp:LinkButton></div>
</form>
</body>
</html>
- 78 -

CONTACTUS.ASPX
- 79 -

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Contactus.aspx.cs"

Inherits="Contactus" %>


<title>contact us</title>
</script>
</head>
<body>

<div id="header" ><marquee>
<img src="image/320-2007-Chevrolet-Impala-SS-Car-of-Tomorrow-
NASCAR-Side-Angle-Top[1].jpg"
style="width: 241px; height: 112px" />

- 80 -




<div id ="sidebar" style="width: 160px; height: 526px;">

 

ForeColor="#FF8000"
NavigateUrl="~/home.aspx">HOME</asp:HyperLink>
 
 

ForeColor="#FF8000"
NavigateUrl="~/Aboutus.aspx">ABOUT US</asp:HyperLink> 
 

ForeColor="#FF8000"
NavigateUrl="~/Contactus.aspx">CONTACT US</asp:HyperLink> 
 

ForeColor="#FF8000"
NavigateUrl="~/Displaydealers.aspx">AUTHORIZED
 

ForeColor="#FF8000"
NavigateUrl="~/Displayvehicle.aspx">VEHICLES
 

ForeColor="#FF8000" NavigateUrl="~/displaychallan.aspx">CHALLAN
 
 

ForeColor="#FF8000"
 

ForeColor="#FF8000" NavigateUrl="~/displaylicense.aspx">LICENSE
AUTHORITY</asp:HyperLink>
</div>
<div style="font-weight: bold">
- 81 -



 <asp:LoginStatus
ID="LoginStatus1"
runat="server" Font-Bold="False"
LogoutAction="RedirectToLoginPage" LogoutPageUrl="~/login.aspx" />
 
 Emergency
Contact : 
Bishnu Jyoti Rajkhowa
 
Mobile no: +919990645631 
E-mail: rajbishnujyoti@yahoo.co.in 
 
Office Contact : 
GEC TECHNICAL INSTITUTE 
Uttam nagar
 
New Delhi 
Phone no: +919212002599
 

 
 
 
 
 
 
 
 
Font-Bold="False" PostBackUrl="~/home.aspx">home</asp:LinkButton>

<asp:LinkButton ID="LinkButton2" runat="server" Font-
Bold="False" PostBackUrl="~/Aboutus.aspx">about us</asp:LinkButton>

Bold="False" PostBackUrl="~/displaylicense.aspx">license
<asp:LinkButton ID="LinkButton4"
runat="server" Font-Bold="False" PostBackUrl="~/Displaydealers.aspx">view
authorized dealers</asp:LinkButton>

- 82 -


Bold="False" PostBackUrl="~/Displayvehicle.aspx">view vehicle
details</asp:LinkButton>
Bold="False" PostBackUrl="~/displayaccident.aspx">accident
Bold="False" Font-Underline="True"
PostBackUrl="~/displaychallan.aspx">challan
details</asp:LinkButton></div>
</form>
</body>
</html>
- 83 -

AUTHORIZED DEALERS.ASPX

CodeFile="Displaydealers.aspx.cs" Inherits="Displaydealers" %>


</script>
</head>
<body>

 ONLINE
VEHICLE CRIME REPORT INFORMATION
SYSTEM 
<div id="header" style="height: 44px">
<marquee> <img
src="image/main[7].jpg"
/> &
nbsp; &nbs
p; &
nbsp;<IMG
/> &
nbsp; &nbs
p; &
nbsp;
 <IMG style="WIDTH: 195px; HEIGHT: 106px"
Top[1].jpg"
/> &
nbsp; &nbs
p; &
nbsp; &nbs
p;
<IMG src="image/main[7].jpg" /></marquee></div>
<div id="sidebar" onclick="return sidebar_onclick()" style="width:
126px; height: 510px;">
 

ForeColor="#FF8000"
- 84 -

 

 

ForeColor="#FF8000" NavigateUrl="~/Aboutus.aspx">ABOUT
 

 

ForeColor="#FF8000" NavigateUrl="~/Contactus.aspx">CONTACT
 

 

ForeColor="#FF8000"
NavigateUrl="~/Displaydealers.aspx">AUTHORIZED DEALERS</asp:HyperLink> 
 
 
runat="server" Font-Bold="True" Font-Underline="True"
ForeColor="#FF8000" NavigateUrl="~/Displayvehicle.aspx">VEHICLE
 
 

 
 

ForeColor="#FF8000"
 
ForeColor="#FF8000" NavigateUrl="~/displaylicense.aspx">LICENSE
<div>

- 85 -


 

 
 Please choose the location

<asp:DropDownList ID="DropDownList1" runat="server"
AutoPostBack="True"
OnSelectedIndexChanged="DropDownList1_SelectedIndexChanged">
<asp:ListItem>-SELECT-</asp:ListItem>
<asp:ListItem>DELHI</asp:ListItem>
<asp:ListItem>MUMBAI</asp:ListItem>
<asp:ListItem>NOIDA</asp:ListItem>
<asp:ListItem>GURGAON</asp:ListItem>
<asp:ListItem>GUWAHATI</asp:ListItem>
<asp:ListItem>GAZIABAD</asp:ListItem>
<asp:ListItem>CHENNAI</asp:ListItem>
<asp:ListItem>KOLKATA</asp:ListItem>
</asp:DropDownList> 


 


<asp:Label ID="Label1" runat="server" Font-Bold="True"
ForeColor="Red" Text="Label"
Visible="False"></asp:Label> 

<asp:GridView ID="GridView1" runat="server"
BackColor="White"
BorderColor="#999999" BorderStyle="Solid" BorderWidth="1px"
CellPadding="3" ForeColor="Black"
GridLines="Vertical" AutoGenerateColumns="False">
<FooterStyle BackColor="#CCCCCC" />
<Columns>
<asp:BoundField HeaderText="Name of the Dealer"
DataField="dname" />
<asp:BoundField HeaderText="Name of Owner"
DataField="downer" />
<asp:BoundField HeaderText="Location" DataField="dlocation"
/>
<asp:BoundField HeaderText="Address" DataField="daddr" />
<asp:BoundField HeaderText="Contact Number"
DataField="contactno" />
</Columns>
<SelectedRowStyle BackColor="#000099" Font-Bold="True"
ForeColor="White" />
- 86 -

<PagerStyle BackColor="#999999" ForeColor="Black"

HorizontalAlign="Center" />
<HeaderStyle BackColor="Black" Font-Bold="True"
<AlternatingRowStyle BackColor="#CCCCCC" />
</asp:GridView>
 

 

 


 


 

 


 

 
 
 
 
runat="server" PostBackUrl="~/home.aspx">home</asp:LinkButton>
PostBackUrl="~/Aboutus.aspx">about us</asp:LinkButton>
PostBackUrl="~/Contactus.aspx">contact us</asp:LinkButton>
PostBackUrl="~/displaylicense.aspx">license authority</asp:LinkButton>
PostBackUrl="~/Displayvehicle.aspx">view vehiclle
PostBackUrl="~/displayaccident.aspx">accident details</asp:LinkButton>

PostBackUrl="~/displaychallan.aspx">challan details</asp:LinkButton></div>
</form>
</body>
</html>
AUTHORIZED DEALERS.ASPX.CS
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
- 87 -

using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.OleDb;
using System.Data.SqlClient;
public partial class Displaydealers : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
String scon = "Trusted_Connection=True;DataBase=bishnu";
SqlConnection con = new SqlConnection(scon);
if (!IsPostBack)
{
SqlDataAdapter da = new SqlDataAdapter("Select * from dealer ",

con);
DataSet ds = new DataSet();
da.Fill(ds);
DropDownList1.DataSource = ds;
DropDownList1.DataTextField = "dlocation";
DropDownList1.DataBind();
}
}
protected void DropDownList1_SelectedIndexChanged(object sender,
EventArgs e)
{
String scom = "Select * from dealer where dlocation=@loc";
SqlCommand com = new SqlCommand(scom, con);
SqlParameter loc = new SqlParameter();

loc.DbType = System.Data.DbType.String;
loc.ParameterName = "@loc";
loc.Value = DropDownList1.SelectedItem.Value;
com.Parameters.Add(loc);
SqlDataAdapter da = new SqlDataAdapter(com);

DataTable ds = new DataTable();
da.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
- 88 -

- 89 -

VEHICLE DETAILS.ASPX

CodeFile="Displayvehicle.aspx.cs" Inherits="Displayvehicle" %>


<title>vehicle details</title>
</head>
<body>

 ONLINE VEHICLE CRIME
REPORT INFORMATION
SYSTEM 
- 90 -

<div id="header" style="width: 1073px; height: 1px; background-color:

white;"><marquee style="height: 55px"><IMG style="WIDTH: 202px; HEIGHT:
93px"
Top[1].jpg"
/> &
nbsp; &nbs
p; &
nbsp; <IMG
/> &
nbsp; &nbs
p; &
nbsp; &nbs
p;
<IMG src="image/main[7].jpg" /></marquee>
</div>
<div id="sidebar" style="width: 144px; height: 605px;">
 

ForeColor="#FF8000"
 

ForeColor="#FF8000" NavigateUrl="~/Aboutus.aspx">ABOUT
US</asp:HyperLink>
 
 

ForeColor="#FF8000" NavigateUrl="~/Contactus.aspx">CONTACT
 
 

ForeColor="#FF8000"
/>
 
 

ForeColor="#FF8000" NavigateUrl="~/Displayvehicle.aspx">VEHICLE
 
 

- 91 -

 
 

ForeColor="#FF8000"
 
 
ForeColor="#FF8000" NavigateUrl="~/displaylicense.aspx"
Width="148px">LICENSE AUTHORITY</asp:HyperLink></div>
<div>
 

<asp:LoginStatus
ID="LoginStatus1" runat="server"
 
Plaese fill up the following: 
 
Manufacturer company of the Vehicle
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox> 
 


<asp:Button ID="Button1" runat="server" Font-Bold="True" Font-
Italic="True" Font-Underline="True"
ForeColor="Red" OnClick="Button1_Click" Text="Submit" />
 

<asp:Label ID="Label1" runat="server" ForeColor="Red" Text="Label"
Visible="False"></asp:Label> 


 
AutoGenerateColumns="False" BackColor="White"
BorderColor="#DEDFDE" BorderStyle="None" BorderWidth="1px"
GridLines="Vertical" Width="449px">
<FooterStyle BackColor="#CCCC99" />
<Columns>
<asp:BoundField DataField="owner" HeaderText="Owner of
Vehicle" />
<asp:BoundField DataField="manufacturer"
HeaderText="Manufacturing Company" />
- 92 -

<asp:BoundField DataField="color" HeaderText="Color of

Vehicle" />
<asp:BoundField DataField="licenseno"
HeaderText="Registration Number" />
<asp:BoundField DataField="model" HeaderText="Model Number"
/>
<asp:BoundField DataField="myear" HeaderText="Manufacturing
Year" />
<asp:BoundField DataField="stolen" HeaderText="Is this
Stolen" />
</Columns>
<RowStyle BackColor="#F7F7DE" />
<SelectedRowStyle BackColor="#CE5D5A" Font-Bold="True"
<PagerStyle BackColor="#F7F7DE" ForeColor="Black"
HorizontalAlign="Right" />
<HeaderStyle BackColor="#6B696B" Font-Bold="True"
<AlternatingRowStyle BackColor="White" />
</asp:GridView>
 


</div>
 
 
 
runat="server" PostBackUrl="~/home.aspx">home</asp:LinkButton>
PostBackUrl="~/Displaydealers.aspx">view authorized

PostBackUrl="~/displaylicense.aspx">license
PostBackUrl="~/displaychallan.aspx">challan details</asp:LinkButton>
PostBackUrl="~/displayaccident.aspx">accident details</asp:LinkButton>
</form>
</body>
</html>
- 93 -

VEHICLE DETAILS.ASPX.CS
using System;
using System.Data;
using System.Web;
using System.Data.OleDb;
public partial class Displayvehicle : System.Web.UI.Page

{
{
}
protected void Button1_Click(object sender, EventArgs e)
{

con.Open();
String scom = "Select * from vehicle where manufacturer=@manu
";
SqlParameter manu = new SqlParameter("@manu",

DbType.StringFixedLength);
manu.Value = TextBox1.Text;
com.Parameters.Add(manu);

da.Fill(ds);
int n = ds.Rows.Count;
if (n == 0)
{
TextBox1.Text = "";
Label1.Visible = true;
Label1.Text = "Sorry.No Update is available for this
Vehicle”;
}
con.Close();
}
- 94 -

CHALLAN DETAILS.ASPX

CodeFile="displaychallan.aspx.cs" Inherits="dispplaychallan" %>


<title>Challan Details</title>
</head>
<body>

 ONLINE
VEHICLE CRIME REPORT INFORMATION
SYSTEM 
<div id="header" style="height: 1px">
- 95 -



<img src="image/Audi_A6-Avant-2004[1].jpg" style="width: 198px;
height: 91px" />


<img src="image/main[7].jpg" style="width: 116px; height: 79px"
/></div>
<div id="sidebar" style="width: 159px; height: 642px">
 

ForeColor="#C04000"
 

 

ForeColor="#C04000" NavigateUrl="~/Aboutus.aspx">ABOUT
 
 

ForeColor="#C04000" NavigateUrl="~/Contactus.aspx">CONTACT
 
 

ForeColor="#C04000"
/>
 
 

ForeColor="#C04000" NavigateUrl="~/Displayvehicle.aspx">VEHICLE
 
 

 
 

ForeColor="#C04000">ACCIDENT DETAILS</asp:HyperLink> 
 
 
- 96 -


<div>








 


 
Please choose the Registration number of the
Vehice
AutoPostBack="True"
OnSelectedIndexChanged="DropDownList1_SelectedIndexChanged">
<asp:ListItem>-SELECT-</asp:ListItem>
</asp:DropDownList>
 
 



AutoGenerateColumns="False" Width="480px" BackColor="#DEBA84"
BorderColor="#DEBA84" BorderStyle="None" BorderWidth="1px" CellPadding="3"
CellSpacing="2">
<Columns>
HeaderText="Registration Number of Vehicle" />
<asp:BoundField DataField="modelno" HeaderText="Vehicle
Model" />
<asp:BoundField DataField="challandate" HeaderText="Challan
Date" />
<asp:BoundField DataField="amount" HeaderText="Challan
Amount" />
<asp:BoundField DataField="cause" HeaderText="Cause of
Challan" />
</Columns>
<FooterStyle BackColor="#F7DFB5" ForeColor="#8C4510" />
<RowStyle BackColor="#FFF7E7" ForeColor="#8C4510" />
<SelectedRowStyle BackColor="#738A9C" Font-Bold="True"
<PagerStyle ForeColor="#8C4510" HorizontalAlign="Center" />
- 97 -

<HeaderStyle BackColor="#A55129" Font-Bold="True"

</asp:GridView>
 
 
 
 
 
 
 
 
 
 

PostBackUrl="~/Displaydealers.aspx">view authorized
PostBackUrl="~/Displayvehicle.aspx">view vehicle
PostBackUrl="~/displaylicense.aspx">license
<asp:LinkButton ID="LinkButton7" runat="server">accident

</div>
</form>
</body>
</html>
CHALLAN DETAILS.ASPX.CS
using System;
using System.Data;
using System.Web;
public partial class dispplaychallan : System.Web.UI.Page

{
{
if (!IsPostBack)
- 98 -

{
SqlDataAdapter da = new SqlDataAdapter("Select * from challan",
con);
da.Fill(ds);
DropDownList1.DataTextField = "licenseno";
}
}

EventArgs e)
{
String scom = "Select * from challan where licenseno=@lno";
SqlParameter lno = new SqlParameter();

lno.DbType = System.Data.DbType.String;
lno.ParameterName = "@lno";
lno.Value = DropDownList1.SelectedItem.Value;
com.Parameters.Add(lno);

da.Fill(ds);
}
}
- 99 -

ACCIDENT DETAILS.ASPX

CodeFile="displayaccident.aspx.cs" Inherits="displayaccident" %>


<title>Accident Details</title>
</head>
<body>

- 100 -


ONLINE
VEHICLE
CRIME REPORT INFORMATION SYSTEM 
<div id="header"> <marquee>
<img
src="image/Audi_A6-Avant-2004[1].jpg"

<img src="image/main[7].jpg"
/></marquee>
</div>
<div id="sidebar" style="width: 126px; height: 646px"> 

ForeColor="#C04000"
 
 

 
 

 


ForeColor="#C04000"
/>
 


 


 
- 101 -


ForeColor="#C04000"
NavigateUrl="~/displayaccident.aspx">ACCIDENT
DETAILS</asp:HyperLink> 

 

AUTHORITY</asp:HyperLink>

</div>
<div>




 

 
Choose the Registration
number of the
Vehicle
OnSelectedIndexChanged="DropDownList1_SelectedIndexChanged"
AutoPostBack="True">
</asp:DropDownList> 
 
 

AutoGenerateColumns="False" BackColor="White"
BorderColor="#999999" BorderStyle="Solid" BorderWidth="1px"
GridLines="Vertical">
<FooterStyle BackColor="#CCCCCC" />
<Columns>
HeaderText="Registration number of vehicle" />
<asp:BoundField DataField="modelno" HeaderText="Model
number of vehicle" />
- 102 -

<asp:BoundField DataField="color" HeaderText="Color of

vehicle" />
<asp:BoundField DataField="accdate" HeaderText="Date of
accident" />
<asp:BoundField DataField="details" HeaderText="Accidental
details" />
</Columns>
<SelectedRowStyle BackColor="#000099" Font-Bold="True"
<PagerStyle BackColor="#999999" ForeColor="Black"
HorizontalAlign="Center" />
<HeaderStyle BackColor="Black" Font-Bold="True"
<AlternatingRowStyle BackColor="#CCCCCC" />
</asp:GridView>
</div>
 
 
 
 
 
 
 
 
 
 

PostBackUrl="~/Displaydealers.aspx">authorized dealers</asp:LinkButton>
PostBackUrl="~/Displayvehicle.aspx">vehicle details</asp:LinkButton>
PostBackUrl="~/displaylicense.aspx">license authority</asp:LinkButton>

</form>
</body>
</html>
- 103 -

ACCIDENT DETAILS.ASPX.CS
using System;
using System.Data;
using System.Web;
public partial class displayaccident : System.Web.UI.Page

{
{
if (!IsPostBack)
{
SqlDataAdapter da = new SqlDataAdapter("Select * from
accident", con);
da.Fill(ds);
DropDownList1.DataTextField = "licenseno";
}
}
EventArgs e)
{
String scom = "Select * from accident where licenseno=@lno";
SqlParameter lno = new SqlParameter();

lno.DbType = System.Data.DbType.String;
lno.ParameterName = "@lno";
lno.Value = DropDownList1.SelectedItem.Value;
com.Parameters.Add(lno);
SqlDataAdapter da = new SqlDataAdapter( com);

da.Fill(ds);
}
}
- 104 -

LICENSE AUTHORITY.ASPX
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="license.aspx.cs"

Inherits="license" %>


<title>License Authority</title>
</head>
<body>

REPORT INFORMATION SYSTEM
 
<div id="header" style="height: 1px" > <marquee>
- 105 -




<img
src="image/main[7].jpg" style="width: 153px; height: 87px" />



<img
src="image/Audi_A6-Avant-2004[1].jpg" style="width: 220px;
height: 131px" />
</marquee></div>
<div id="sidebar" style="width: 130px; height: 559px">
 

ForeColor="#C04000"
 

 

 

ForeColor="#C04000"
/>
 

 

 

ForeColor="#C04000"
NavigateUrl="~/displayaccident.aspx">ACCIDENT DETAILS</asp:HyperLink></div>
<div>
 
- 106 -

 Name of the Authority

<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
 
 
 Location


 
 Address

<asp:TextBox
ID="TextBox3"
runat="server" Width="290px"></asp:TextBox>

 
 .Contact Number


 
Email
Address

 
 

<asp:Button ID="Button1" runat="server" Font-Bold="True" Font-
Italic="True" Font-Underline="True"
ForeColor="Red" OnClick="Button1_Click" Text="Submit" /> 
 
 
 
 
 
 
 
 



PostBackUrl="~/Displaydealers.aspx">authorized dealers</asp:LinkButton>

PostBackUrl="~/Displayvehicle.aspx">vehicle details</asp:LinkButton>

- 107 -


PostBackUrl="~/displayaccident.aspx">accidental
details</asp:LinkButton></div>
</form>
</body>
</html>
LICENSE AUTHORITY.ASPX.CS
using System;
using System.Data;
using System.Web;
public partial class displaylicense : System.Web.UI.Page

{
{
SqlConnection con= new SqlConnection(scon);
if (!IsPostBack)
{
SqlDataAdapter da = new SqlDataAdapter("Select * from license",
con);
da.Fill(ds);
DropDownList1.DataTextField = "location";
}
}
EventArgs e)
{
String scom = "Select * from license where location=@loc";
SqlCommand com = new SqlCommand();
com.CommandText = scom;
com.Connection = con;
SqlParameter loc = new SqlParameter();

loc.DbType = System.Data.DbType.String;
loc.ParameterName = "@loc";
loc.Value = DropDownList1.SelectedItem.Value;
com.Parameters.Add(loc);

da.Fill(ds);
- 108 -

}
}
PAGES UNDER ADMINISTRATOR’S CONTROL

AUTHORIZED DEALERS.ASPX

CodeFile="Authorizedealer.aspx.cs" Inherits="Authorizedealer" %>


<title>Authorized dealers</title>
</head>
<body>

ONLINE
VEHICLE CRIME REPORT
- 109 -

1843

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1843

Uploaded by

Copyright:

Available Formats

Balujalabs Contact us at 9313565406, 9212002599

A Project for MCA

(Dynamic Site using ASP.NET ,C# and SQL Server)

PINKY (Enrollment No. : 050185527)

Balujalabs Contact us at 9313565406, 9212002599

ONLINE VEHICLE TRACKING SYSTEM

Under Supervision of: G.S.BALUJA

Enrolment No. : 050185527

Address : WZ-A/93, Vidhya Vihar, Hastsal

Road, New Delhi-59

Programme Code : MCA

Course Code : MSCP-60

Subject Title : PROJECT REPORT

Project Title : ONLINE VEHICLE TRACKING SYSTEM

Name of the Study : MAHARAJ SURAJMAL INSTITUTE,

Balujalabs Contact us at 9313565406, 9212002599

Finally, I gratefully acknowledge the support, encouragement & patience of my

Balujalabs Contact us at 9313565406, 9212002599

Balujalabs Contact us at 9313565406, 9212002599

Balujalabs Contact us at 9313565406, 9212002599

8. Post Implementation Maintenance and Review

Balujalabs Contact us at 9313565406, 9212002599

This is a Project work is undertaken in context of partial fulfillment of the MCA.

I have tried my best to make the complicated process of ONLINE VEHICLES

I am confident that this software package can be readily used by non-programming

Balujalabs Contact us at 9313565406, 9212002599

ii. Administrator (management of the company).

Administrator can maintain l records of accidental vehicles, theft vehicles, vehicles

Balujalabs Contact us at 9313565406, 9212002599

OBJECTIVES OF THE PROJECT

• Maintain records of the all vehicles.

• Generate reports for the vehicles.

• Generate reports for the details about the accidental vehicles.

• Deletion of data of Vehicles and users from the table.

• Searching of records according to users requirements.

• Administrator Module to generate following reports

ii. Theft Vehicles

iii. Challans & jumps

ii. Vehicle Details

iii. Vehicles having pollution checking certificate.

• Collecting Feedbacks from the users.

Balujalabs Contact us at 9313565406, 9212002599

DRAWBACKS OF CURRENT MANUAL- SYSTEM

old and new car purchase and sale.

• To maintain the records of sale and service manually, is a Time-consuming

bit of space in the office, which can be used

for storing records of previously sale vehicles.

• The retrieval of records of previously sold vehicle will be a tedious job.

does not provide any necessary detail of this type.

Balujalabs Contact us at 9313565406, 9212002599

ESTABLISH THE NEED OF NEW SYSTEM

1. Problem of Reliability: Current system is not reliable. It seems to vary in quality

2. Problem of Accuracy: There are too many mistakes in reports.

4. Problem of Validity: The output and reports mostly contains misleading

6. Problem of Capacity: The current system is suffering from problem of capacity

Balujalabs Contact us at 9313565406, 9212002599

2. Calculations: The new proposed system updates tables and other

3. Registers: There is no need of keeping and maintaining salary and

8. Reduces redundancy: The most important benefit of this system is that it

10. Easy statements: Month-end and day-end statement easily taken

Balujalabs Contact us at 9313565406, 9212002599

• Efficiency: The basic need of this website is efficiency. The website

• Control: The complete control of the project is under the hands of

Balujalabs Contact us at 9313565406, 9212002599