Abstract

Government Scheme Management System projects main idea is to

implement a software application for helping citizens to utilize and apply for
schemes through an online application.

Most of the schemes introduced by the Government go into dustbin just

because the officials who implement the schemes could not make them
available to suitable people. So there is a secured and transparent system
needed which enable an ordinary person to directly apply for a scheme and
track the status from time to time and know whether he is entitled to receive
the fruit or his application is rejected by the officials. In any case, the
applicant should be able to know the reason for rejection openly. This
catches trust in the Government from the people and avoids mis-utilization
of funds.

Design an AADHAR based application to resolution process for taking benefit

of such welfare schemes. Provide facility to enter eligibility to the scheme. If
application to one scheme disqualifies application other then such conflicting
applications should not be allowed using the system.

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, User wise report etc.
Introduction

Government Scheme Management System is a software application to

automate the process for utilization of various schemes provided by
government. Government Scheme Management System Software takes care
of the activities related to the schemes provided by the government. The
major responsibility is to take care of the proper utilization of different
schemes in a transparent way.

Main idea is to develop a online application for citizens through which

citizens can apply for schemes that are provided by government by
submitting required documents. Using these system government officials will
process the application and submit their opinion on the application with
details on why it is accepted and why it is not accepted.

In present scenario government is introducing many schemes for citizens but

they are not reaching to normal man because of its application process. So
with this application it will be easy to know information about schemes and
easy to apply. Using this application can increase trust in government from
the people and reduce misusing of funds. This system clearly keeps track of
the status of user’s application by tracking the actual activities that are
under process within the low or at higher level at any point of time, by the
administrators. This system provides effective way to manage the important
information in a very secure manner by authenticating users at various
levels. When the user applies for a scheme, his details will be stored in the
database and sent to for verification. Panchayat people conduct a physical
verification and send their remarks to the DDO who would write his
comments. These details are sent to final approving authority and help him
to approve or disapprove the person for the scheme. The same details can
be viewed by the user so that the user would get a clear picture of what is
happening from time to time.
Existing system

Current system is a manual one in every panchayat displays the list of

available schemes provided by the Government. 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.

Using existing system there is a gap between citizens and officials and
government schemes. There are a lot of schemes which are introduced by
the government but they are not used effectively by citizens.

Disadvantages:

The following are the disadvantages of current system

 It is not secure to maintain important information manually

 More manual hours need to generate required reports
 It is tedious to manage historical data which needs much space to
keep
 All the past years applications, books etc.
 User needs to wait more time to get his application status.
 Data is not in sync in case of manual system.
Literature Survey

Reference 1:

Title: “Guidelines for Indian government websites-standards for

enhancing web usability”

Author: Verma, N. and Joshi, L

Description: Web enablement of citizen services is one of the focus areas of

NeGP (National e-Governance Plan) which was formed and approved on May
18, 2006 by the Government of India. As it is well established that websites
facilitate an efficient and timely interaction between the citizens and the
Government, the availability of web driven information and services also
finds its space as one of the 27 Mission Mode Projects of the NeGP. With the
penetration of the Internet and its availability on a range of devices, it is
highly likely that the first point of interface for enabling information and
services from Government departments to the citizens' will be the
Government Websites.
Reference 2:

Title: “E‐Governance Assessment Frameworks”.

Author: Bhatnagar, S.

Description: E-Government progress is being evaluated by multiple surveys

using different methods, indexes and addressing different perspectives. In
this paper, an overview of the assessment frameworks for e-Government
software projects' will be presented. All major assessment approaches -from
European Commission, the United Nations, the World Bank etc. -will be
analyzed and compared. As a result will emerge, the need for developing a
multi-facet e-government project's assessment framework, able to
systematically analyze and evaluate the efficiency and the effectiveness of
these projects.

Reference 3:

Title: “Single window electronic delivery of services”.

Author: Parks, T.

Description: Web portal is a interactive portal which combines information

content and interactive web services into one single fabric. This portal is
meant primarily for the citizens/businesses of in India. Through Online, the
citizen has comprehensive access to information content and web services
through a single window. Through AP Portal the citizens can avail a wide
variety of services like registrations, issue of certificates, utility services,
payments services. In addition, regularly updated information about matters
of general concern to the citizens is available for access through the portal
home page.

Reference 4:

Title: “E-Governance and Developing Countries Introduction and

examples”.

Author: Backus, M.

Description: The objectives of e-governance are similar to the objectives of

good governance. Good governance can be seen as an exercise of economic,
political, and administrative authority to better manage affairs of a country
at all levels. It is not difficult for people in developed countries to imagine a
situation in which all interaction with government can be done through one
counter 24 hours a day, 7 days a week, without waiting in lines.

Reference 5:

Title: “Technical Standards and E-Governance Architecture”.

Author: Suchitra Pyarelal.

Description: This paper provides an overview of the work currently being

undertaken at an international level by the OASIS e-Government Technical
Committee on developing ICT standards for interoperability to support the
work of putting government services on-line.
Scope

The goal of the project is to help the rural people by providing single window
monitoring system. We use java to develop this web application. It contains
the schemes that are implemented by the government which will be useful
to them and it will reach to the desired persons as we add verifier to verify
the application that are submitted by the users and the approver views the
application and approves or rejects the application based on the criteria.
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

Advantages:

The following are the advantages of proposed system

 Easy to track the status of applications at any level at any point of

time
 Can generate required reports easily
 Easy to manage historical data in a secure manner
 Centralized database helps in avoiding conflicts
 Easy to use GUI that does not requires specific training.
Modules

The system after careful analysis has been identified to present itself with
the following modules:

Scheme Management Module:

This module provides user interface to add, edit, and delete various
government schemes. This module takes care of accepting various
applications from users and escalating those applications to DDO for
approval. In scheme management module available schemes list and
eligibility criteria for corresponding schemes details will be displayed in
schemes list, Eligibility details, how many members are already applied for
the schemes all these details will be displayed. Only the admin user can add
the details of users for the related schemes. He only the user to update or
delete the details of users from schemes list. All the remaining users can
view the details of schemes.

Panchayat Management Module:

This module provides facility to add or delete or edit various panchayats.

Also provides interface to view the status of applications at panchayat level.
Provides an interface to accept/reject applications at panchayat level itself.
In panchayat management module all the available panchayaties will be
displayed in panchayaties list. Every panchayat has its own ID. This list
contains details of all the panchayaties means panchayat ID, Name, district
ID, name of the GPO, population of the corresponding panchayat, how many
literates and illiterates are living there in that panchayat, how many families
are living with BPL(Below Poverty Line), their occupation all these details will
be included. Only the admin user can add the new panchayaties. He is only
the user to update or delete the panchayaties from the list. Remaining users
can view the details of all the panchayaties.

Administration module:

This module provides administrators to add/remove users and assign various

access rights to them. This module contains all the adding and removing
functions. This module contains all the users’ details, panchayaties details,
schemes details, and district details. The administrator can add / update or
remove any of the above functions. The administration module having
authority to add or update the details of all the above mentioned functions.
This module maintains all the departments. Each and every user should be
created by administrator. He can maintain all the departments. Applications
of the eligible users and available schemes will be added by administrator.

Reporting module:

In this module we can see various types of reports like scheme wise report,
panchayat wise report, and user wise report. Various reports like Approved
applications, Pending applications and Rejected applications at different
levels panchayat wise as well as user wise. Name of the scheme, eligibility
for the scheme and maximum strength of the scheme all these details will be
included in scheme wise report. Name of the panchayat and in which district
it will be located all the details will be added in panchayat wise report.
Application ID, name of the applicant, scheme ID, panchayat ID, status of
the application all these details will be included in user wise applications
report. Status of the application and any remarks information will be
displayed in approved applications report. All the rejected applications report
will be placed in the rejected applications report.
Software Development Life Cycle

Software Development Life Cycle, SDLC for short, is a well-defined,

structured sequence of stages in software engineering to develop the
intended software product.

Software Development Paradigm:

The software development paradigm helps developer to select a strategy to

develop the software. A software development paradigm has its own set of
tools, methods and procedures, which are expressed clearly and defines
software development life cycle. A software development paradigms or
process models are defined as follows:

Spiral Model

Spiral model is a combination of both, iterative model and one of the SDLC
model. It can be seen as if you choose one SDLC model and combine it with
cyclic process (iterative model).
This model considers risk, which often goes un-noticed by most other
models. The model starts with determining objectives and constraints of the
software at the start of one iteration. Next phase is of prototyping the
software. This includes risk analysis. Then one standard SDLC model is used
to build the software. In the fourth phase of the plan of next iteration is
prepared.
SDLC Implementation

SDLC provides a series of steps to be followed to design and develop a

software product efficiently. SDLC framework includes the following steps:
Requirement Gathering

This step onwards the software development team works to carry on the
project. The team holds discussions with various stakeholders from problem
domain and tries to bring out as much information as possible on their
requirements. The requirements are contemplated and segregated into user
requirements, system requirements and functional requirements. The
requirements are collected using a number of practices as given -

 studying the existing or obsolete system and software,

 conducting interviews of users and developers,
 referring to the database or
 Collecting answers from the questionnaires.
Feasibility Study

After requirement gathering, the team comes up with a rough plan of

software process. At this step the team analyzes if a software can be made
to fulfill all requirements of the user and if there is any possibility of software
being no more useful. It is found out, if the project is financially, practically
and technologically feasible for the organization to take up. There are many
algorithms available, which help the developers to conclude the feasibility of
a software project.

Types of Feasibility Study:

The feasibility study mainly concentrates on bellow five mentioned areas.

Among this Economic Feasibility Study is most important part of the
feasibility analysis and Legal Feasibility Study is less considered feasibility
analysis.

Technical Feasibility:

In Technical Feasibility current resources both hardware software along with

required technology are analyzed/assessed to develop project. This technical
feasibility study gives report whether there exists correct required resources
and technologies which will be used for project development. Along with
this, feasibility study also analyzes technical skills and capabilities of
technical team, existing technology can be used or not, maintenance and
up-gradation is easy or not for chosen technology etc.
Operational Feasibility:

In Operational Feasibility degree of providing service to requirements is

analyzed along with how much easy product will be to operate and
maintenance after deployment. Along with this other operational scopes are
determining usability of product, Determining suggested solution by software
development team is acceptable or not etc.

Economic Feasibility:

In Economic Feasibility study cost and benefit of the project is analyzed.

Means under this feasibility study a detail analysis is carried out what will be
cost of the project for development which includes all required cost for final
development like hardware and software resource required, design and
development cost and operational cost and so on. After that it is analyzed
whether project will be beneficial in terms of finance for organization or not.

Legal Feasibility:

In Legal Feasibility study project is analyzed in legality point of view. This

includes analyzing barriers of legal implementation of project, data
protection acts or social media laws, project certificate, license, copyright
etc. Overall it can be said that Legal Feasibility Study is study to know if
proposed project conform legal and ethical requirements.
Schedule Feasibility:

In Schedule Feasibility Study mainly timelines/deadlines is analyzed for

proposed project which includes how many times teams will take to
complete final project which has a great impact on the organization as
purpose of project may fail if it can’t be completed on time.
System Analysis

At this step the developers decide a roadmap of their plan and try to bring
up the best software model suitable for the project. System analysis includes
Understanding of software product limitations, learning system related
problems or changes to be done in existing systems beforehand, identifying
and addressing the impact of project on organization and personnel etc. The
project team analyzes the scope of the project and plans the schedule and
resources accordingly.

Requirements analysis:

It is very critical process that enables the success of a system or software

project to be assessed. Requirements are generally split into two types:
Functional and Non-functional requirements.
Functional Requirements:

These are the requirements that the end user specifically demands as basic
facilities that the system should offer. All these functionalities need to be
necessarily incorporated into the system as a part of the contract. These are
represented or stated in the form of input to be given to the system, the
operation performed and the output expected. They are basically the
requirements stated by the user which one can see directly in the final
product, unlike the non-functional requirements.

 registration
 login
 add verifier
 add approver
 view verifier
 view approver
 delete verifier
 delete approver
 add scheme
 edit scheme
 delete scheme
 apply for scheme
 view application
 verify application
 view verified application
 approve application
 reject application
 view application status
 logout
Non-functional requirements:

These are basically the quality constraints that the system must satisfy
according to the project contract. The priority or extent to which these
factors are implemented varies from one project to other. They are also
called non-behavioral requirements.

They basically deal with issues like:

 Portability
 Security
 Maintainability
 Reliability
 Scalability
 Performance
 Reusability
 Flexibility
Software and Hardware Requirements

Hardware Requirements

 Processor : I3.
 Ram : 4GB.
 Hard Disk : 500 GB.

Software Requirements:

 Database Server : Mysql

 Database Client : Sql yog
 Server : Apache Tomcat
 Platform : Java
 Technology : Servlets, JSP, JDBC
 Client Side Technologies : Html, CSS, Java Script
 IDE : Eclipse
 Uml Design/E-R Modeling Tools : Rational Rose, Sql-Developer
 Testing : Junit
Software Design

Next step is to bring down whole knowledge of requirements and analysis on

the desk and design the software product. The inputs from users and
information gathered in requirement gathering phase are the inputs of this
step. The output of this step comes in the form of two designs; logical
design and physical design. Engineers produce meta-data and data
dictionaries, logical diagrams, data-flow diagrams and in some cases pseudo
codes.
Architectural Design:

MVC stands for Model View and Controller. It is a design

pattern that separates the business logic, presentation
logic and data.
MVC Structure has the following three parts :

Controller acts as an interface between View and Model.

Controller intercepts all the incoming requests.

Model represents the state of the application i.e. data. It

can also have business logic.

View represents the presentation i.e. UI (User Interface).

Advantage of MVC Architecture

1. Navigation Control is centralized
2. Easy to maintain the large application
Data Flow Diagram:

Also known as DFD, Data flow diagrams are used to graphically represent
the flow of data in a business information system. DFD describes the
processes that are involved in a system to transfer data from the input to
the file storage and reports generation.

Data flow diagrams can be divided into logical and physical. The logical data
flow diagram describes flow of data through a system to perform certain
functionality of a business. The physical data flow diagram describes the
implementation of the logical data flow.
UML Design

Unified Modeling Language (UML) is a general purpose modeling language.

The main aim of UML is to define a standard way to visualize the way a
system has been designed. It is quite similar to blueprints used in other
fields of engineering.

UML is not a programming language; it is rather a visual language. We use

UML diagrams to portray the behavior and structure of a system, UML helps
software engineers, businessmen and system architects with modeling,
design and analysis. The Object Management Group (OMG) adopted Unified
Modeling Language as a standard in 1997. It’s been managed by OMG ever
since. International Organization for Standardization (ISO) published UML as
an approved standard in 2005. UML has been revised over the years and is
reviewed periodically.

Do we really need UML?

 Complex applications need collaboration and planning from multiple

teams and hence require a clear and concise way to communicate
amongst them.
 Businessmen do not understand code. So UML becomes essential to
communicate with non programmer’s essential requirements,
functionalities and processes of the system.
 A lot of time is saved down the line when teams are able to visualize
processes, user interactions and static structure of the system.
 UML is linked with object oriented design and analysis. UML makes the
use of elements and forms associations between them to form
diagrams. Diagrams in UML can be broadly classified as:
The Primary goals in the design of the UML are as follows:
 Provide users a ready-to-use, expressive visual modeling Language so
that they can develop and exchange meaningful models.
 Provide extendibility and specialization mechanisms to extend the core
concepts.
 Be independent of particular programming languages and development
process.
 Provide a formal basis for understanding the modeling language.
 Encourage the growth of OO tools market.
 Support higher level development concepts such as collaborations,
frameworks, patterns and components.
 Integrate best practices.

Types of UML Diagrams:

Structural Diagrams:

Capture static aspects or structure of a system. Structural Diagrams

include: Component Diagrams, Object Diagrams, Class Diagrams and
Deployment Diagrams.

Behavior Diagrams:

Capture dynamic aspects or behavior of the system. Behavior

diagrams include: Use Case Diagrams, State Diagrams, Activity
Diagrams and Interaction Diagrams.
The image below shows the hierarchy of diagrams according to UML
USE CASE DIAGRAM:

A use case diagram in the Unified Modeling Language (UML) is a type of

behavioral diagram defined by and created from a Use-case analysis. Its
purpose is to present a graphical overview of the functionality provided by a
system in terms of actors, their goals (represented as use cases), and any
dependencies between those use cases. The main purpose of a use case
diagram is to show what system functions are performed for which actor.
Roles of the actors in the system can be depicted.
CLASS DIAGRAM:

In software engineering, a class diagram in the Unified Modeling Language

(UML) is a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, operations (or
methods), and the relationships among the classes. It explains which class
contains information.
SEQUENCE DIAGRAM:

A sequence diagram in Unified Modeling Language (UML) is a kind of

interaction diagram that shows how processes operate with one another and
in what order. It is a construct of a Message Sequence Chart. Sequence
diagrams are sometimes called event diagrams, event scenarios, and timing
diagrams.
ACTIVITY DIAGRAM:

Activity diagrams are graphical representations of workflows of stepwise

activities and actions with support for choice, iteration and concurrency. In
the Unified Modeling Language, activity diagrams can be used to describe
the business and operational step-by-step workflows of components in a
system. An activity diagram shows the overall flow of control.
Deployment diagram

There may be more steps involved, depending on what specific requirements

you have, but below are some of the main steps:
Entity-Relationship Diagrams:

ER-modeling is a data modeling method used in software engineering to

produce a conceptual data model of an information system. Diagrams
created using this ER-modeling method are called Entity-Relationship
Diagrams or ER diagrams or ERDs.

Purpose of ERD
 The database analyst gains a better understanding of the data to be
contained in the database through the step of constructing the ERD.
 The ERD serves as a documentation tool.
 Finally, the ERD is used to connect the logical structure of the
database to users. In particular, the ERD effectively communicates the
logic of the database to users.

E-R Diagram:
Database Tables: