11

CHAPTER 1

INTRODUCTION

Yellow Pages refer to a telephone directory of

businesses, categorized according to the product or
service provided. As the name suggests, such
directories were originally printed on yellow paper,
as opposed to white pages for non-commercial
listings. The traditional term Yellow Pages is now
also applied to online directories of businesses.

The name and concept of "Yellow Pages" came

about in 1883, when a printer in Cheyenne, Wyoming
working on a regular telephone directory ran out of
white paper and used yellow paper instead. In 1886
Reuben H. Donnelley created the first official yellow
pages directory, inventing an industry.
 12

Today, the expression Yellow Pages is used

globally, in both English-speaking and non-English
speaking countries. In the United States, it refers to
the category, while in some other countries it is a
registered name and therefore a proper noun. The
term Yellow Pages is not a registered name within
the United States and is freely used by many
companies.

1.1 TELEPHONE DICTIONARY

A telephone directory (also called a telephone

book and phone books) is a listing of telephone
subscribers in a geographical area or subscribers to
services provided by the organization that publishes
the directory.

Subscriber names are generally listed in

alphabetical order, together with their postal or street
address and telephone number. Every subscriber in
the geographical coverage area is usually listed, but
 13

subscribers may request the exclusion of their

number from the directory, often for a fee. Their
number is then said to be "unlisted" (American
English), "ex-directory" (British English) or "private"
(Australia and New Zealand).

In the case of unlisted numbers, practices as to

Caller-ID vary by jurisdiction. Sometimes, the
Caller-ID on outbound calls is blank; in other
jurisdictions, unlisted numbers still appear, unless the
caller dials a blocking code; in still others, the
customer may request automatic blocking from the
telephone company's service representatives.

In the US, under current rules and practices,

mobile phone and Voice over IP listings are not
included in telephone directories. Efforts to create
cellular directories have met stiff opposition from
several fronts, including a significant percentage of
subscribers who seek to avoid telemarketers
 14

1.2 ELECTRONIC YELLOW PAGES

Electronic Yellow Pages are online versions of

traditional printed business directories produced by
telephone companies around the world. Typical
functionalities of online yellow pages include the
alphabetical listings of businesses and search
functionality of the business database by name,
business or location. Since Electronic Yellow Pages
are not limited by space considerations, they often
contain far more comprehensive business information
such as vicinity maps, company profiles, product
information, and more.

An advantage of Electronic Yellow Pages is that they

can be updated in real time; therefore, listed
businesses are not constrained by once-a-year
publishing of the printed version which leads to
greater accuracy of the listings since contact
information may change at any time.
 15

CHAPTER 2

SYSTEM ANALYSIS

2.1 INTRODUCTION
After analyzing the requirements of the task to be
performed, the next step is to analyze the problem
and understand its context. The first activity in the
phase is studying the existing system and other is to
understand the requirements and domain of the new
system. Both the activities are equally important, but
the first activity serves as a basis of giving the
functional specifications and then successful design
of the proposed system. Understanding the properties
and requirements of a new system is more difficult
 16

and requires creative thinking and understanding of

existing running system is also difficult, improper
understanding of present system can lead diversion
from solution.
2.2 ANALYSIS MODEL
This document play a vital role in the
development of life cycle (SDLC) as it describes
the complete requirement of the system. It means
for use by developers and will be the basic during
testing phase. Any changes made to the
requirements in the future will have to go through
formal change approval process.
SPIRAL MODEL was defined by Barry Boehm
in his 1988 article, “A spiral Model of Software
Development and Enhancement. This model was
not the first model to discuss iterative
development, but it was the first model to explain
why the iteration models.
 17

As originally envisioned, the iterations were

typically 6 months to 2 years long. Each phase
starts with a design goal and ends with a client
reviewing the progress thus far. Analysis and
engineering efforts are applied at each phase of the
project, with an eye toward the end goal of the
project.
The steps for Spiral Model can be generalized as
follows:
• The new system requirements are defined in as
much details as possible. This usually involves
interviewing a number of users representing all
the external or internal users and other aspects
of the existing system.

• A preliminary design is created for the new

system.

• A first prototype of the new system is

constructed from the preliminary design. This
 18

is usually a scaled-down system, and

represents an approximation of the
characteristics of the final product.

• A second prototype is evolved by a fourfold

procedure:
1. Evaluating the first prototype in terms of
its strengths, weakness, and risks.
2. Defining the requirements of the second
prototype.
3. Planning an designing the second
prototype.
4. Constructing and testing the second
prototype.
• At the customer option, the entire project can
be aborted if the risk is deemed too great.
Risk factors might involved development cost
overruns, operating-cost miscalculation, or any
other factor that could, in the customer’s
judgment, result in a less-than-satisfactory
final product.
 19

• The existing prototype is evaluated in the same

manner as was the previous prototype, and if
necessary, another prototype is developed
from it according to the fourfold procedure
outlined above.
• The preceding steps are iterated until the
customer is satisfied that the refined prototype
represents the final product desired.
• The final system is constructed, based on the
refined prototype.
• The final system is thoroughly evaluated and
tested. Routine maintenance is carried on a
continuing basis to prevent large scale failures
and to minimize down time.

The following diagram shows how a spiral

model acts like:
 20

FIG 2.1 Spiral Model

2.3 STUDY OF THE SYSTEM

In the flexibility of the uses the interface has been

developed a graphics concept in mind, associated
through a browses interface. The GUI’S at the top
level have been categorized as

1. Administrative user interface

2. The operational or generic user interface

 21

The administrative user interface concentrates on the

consistent information that is practically, part of the
organizational activities and which needs proper
authentication for the data collection. The interfaces
help the administrations with all the transactional
states like Data insertion, Data deletion and Date
updation along with the extensive data search
capabilities.

The operational or generic user interface helps the

users upon the system in transactions through the
existing data and required services. The operational
user interface also helps the ordinary users in
managing their own information helps the ordinary
users in managing their own information in a
customized manner as per the assisted flexibilities.

NUMBER OF MODULES

The system after careful analysis has been identified

to be presented with the following modules:
 22

The modules involved are:

1. Admin Module
2. User Module
3. General Module

Accordingly,there functions are:

2.3.1 Admin module:
User Registration: Users are nothing but
Customers. Every customer must be a register user.
So that they can be a registered person. After
registering they may obtain a valid username and
password. After that they can login by using that
username and password for using services provided
by the application. Admin is the super user, he has all
the privileges. After completion of the vehicle
registration that vehicle is available for the
customers. Every user must have an unique Id from
identify.
 23

Settings: Admin can alter modify or create the

database entries and also see the various user’s
entries, feedbacks, messages etc. User’s forgot
password requests etc.
Email: In this we have created smtp server so that
admin can send its employees and others registered
or unregistered users emails.

2.3.2 User module:

Search : Customer can search his requirements for a
phone numbers, address available in the database. For
specifically finding out the exact requirement a
choice has been given to the user to select the
location and state. If the user left the choices blank
search will be performed on the total database simply
like pattern matching.
Profile: This has been added as a extra feature , here
the user can upload his or her photo and fill some
common type entries like hobbies, address ,interest
 24

,qualification etc .This option was purposely created

so that we may extend in future as the social
network .
Feedback: The registered users can send messages,
feedbacks to the admin.

2.3.3 General Module:

This is the default module accessible to the
unregistered users they can’t search anything but:-
Contact Us: They can send messages to the admin
side by using this.
About Us: See and read about the clients.

2.4 HARDWARE/SOFTWARE
SPECIFICATIONS

HARDWARE REQUIREMENTS:

• PIV 2.8 GHz Processor and Above

• RAM 512MB and Above
 25

• HDD 20 GB Hard Disk Space and Above

SOFTWARE REQUIREMENTS:
• WINDOWS OS (XP / 2000 / 200 Server / 2003
Server)
• Visual Studio .Net 2008 Enterprise Edition
• Internet Information Server 5.0 (IIS)
• Visual Studio 3.5 .Net Framework (Minimal for
Deployment)
• SQL Server 2000 Enterprise Edition

2.5 INPUT AND OUTPUT :

The main inputs, outputs and major functions of the

system are as follows.
The main inputs, outputs and major functions of the
system are as follows.
Inputs:
• Admin enters his or her user id and password.
 26

• Users enter his or her user id and password.

• General Users send messages to admin.
• User send messages to admin
• User requests the search.
• Admin can edit anything , any entry.
• User can edit the personal details and so on.
• Users select the state and location entries for
enhancing searching.

Outputs:
• Admin see all details.
• Users receive the personal mails.
• Users see personal profiles.
• User recieve registration details.
• Display search results.
 27

CHAPTER 3

FEASIBILITY REPORT

Preliminary investigation examine project feasibility,

the likelihood the system will be useful to the
organization. The main objective of the feasibility
 28

study is to test the Technical, Operational and

Economical feasibility for adding new modules and
debugging old running system. All system is feasible
if they are unlimited resources and infinite time.
There are aspects in the feasibility study portion of
the preliminary investigation:

• Technical Feasibility
• Operation Feasibility
• Economical Feasibility

3.1 Technical Feasibility

The technical issue usually raised during the

feasibility stage of the investigation includes the
following:

• Does the necessary technology exist to do what

is suggested?
 29

• Do the proposed equipments have the technical

capacity to hold the data required to use the new
system?
• Will the proposed system provide adequate
response to inquiries, regardless of the number or
location of users?
• Can the system be upgraded if developed?
• Are there technical guarantees of accuracy,
reliability, ease of access and data security?

Earlier no system existed to cater to the needs of

‘Secure Infrastructure Implementation System’. The
current system developed is technically feasible. It is
a web based user interface for audit workflow at
NIC-CSD. Thus it provides an easy access to the
users. The database’s purpose is to create, establish
and maintain a workflow among various entities in
order to facilitate all concerned .
 30

3.2 Operational Feasibility

Proposed projects are beneficial only if they can be

turned out into information system. That will meet
the organization’s operating requirements.
Operational feasibility aspects of the project are to be
taken as an important part of the project
implementation. Some of the important issues raised
are to test the operational feasibility of a project
includes the following: -

• Is there sufficient support for the management

from the users?
• Will the system be used and work properly if it is
being developed and implemented?
• Will there be any resistance from the user that
will undermine the possible application benefits?

This system is targeted to be in accordance with

the above-mentioned issues. Beforehand, the
 31

management issues and user requirements have been

taken into consideration. So there is no question of
resistance from the users that can undermine the
possible application benefits.

The well-planned design would ensure the optimal

utilization of the computer resources and would help
in the improvement of performance status.

3.3 Economic Feasibility

A system can be developed technically and that will

be used if installed must still be a good investment
for the organization. In the economical feasibility, the
development cost in creating the system is evaluated
against the ultimate benefit derived from the new
systems. Financial benefits must equal or exceed the
costs.
The system is economically feasible. It does not
require any addition hardware or software. Since the
interface for this system is developed using the
existing resources and technologies available at NIC,
 32

There is nominal expenditure and economical

feasibility for certain.

CHAPTER 4

SELECTED SOFTWARE

4.1 INTRODUCTION TO .NET Framework

The .NET Framework is a new computing platform

that simplifies application development in the highly
distributed environment of the Internet. The .NET
Framework is designed to fulfill the following
objectives:

• To provide a consistent object-oriented

programming environment whether object code is
stored and executed locally, executed locally but
Internet-distributed, or executed remotely.
 33

• To provide a code-execution environment that

minimizes software deployment and versioning
conflicts.
• To provide a code-execution environment that
guarantees safe execution of code, including code
created by an unknown or semi-trusted third party.
• To provide a code-execution environment that
eliminates the performance problems of scripted or
interpreted environments.
• To make the developer experience consistent
across widely varying types of applications, such
as Windows-based applications and Web-based
applications.
• To build all communication on industry
standards to ensure that code based on the .NET
Framework can integrate with any other code.
 34

FEATURES OF THE COMMON LANGUAGE

RUNTIME
The common language runtime manages
memory, thread execution, code execution, code
safety verification, compilation, and other system
services. These features are intrinsic to the managed
code that runs on the common language runtime.

NET FRAMEWORK CLASS LIBRARY

The .NET Framework class library is a collection

of reusable types that tightly integrate with the
common language runtime. The class library is object
oriented, providing types from which your own
managed code can derive functionality. This not only
makes the .NET Framework types easy to use, but
also reduces the time associated with learning new
features of the .NET Framework. In addition, third-
 35

party components can integrate seamlessly with

classes in the .NET Framework.
For example, you can use the .NET Framework
to develop the following types of applications and
services:
• Console applications.
• Scripted or hosted applications.
• Windows GUI applications (Windows Forms).
• ASP.NET applications.
• XML Web services.
• Windows services.

CLIENT APPLICATION DEVELOPMENT

Client applications are the closest to a traditional

style of application in Windows-based programming.
These are the types of applications that display
windows or forms on the desktop, enabling a user to
perform a task. Client applications include
applications such as word processors and
 36

spreadsheets, as well as custom business applications

such as data-entry tools, reporting tools, and so on.
Client applications usually employ windows, menus,
buttons, and other GUI elements, and they likely
access local resources such as the file system and
peripherals such as printers.

4.2 ASP.NET

Server Application Development

Server-side applications in the managed world
are implemented through runtime hosts. Unmanaged
applications host the common language runtime,
which allows your custom managed code to control
the behavior of the server. This model provides you
with all the features of the common language runtime
and class library while gaining the performance and
scalability of the host server.
 37

 SERVER-SIDE MANAGED CODE

ASP.NET is the hosting environment that

enables developers to use the .NET Framework to
target Web-based applications. However, ASP.NET
is more than just a runtime host; it is a complete
architecture for developing Web sites and Internet-
distributed objects using managed code. Both Web
Forms and XML Web services use IIS and ASP.NET
as the publishing mechanism for applications, and
both have a collection of supporting classes in the
.NET Framework.

 ACTIVE SERVER PAGES.NET

ASP.NET is a programming framework built on
the common language runtime that can be used on a
server to build powerful Web applications. ASP.NET
 38

offers several important advantages over previous

Web development models:
• Enhanced Performance.
• World-Class Tool Support.
• Power and Flexibility.
• Simplicity.
• Manageability.
• Scalability and Availability.
• Customizability and Extensibility.
• Security.

4.3 LANGUAGE SUPPORT

The Microsoft .NET Platform currently offers

built-in support for three languages: C#, Visual
Basic, and JScript.

4.4 INTRODUCTION TO ASP.NET SERVER

CONTROLS
 39

In addition to (or instead of) using <% %> code

blocks to program dynamic content, ASP.NET page
developers can use ASP.NET server controls to
program Web pages. Server controls are declared
within an .aspx file using custom tags or intrinsic
HTML tags that contain a runat="server" attributes
value. Intrinsic HTML tags are handled by one of the
controls in the System.Web.UI.HtmlControls
namespace. Any tag that doesn't explicitly map to one
of the controls is assigned the type of
System.Web.UI.HtmlControls.HtmlGenericContr
ol.
Server controls automatically maintain any
client-entered values between round trips to the
server. This control state is not stored on the server (it
is instead stored within an <input type="hidden">
form field that is round-tripped between requests).
Note also that no client-side script is required.
 40

In addition to supporting standard HTML input

controls, ASP.NET enables developers to utilize
richer custom controls on their pages. For example,
the following sample demonstrates how the
<asp:adrotator> control can be used to dynamically
display rotating ads on a page.
1. ASP.NET Web Forms provide an easy and
powerful way to build dynamic Web UI.
2. ASP.NET Web Forms pages can target any
browser client (there are no script library or cookie
requirements).
3. ASP.NET Web Forms pages provide syntax
compatibility with existing ASP pages.
4. ASP.NET server controls provide an easy way to
encapsulate common functionality.
5. ASP.NET ships with 45 built-in server controls.
Developers can also use controls built by third
parties.
 41

6. ASP.NET server controls can automatically

project both up level and down level HTML.
7. ASP.NET templates provide an easy way to
customize the look and feel of list server controls.
8. ASP.NET validation controls provide an easy
way to do declarative client or server data
validation.

4.5 C#.NET
 42

ADO.NET OVERVIEW:ADO.NET is an evolution

of the ADO data access model that directly
addresses user requirements for developing
scalable applications. It was designed
specifically for the web with scalability,
statelessness, and XML in mind. ADO.NET
uses some ADO objects, such as the
Connection and Command objects, and also
introduces new objects. Key new ADO.NET
objects include the DataSet, DataReader, and
DataAdapter.

The following sections will introduce you to some

objects that have evolved, and some that are new.
These objects are:

• Connections. For connection to and managing

transactions against a database.
 43

• Commands. For issuing SQL commands against

a database.
• DataReaders. For reading a forward-only
stream of data records from a SQL Server data
source.
• DataSets. For storing, Remoting and
programming against flat data, XML data and
relational data.
• DataAdapters. For pushing data into a DataSet,
and reconciling data against a database.

4.6 SQL SERVER

A database management, or DBMS, gives the user

access to their data and helps them transform the data
into information. Such database management systems
include dBase, paradox, IMS, SQL Server and SQL
 44

Server. These systems allow users to create, update

and extract information from their database.
A database is a structured collection of data.
Data refers to the characteristics of people, things and
events. SQL Server stores each data item in its own
fields. In SQL Server, the fields relating to a
particular person, thing or event are bundled together
to form a single complete unit of data, called a record
(it can also be referred to as row or an occurrence).
Each record is made up of a number of fields. No
two fields in a record can have the same field name.
During an SQL Server Database design project,
the analysis of your business needs identifies all the
fields or attributes of interest. If your business needs
change over time, you define any additional fields or
change the definition of existing fields.
 45

CHAPTER 5

SYSTEM DESIGN

INTRODUCTION

Software design sits at the technical kernel of the

software engineering process and is applied
regardless of the development paradigm and area of
application. Design is the first step in the
development phase for any engineered product or
system. The designer’s goal is to produce a model or
representation of an entity that will later be built.
Beginning, once system requirement have been
specified and analyzed, system design is the first of
 46

the three technical activities -design, code and test

that is required to build and verify software.

The importance can be stated with a single word

“Quality”. Design is the place where quality is
fostered in software development. Design provides us
with representations of software that can assess for
quality. Design is the only way that we can
accurately translate a customer’s view into a finished
software product or system. Software design serves
as a foundation for all the software engineering steps
that follow. Without a strong design we risk building
an unstable system – one that will be difficult to test,
one whose quality cannot be assessed until the last
stage.

During design, progressive refinement of data

structure, program structure, and procedural details
are developed reviewed and documented. System
 47

design can be viewed from either technical or project

management perspective. From the technical point of
view, design is comprised of four activities –
architectural design, data structure design, interface
design and procedural design.

CHAPTER 6

DATA FLOW DIAGRAMS

6.1. DFD OF INDIA YELLOW PAGES :

LEVEL-0
 48

Client
Front Page

Search Page

Login Page

Registration Page

Forget Page

Profile Page
ADMIN
Setting Page

Contact Us

About Us

Feedback

EMAIL SENDING

FIG 6.1 0- LEVEL DFD

LEVEL –1
 49

Client
Front Page

Search Page

Login Page

Registration Page

Forget Page

Profile Page

Contact Us
YELLOW
About Us DB

Feedback

FIG 6.2.1 1-LEVEL

 50

ADMIN
Front Page

Search Page

Login Page

Registration Page
YELLOWD
Forget Page B

Profile Page

Setting Page

Contact Us

About Us

Feedback

EMAIL SENDING

FIG 6.2.2 1-LEVEL

 51

LEVEL –2

1).Front Page

ADMIN Front Page

FIG 6.3.1 2-LEVEL

2).Search Page before Login

ADMIN Login
Login
Table

FIG 6.3.2 2-LEVEL

3).After Login
 52

ADMIN Categorie
Search
s
Customize
Search
Main
Table

FIG 6.3.3 2-LEVEL

4) Setting.aspx

ADMIN Categories

Main Table

Setting Login
Table
Forgot Table

Feedback
Table

FIG 6.3.4 2-LEVEL

 53

5) EmailSending.aspx

ADMIN Forgot
Email
Sending Table

FIG 6.3.5 2-LEVEL

6) Front Page

Client Front Page

FIG 6.3.6 2-LEVEL

 54

7)Search Page before Login

Client Login Main

Table
Create

Forgot

FIG 6.3.7 2-LEVEL

8) Search Page.aspx
 55

Client Categorie
Search
s
Customize
Search
Main
Table

FIG 6.3.8 2-LEVEL

9) ProfilePage.aspx

Client Login Table

Profile

FIG 6.3.9 2-LEVEL

10) FeedbackPage.aspx

Client Feedback
Feedback
Table

FIG 6.3.10 2-LEVEL

 56

11) AboutUsPage.aspx

Client
About us

FIG 6.3.11 2-LEVEL

12)Contactusage.aspx

Client
Contact Us

FIG 6.3.12 2-LEVEL

6.2. DATA DICTIONARY:

 57

After carefully understanding the requirements of

the client the the entire data storage
requirements are divided into tables. The below
tables are normalized to avoid any
anomalies during the course of data entry.

1.Category Table
 58

2.Feedback Table

3.Login Table:

4.Main Table:
 59

CHAPTER -7
SCREEN SHOTS
60
61
62
63
 64

CHAPTER -8

SYSTEM TESTING AND IMPLEMENTATION

8.1. INTRODUCTION

Software testing is a critical element of software

quality assurance and represents the ultimate review
of specification, design and coding. In fact, testing is
the one step in the software engineering process that
could be viewed as destructive rather than
constructive.

A strategy for software testing integrates

software test case design methods into a well-planned
series of steps that result in the successful
construction of software. Testing is the set of
activities that can be planned in advance and
conducted systematically. The underlying motivation
of program testing is to affirm software quality with
methods that can economically and effectively apply
 65

to both strategic to both large and small-scale

systems.

8.2. STRATEGIC APPROACH TO SOFTWARE

TESTING
The software engineering process can be viewed
as a spiral. Initially system engineering defines the
role of software and leads to software requirement
analysis where the information domain, functions,
behavior, performance, constraints and validation
criteria for software are established. Moving inward
along the spiral, we come to design and finally to
coding. To develop computer software we spiral in
along streamlines that decrease the level of
abstraction on each turn.

A strategy for software testing may also be

viewed in the context of the spiral. Unit testing
begins at the vertex of the spiral and concentrates on
 66

each unit of the software as implemented in source

code. Testing progress by moving outward along the
spiral to integration testing, where the focus is on the
design and the construction of the software
architecture. Talking another turn on outward on the
spiral we encounter validation testing where
requirements established as part of software
requirements analysis are validated against the
software that has been constructed. Finally we arrive
at system testing, where the software and other
system elements are tested as a whole.

UNIT TESTING

MODULE TESTING

Component Testing SUB-SYSTEM

TESING

SYSTEM TESTING
Integration Testing

ACCEPTANCE
TESTING
User Testing
 67

8.3. Unit Testing

Unit testing focuses verification effort on the smallest

unit of software design, the module. The unit testing
we have is white box oriented and some modules the
steps are conducted in parallel.

• WHITE BOX TESTING

• BASIC PATH TESTING
• CONDITIONAL TESTING
• DATA FLOW TESTING
 68

• LOOP TESTING
CHAPTER -9

SYSTEM SECURITY

SYSTEM SECURITY refers to the technical

innovations and procedures applied to the hardware
and operation systems to protect against deliberate or
accidental damage from a defined threat.

DATA SECURITY is the protection of data from

loss, disclosure, modification and destruction.

SYSTEM INTEGRITY refers to the power

functioning of hardware and programs, appropriate
physical security and safety against external threats
such as eavesdropping and wiretapping.
 69

PRIVACY defines the rights of the user or

organizations to determine what information they are
willing to share with or accept from others and how
the organization can be protected against unwelcome,
unfair or excessive dissemination of information
about it.

CONFIDENTIALITY is a special status given to

sensitive information in a database to minimize the
possible invasion of privacy. It is an attribute of
information that characterizes its need for protection.
 70

CHAPTER -10

CONCLUSION

It has been a great pleasure for me to work on

this exciting and challenging project. This project
proved good for me as it provided practical
knowledge of not only programming in ASP.NET
and C#.NET web based application and no some
extent Windows Application and SQL Server, but
also about all handling procedure related with
“YELLOW PAGES”. It also provides knowledge
about the latest technology used in developing web
enabled application and client server technology that
will be great demand in future. This will provide
better opportunities and guidance in future in
developing projects independently.
 71

 BENEFITS:

The project is identified by the merits of the system

offered to the user. The merits of this project are as
follows: -

• It’s a web-enabled project.

• This project offers user to enter the data through
simple and interactive forms. This is very helpful
for the client to enter the desired information
through so much simplicity
• Data storage and retrieval will become faster and
easier to maintain because data is stored in a
systematic manner and in a single database.
• Decision making process would be greatly
enhanced because of faster processing of
information since data collection from information
available on computer takes much less time then
manual system.
 72

• Allocating of sample results becomes much faster

because at a time the user can see the records of
last years.
• Easier and faster data transfer through latest
technology associated with the computer and
communication.
• Through these features it will increase the
efficiency, accuracy and transparency,

 LIMITATIONS:

• The size of the database increases day-by-day,

increasing the load on the database back up and
data maintenance activity.
• Training for simple computer operations is
necessary for the users working on the system.

FUTURE IMPROVEMENT
 73

• This System being web-based and an

undertaking of Cyber Security Division, needs to
be thoroughly tested to find out any security
gaps.

• A console for the data centre may be made

available to allow the personnel to monitor on
the sites which were cleared for hosting during a
particular period.

• Moreover, it is just a beginning; further the

system may be utilized in various other types of
auditing operation viz. Network auditing or
similar process/workflow based applications...

• One extension can be to enable the social

networking by using the profile as the basis of
networks.
 74

BIBLIOGRAPHY

BOOKS:

• Wrox Beginners’ ASP.Net 3.5 by Peter Norton

• Wrox Professional ASP.Net 3.5

WEBSITES:
 75

• www.yellowpages.com

• www.script.com

• www.msdn.microsoft.com