1.

Introduction
1.1Abstract

e-Governance.in
The word electronic in the term e-Governance implies technology driven governance. EGovernance is the application of Information and Communication Technology (ICT) for
delivering government services, exchange of information communication, integration of various
stand-alone systems and services between Government-to-Citizens (G2C), Government-toGovernment( G2G) as well as back office processes and interactions within the entire
government frame work.
Through the e-Governance, the government services will be made available to the citizens in a
convenient, efficient and transparent manner. The three main target groups that can be
distinguished in governance concepts are Government, citizens and businesses/interest groups. In
e-Governance, there are no distinct boundaries.Generally four basic models are availableGovernment to Customer (Citizen), Government to Employees, Government to Government and
Government to Business. The essence of E-governance is to reach the beneficiary and ensure that
the services intended to reach the desired individual has been met with. There should be an autoresponse system to support the essence of E-governance, whereby the Government realizes the
efficacy of its governance.

E-governance is By the Governed, For the Governed and Of the Governed

Project aim is to provide efficient needs for citizen of India. This project gives all the information
about Online Passport application, Pan card, Voter ID, Ration card, aadhar card and Birth and
death certificate and one can apply online. One can also fix appointment and download the
application and get the ID proof in the particular center by showing the acknowledgment given
to you when applied online.
This saves lot of time for the citizens of India. Its very useful to senior citizens who can save lot
of time by applying online and not physically stand and wait in a queue for a long time. It also
helps the people of India to use technology at its best at their own place and get things done

faster. This online based application not only helps the users to apply but also makes it easier for
the government people to organize things in an efficient manner.
The following Modules involved are:1.

Register Module

2.

Central Government module

3.

State Government module

4.

Admin Module

REGISTER MODULE:This module helps in signing up for the new user. Here the personal details are provided like
First Name, Last Name, City, Age, Sex, Mobile number, email-id, Address, Username, Password
and DOB. Once registered, the user can login in to the website and can download any required
applications as per choice.

CENTRAL GOVERNMENT MODULE:The Government of India, officially known as the Union Government, and also known as the
Central Government, was established by the Constitution of India, and is the governing authority
of the union of 28 states and seven union territories, collectively called the Republic of India.
There are four sub modules in this namely:
a. Passport :- Here, the passport application is available where in you can apply for fresh
passport, reissue of passport, fix appointment, fee details and documents required.
b. PAN-Card :- Permanent Account Number is an unique alpha numeric combination issue
to all juristic entities identifiable under the Indian Income Tax Act 1961. Which is almost
equivalent to a national identification number, it also serves as an important Id proof. Its
mandatory for financial transactions. The PAN is unique, national and permanent.
c. Aadhaar Card :- The Unique Identification Authority of India( UIDAI) is an agency of
the government of India responsible for implementing the AADHAAR scheme, an
unique identification project. The authority will maintain a database of residents
containing bio-metric and other datas.
d. Voter ID:- Voter registration is the requirement in some democracies for citizens and
residents to check in with some central registry specifically for the purpose of being

allowed to vote in elections.The Government of India conducts an intensive revision of

the voters list every 5 years. Apart from this, citizens can request their inclusion in the
Voters list by applying through form 6. If the application is valid, the applicant's name
will get included in the list

STATE GOVERNMENT MODULE:In India, the state governments are the level of government below the central government.India is
a Sovereign Socialist Secular Democratic Republic with a Parliamentary system of government.
The Republic is governed in terms of the Constitution. Sovereignty is shared between the centre
and the state government, but the central government is given greater powers. The President is
the constitutional head of Executive of the Union. There are two sub modules, Namely
a. RATION Card:- A ration stamp or ration card is a stamp or card issued by a government
to allow the holder to obtain food or other commodities that are in short supply during
wartime or in other emergency situations. Ration stamps were widely used during World
War II by both sides after hostilities caused interruption to the normal supply of goods.
They were also used after the end of the War while the economies of the belligerents
gradually returned to normal.Ration cards have been an important part of the Public
Distribution System (PDS) in India. On the basis of their economic condition, people can
buy goods like food grains, sugar and kerosene with the help of their ration cards. They
are three types of ration card:
Antyodaya ration cards, issued to the poorest of the poor.
Below Poverty Line (BPL) cards.
Above Poverty Line (APL) cards.

b. BIRTH & DEATH CERTIFICATE:- A birth certificate is a vital record that documents
the birth of a child. The term "birth certificate" can refer to either the original document
certifying the circumstances of the birth or to a certified copy of or representation of the
ensuing registration of that birth. Depending on the jurisdiction, a record of birth might or
might not contain verification of the event by such as a midwife or doctor.The phrase
death certificate can describe either a document issued by a medical practitioner
certifying the deceased state of a person or popularly to a document issued by a person
such as a registrar of vital statistics that declares the date, location and cause of a person's
death as later entered in an official register of deaths.

1.1Problem Definition

This saves lot of time for the citizens of India. Its very useful to senior citizens who can save
lot of time by applying online and not physically stand and wait in a queue for a long time. It
also helps the people of India to use technology at its best at their own place and get things
done faster. This online based application not only helps the users to apply but also makes it
easier for the government people to organize things in an efficient manner.

2. Requirements
2.1 Hardware

Processor

Intel Pentium III

RAM

256 MB

Hard Disk

20 GB

Software

Operating System

: Windows 98/2000/XP/NT

Server side Script

Back-End Tool

: SQL Server 2000

JAVA/ J2EE

Software Development Process Model Adopted (SDLC Model)

The Systems Development Life Cycle (SDLC) is a

conceptual model used in project management

that describes the stages involved in an information

system development project from an initial feasibility
study through maintenance of the completed application.
Various SDLC methodologies have been developed to
guide the processes involved including the waterfall
model (the original SDLC method), rapid application
development (RAD), joint application development (JAD),
the fountain model and the spiral model.
Mostly, several models are combined into some sort
of

hybrid

methodology.

Documentation

is

crucial

regardless of the type of model chosen or devised for any

application, and is usually done in parallel with the
development process. Some methods work better for
specific types of projects, but in the final analysis, the
most important factor for the success of a project may be
how closely particular plan was followed.
The image below is the classic Waterfall model
methodology, which is the first SDLC method and it
describes the various phases involved in development.

SYSTEM DEVELOPMENT LIFE CYCLE

The Systems Development Life Cycle (SDLC), or Software Development Life Cycle in systems
engineering, information systems and software engineering, is the process of creating or altering
systems, and the models and methodologies that people use to develop these systems. The
concept generally refers to computer or information systems.
In software engineering the SDLC concept underpins many kinds of software development
methodologies. These methodologies form the framework for planning and controlling the
creation of an information system: the software development process.
Software Development Life Cycle (SDLC) is a process used by a systems analyst to develop
an information system, including requirements, validation, training, and user (stakeholder)
ownership. Any SDLC should result in a high quality system that meets or exceeds customer
expectations, reaches completion within time and cost estimates, works effectively and
efficiently in the current and planned Information Technology infrastructure, and is inexpensive
to maintain and cost-effective to enhance.
Computer systems are complex and often (especially with the recent rise of Service-Oriented
Architecture) link multiple traditional systems potentially supplied by different software vendors.
SDLC models can be described along a spectrum of agile to iterative to sequential. Agile
methodologies, such as XP and Scrum, focus on light-weight processes which allow for rapid
changes along the development cycle. Iterative methodologies, such as Rational Unified
Process and Dynamic Systems Development Method, focus on limited project scopes and

expanding or improving products by multiple iterations. Sequential or big-design-up-front

(BDUF) models, such as Waterfall, focus on complete and correct planning to guide large
projects and risks to successful and predictable results. Other models, such as Anamorphic
Development, tend to focus on a form of development that is guided by project scope and
adaptive iterations of feature development.
In project management a project can be defined both with a project life cycle (PLC) and an
SDLC, during which slightly different activities occur.
The System Development Life Cycle framework provides a sequence of activities for system
designers and developers to follow. It consists of a set of steps or phases in which each phase of
the SDLC uses the results of the previous one.
A Systems Development Life Cycle (SDLC) adheres to important phases that are essential for
developers, such as planning, analysis, design, and implementation, and are explained in the
section below. A number of system development life cycle (SDLC) models have been created:
waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize and
stabilize. The oldest of these, and the best known, is the waterfall model: a sequence of stages in
which the output of each stage becomes the input for the next. These stages can be characterized
and divided up in different ways, including the following:
Project planning, feasibility study: Establishes a high-level view of the intended project
and determines its goals.
Systems analysis, requirements definition: Defines project goals into defined functions
and operation of the intended application. Analyzes end-user information needs.
Systems design: Describes desired features and operations in detail, including screen
layouts, business rules, process diagrams, pseudo code and other documentation.
Implementation: The real code is written here.

 Integration and testing: Brings all the pieces together into a special testing environment,
then checks for errors, bugs and interoperability.
Acceptance, installation, deployment: The final stage of initial development, where the
software is put into production and runs actual business.
Maintenance: What happens during the rest of the software's life: changes, correction,
additions, and moves to a different computing platform and more. This, the least
glamorous and

To manage this level of complexity, a number of SDLC models have been created: Waterfall
model, Fountain model, Spiral model, Build and Fix model, Rapid Prototyping model,
Incremental model and Synchronize and Stabilize model.

Process Model Selected

The image below is the classic Waterfall Model methodology which is used in this project: Fee
Collection System, which is the first SDLC method and it describes the various phases involved
in development:

The waterfall model is a sequential design process, often used in software development
processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the
phases

of

Conception,

Initiation,

Analysis,

Design,

Construction,

Testing,

Production/Implementation and Maintenance.

Stages of Waterfall model

Requirement Analysis & Definition: All possible requirements of the system to be developed
are captured in this phase. Requirements are set of functionalities and constraints that the enduser (who will be using the system) expects from the system. The requirements are gathered
from the end-user by consultation, these requirements are analyzed for their validity and the
possibility of incorporating the requirements in the system to be development is also studied.

Finally, a Requirement Specification document is created which serves the purpose of guideline
for the next phase of the model.

System & Software Design: Before a starting for actual coding, it is highly important to
understand what we are going to create and what it should look like? The requirement
specifications from first phase are studied in this phase and system design is prepared. System
Design helps in specifying hardware and system requirements and also helps in defining overall
system architecture. The system design specifications serve as input for the next phase of the
model.

Implementation & Unit Testing: On receiving system design documents, the work is divided in
modules/units and actual coding is started. The system is first developed in small programs
called units, which are integrated in the next phase. Each unit is developed and tested for its
functionality; this is referred to as Unit Testing. Unit testing mainly verifies if the modules/units
meet their specifications.

Integration & System Testing: As specified above, the system is first divided in units which are
developed and tested for their functionalities. These units are integrated into a complete system
during Integration phase and tested to check if all modules/units coordinate between each other
and the system as a whole behaves as per the specifications. After successfully testing the
software, it is delivered to the customer.

Operations & Maintenance: This phase of "The Waterfall Model" is virtually never ending
phase (Very long). Generally, problems with the system developed (which are not found during
the development life cycle) come up after its practical use starts, so the issues related to the
system are solved after deployment of the system. Not all the problems come in picture directly
but they arise time to time and needs to be solved; hence this process is referred as Maintenance.

Purpose of this process model selected for the project

Clear project objectives.

Stable project requirements.
Progress of system is measurable.
Strict sign-off requirements.
Model is simple and easy to understand.

4. Analysis and Design Models

Requirement Analysis:
Requirements analysis in systems engineering and software
engineering, encompasses those tasks that go into determining
the needs or conditions to meet for a new or altered product,
taking account of the possibly conflicting requirements of the
various stakeholders, such as beneficiaries or users.
Requirements analysis is the first stage in the systems
engineering process and software development process.
4.1 Functional Requirement

An User should be able to:

 Log in to the system through the initial screen of the

system.
Change password after logging in(if required).
Should be able to download forms.

An Admin should be able to:

Log in to the system
Manage the user account.
Check for the approving appointment.
Check how many customers are registered.
4.1.2 Input Design

In information systems the input data are entered according to

the format that is designed in the forms. Inaccurate input data are
the most common cause of errors in data entry. These can be
controlled by proper input design.
Input design is a process of converting user organized inputs to a
computer based format. Input data are controlled and organized
into groups of similar data. The goal of designing input data is to
make data entry as easy, logical & free from errors as possible
through JFC input design of forms.
During design of input, the analyst should decide on the following
details:
What data to input.
What medium to use.
How data should be arranged.

 How data should be coded i.e. data representation

conventions.
Data items and transactions needing validation to detect
errors
Methods for performing input validation and steps to follow
when errors occur

4.1.3 Output Design

Output is the most important and direct source of information to

the user. Efficient, intelligible output design should improve the
system relationships with the user and help in better decision
making capability.
Output refers to the results and information that are generated by
the system. In many cases, output is the main reason for
developing the system and the basis on which the usefulness of
the system is evaluated. Most end-users will not actually operate
the information system or enter data through workstations, but
they will use the output from the system.
While designing the output of system, the following factors should
be considered:

Determine what information to present

Decide on the mode of output, i.e. whether to display, print, or

"speak" the information and select the output medium

Arrange the presentation of information in an acceptable format

Decide how to distribute the output to intended recipients.

System Design
Function Architecture Design

Use Case Diagram

System

State Government
<<include>>

Register

Citizen Of India

Class Diagram

<<include>>

Central Government

Sequence Diagram 1.a

Sequence Diagram 1.b

Collaboration Diagram 1.a

Collaboration Diagram 1.b

Data Flow Diagram

A DFD is a modeling tool that allows us to show a system as a network of processes (mini
systems) connected to each other by paths of data.

Data Flow:
Each arrow in a DFD Represents a path (or pipeline of conveyer belt) of data, called the Data
Flow.

Process:
A process represents an automated or manual activity that transforms incoming data flows to
outgoing data flows.

Data-Store:
A Data-Store holds the data (for reference), which the system cannot remember.
External events and system responses ate From/To Sources or Destination of the system.

Components of DFD:
The basic components of DFD are following

Source/Destination

Process

Data Source

DFD are based on the strategy of structured techniques namely:1. Graphics

2. Top Down Approach
3. Separation of logical from the physical
4. Partitioning

DFDs do not show1

How things begin & end

2

Loops

Decisions

REGISTER MODULE: Level 0

SIGN UP

FILL DETAILS
SAVE THE INFORMATION
IIIIII
III
INFORMATION
DETAILS
STORES IN REGISTER
MODULE

CENTRAL GOVERNMENT MODULE: Level 1

DOWNLOAD APPLICATION FORM

LOGIN

LOGIN TABLE
MODULE

INVALID
LOGIN AUTHENTICATION

PAN CARD

CENTRAL GOVERNMENT

PASSPORT

AADHAAR

VOTERS ID

DOWNLOAD APPLICATION FORM

DOWNLOAD APPLICATION FORM

DOWNLOAD APPLICATION FORM

TAKES APPOINTMENT

TAKES APPOINTMENT

ADMIN APPROVES
MODULE

ADMIN APPROVES
MODULE

TAKES APPOINTMENT

ADMIN APPROVES
MODULE

STATE GOVERNMENT MODULE: Level 2

DOWNLOAD APPLICATION FORM

LOGIN

LOGIN TABLE
MODULE

INVALID
LOGIN AUTHENTICATION

RATION CARD

STATE GOVERNMENT

BIRTH & DEATH CERTIFICATE

DOWNLOAD APPLICATION FORM

TAKES APPOINTMENT

ADMIN APPROVES
MODULE

ADMIN MODULE: Level 3

LOGIN

LOGIN TABLE
MODULE

INVALID

LOGIN AUTHENTICATION

MANAGES APPOINTMENTS

APPROVES APPOINTMENT

APPROVED APPOINMENT TABLE

APPROVAL

ER DIAGRAM:
In software engineering, an entity-relationship model (ERM) is an abstract and conceptual
representation of data. Entity-relationship modeling is a database modeling method, used to
produce a type of conceptual schema or semantic data model of a system, often a relational
database, and its requirements in a top-down fashion. Diagrams created by this process are called
entity-relationship diagrams, ER diagrams, or ERDs.

UserName

LOGIN

REGISTER

STATE
GOVERNMENT

BIRTH & DEATH

CERTIFICATE

Password

LOGIN

CENTRAL
GOVERNMENT

PAN CARD
RATION
CARD

PASSPORT

VOTERS
ID

AADHAR
CARD
MANAGES APPOINTMENT

APPOINTMENT APPROVAL

ADMIN

USER

1. TESTING

After a test plan has been developed, system testing begins by

testing program modules separately, followed by testing bundled
modules as a unit.
1) SYSTEM TESTING:
The proposed system is tested in parallel with the software
effort that consists of its own phases of analysis,
implementation, testing and maintenance.
2) UNIT TESTING:
During the implementation of the system, each part of the system
is tested separately to uncover errors within its boundaries. User
interface was a guide in the process.
Eg: user_id/password.
When the USER provide the same user_id/password in the login
box, same to the one existing in the database, and its
functionality is working, then the unit testing is successful.
3) FUNCTIONAL TESTING:
To determine if the various display screen needs the designed
rules and are completed and correct.
Eg: At the time of registering the system, it performs unit testing
alongside. We check for all the modules and database tables

which are directly or indirectly affected by the execution of that

module.
4) ACCEPTANCE TESTING:
Acceptance testing is done to verify readiness for implementation
and use. The proposed system provides the end user the
confidence and assurance that the software is completely ready
to use.
5) INTEGRATION TESTING:
The objective of integration testing is to take unit modules and
build a program that has been defined and designed. We have
done a top down integration test which is an increment approach.

TEST CASES:
User-Id and Password for a User
Test
case ID

Description

Input

Expected
Output

Actual Output Test Result

A blank user name

and password given
by the admin

User name
blank

A valid user name Valid user name Should show

and blank password
error message
Password blank that password
given by the
manager
is required

Display
password is
mandatory

Pass

A blank id and valid

password are given
by the branch-

Display id
shouldnt be

Pass

Should show
Display user
error message
name and
that user name password are
password blank & password are mandatory
required

Blank user
name

Should show
error message
that password

Pass

manager

is required

blank

Valid password
4

A valid user name Valid user name Should validate

and valid password
the values &
are given by the Valid password allow to login
customer

Login
successfully

Pass