Project Report 2013e-Panchayat

Project Report 2013 e-
Panchayat
INTRODUCTION
1
Panchayat
1.1 PROJECT OVERVIEW
The main idea of 'e-panchayat' is to implement a software application

for helping citizens to utilize and apply for schemes,tenders and certificates through an
online application. This application will be installed in each panchayats all over the
country, using this system people can check details of each scheme and apply for a scheme
which is suitable for them using online application form. Also they can participate in
tenders that conducted in each panchayat for various purposes. And also people can apply
for various certificates that has been provided by panchayat.
The 'e-panchayat' is mainly concentrated in giving out the various schemes

to the people at right time and help's them to gain benefit from it. Using existing system
there is gap between citizens and officials and government schemes. There are a lot of
schemes which are introduced by government but they are not used effectively by citizens.
In order to solve this problem I am introducing an online system which will make work
simpler and efficient. It is a bird's eye view of the Government schemes. Citizens need to
apply for the scheme through online which the help of a government officials. Application
processing information will be updated on this application. This system will save the time
for citizens and government.
This system has very good GUI so that a novice user did not feel any
operational difficulties. This system mainly concentrated in designing various reports
requested by the users as well as higher authorities such as Scheme wise details report,
Panchayat wise details report, User wise report etc.
2
Panchayat
SYSTEM CONFIGURATION
3
Panchayat
2.1 HARDWARE SPECIFICATION
Processor : Intel(R) Core 2 Duo
Processor speed : E4600 @ 2.40GHz
: 80GB
Hard Disk
: 1GB
RAM
: Wipro USB Keyboard
Keyboard
: Logitech USB Mouse

Mouse
: 15.6 Color LCD monitor
Monitor
2.2 SOFTWARE SPECIFICATION
Operating System : Microsoft Windows XP Professional, Service Pack 2
Front End : Microsoft Visual Studio 2008
Back End : SQL Server 2005
Web Server : IIS
Web application tools: HTML
Scripting language : Java Script
4
SYSTEM ANALYSIS
5
Project Report 2013 e-Panchayat
3.1 PRELIMINARY INVESTIGATION

The first stage of any project, sometimes called the preliminary assessment is a brief
investigation of the system under consideration. System study and analysis deals with the
study of the current system. This is the critical process of information development. It can
be defined as problem solving which consists of four phases that can be successfully
completed by applying appropriate skill and carefully addressing each dimension of the
information system.
The purpose of preliminary study phase is to determine the initial feasibility

of a project work. The product of this phase is a feasibility survey that is presented to a
steering committee for a decision on whether the project should be developed.
After feasibility analysis, the next phase is the study of the current system.
The purpose of this phase is to learn how the current system operates. The analyst identifies
the problems, limitations and constraints and forms preliminary solutions finally. The
analyst updates the feasibility estimates and presents the findings as a problem statement
for final study of phase reports.
The third phase of the system analysis is to define end-user requirements for
a new system. The purpose of this phase is to identify what the new and improved
information system must be able to do. The product of this phase is the requirement
statement.
The fourth phase is to select a feasible solution from alternatives that are
evaluated in terms of operational, technical and economic feasibility. The analyst will
recommend the best solution to the management for approval. A cost benefit analysis
determine the expected system development life time, cost for a new system and the
benefits of the new system.
6
3.2 EXISTING SYSTEM

Existing system is a manual one that every panchayat displays the list of
available schemes, tenders provided by the Government or panchayat. It invites the
applications from the eligible users based on certain criteria. All the applications are
verified at panchayat level and then approved applications are sent to District level for
approval. All the approved users avail the benefits of the scheme.
Loopholes with the Existing System:
o It is not secure to maintain important information manually.

o More manual hours need to generate required reports.
o It is tedious to manage historical data which needs much space to keep all the past
years applications, books etc.
o User need to wait more time to get his application status.
o Data is not in sync in case of manual system.
7
Panchayat
3.3 PROPOSED SYSTEM

Proposed system is a software application which avoids more manual hours that
need to spend in record keeping and generating reports. This application keeps the data in a
centralized way which is available to all the users simultaneously. It is very easy to manage
historical data in database. No specific training is required for the employees to use this
application. They can easily use the tool that decreases manual hours spending for normal
things and hence increases the performance.
Benefits:
o Easy to apply for any schemes or tenders or certificates if you are eligible for the
same.
o Can generate required reports easily.
o Easy to manage historical data in a secure manner.
o Centralized database helps in avoiding conflicts.
o Easy to use GUI that does not requires specific training.
8
3.5 ADVANTAGES OF PROPOSED SYSTEM

By developing the system we can attain the following advantages:
Accuracy
Proposed system provides accuracy in calculation as all data manipulations

are done through computers. We don't have to manually copy one information from one
register to another; this is done automatically in the system.
Speed
The proposed system is very much faster than existing system.
User friendliness
The proposed system is very user friendly so that users can learn and use very
easily. The controls and buttons are placed and well named for the user to understand
easily.
Security
Security is provided in the software, so that the data remain confidential. Login
screen is provided so that unauthorized access can be prevented and the data will be secure.
Efficient data handling
Since system uses databases, the data is organized in a very efficient

manner, so that redundancy of data will not occur
Modularity
The project has required number of modules for data entry. These modules
are implemented and interpreted at a later stage. The user interface and screen layout of all
the modules have been interpreted to achieve an integrated package.
9
3.6 REQUIREMENT SPECIFICATION
3.6.1 Introduction
Software requirements specification (SRS) is the requirements document

that provides the technical specification for the design and development of the software.
This document enhances the system's quality by formalizing communication between the
system developer and the user and provides the proper information for accurate
documentation. It produces a consequence of the analysis task at its culmination.
The introduction of the SRS states the goals and objectives of the software,
describing it in the context of the computer based system. It is nothing more than the
software scope.
The information description provides a detailed description of the problem

that the software must solve. Information content, flow and structure are documented and
hardware, software and human interfaces are described.
A description of each function required to solve the problem is presented in

the functional description.
The behavioral description section of the specification examines the

operation of the software as a consequence of external events and internally generated
control characteristics.
Validation criteria is perhaps the most important and, ironically, the most
often neglected section of the SRS. Specification of validation criteria acts as an implicit
review of all other requirements.
Finally, the specification includes a Bibliography and Appendix. The

bibliography contains references to all documents that relate to the software. The appendix
10
contains information that supplements the specifications. Eg. Tabular data, charts,
description for algorithms etc.
Specification Review
A review of the SRS is conducted by both the software developer and the
customer. The review is first conducted at a macroscopic level; ie., reviewers attempt to
ensure that the specification is complete, consistent and accurate when the overall
information. functional, and behavioral domains are considered. Once the review is
complete the SRS is signed off by both the customer and the developer. During the
review changes to the specification may be recommended. Thus it is ensured that the
developer and the customer have the same perception of the system.
3.6.2 SOFTWARE REQUIREMENT SPECIFICATION
This document describes the requirements of the system. It is meant for use
by the developers, and will also be the basis for validating the final delivered system. Any
changes made to the requirements in the future will have to go through a formal change
approval process. The developer is responsible for asking for clarifications, where
necessary, and will not make any alterations without the permission of the client.
Overview of Developer's Responsibilities
The developer is responsible for:
Developing the site.
Installing the software.
Conducting a demonstration about the usage.
11
3.6.2.1 General description
The main idea of 'e-panchayat' is to giving out the various schemes to the people
at right time and help's them to gain benefit from it. This application will be installed in
each panchayats all over the country, using this system people can check details of each
scheme and apply for a scheme which is suitable for them using online application form.
Also they can participate in tenders that conducted in each panchayat for various purposes.
And also people can apply for various certificates that has been provided by
panchayatIt is a bird's eye view of the Government schemes. Citizens need to apply for the
scheme through online which the help of a government officials. Application processing
information will be updated on this application. This system will save the time for citizens
and government.
3.6.2.2 Functional requirements
Action specified by the user:

These come as request from the browser and include messages specifying events
like clicking of various controls on the pages like buttons, hyperlinks etc.
Information provided by the user:

These include different types information and information regarding any
programs Discussion Forum for any user, other information etc.
3.6.2.3 Performance Constraints

Concurrent access to the site should be possible. Independent of the browser
used, the system must be able to display all the matter content. The storage and retrieval of
data from the database must be optional.
3.6.2.4 Acceptance Criteria
Before accepting the system, the developers will have to demonstrate that
the system fulfils its requirements. The system should be shown to run on a web server with
the ability to create WebPages and handle, simulations requests without failing.
12
Panchayat
SYSTEM DESIGN
13
4.1 INTRODUCTION
System design involves translating information requirements and conceptual

design into technical specification and general flow of processing. After the user
requirements are identified, related information is gathered to verify the problem and after
evaluating the existing system , a new system is proposed. The proposed system consists of
various tables, their maintenance and report generation.
For the Design of get unsettled software, care has been given for developing
an efficient system, which is user friendly as well as high in performance. It has been
assured that the system will have the functions and promises of the proposed system. In the
design, the various techniques are used to present a simple efficient system. Design phase
acts as a bridge between the software requirement specification and the implementation
phase, which satisfies the requirements.
The major step in design is the preparation of input forms and the design of
all major output forms in a manner acceptable to the user in all aspects. The base lies in the
complete understanding of the system. The data flow diagrams explicitly specify the
process flow. Table design or database design is the next major step. Extreme care has to
be given here and several concepts of normalization have to be applied at many levels.
Program specification comes next. Here we specify various aspects of the

program and also will in detail the major components used in the program. The overall
process flow is also explained in much detail. Validation rules and checks come next.
Several degrees of validation have to be applied to all inputs and various other operations
made on the system. Deviation, if any, has to be checked from these validation rules,
Imposing the not null' constraint is one of the best examples. It has been used in many
aspects. Various other constraints are also used. Security checks refer to avoiding
unnecessary access to data that is under use and guarding data from any malice.
14
Inputs, outputs has to be designed as per predefined guidelines. Effective

and meaningful navigation has to be applied. In the input design, the user-oriented inputs
are converted into computer-based formats whereas in the output design, the emphasis is on
producing the hard copy or soft copy of the information requested for. Code design is also
of much importance. It directly refers to various codes used in the programs and their usage
specification . The category to which these codes belong should also be specified.
15
4.2 DATA FLOW DIAGRAM
All data flow diagrams are graphical. It can be used to show current physical
activities and for the logical model of the system. The objective of this method is the
derivation of the program structure, which supports architectural design. It is a network that
describes the flow of data and process that transform the data through out the system.
The DFD also known as a data flow graph or a bubble chart. DFDs are
directed graphs in which nodes specify processing activities and arcs specify data item
transformed between processing nodes. It may partition in to levels that represents
increasing information flow and functional details. At level 0 DFD, fundamental system
models are representing the entire software elements as a single bubble with input and
output data indicated by incoming and outgoing arrows.
Following are the advantages
Provide an overview of DFD and the transformation of the data.

Act as a good communication tool with users. Several methods have been
devised to control processing activities. One such is batch processing.
Sequence checks verify that data records are in sequence prior to processing
Basic DFD Symbols
A square defines a Source or Destination of system data
Arrow identifies Data Flow - Data in motion. It is a pipeline through which

information flows.
16
Panchayat
Circle represents a Process that transforms incoming data flow(s) into

outgoing data flow(s)
Open rectangle is the data store- data at rest, stored information that is used
by the software.
Representation of duplication of source or destination
17
Panchayat
DATA FLOW DIAGRAMS
CONTEXT LEVEL
LEVEL 0
18
Panchayat
LEVEL 1 DFD FOR ADMIN MODULE
19
Panchayat
LEVEL1 DFD FOR PANCHAYAT MODULE
20
Panchayat
LEVEL 2 DFD FOR PANCHAYAT MODULE

2.7 VIEW APPLICATIONS
LEVEL 3 DFD FOR PANCHAYAT MODULE
2.7.1 TENDER
21
Panchayat
2.7.2 SCHEME
2.7.3 CERTIFICATE
22
Panchayat
LEVEL 1 DFD FOR USER MODULE
23
Panchayat
LEVEL 1 DFD FOR GUEST USER MODULE
24
4.3. INPUT DESIGN

The input is the set of values that is provided by the user to the system. The
input design must enable the user to provide the error free input to the system for efficient
processing. It defines the interface between user and system. Carefully designed inputs and
outputs define how effective the system is.
The input design is the process of converting the user-oriented inputs into
computer based formats. The collection of input data is the most expensive part of the
system in terms of the equipment used and the number of people involved. The data's fed
into the system using simple interactive forms. The forms have been supplied with
messages so that user can enter data without facing any difficulty. A set of menus is
provided which help for better application navigation. The data is validated wherever it
requires in the project. This ensures that only the correct data have been incorporated into
the system. The input data have to be validated, edited, organized, and accepted by the
system before being proposed to produce the outputs. Inaccurate input data is the most
common cause of errors in data processing.
The main objectives of input design are as follows:
Produce effective method of input

Achieve high level accuracy
Ensure that the input is acceptable and understood by the user
The different types of input data handled by the system are:
External
They are the primary inputs to the system. The external input is what the
user supplies to the system. The user can give different types of external inputs in this
project such as add new threads, post reply etc.
25
Internal
When the external inputs are obtained from the user, these inputs are
transferred to the system as messages. These messages are captured and handled as input
for further processing.
In this project the input design is done with ASP.Net codes. The external
inputs are the data given to the system by the user such as username and password for
authentication process. The external input also includes the request as per the user's interest
for displaying today's, yesterday's and last week's threads/posts and its replies. The internal
input covers the fetching of data from the database and it will be the input for
displaying the results on the screen.
The necessary external inputs are given to the system by Graphical User
Interface (GUI) technology. The GUI system applied to this project enables the user to
avoid error and confusion arises while entering the input.
26
4.4. OUTPUT DESIGN

A quality output is one, which meets the requirements of the end user and
presents the information clearly. In any systems results of processing are communicated to
the user and to the other systems through outputs. In the output design it is determined how
the information is to be displayed for immediate need. It is the most important and direct
source information to the user. Efficient and intelligent output design improves the
system's relationship with the user and helps in decision making. The objective of the
output design is to convey the information of all the past activities, current status and to
emphasize important events.
The output generally refers to the results and information that is generated
from the system. Outputs from computers are required primarily to communicate the results
of processing to the users. The result for each query option that is submitted by the user, the
system displays the output. The output that is obtained for each query submitted should be
tested before confirming the result.
27
4.5 DATABASE DESIGN

A database is a collection of interrelated data stored with minimum
redundancy to serve many users quickly and efficiently. The general objective is to make
information access easy, quick, inexpensive and flexible for the users. The general theme
behind a database is to integrate all the information. In database design several specific
objectives are considered:-
Controlled redundancy
Ease of learning and use
Data Independence
Accuracy and integrity
Recovery from failure
Performance
A database is an integrated collection of data and provides centralized
access to the data. Usually the centralized data managing the software is called RDBMS
and the other DBMS is the separation of data as seen by the program and data has stored in
direct access to stores device. This is the difference between logical and physical data.
Database is recognized as standard of MIS and is available virtually for every computer
system. The general theme behind a database is to integrate all the information. A database
is an integrated collection of data and provides centralized access to the data. Databases are
designed to manage large bodies of information. One of the major purposes of a database
system is to provide users with an abstract view of data. A database is designed so that it
can be used both to specify the overall logical structure of the database and provide a
higher level description of the implementation. The database is structured in fixed format
records of several types. Each record type defines a fixed number of fields or attributes and
each field is usually of a fixed length.
28
Design Consideration
The system is analyzed to the requirements and possible tables and fields are
identi
fied.
Identifying keys:
Once we have drawn up the lists of possible tables and fields, the
next step in the logic database is to identify and set foreign keys for each
table.
Primary keys: A primary key consists of a field or a set of fields that
uniquely identify each record in that table. The primary field defines
the primary key.
Foreign keys: A foreign key comprises a field or multiple fields that link
to the primary key of another table.
For any database application data is stored in tables. So the table designing
is a most important part of backend designing. Steps are taken to avoid unnecessary
replication of data and to achieve maximum data consistency and integrity.
The database design procedure transforms the information domain model created
during the analysis into tables that will be requires to implement the software or system. The
database design is made-up of two levels
Conceptual Level
Normalization
Conceptual Level
This level represents the major data objects and relationships between them. Conceptual
levels describe the essential feature of the system data.
29
Normalization
After the conceptual level, the next level of process a database design to organize the
date structure into a good shape is called Normalization. The normalization simplifies the entire,
removing the redundancies from the system data and finally builds a data structure, which is
both flexible and adaptable to the system. Normalization is the process of simplifying the
relationship between the data in a record. It is carried out for following reasons:
To simplify the maintenance of data through updates, insertions and deletions

To structure the data so that any relationships can be easily represented.
To allow simple retrieval of data in response to query and requests.
First Normal Form (1NF): Each row or column must be atomic ie., it must have a single
value with no repeating values.
Second Normal Form (2NF): Each non-key column must be depending upon the primary key
column.
Third Normal Form (3NF): No non-key column can depend on another non-key column.
Table Design
The most important aspect of building an application is the design of tables

or the database schema. The data stored in the tables must be organized in some manner,
which is meaningful. The overall objective in the process of table design has been to treat
data as an organizational resource and as an integrated whole. The organization of data in a
database aims to achieve these objectives:
- Data Integrity
- Data Independence
Several degrees of normalization have to be applied during the process of

table design.
30
1. Panchayat
Table Description: This table stores panchayat details

F DATATYPE WIDTH DESCRIPTION
I
E
int 4 Panchayat identifier
L varchar 35 Panchayat name
D
S varchar 35 District
Varchar 45 Address
PId Varchar 20 Phone
PName Varchar MAX History of panchayat
PDist Varchar MAX Details of panchayat
PAddrs int 4 Login identifier
PPhn
PHist
Pdet
LId
Primary Key: PId

Foreign Key:LId references Login table
2. Admin Photo
Table Description: This table stores the photos uploaded by

admin
FIELDS DATATYPE WIDTH DESCRIPTION
APhId int 4 Photo identifier
APhName varchar 30 Name of photo
APhotos Varchar 40 Location name

Primary Key: APhId
31
3. Login
Table Description: This table stores login details
I int 4 Login identifier
E
L varchar 30 Login name
D
S Varchar 20 Login password
LId Varchar 20 Role of user
LName Varchar 30 Question to

remember password
LPwd
Varchar 50 Answer to remember
LRole password
Questn
Answr
Primary Key: LId
4. Photo
Table Description: This table stores the photos uploaded by
each panchayat
PhId int 4 Photo identifier

PhName varchar 20 Name of photo
Photo Varchar 20 Location name
PId int 4 Panchayat identifier
Primary Key: PhId

Foreign Key: PId references Panchayat table
32
5. User
Table Description: This table stores the user details
FIE DATATYPE WIDTH DESCRIPTION
LDS int 4 User identifier
UId
varchar 20 User name
UName
int 4 Panchayat Identifier
PId
varchar 25 District
UDist
int 4 Age
UAge
Varchar 10 Sex of the user
USex
varchar 25 Religion of the user
URelgn
varchar 20 Caste
UCast
varchar 25 Group of user
UGroup
varchar 30 Phone
UPhn
varchar 30 Email of user
UEmail
varchar 50 Upload Id card
UIdcard
Int 4 Login id of the user
LId
Varchar 30 Status of user
Status
varchar 50 Occupation
UOcupation
Primary Key: UId

LId references Login table
33
Panchayat
6. Election Details
Table Description: This table stores the election details

El int 4 Election identifier

ElId varchar 20 Election identifier
ElName varchar 30 Name of candidate
ElPost varchar 30 Elected post
ElDate varchar 20 Election date
PId Int 4 Panchayat identifier

UId Int 4 User identifier
Primary Key: El
Foreign Key: UId references User table
PId references Panchayat table
34
7. Add Scheme
Table Description: This table stores the scheme details
SchmId int 4 Scheme identifier

SchmDate varchar 20 Date of posting
SchmDetail varchar 50 Detail of the scheme
SchmCatg varchar 25 Category identifier
SchmAmt varchar 30 Amount

SchmForm varchar 40 Form upload
Primary Key: SchmId
8. Apply scheme
Table Description: This table stores the details of applied users
of a particular scheme
ASId int 4 Apply identifier

SchmId Int 4 Scheme identifier
ASDate Varchar 20 Apply date

ASForm Varchar 40 Filled form
Primary Key: ASId

Foreign Key: SchmId references Add Scheme table
UId references User table
35
Panchayat
9. Confirm scheme
Table Description: This table stores the details of confirmed
scheme
I
int 4 Confirm identifier
E
Int 4 Scheme identifier
L
D Int 4 User identifier
S varchar MAX Confirmation
message
CSId
SchmId
UId
CSMsg
Primary Key: CSId
SchmId references Add Scheme table
10. Add Tender

Table Description: This table stores the tender details
TenDate Varchar
F DATATY
IELDS PId PE Varchar
Varchar
TenId i
n
t Int
TenName
TenDetail
Varch
TenForm ar
20 Tender identifier
WIDTH DE
4 SC Tender name
4
RI Tender detail
40
PT
Tender form
50 IO
Tender date
40 N
Panchayat identifier
Primary Key: TenId

36
11. Apply tender
Table Description: This table stores the details of user

applied for a tender
ATId int 4 Application
identifier
TenId int 4 Tender identifier
UId int 4 User identifier
ATDate Varchar 20 Applied date
ATFrm Varchar 40 Fiiled form
Primary Key: ATId
Foreign Key: TenId references Add Tender table
12. Confirm tender
Table Description: This table stores the tender confirmation
details
CTId int 4 Confirmed identifier

TenId Int 4 Tender identifier
UId int 4 User identifier
CTDate Varchar 20 Date
CTLtr Varchar MAX Confirmation letter
Primary Key: CTId

Foreign Key: TenId references Add Tender table
37
13. Apply Certificate

Table Description: This table stores the certificate details
DATATYPE WIDTH DESCRIPTION
FIELDS
int 4 Certificate identifier
ACId
varchar 30 Certificate type
ACType
int 4 User identifier
UId
varchar 40 Filled form
ACForm
Int 4 Panchayat identifier
PId
Primary Key: CEName

14. Confirm Certificate

Table Description: This table stores the reply details of the
certificate
CCId Int 4 Reply identifier

CCLtr Varchar MAX Sanction letter
CCForm Varchar 40 Copy of certificate
Primary Key: CCId

38
15. Add News

Table Description: This table stores the news uploaded by each
panchayat
NwsId int 4 News identifier
PId int 4 Panchayat identifier
NmsDate varchar 20 Date of news
NwsHdline varchar 50 Head line of news
NwsDetail varchar MAX Detail of news
Primary Key: NwsId

16. Add Notifications

Table Description: This table stores the notifications
uploaded by admin
I
E int 4 Notification identifier
L
D varchar 20 Notification heading
S
varchar 40 Notification form
NId
Primary Key: NId
NName
NForm
39
17. Message
Table Description: This table stores the messages send by
panchayat to users.
I
E int 4 Message identifier
L
D int 4 User identifier
S
int 4 Panchayat identifier
MsgId varchar 50 Message
UId Varchar 20 Date of message
PId
Msg
MDate
Primary Key: MsgId

40
Panchayat
SYSTEM DEVELOPMENT
41
5.1 I NTRODUCTION
The project is developed to assist the administrator in minimizing the time

and man power require to manage the content of the site. The software will prove useful
when the administrator will face acute shortage of time in changing the content of site
frequently. The project is a modular template system with the unique decision of having a
simple, user friendly environment.
5.2 MENU LEVEL DESCRIPTION
The project helps in minimizing the time and manpower required to manage
the content of the site. This project is a modular template system with the unique
distinction of having a simple, user-friendly environment. This means the users do not need
any programming knowledge.
There are mainly four modules, they are listed below
1. Admin
2. Panchayat
3. User
4. Guest User
Module 1 -Administrator
The administrator is the the government itself who has full privilege for governing
the site. The server side work as a hierarchy of different levels. The administrator can
perform not all functions.
Section 1- Add or delete panchayat.
In this section the administrator can add or delete panchayat.
42
Section 2- Add schemes.
In this section the administrator can add schemes for people.
Section 3- Add rules.
In this section the administrator can add rules that generally for every
citizens.
Section 4- Add photo.
In this section the administrator can add photos that a user can view.
Section 5- Change password.
In this section the administrator can change his password. This ensures
security.
Module 2 - Panchayat
The panchayat is controlling the various functions of this system. They are the
authorities who grant certain things that the user request for.
Section 1- Add news.
In this section the panchayat can add news.
Section 2 - View users.
In this section panchayat can view the registered users. He can also view the
full details that include ID card and photo.
43
Section 3- Approve users
In this section panchayat can approve users who are registered.
Section 4- Add tender.
In this section the panchayat can add tenders publically .
Section 5- Edit elected members.
In this section the panchayat can edit elected members if there is any change
occurred.
In this section the panchayat can change his password. This ensures security
to his account.
Section 7- View applications
In this section panchayat can view the applications for scheme,tender and
certificates. Panchayat can approve them or discard them.
Section 8- Add/Edit photo.
In this section the panchayat can add or edit photos.
Section 9- Send message
In this section the panchayat can send any private message to users under
that panchayat.
Section 10-Add certificate

In this section panchayat can add any modified certificates.
44
Module 3- User
The user must register first in order to use this system. The user is given full
privilege to access his profile. The user module allows users to apply for any scheme or
tender or certificates if they are eligible.
Section 1- View history.
In this section the user can view the history of their panchayat.
Section 2 - View photos.
In this section the user can view the photos of their panchayat.
Section 3- View election details
In this section user can view the last election details.
Section 4- View contact.
In this section the user can view the contact address of panchayat .
Section 5- View geographical details.
In this section the user can view the geographical details of their panchayat.
In this section the user can change his password. This ensures security to his
account.
Section 7- Apply scheme
In this section user can apply for schemes that provided by the government.
45
Section 8- Apply tender.
In this section user can apply for tenders which are published by the
panchayat.
Section 9- Apply certificate
In this section user can apply for certificates provided by panchayat.
Section 10-View messages

In this section user can view the messages that send by the panchayat.
Module 4-Guest User
The guest user can view the site and also search for schemes or they can download the
forms for the same or for the certificates. If they wish to apply for anything, they have to
register first.
Section 1- View history.
In this section the user can view the history of any panchayat.
Section 2 - View photos.
In this section the user can view the photos of any panchayat.
Section 3- View election details
In this section user can view the last election details of any panchayat.
Section 4- View contact.
In this section the user can view the contact address of each panchayat .
46
Section 5- View geographical details.
In this section the user can view the geographical details of every panchayat.
Section 6- View/Download forms.
In this section the guest user can view or download the forms for schemes or
certificates.
47
Panchayat
SYSTEM TESTING
48
6.1 TESTING METHOD

The entire testing process can be divided into 3 phases
Unit testing
Integrated Testing
Final/System Testing
Unit testing
Unit testing focuses verification effort on the smallest unit of software

designs the module. To check whether each module in the software works properly so that it
gives desired outputs to the given inputs. All Validations and conditions are tested in the
module level in the unit test. Control paths are tested to ensure the information properly
flows into, and out of the program unit and out of the program unit under test. Boundary
condition is tested to ensure that the modules operates at boundaries, establishes that it
restricts processing. All independent paths through the control structure ensure that all
statements in a module have been executed at least once. In conclusion, all errors handling
paths are tested.
In this system, Unit testing has been successfully handled. The test data was
given to each and every module in all respects and got the desired output. Each module has
been tested found working properly.
Integrated Testing
After testing all small units, I integrated all these small units and the testing
process repeated. The major concerns of integration testing are developing an incremental
strategy that will limit the complexity of entire actions among components as they are
added to the system. Developing a component as they are added to the system, developing
49
an implementation and integration schedules that will demonstrate the viability of the
evolving system. Though each program works individually, they should work after linking
them together. This is also referred to as Interfacing. Data may be lost across interface and
one module can have an adverse effect on another. Integration testing is a Systematic
technique for constructing program structure while at the same time, conducting test to
uncover errors associated with the interface. In the testing, the programs are constructed
and tested in small segments.
Validation testing
I made the data validations for this project by inserting different types of
data to all tables and updating the table contents many ways. Data validation is done to see
whether the corresponding entries made in the tables are correct. Proper validations are
done in case of insertion and updating of tables.
If any search case arises, then proper error messages or warning, if any, has to be
displayed.
The different test cases are;
Guarantee that all independent parts within a module have been

exercised at least once.
Exercise all logical decisions on their true /false side.
Execute all loops at their boundaries and within their operational

bounds.
Exercise internal data structure to ensure their validity.
Undertaken in this project an acceptance test has the objective of selling the
user on the validity and reliability of the system it verifies that the system procedures
50
operate to the system specification and that the integrity of vital data is maintained. I tested
the system with a large collection of records. The system is found to be user friendly and
working efficiently. All the above was successful.
Final/System testing
This is the final step in testing. In this, the entire system was tested as a
whole with all forms, code, modules and class modules. This form of testing is popularly
known as black box testing or system testing. Black box testing methods focus on the
functional requirement of the software. That is, black box testing enables the software
engineer to derive sets of input conditions that will fully exercise all functional
requirements for a program. Black box testing attempts to find errors in the following
categories; incorrect or missing functions, interface errors, errors in data structures or
external database access, performance errors and initialization errors and termination
errors. In this system, black box testing has been successfully handled. Any mistakes found
are rectified and found running successfully. The test-input data was given to the system
and got desired input.
51
6.2 TEST PLAN ACTIVITIES
Testing commences with a test plan and terminates with acceptance testing. A
test plan is a general document for the entire project that defines the scope, approach to be
taken, and the schedule of testing as well as identifies the test items for the entire testing
process and the personal responsibilities for the different activities of testing. The test
planning can be done in parallel with coding and design activities. The inputs for forming a
test plan are:
1. Project plan
2. Requirements documents
3. System design document.
The project plan is needed to make sure that the test plan is consistent with
the overall quality plan for the project and the testing schedule matches that of the project
plan. The requirements document and the design document are the basic documents used
for selecting the text units and deciding the approaches to be used during testing. A test
plan should contain the following activities:
Test unit specification

Features to be tested
Approach for testing
Test deliverables
Personnel allocation
One of the most important activities of the test plan is to identify the test units. A
test unit is a set of one or more modules, together with associated data, that are from a
single computer program and that are the object of testing. A test unit can occur at any level
and contain from a single module to the entire system. Thus a test unit may be a
52
module, a few modules, or a complete system. Different levels of testing must be used
during the testing activity. The levels are specified in the test plan by identifying the test
units for the project. Different units are specified for unit, integration and system testing.
The identification of test units establishes the different levels of testing that will be
performed in the project. Generally, a number of test units are formed during the testing,
starting from the lower-level modules, which have to be unit-tested. An important factor
while forming a unit is the testability of a unit. A unit should be such that it can be easily
tested. In other words, it should be possible to form meaningful test cases and execute the
unit without much effort with these test cases.
Features to be tested include all software features and combinations of

features that should be tested. A software feature is a software characteristic specified or
implied by the requirements or design documents. These may include functionality,
performance, design constraints and attributes.
The approach for testing specifies the overall approach to be followed in the
current project. The techniques that will be used to judge the testing effort should also be
specified. This is sometimes called testing criterion or the criterion for evaluating the set of
test cases used in test cases.
Testing deliverables should be specified in the test plan before the actual
testing begins. Deliverables could be a list of test cases that were used, detailed results of
testing including the list of defects found, test summary report, and data about the code
coverage. In general, a test case specification report, test summary report, and a list of
defects should always be specified as deliverables.
The test plan, if it is a document separate from the project management plan,
typically also specifies the schedule which specifies the amount of time and effort to be
spent on different activities for testing. This schedule should be consistent with the overall
project schedule. Personnel allocation identifies the process responsible for performing the
different activities.
53
Panchayat
6.3 SCREEN LAYOUTS
MAIN HOME
54
Panchayat
GUEST USER HOME PAGE
PHOTOS
55
Panchayat
HISTORY
CONTACTS
56
Panchayat
ELECTION DETAILS
GEOGRAPHICAL DETAILS
57
Panchayat
VIEW THE SCHEMES
TO VIEW THE TENDERS
58
Panchayat
DOWNLOAD FORM FOR CERTIFICATES
VIEW NOTIFICATIONS
59
Panchayat
USER REGISTRATION
60
Panchayat
USER
HOME PAGE
EDIT ACCOUNT
61
Panchayat
CHANGE PASSWORD
VIEW MESSAGES
6275
Panchayat
APPLY SCHEME
APPLY SCHEME
63
Panchayat
APPLY FOR CERTIFICATE
64
Panchayat
PANCHAYAT
LOGIN
HOME PAGE
65
Panchayat
ADD NEWS
VIEW USERS
66
Panchayat
APPROVE USERS
ADD TENDER
67
Panchayat
EDIT ELECTED MEMBERS
VIEW APPLICATIONS
68
Panchayat
VIEW APPLICATION FOR SCHEME
VIEW CONFIRMED USERS FOR SCHEME
69
Panchayat
VIEW APPLICATION FOR CERTIFICATES
CHANGE PASSWORD
70
Panchayat
ADD/EDIT PHOTO
ADD CERTIFICATES
71
Panchayat
ADD ELECTION DETAILS
SEND MESSAGE
72
Panchayat
ADMIN
LOGIN
HOME
73
Panchayat
ADD NOTIFICATION
ADD PANCHAYAT
74
Panchayat
ADD PHOTO
ADD SCHEME
75
7. SYSTEM IMPLEMENTATION
Implementation is the stage in the project where the theoretical design is

turned into a working system and is giving confidence on the new system for the users,
which it will work efficiently and effectively. It involves careful planning, investigation of
the current system and its constraints on implementation, design of methods to achieve the
change over, an evaluation, of change over methods. Apart from planning major task of
preparing the implementation are education and training of users. The more complex
system being implemented, the more involved will be the system analysis and the design
effort required just for implementation.
An implementation co-ordination committee based on policies of individual

organization has been appointed. The implementation process begins with preparing a plan
for the implementation of the system. According to this plan, the activities are to be carried
out, discussions made regarding the equipment and resources and the additional equipment
has to be acquired to implement the new system.
Implementation is the final and more important phase. The system can be
implemented only after through testing is done and if it found to work according to the
specification. This method also offers the greatest security since the old system can take
over if the errors are found or inability to handle certain type of transactions while using
the new system.
Implementation involves careful planning to avoid any unwelcome

consequences. The effort spends on developing any system results in success only when the
system implemented properly. System implementation involves actual installation,
evaluation of the installation, organizational impact and finally the quality assurance.
76
The implementation plan consists of
Testing the developed system with the sample data

Detection and correction of errors
Making necessary changes in the system
Checking it with the existing system.
Implementation Plan
The implementation phase is less creative than design phase. The Internet
Discussion Forum is implemented using Hypertext Preprocessor (PHP), MySQL and
Apache web server. This system is platform independent that can run on any Operating
System.
User Training
The implementation of the system operators includes the training of the

system. Training of the system includes not only the implementation on how to use the
system, but also how to diagnose the system errors, malfunctions and ways to resolve the
same. Therefore proper training should be provided to system operators.
77
Panchayat
CONCLUSION AND SCOPE FOR

FUTURE ENHANCEMENT
78
8. CONCLUSION
The project entitled 'e-panchayat' implements a software application for helping

citizens to utilize and apply for schemes, tenders and certificates through a online
application. Using this system people can check details of each scheme and apply for a
scheme which is suitable for them using online application form. Also they can participate
in tenders that conducted in each panchayat for various purposes. And also people can
apply for various certificates that has been provided by panchayat. The 'e-panchayat'
provides various schemes to the people at right time and help's them to gain benefit from it.
This online system will make work simpler and efficient. It is a bird's eye view of the
Government schemes. This system will save the time for citizens and government. This
system has very good GUI so that a novice user did not feel any operational difficulties.
SCOPE FOR FUTURE ENHANCEMENT
The changes may occur to all systems in future. The project

e-panchayat is designed for any future addition so that any user requirements can be
made easy. Though the system is working on various assumptions it can be modified easily
to any kind of requirements.
Further enhancements are possible even in specific modules as entire system is

computerized in modular approach. The system is flexible enough to incorporate new
databases to existing one. Since the entire system is developed in a modular approach,
modifications if necessary can be done on specific module without disturbing the entire
system.
79
BIBLIOGRAPHY
Books
Elias.M.Award , System Analysis And Design, Galgotia Publication Pvt. Ltd, 1991.
Roger.S.Pressman, Software Engineering, Mc GrawHill International Editions ,
1991.
A.Silbershatz-H.F.Korth-Sudarshan, DataBase System Concepts(4th Edition), Mc
GrawHill International Editions.
Laura Lemay, ASP.NET-Programmers Guide, Macmillan London Pvt. Ltd,
London, 2002.
Websites
www.google.com
www.wikipedia.com
www.keralagov.in
www.w3schools.com
www.codeproject.com
www.tigweb.org
80

Project Report 2013e-Panchayat

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Project Report 2013e-Panchayat

Diunggah oleh

Hak Cipta:

Format Tersedia

Project Report 2013 e-

1.1 PROJECT OVERVIEW

The main idea of 'e-panchayat' is to implement a software application

The 'e-panchayat' is mainly concentrated in giving out the various schemes

2.1 HARDWARE SPECIFICATION

Processor : Intel(R) Core 2 Duo

Processor speed : E4600 @ 2.40GHz

: Logitech USB Mouse

2.2 SOFTWARE SPECIFICATION

Operating System : Microsoft Windows XP Professional, Service Pack 2

Front End : Microsoft Visual Studio 2008

Back End : SQL Server 2005

Web Server : IIS

Web application tools: HTML

Scripting language : Java Script

3.1 PRELIMINARY INVESTIGATION

The purpose of preliminary study phase is to determine the initial feasibility

3.2 EXISTING SYSTEM

Loopholes with the Existing System:

o It is not secure to maintain important information manually.

3.3 PROPOSED SYSTEM

3.5 ADVANTAGES OF PROPOSED SYSTEM

Proposed system provides accuracy in calculation as all data manipulations

The proposed system is very much faster than existing system.

Efficient data handling

Since system uses databases, the data is organized in a very efficient

3.6 REQUIREMENT SPECIFICATION

Software requirements specification (SRS) is the requirements document

The information description provides a detailed description of the problem

A description of each function required to solve the problem is presented in

The behavioral description section of the specification examines the

Finally, the specification includes a Bibliography and Appendix. The

3.6.2 SOFTWARE REQUIREMENT SPECIFICATION

Overview of Developer's Responsibilities

The developer is responsible for:

Developing the site.

Installing the software.

Conducting a demonstration about the usage.

3.6.2.1 General description

3.6.2.2 Functional requirements

Action specified by the user:

Information provided by the user:

3.6.2.3 Performance Constraints

System design involves translating information requirements and conceptual

Program specification comes next. Here we specify various aspects of the

Inputs, outputs has to be designed as per predefined guidelines. Effective

4.2 DATA FLOW DIAGRAM

Following are the advantages

Provide an overview of DFD and the transformation of the data.

Basic DFD Symbols

A square defines a Source or Destination of system data

Arrow identifies Data Flow - Data in motion. It is a pipeline through which

Circle represents a Process that transforms incoming data flow(s) into

Representation of duplication of source or destination

DATA FLOW DIAGRAMS

LEVEL 1 DFD FOR ADMIN MODULE

LEVEL1 DFD FOR PANCHAYAT MODULE

LEVEL 2 DFD FOR PANCHAYAT MODULE

LEVEL 3 DFD FOR PANCHAYAT MODULE

LEVEL 1 DFD FOR USER MODULE

LEVEL 1 DFD FOR GUEST USER MODULE

4.3. INPUT DESIGN

The main objectives of input design are as follows: