ACKNOWLEDGEMENT

First of all, it is a proud privilege to express my gratitude to our principal

DR.T.RAVICHANDRAN,M.sc.,M.Phil.,Ph.D. Jesu arts and science college,
Alangudi for giving a golden opportunity to undertake the project work.

My hearty thanks to Prof.P.THENMOZHI,M.sc.,M.Phil Head of the

department of computer science, jesu arts and science college, for his valuable
support throughout the project.

I am greatly indebted to express my deep sense gratitude to

M.PANDIDURAI,MCA.,M.Phil.,B.Ed project guide for his overwhelming
support and valuable guidance for successful completion of my project.

At the outset we wish to convey our sincere thanks to staff members of

Computer Science Department and all our friends who guided in our guided our
endeavor.

1.VIJAYAKUMAR.M

2.VINITHA.M

3.VISHNU.S

4.YOGESWARI.R
S.NO TITLE PAGE NO

ABSTRACT
1 INTRODUCTION

2 SOFTWARE REQUIREMENT

SPECIFICATION

2.1
Hardware Requirements

2.2 Software Requirements

2.3 Functional Requirements

3 SYSTEM ANALYSIS
3.1 Introduction
3.2 Analysis Model
3.3 Study of the system

3.4 Problem in existing system

3.5 Proposed system

3.6 Feasibility study

4
SYSTEM ANALYSIS
4.1
ER Diagram
4.2
Data flow diagram
4.3
UML diagram
4.4
Class diagram
5
SYSTEM TESTING
5.1
Unit Testing
 5.2
White Box Testing
5.3
Basic Path Testing
5.4
Conditional Testing
5.5
Data Flow Testing
5.6
Loop Testing
6
IMPLEMENTATION

6.1 Source Code

6.2
Screen Layout
7
FUTURE ENHANCEMENT
8
CONCLUSION

BIBLIOGRAPHY
 ABSTRACT
Local bodies like municipalities need collect different kind of taxes from the
citizens. Every citizen need to pay Water Bills and Electricity Bills to the particular
authorities. Actually a citizen want to pay his municipal tax means he should go to
municipal office and collect the necessary bill, pay there only. Same as water and
electricity bills. This is not an easy job to get all these tax information in different
authorities now days.

For that purpose we are developing this application, which can collect the tax
information from different authorities based on the house no’s and owner name by
using Web Services and stores the data in our own database. For getting the
information regarding taxes citizens need to register first. The bill are calculating
on different modes like annual, half yearly, quarterly etc...

By using the user id and password citizens can log into the system and collect
the necessary information from the home page. For this every user need to provide
his house no and owner name. By clicking on the search button they will get their
own

 House Details
 Electricity Bill Details
 Water Bill Details
 Municipality Bill Details
 Pending Bills
 Dues
Web services play vital role here. Why because this system get the information
from other sources. A web service is only capable to get the information from other
sources.
 1. INTRODUCTION

Local bodies like municipalities need collect different kind of taxes from the
citizens. Every citizen need to pay Water Bills and Electricity Bills to the
particular authorities. Actually a citizen want to pay his municipal tax means he
should go to municipal office and collect the necessary bill, pay there only.
Same as water and electricity bills. This is not an easy job to get all these tax
information in different authorities now days.

For that purpose we are developing this application, which can collect the tax
information from different authorities based on the house no’s and owner name
by using Web Services and stores the data in our own database. For getting
the information regarding taxes citizens need to register first. The bill are
calculating on different modes like annual, half yearly, quarterly etc...

2. SOFTWARE REQUIREMENT SPECIFICATION

2.1 Hardware Requirements

 PIV 2.8 GHz Processor and Above

 RAM 512MB and Above
  HDD 40 GB Hard Disk Space and Above

2.2 Software Requirements

 WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)

 Visual Studio .Net 2008 Enterprise Edition
 Internet Information Server 5.0 (IIS)
 Visual Studio .Net Framework (Minimal for Deployment) version 3.5
 SQL Server 2005 Enterprise Edition

2.3 Functional Requirements

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the

results of processing to users. They are also used to provides a permanent copy of
the results for later consultation. The various types of outputs in general are:

 External Outputs, whose destination is outside the organization.

 Internal Outputs whose destination is within organization and they are the
 User’s main interface with the computer.
 Operational outputs whose use is purely within the computer department.
 Interface outputs, which involve the user in communicating directly.
OUTPUT DEFINITION

The outputs should be defined in terms of the following points:

 Type of the output

 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
 Volume of the output
 Sequence of the output
It is not always desirable to print or display data as it is held on a computer. It
should be decided as which form of the output is the most suitable.
For Example

 Will decimal points need to be inserted

 Should leading zeros be suppressed.
Output Media:

In the next stage it is to be decided that which medium is the most

appropriate for the output. The main considerations when deciding about the output
media are:

 The suitability for the device to the particular application.

 The need for a hard copy.
 The response time required.
 The location of the users
 The software and hardware available.
Keeping in view the above description the project is to have outputs mainly coming
under the category of internal outputs. The main outputs desired according to the
requirement specification are:

The outputs were needed to be generated as a hot copy and as well as queries to
be viewed on the screen. Keeping in view these outputs, the format for the output
is taken from the outputs, which are currently being obtained after manual
processing. The standard printer is to be used as output media for hard copies.

INPUT DESIGN

Input design is a part of overall system design. The main objective during the
input design is as given below:

 To produce a cost-effective method of input.

 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.
INPUT STAGES:

The main input stages can be listed as below:

 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation
 Data correction

INPUT TYPES:

It is necessary to determine the various types of inputs. Inputs can be categorized

as follows:

 External inputs, which are prime inputs for the system.

 Internal inputs, which are user communications with the system.
 Operational, which are computer department’s communications to the system?
 Interactive, which are inputs entered during a dialogue.
INPUT MEDIA:

At this stage choice has to be made about the input media. To conclude
about the input media consideration has to be given to;

 Type of input
 Flexibility of format
 Speed
 Accuracy
 Verification methods
 Rejection rates
 Ease of correction
 Storage and handling requirements
 Security
 Easy to use
 Portability
Keeping in view the above description of the input types and input media, it
can be said that most of the inputs are of the form of internal and interactive. As
Input data is to be the directly keyed in by the user, the keyboard can be
considered to be the most suitable input device.

ERROR AVOIDANCE

At this stage care is to be taken to ensure that input data remains accurate
form the stage at which it is recorded up to the stage in which the data is accepted
by the system. This can be achieved only by means of careful control each time the
data is handled.

ERROR DETECTION

Even though every effort is make to avoid the occurrence of errors, still a
small proportion of errors is always likely to occur, these types of errors can be
discovered by using validations to check the input data.

DATA VALIDATION

Procedures are designed to detect errors in data at a lower level of detail.

Data validations have been included in the system in almost every area where there
is a possibility for the user to commit errors. The system will not accept invalid
data. Whenever an invalid data is keyed in, the system immediately prompts the
user and the user has to again key in the data and the system will accept the data
only if the data is correct. Validations have been included where necessary.

The system is designed to be a user friendly one. In other words the system
has been designed to communicate effectively with the user. The system has been
designed with popup menus.

USER INTERFACE DESIGN

It is essential to consult the system users and discuss their needs while
designing the user interface:

USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:

1. User initiated interface the user is in charge, controlling the progress of the
user/computer dialogue. In the computer-initiated interface, the computer
selects the next stage in the interaction.
 2. Computer initiated interfaces
In the computer initiated interfaces the computer guides the progress of the
user/computer dialogue. Information is displayed and the user response of the
computer takes action or displays further information.

USER_INITIATED INTERGFACES

User initiated interfaces fall into tow approximate classes:

1. Command driven interfaces: In this type of interface the user inputs commands
or queries which are interpreted by the computer.
2. Forms oriented interface: The user calls up an image of the form to his/her
screen and fills in the form. The forms oriented interface is chosen because it is
the best choice.

COMPUTER-INITIATED INTERFACES

The following computer – initiated interfaces were used:

1. The menu system for the user is presented with a list of alternatives and the
user chooses one; of alternatives.
2. Questions – answer type dialog system where the computer asks question and
takes action based on the basis of the users reply.
Right from the start the system is going to be menu driven, the opening
menu displays the available options. Choosing one option gives another popup
menu with more options. In this way every option leads the users to data entry
form where the user can key in the data.

ERROR MESSAGE DESIGN:

The design of error messages is an important part of the user interface

design. As user is bound to commit some errors or other while designing a system
the system should be designed to be helpful by providing the user with information
regarding the error he/she has committed.
 This application must be able to produce output at different modules for
different inputs.

3. SYSTEM ANALYSIS

3.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 and requires creative thinking and understanding of
existing running system is also difficult, improper understanding of present system
can lead diversion from solution.
3.2 Analysis Model
SDLC METHDOLOGIES

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.

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 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.
  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:

 Fig 1.0-Spiral Model

3.3 study of the system

 In the flexibility of the uses the interface has been developed a graphics
concept in mind, associated through a browser interface. The GUI’S at the top level
have been categorized as

1. Administrative user interface

2. The operational or generic user interface

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 Data updating
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:

The Modules involved are

Module Description

1. Administrator

2. Citizen’s

3. Web Services

4. Citizen’s Bill Information

5. Search

6. Reports

7. Authentication

Administration
 Administration is the main person of this system. He can have all the
privileges to do anything in this system. Admin can get the information regarding
citizen’s water bills, electric bills, and municipal taxes from various sources. For
that administrator need to send a request for that particular authority throw web
services.

Citizens

People who are living in that municipality area are called as citizens. Citizens
need to pay water bill, electricity bill, property tax for a certain of intervals. By
using this system interface citizen’s know their different bill amounts, pending bills,
due dates etc.

Web Services

Citizen Bill Information

The system interface is going to show the Bill information of different

authorities. The bills mainly going to these types

 Water Bills

 Electricity Bills

 Property Taxes

These interface also shows the

 Pending Bills

 Penalties

Due Dates

3.4 Problem in existing system

The existing system is a manual system. Here the employees needs to save the
information in the form of excel sheets or Disk Drives. There is no sharing is
possible if the data is in the form of paper or Disk drives. The manual system gives
us very less security for saving data; some data may be lost due to is management.
It’s a limited system and fewer users friendly. Searching of particular information is
very critical it takes lot of time. Gathering information of different sources is not an
easy job, data will be mismanaged. Calculating different bills manually going to be
as a process of mistake. There is no interface to provide various bills in the existing
system. In the existing system citizen get the bills information manually, in various
authorities like water board, electricity department, property tax department etc.

SOLUTION OF THESE PROBLEMS

The development of this new system contains the following activities, which try
to automate the entire process keeping in the view of database integration
approach. User Friendliness is provided in the application with various controls
provided by system Rich User Interface. The system makes the overall project
management much easier and flexible. It can be accessed over the Intranet. The
employee information can be stored in centralized database which can be
maintained by the system. This can give the good security for user information
because data is not in client machine. Authentication is provided for this application
only registered Users can access. There is no risk of data management at any level
while the project development is under process. The automated system will provide
to the employees for reliable services. The proposed system using web services, a
web service can get the information from other sources also. There no burden of
calculating water, electric, house tax bills in this system, by sending a request to
the particular authority via web service we can get all the information regarding
these issues.

3.5 Proposed system

To debug the existing system, remove procedures those cause data

redundancy, make navigational sequence proper. To provide information about
users on different level and also to reflect the current work status depending on
organization. To build strong password mechanism.

NEED FOR COMPUTERIZATION

We all know the importance of computerization. The world is moving ahead

at lightning speed and everyone is running short of time. One always wants to get
the information and perform a task he/she/they desire(s) within a short period of
time and too with amount of efficiency and accuracy. The application areas for the
computerization have been selected on the basis of following factors:

 Minimizing the manual records kept at different locations.

 There will be more data integrity.
 Facilitating desired information display, very quickly, by retrieving information
from users.
 Facilitating various statistical information which helps in decision-making?
 To reduce manual efforts in activities that involved repetitive work.
Updating and deletion of such a huge amount of data will become easier.

FUNCTIONAL FEATURES OF THE MODEL

As far as the project is developed the functionality is simple, the objective of

the proposal is to strengthen the functioning of Audit Status Monitoring and make
them effective and better. The entire scope has been classified into five streams
knows as Coordinator Level, management Level, Auditor Level, User Level and State
Web Coordinator Level. The proposed software will cover the information needs with
respect to each request of the user group viz. accepting the request, providing
vulnerability document report and the current status of the audit.

3.6 Feasibility study

Preliminary investigation examine project feasibility, the likelihood the

system will be useful to the organization. The main objective of the feasibility 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
 Operational Feasibility
 Economical Feasibility

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?
 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 users in their
various capacities or roles. Permission to the users would be granted based on the
roles specified. Therefore, it provides the technical guarantee of accuracy,
reliability and security. The software and hard requirements for the development of
this project are not many and are already available in-house at NIC or are available
as free as open source. The work for the project is done with the current equipment
and existing software technology. Necessary bandwidth exists for providing a fast
feedback to the users irrespective of the number of users using the system.

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

ECONOMICAL 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, There is nominal expenditure
and economical feasibility for certain.

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

Normalization
It is a process of converting a relation to a standard form. The process is
used to handle the problems that can arise due to data redundancy i.e. repetition of
data in the database, maintain data integrity as well as handling problems that can
arise due to insertion, updating, deletion anomalies.

Decomposing is the process of splitting relations into multiple relations to

eliminate anomalies and maintain anomalies and maintain data integrity. To do this
we use normal forms or rules for structuring relation.

Insertion anomaly: Inability to add data to the database due to absence of other
data.
Deletion anomaly: Unintended loss of data due to deletion of other data.

Update anomaly: Data inconsistency resulting from data redundancy and partial
update

Normal Forms: These are the rules for structuring relations that eliminate
anomalies.

FIRST NORMAL FORM:

A relation is said to be in first normal form if the values in the relation are
atomic for every attribute in the relation. By this we mean simply that no attribute
value can be a set of values or, as it is sometimes expressed, a repeating group.

SECOND NORMAL FORM:

A relation is said to be in second Normal form is it is in first normal form and

it should satisfy any one of the following rules.

1) Primary key is a not a composite primary key

2) No non key attributes are present
3) Every non key attribute is fully functionally dependent on full set of primary
key.

THIRD NORMAL FORM:

A relation is said to be in third normal form if their exits no transitive

dependencies.

Transitive Dependency: If two non key attributes depend on each other as well
as on the primary key then they are said to be transitively dependent.

The above normalization principles were applied to decompose the data in

multiple tables thereby making the data to be maintained in a consistent state.

4.1 E-R Diagrams

 The relation upon the system is structure through a conceptual

ER-Diagram, which not only specifics the existential entities but also the
 standard relations through which the system exists and the cardinalities that are
necessary for the system state to continue.

 The entity Relationship Diagram (ERD) depicts the relationship between the data
objects. The ERD is the notation that is used to conduct the date modeling
activity the attributes of each data object noted is the ERD can be described
resign a data object descriptions.

 The set of primary components that are identified by the ERD are

 Data object
 Relationships
 Attributes
 Various types of indicators.
The primary purpose of the ERD is to represent data objects and their relationships.
Geo Spatial Info Tech Solutions E-R
4.2 Data flow diagrams

A data flow diagram is graphical tool used to describe and analyze

movement of data through a system. These are the central tool and the basis from
which the other components are developed. The transformation of data from input
to output, through processed, may be described logically and independently of
physical components associated with the system. These are known as the logical
data flow diagrams. The physical data flow diagrams show the actual implements
and movement of data between people, departments and workstations. A full
description of a system actually consists of a set of data flow diagrams. Using two
familiar notations Yourdon, Gane and Sarson notation develops the data flow
diagrams. Each component in a DFD is labeled with a descriptive name. Process is
further identified with a number that will be used for identification purpose. The
development of DFD’S is done in several levels. Each process in lower level
diagrams can be broken down into a more detailed DFD in the next level. The lop-
level diagram is often called context diagram. It consists a single process bit, which
plays vital role in studying the current system. The process in the context level
diagram is exploded into other process at the first level DFD.

The idea behind the explosion of a process into more process is that
understanding at one level of detail is exploded into greater detail at the next level.
This is done until further explosion is necessary and an adequate amount of detail is
described for analyst to understand the process.

Larry Constantine first developed the DFD as a way of expressing system

requirements in a graphical from, this lead to the modular design.

A DFD is also known as a “bubble Chart” has the purpose of clarifying system
requirements and identifying major transformations that will become programs in
system design. So it is the starting point of the design to the lowest level of detail.
A DFD consists of a series of bubbles joined by data flows in the system.

DFD SYMBOLS:

In the DFD, there are four symbols

1. A square defines a source(originator) or destination of system data

2. An arrow identifies data flow. It is the pipeline through which the information
flows
3. A circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of data

Process that transforms data flow.

Source or Destination of data

Data flow

Data Store

CONSTRUCTING A DFD:

Several rules of thumb are used in drawing DFD’S:

1. Process should be named and numbered for an easy reference. Each name
should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow back to
the source. One way to indicate this is to draw long flow line back to a source.
An alternative way is to repeat the source symbol as a destination. Since it is
used more than once in the DFD it is marked with a short diagonal.
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters. Process
and dataflow names have the first letter of each work capitalized.
A DFD typically shows the minimum contents of data store. Each data store
should contain all the data elements that flow in and out.

Questionnaires should contain all the data elements that flow in and out.
Missing interfaces redundancies and like is then accounted for often through
interviews.

SAILENT FEATURES OF DFD’S

1. The DFD shows flow of data, not of control loops and decision are controlled
considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process whether the
dataflow take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.

TYPES OF DATA FLOW DIAGRAMS

1. Current Physical
2. Current Logical
3. New Logical
4. New Physical

CURRENT PHYSICAL:

In Current Physical DFD process label include the name of people or their
positions or the names of computer systems that might provide some of the overall
system-processing label includes an identification of the technology used to process
the data. Similarly data flows and data stores are often labels with the names of
the actual physical media on which data are stored such as file folders, computer
files, business forms or computer tapes.

CURRENT LOGICAL:
 The physical aspects at the system are removed as much as possible so that
the current system is reduced to its essence to the data and the processors that
transforms them regardless of actual physical form.

NEW LOGICAL:

This is exactly like a current logical model if the user were completely happy
with the user were completely happy with the functionality of the current system
but had problems with how it was implemented typically through the new logical
model will differ from current logical model while having additional functions,
absolute function removal and inefficient flows recognized.

NEW PHYSICAL:

The new physical represents only the physical implementation of the new
system.

RULES GOVERNING THE DFD’S

PROCESS

1) No process can have only outputs.

2) No process can have only inputs. If an object has only inputs than it must be a
sink.
3) A process has a verb phrase label.

DATA STORE

1) Data cannot move directly from one data store to another data store, a process
must move data.
2) Data cannot move directly from an outside source to a data store, a process,
which receives, must move data from the source and place the data into data
store
3) A data store has a noun phrase label.
SOURCE OR SINK

The origin and /or destination of data.

1) Data cannot move direly from a source to sink it must be moved by a process
2) A source and /or sink has a noun phrase land

DATA FLOW

1) A Data Flow has only one direction of flow between symbols. It may flow in both
directions between a process and a data store to show a read before an update.
The later is usually indicated however by two separate arrows since these
happen at different type.
2) A join in DFD means that exactly the same data comes from any of two or more
different processes data store or sink to a common location.
3) A data flow cannot go directly back to the same process it leads. There must be
at least one other process that handles the data flow produce some other data
flow returns the original data into the beginning process.
4) A Data flow to a data store means update (delete or change).
5) A data Flow from a data store means retrieve or use.
A data flow has a noun phrase label more than one data flow noun phrase can
appear on a single arrow as long as all of the flows on the same arrow move
together as one package.

Geospatial InfoTech Solutions:

DFD Diagrams:

Context 0th Level Diagram:

Login DFD Diagram:

Admin Details Data Flow:

1st level DFD:
2nd Level DFD
User Details Data Flow
1st level DFD

2nd level DFD

 Data dictionary

After carefully understanding the requirements of the client the

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

Use-Case Diagrams:

UNIFIED MODELING LANGUAGE DIAGRAMS

 The unified modeling language allows the software engineer to express an analysis model using the
modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

 A UML system is represented using five different views that describe the system from distinctly
different perspective. Each view is defined by a set of diagram, which is as follows.

 User Model View

i. This view represents the system from the users perspective.

ii. The analysis representation describes a usage scenario from the end-users perspective.
Structural model view

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

 This model view models the static structures.

Behavioral Model View

 It represents the dynamic of behavioral as parts of the system, depicting the interactions of collection
between various structural elements described in the user model and structural model view.

Implementation Model View

 In this the structural and behavioral as parts of the system are represented as they are to be built.

Environmental Model View

In this the structural and behavioral aspects of the environment in which the system is to be implemented
are represented.

UML is specifically constructed through two different domains they are

  UML Analysis modeling, which focuses on the user model and structural model views of the
system.

 UML design modeling, which focuses on the behavioral modeling, implementation modeling and
environmental model views.

Use case Diagrams represent the functionality of the system from a user’s point of
view. Use cases are used during requirements elicitation and analysis to represent
the functionality of the system. Use cases focus on the behavior of the system from
external point of view.

Actors are external entities that interact with the system. Examples of actors
include users like administrator, bank customer …etc., or another system like
central database.
Over view Use Case Diagram:

Admin Use Case Diagram:

User Use Case Diagram:

Activity Diagrams:

An Activity diagram is a variation of a special case of a state machine, in which the

states are activities representing the performance of operations and the transitions are
triggered by the completion of the operations. The purpose of Activity diagram is to provide
a view of flows and what is going on inside a use case or among several classes.

Activities:

An activity represents the performance of some behavior in the workflow.

Transitions:

Transitions are used to show the passing of the flow of control from activity to activity.
They are typically triggered by the completion of the behavior in the originating activity.

Decision Points:

When modeling the workflow of a system it is often necessary to show where the flow
of control branches based on a decision point. The transitions from a decision point contain a
guard condition, which is used to determine which path from the decision point is taken.

Synchronization Bars:
 In a workflow there are typically some activities that may be done in parallel. A
synchronization bar allows you to specify what activities may be done concurrently.
Synchronization bars are also used to show joins in the workflow.

Swim lanes:

Swim lanes may be used to partition an activity diagram.

Initial and Final Activities:

There are special symbols that are used to show the starting and final activities in a
workflow. The starting activity is shown using a solid filled circle and the final activities are
shown using a bull's eye.

Registration Diagram:
Login Activity Diagram:
Admin Activity Diagram
User Activity Diagram:
Geospatial Info Solutions:
Admin Login Sequence Diagram

Admin LoginPage BL:Cls_Login() DAL:SqlHelper() Database

1 : Admin
Login

2 : ValidateUser()

3 : ExecuteNonQuery()

4 : ExecuteComand()

5 : Return QueryResult()

6: ResponseForValidateUser()

Sequence Diagram for add municipal taxes

 Admin MunicipalTaxes BAL : clsMunicipalTax DAL : clsSqlHelper Database

1 : add Taxes()

2 : InsertTaxData()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : return Response()

6 : Show Msg()

Sequence diagram for Manage Local Data

Admin Add Streets/Area/Location BAL : cls_Common DAL : clsSqlHelper Database

1 : add S/A/L/Info()

2 : InsertTaxData()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : return Response()

6 : Show Msg()

Sequence Diagram for Building Approvals

 Admin Add BuildingApproval BAL : clsBuildingApprovals DAL : clsSqlHelper Database

1 : BApprovals()

2 : InsertData()

3 : ExecuteNonQuery()

4 : ExecuteNonQuery()

5 : return Response()

6 : Show Msg()

Sequence Diagram for Users Municipal Bills

 Users MuicipalTaxes BAL : clsUsers WebService Database

1 : getBills()

2 : GetMunicipal_tax()

3 : WebMethodGetMBills()

4 : ExecuteNonQuery()

5 : return Response()

6 : Show Data()

Sequence Diagram for Users Electricity Bills

 Users ElectricalBill BAL : clsUsers WebService Database

1 : getBills()

2 : GetElectricalBill()

3 : WebMethodGetEBills()

4 : ExecuteNonQuery()

5 : return Response()

6 : Show Data()

Geospatial Info Solutions:

Admin Login collaboration Diagram

DataAcessLayer
6 : Returns value()
4 : ExecuteCommand()

Database 5 : CommandResponse()
3 : ExecuteCommand
Business Object

7 : ResponseData()

Admin 2 : ValidateUser()
1 : GetAdminHome()

LoginPage

Collaboration Diagram for add municipal taxes

DAL : clsSqlHelper

4 : ExecuteNonQuery()
3 : ExecuteNonQuery()
Database
5 : return Response()

BAL : clsMunicipalTax

2 : InsertTaxData() 6 : Show Msg()

1 : add Taxes()
Admin MunicipalTaxes

Collaboration Diagram for Add Local information

 Database

4 : ExecuteNonQuery()
5 : return Response()
DAL : clsSqlHelper

3 : ExecuteNonQuery()

BAL : cls_Common 6 : Show Msg()

2 : InsertTaxData()

Add Streets/Area/Location
1 : add S/A/L/Info()

Admin

Collaboration Diagram for Building Approvals

5 : return Response()
BAL : clsBuildingApprovals Database

6 : Show Msg()
3 : ExecuteNonQuery()
4 : ExecuteNonQuery()
2 : InsertData()

1 : BApprovals() DAL : clsSqlHelper

Admin Add BuildingApproval

Collaboration Diagram for Users Municipal Bills

 Database

4 : ExecuteNonQuery() 5 : return Response()

3 : WebMethodGetMBills()
BAL : clsUsers
WebService

2 : GetMunicipal_tax()
6 : Show Data()

1 : getBills()
Users MuicipalTaxes

4.4 Class Diagram

 5. SYSTEM TESTING
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 to both
strategic to both large and small-scale systems.

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

5.2 white box testing

This type of testing ensures that

 All independent paths have been exercised at least once

 All logical decisions have been exercised on their true and false sides
 All loops are executed at their boundaries and within their operational bounds
 All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we
have created independently to verify that Data flow is correct, All conditions are
exercised to check their validity, All loops are executed on their boundaries.

5.3 Basic path testing

Established technique of flow graph with Cyclomatic complexity was used to derive
test cases for all the functions. The main steps in deriving test cases were:

Use the design of the code and draw correspondent flow graph.
Determine the Cyclomatic complexity of resultant flow graph, using formula:

V(G)=E-N+2 or

V(G)=P+1 or

V(G)=Number Of Regions

Where V(G) is Cyclomatic complexity,

E is the number of edges,

N is the number of flow graph nodes,

P is the number of predicate nodes.

Determine the basis of set of linearly independent paths.

5.4 Conditional testing

In this part of the testing each of the conditions were tested to both true and false
aspects. And all the resulting paths were tested. So that each path that may be
generate on particular condition is traced to uncover any possible errors.

5.5 Data flow testing

This type of testing selects the path of the program according to the location of
definition and use of variables. This kind of testing was used only when some local
variable were declared. The definition-use chain method was used in this type of
testing. These were particularly useful in nested statements.

5.6 Loop testing

In this type of testing all the loops are tested to all the limits possible. The
following exercise was adopted for all loops:

All the loops were tested at their limits, just above them and just below them.

All the loops were skipped at least once.

For nested loops test the inner most loop first and then work outwards.

For concatenated loops the values of dependent loops were set with the help of
connected loop.
 Unstructured loops were resolved into nested loops or concatenated loops and
tested as above.

Each unit has been separately tested by the development team itself and all
the input have been validated.

IMPLEMENTATION

Source Code

using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;

public partial class SubAdmin_frmBuildingApprovalCategoryUsagaMaster :

System.Web.UI.Page
{
Cls_BuildingApprovalCategoryusageMaster objcategoryusagemaster = new
Cls_BuildingApprovalCategoryusageMaster();
protected void Page_Load(object sender, EventArgs e)
{
try
{
if (!IsPostBack)
{
ShowBuildingApprno();
ShowCategoryUsagemaster();
ddlFloorNo.Items.Insert(0, "--SelectOne--");
}
}
catch (Exception ex)
 {

lblError.Text = ex.Message;
}
}
protected void btnAdd_Click(object sender, EventArgs e)
{
try
{
objcategoryusagemaster.BuildingApprovalNo =
Convert.ToInt32(ddlBuildingApprno.SelectedValue);
objcategoryusagemaster.CategoryusagemasterId =
Convert.ToInt32(ddlCategoryMasterId.SelectedValue);

objcategoryusagemaster.Floorid=Convert.ToInt32(ddlFloorNo.SelectedValue);
int
i=objcategoryusagemaster.InsertBuildingApprovalCategoryUsageMaster();
mainpanel.Enabled = false;
System.Threading.Thread.Sleep(2000);
mainpanel.Enabled = true;

if(i>0)
{
lblError.Text="Sucessfully Added";
Cleardata();
}
else
{
lblError.Text="Not Added";
}

}
catch (Exception ex)
{

lblError.Text = ex.Message;
}
}
protected void btnClear_Click(object sender, EventArgs e)
{
Cleardata();
lblError.Text = "";
}
public void ShowCategoryUsagemaster()
{
try
{
DataSet ds = objcategoryusagemaster.ShowCategoryUsageMasterId();
if (ds.Tables[0].Rows.Count != 0)
{
ddlCategoryMasterId.DataSource = ds.Tables[0];
ddlCategoryMasterId.DataTextField = "CategoryusageName";
ddlCategoryMasterId.DataValueField = "CategoryusageMasterId";
ddlCategoryMasterId.DataBind();
ddlCategoryMasterId.Items.Insert(0, "--SelectOne--");
}

}
 catch (Exception ex)
{

lblError.Text = ex.Message;
}
}
public void Cleardata()
{
if (ddlCategoryMasterId.SelectedIndex != 0)
ddlCategoryMasterId.SelectedIndex = 0;
if (ddlBuildingApprno.SelectedIndex != 0)
ddlBuildingApprno.SelectedIndex = 0;
if (ddlFloorNo.SelectedIndex != 0)
ddlFloorNo.SelectedIndex = 0;
}
public void ShowBuildingApprno()
{

try
{
Cls_Buildingfloormaster objbuildingfloorMaster = new
Cls_Buildingfloormaster();
DataSet ds = objbuildingfloorMaster.ShowBuildingApprno();
if (ds.Tables[0].Rows.Count != 0)
{
ddlBuildingApprno.DataSource = ds.Tables[0];
ddlBuildingApprno.DataTextField = "BuildingApprNo";
ddlBuildingApprno.DataValueField = "BuildingApprNo";
ddlBuildingApprno.DataBind();
}
ddlBuildingApprno.Items.Insert(0, "--SelectOne--");
}
catch (Exception ex)
{

lblError.Text = ex.Message;
}
}
protected void ddlBuildingApprno_SelectedIndexChanged(object sender,
EventArgs e)
{
try
{
if (ddlBuildingApprno.SelectedIndex != 0)
{
Cls_Buildingfloormaster objbuildingfloorMaster = new
Cls_Buildingfloormaster();
DataSet ds =
objbuildingfloorMaster.ShowFloorIDSelectApprovalCategory(Convert.ToInt32(ddlBuild
ingApprno.SelectedValue));
if (ds.Tables[0].Rows.Count != 0)
{
ddlFloorNo.DataSource = ds.Tables[0];
ddlFloorNo.DataTextField = "FloorName";
ddlFloorNo.DataValueField = "FloorId";
ddlFloorNo.DataBind();
ddlFloorNo.Items.Insert(0, "--SelectOne--");
}
 }
else
{
ddlFloorNo.Items.Clear();
ddlFloorNo.Items.Insert(0, "--SelectOne--");
}
}
catch (Exception ex)
{

lblError.Text = ex.Message;
}
}
}

Screen Layout
FUTURE ENHANCEMENT
  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...

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 andC#.NET web based application and no some
extent Windows Application and SQL Server, but also about all handling procedure
related with “Geo Spatial Info Tech Solutions”. 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.
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.
 The user is mainly more concerned about the validity of the data, whatever he is
entering. There are checks on every stages of any new creation, data entry or
updation so that the user cannot enter the invalid data, which can create
problems at later date.
 Sometimes the user finds in the later stages of using project that he needs to
update some of the information that he entered earlier. There are options for
him by which he can update the records. Moreover there is restriction for his that
he cannot change the primary data field. This keeps the validity of the data to
longer extent.
 User is provided the option of monitoring the records he entered earlier. He can
see the desired records with the variety of options provided by him.
 From every part of the project the user is provided with the links through
framing so that he can go from one option of the project to other as per the
requirement. This is bound to be simple and very friendly as per the user is
concerned. That is, we can sat that the project is user friendly which is one of
the primary concerns of any good project.
 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.
 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.

BIBLIOGRAPHY

 FOR .NET INSTALLATION

 www.support.mircosoft.com

 FOR DEPLOYMENT AND PACKING ON SERVER

www.developer.com

www.15seconds.com

 FOR SQL
www.msdn.microsoft.com

 FOR ASP.NET
Asp.Net 3.5 Unleashed
www.msdn.microsoft.com/net/quickstart/aspplus/
default.com

www.asp.net

www.fmexpense.com/quickstart/aspplus/default.com

www.asptoday.com

www.aspfree.com

www.4guysfromrolla.com/index.aspx

 Software Engineering (Roger’s Pressman)