A

Project Report
on
”E-Grampanchayat System”

At
Mwell Software Solution
Submitted By:
Mahesh Prabhakar Patil

To

Institute of Management Research &

Development, Shirpur
KBC North Maharashtra University, Jalgaon

Guided By:
Prof. Amit Patil

In the partial fulfillment of the requirement for the award of

the degree of Integrated Master of Computer Application

2022-23
 R. C. Patel Educational Trust’s

R. C. Patel Institute of Managment

Research & Development
Shirpur, Dist-Dhule 425405
—————————————————————————–

CERTIFICATE

This is to certify that Mr. Mahesh Prabhakar Patil, a final year

student of ’Integrated Master of Computer Application’ from

Institute of Management Research & Development, Shirpur has

successfully completed the project entitled ”E-Grampanchayat

System” as a part of academic six month industrial training which

is approved for degree of Integrated Master of Computer Application

a post graduate course of ’KBC North Maharashtra

University, Jalgaon’ during acadmic year 2022-23.

Director Examiner
RCP IMRD,
Shirpur
 Acknowledgement

I take this opportunity to express my sincere thanks to Mwell Software Solu-

tion for providing me an opportunity to work in the organization. I also express
my gratitude to Mr. M. S. Patil (Project Manager And Team Leader).
for their valuable guidance and experienced suggestion, encouragement and support
extended by them helped me in various stages where I needed help and suggestions.
His prudent ideas of work, keen interest in developing the system and constant effort
were a great source of inspiration for me. He not only guided us on the technical
aspect but his acknowledgement of marketing strategies helped us in broadening our
perspective.

I am thankful to Dr. Vaishali Patil. (Director), Prof. M. N. Behere

(Head Dept.of MCA), and Prof. Amit Patil (Project Guide), R. C. Pa-
tel Institute of Management Research and Development, Shirpur, for giving me his
valuable guidance and encouragement during our course. I am thankful to the col-
lege staff for their constant encouragement.
Last but not least, I am thankful to all people who directly or indirectly contributed
to make this project a success.

Thanks & Regards

Mahesh Prabhakar Patil
 Contents

1 Introduction 1
1.1 Company Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Services Offered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 E-Grampanchayat System . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3.1 Need And Motivation . . . . . . . . . . . . . . . . . . . . . . . 3
1.3.2 Detailed Problem Definition . . . . . . . . . . . . . . . . . . . 3
1.3.3 Scope of Work . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.4 Benefits of Proposed System . . . . . . . . . . . . . . . . . . . 6

2 System Requirement Analysis 7

2.1 System Requirement Analysis . . . . . . . . . . . . . . . . . . . . . . 7
2.1.1 Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.2 Need of New System . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Software Process and Development . . . . . . . . . . . . . . . . . . . 10
2.3 Technical Specification . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3.1 Technology Used . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Feasibility Study 14
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 Factors of Feasibility Study (TELOS) . . . . . . . . . . . . . . . . . . 14
3.2.1 Technology and System Feasibility . . . . . . . . . . . . . . . 15
3.2.2 Financial and Economical Feasibility . . . . . . . . . . . . . . 15
3.2.3 Operational Feasibility . . . . . . . . . . . . . . . . . . . . . . 15
3.2.4 Legal Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.5 Schedule Feasibility . . . . . . . . . . . . . . . . . . . . . . . . 16

4 Proposed System 17
4.1 Proposed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 User Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3 Objective of the System . . . . . . . . . . . . . . . . . . . . . . . . . 18

5 Preliminary Design 19
5.1 Tools of data flow strategy . . . . . . . . . . . . . . . . . . . . . . . . 19

i
 5.2 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.3 Entity Relationship Diagram . . . . . . . . . . . . . . . . . . . . . . . 20
5.4 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6 Detailed Design 24
6.1 Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.2 Input and Output Design . . . . . . . . . . . . . . . . . . . . . . . . 25
6.2.1 Screenshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.3 Database structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7 Testing 34
7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.1.1 White Box Testing . . . . . . . . . . . . . . . . . . . . . . . . 34
7.1.2 Black Box Testing . . . . . . . . . . . . . . . . . . . . . . . . 35
7.1.3 Validation Testing . . . . . . . . . . . . . . . . . . . . . . . . 35
7.1.4 GUI Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.2 TESTING METHODOLOGY . . . . . . . . . . . . . . . . . . . . . . 36
7.3 TEST CASES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

8 Concluding Remarks 38
8.1 Strengths of System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
8.2 Limitations of system . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
8.3 Scope for future development . . . . . . . . . . . . . . . . . . . . . . 39
8.4 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

ii
Chapter 1

Introduction

1.1 Company Profile

Mwell Software Solution provides all media services and solutions. The com-
pany is working in many sectors like web developing, graphic designing, internet
marketing, etc. We try hard to deliver superior quality and cost effective software
development solutions to our clients on-time and giving quality outputs to complete
customer expectations. Our mission is to enhance the customer satisfaction through
providing quality software development services with a team of experienced software
developers, who have won the trustworthiness from our clients.

1.2 Services Offered

Website Development
Company have been providing website development from last 2 years and during
we have established competitive foundation. Company developing new websites at
various platforms like .net, java, python, etc. Mwell Software Solutions helps to
optimize their business processes. Company also working in various websites de-
velopment projects. Company has aim to provide unique, innovative fastest web
solutions in India abroad.

1
 Mwell Software Solution

Software Development
Mwell Software Solutions believes that software development should not be re-
stricted to code creation and project delivery. It is inclusive of an accurate com-
prehension of the requirement and business goals and, on the basis of this compre-
hension, recommendations of a cost-effective solution with a fine blend of technology.

Graphic Designing
This is one of the important activities of the Mwell Software Solutions. Now
days, Peoples are easily attracted by the colorful objects. Graphic designing is also
a important factor in to the web designing. There are several designs which we make
using graphic designing. The combination of graphic designing and web develop-
ing is makes a better combination to attract the peoples and grab a big audience.
These days web developing is not only remained for code efficiency and loading
speed. It also containing well designed websites to attract more and more audience,
and graphic designing improves website design a lot. Thats why graphic design is
also an important part of Mwell Software Solutions.

Web Hosting
The important and most overlooked aspect of site development is hosting. We
offer reliable, secure and super-fast hosting services. One of the most important
things to consider when choosing a good Web hosting company is uptime, and we
managed to get our hosting uptime at 99.9. We offer many hosting plans for small
businesses. We offer all time support for web hosting.

2
 Mwell Software Solution

1.3 E-Grampanchayat System

E-Grampanchayat is a web application that is specially designed to establish
an environment, wherein village public can easily communicate with the village
councils. Our application features: PDO and village public. PDO will handle the
whole website and manage the activities of users. PDO will update panchayat
services, application, payments and complaints filled by public. The village public
will register to the application and avail for the facilities. This post has complete
information of Smart E-Panchayat Project Documentation.

1.3.1 Need And Motivation

Our project is aimed at achieving the solution for the problems that are faced by
the public in villages. Through this application public can easily contact the PDO
regarding any issues such as availing for services, complaints filling. Bill payments,
application filling and feedbacks. The PDO can easily keep track on the village
problems and managements.

1.3.2 Detailed Problem Definition

Now a days people in the rural areas have to go to panchayat office in their
location to apply and get their certificates provided in that office. It requires a lot
of time and may result in work delay. The data in the office has to be maintained
manually. There is no security for the data and faults can be encountered during
entering the data mainly which require higher calculations. People also face so many
problems in their area. They complain to their respective ward members but they
may or may not respond quickly. There are many other problems in the present
day panchayat raj system. So, the E-Gram panchayat provides solutions to all the
problems in the current system. E-Gram Panchayat provides online service to the
people living in that area. All the services which are done manually are made online

3
 Mwell Software Solution

in the project. The people can about their panchayat, activities notifications and
all other information related their villages. All the applications and certificates are
applied and verified online. The users on the people in the village can complain about
their problem through online. Suggestions are also accepted from the people for the
development of their village. The user can request any application, suggestion,
and complaint at anywhere and at any time. The grampanchayat provide birth
Certificate, death certificate, domicile certificate, receipts for house tax, water tax
etc. They give order for construction of road, buildings, renewal of building. They
keep records of their monthly and yearly budge.

4
 Mwell Software Solution

1.3.3 Scope of Work

• To show the Grampanchayat’s profile and portfolio.

• To provide a user friendly system.
• To make a ’Smart Grampanchayat’.
• To facilitate speedy access to any particular details.
• To show all schemes running in grampanchayat.
• The people of village is get information on their mobile and computer at
home.

Improved services:
Grampanchayat have much more work to do. To improve speed of the services
of grampanchayat, An objective of the proposed system is to improve the existing
system’s services. The system contains additional services than existing system.

Better performance:
It is an objective of our proposed system to provide better performance which is
managed by providing desired flexibility, fast response, ability to support changes
and ability to maintain the quality of services.

Data Efficiency:
Grampanchayat have much more information to store. That’s why, One of the
objectives of the proposed system is to store more data with a efficiency. The system
allows user to access any data at a single click.

Efficient GUI:
System is has to be user friendly. One of the objectives of the proposed system
is to provide a user friendly GUI, that will enable the user to work on clicks and
make the information transfer possible with the most common I/O devices.

5
 Mwell Software Solution

1.3.4 Benefits of Proposed System

• To improve the work efficiency of grampanchayat.

• Quickly find out information of schemes, citizens, Documents, etc.
• To provide easy and faster access information.
• To provide user friendly environment for users.

Saves Time
No more time consuming paper work for Grampanchayat. The proposed system
saves more and more time of Grampanchayat Staff. Citizens also save their time to
get any type of document from grampanchayat.

Saves Money
Reduction of overhead cost involved in paperwork. It reduces the cost of services.

Fast and Efficient

Obviously, If any manual system is getting computerized, Then it will be time
saving. As compared to existing manual system, in proposed system the user can
get the information fast, easily and efficiently from the computer.

6
Chapter 2

System Requirement Analysis

2.1 System Requirement Analysis

The Software Requirement Specification is produced at the culmination of the
analysis task. The function and performance allocated to software as part of sys-
tem engineering are redefined by establishing a complete information description
as functional requirement, a representation of system behaviour, an indication of
performance requirement and design constraints, appropriate validation criteria.

Computerization
All the details regarding Grampanchayat, whether it is small or big, will be com-
puterized. All data and documents of Scheme is also computerized. No Redundant
Data As this management system will be centralized, the chances of the duplicate
data in the system are close to nil.

Automation
The automation feature of this management system will mitigate the task of
writing the papers. E.g. there is no need to write the letter to grampanchayat if
you need any document. You can go directly on website and ask for document by
sending request in simple interface.

7
 Mwell Software Solution

Easy Interaction
The proposed system is make the communication easy between grampanchayat
and citizens. Citizens can visit on system any time and ask for appropriate help. As
a matter of fact, it will be easier for each individual person who is associated with
the system to be in touch as per needed.

2.1.1 Existing System

The existing system is a manual paper work system. All the work is done man-
ually. It is time consuming. All work is required a man power. Payments was also
made manually.
Drawbacks of the existing system:
• The existing system is stand alone system.
• Report generation are also done manually.
• User does not view the detail of the entire plan together.
• Email service is not available
• Mobile message is not available
• No reminder for payments for taxes of grampanchayat.
• Online payment system is not available.
• It is too much time consuming.

8
 Mwell Software Solution

2.1.2 Need of New System

User friendly
This system provides user friendliness. Because in the existing system register
work was very difficult to handle. The manual paperwork is too much complicated
and time consuming. Our proposed system solve these problems.

Data Security
The proposed system will also prevent unauthorized access to enter in the system.
At the very beginning, the administrator enters the user name and password and
checks the permission to use that software. All other data regarding schemes is also
secured.

Data redundancy
System is avoid duplicate data entries. The data is stored only once. Which can
be accessed at any time and at any place. So it can be minimized but cannot be
removed completely. System reduces duplicate entries to reduce storage usage.

Easy to access
Data can be accessed easily. Searching or getting information of a particular is
easy. Once authorised user enters in the system, it is easy to access any data.

Cost Reduction
It requires less amount of cost as compared to existing system. All the cost of
paperwork is reduced. Papers are required only for report generations.

Security mechanism
All data is secured. Database can be secured by applying password in encryption
and decryption techniques. All data stored in the system is secured. The system
prevents unauthorised users to enter in it.

9
 Mwell Software Solution

2.2 Software Process and Development

The software engineering process can be viewed as a spiral. Initially system
engineering defines the role of software and leads to software requirement analysis
where the information domain, functions, behaviour, performance, constraints and
validation criteria for software are established. Moving inward along the spiral, we
come to design and finally to coding. To develop computer software we spiral in
along streamlines that decrease the level of abstraction on each turn.
Waterfall model
The Waterfall Model was the first Process Model to be introduced. It is also
referred to as a linear-sequential life cycle model. It is very simple to understand and
use. In a waterfall model, each phase must be completed before the next phase can
begin and there is no overlapping in the phases. The Waterfall model is the earliest
SDLC approach that was used for software development. The waterfall Model illus-
trates the software development process in a linear sequential flow. This means that
any phase in the development process begins only if the previous phase is complete.
In this waterfall model, the phases do not overlap.

10
 Mwell Software Solution

Waterfall approach was first SDLC Model to be used widely in Software En-
gineering to ensure success of the project. In ”The Waterfall” approach, the whole
process of software development is divided into separate phases. In this Waterfall
model, typically, the outcome of one phase acts as the input for the next phase
sequentially..

2.3 Technical Specification

• Hardware Specification
Processor : Min. Pentium 3
RAM : Min. 2 GB
Hard Disk : Min. 20 GB free

• Software Specification
Platform : Windows 7 or above
Languages : HTML, CSS, Bootstrap, Javascript, Jquery, PHP
Database : MYSQL
Server : Xamp+Apache Server
Framework : Bootstrap

11
 Mwell Software Solution

2.3.1 Technology Used

Waterfall Model
All these phases are cascaded to each other in which progress is seen as flowing
steadily downwards (like a waterfall) through the phases. The next phase is started
only after the defined set of goals are achieved for previous phase and it is signed
off, so the name ”Waterfall Model”. In this model, phases do not overlap

Requirement Gathering and analysis

All possible requirements of the system to be developed are captured in this phase
and documented in a requirement specification document.

System Design
springs asynchronous, no blocking architecture means you can get more from your
computing resources.

Implementation
With inputs from the system design, the system is first developed in small pro-
grams called units, which are integrated in the next phase. Each unit is developed
and tested for its functionality, which is referred to as Unit Testing.

Integration and Testing

All the units developed in the implementation phase are integrated into a system
after testing of each unit. Post integration the entire system is tested for any faults
and failures.

12
 Mwell Software Solution

Deployment of system
Once the functional and non-functional testing is done; the product is deployed
in the customer environment or released into the market.

Maintenance
There are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.

13
Chapter 3

Feasibility Study

3.1 Introduction
After doing the project E-Grampanchayat System, study and analysing all the
existing or required functionalities of the system, the next task is to do the feasibility
study for the project. All projects are feasible-given unlimited resources and infinite
time. Feasibility study includes consideration of all the possible ways to provide
a solution to the given problem. The proposed solution should satisfy all the user
requirements and should be flexible enough so that future changes can be easily
done based on the future upcoming requirements. There are many different types
of feasibility. Such as Economical Feasibility, Technical Feasibility, Operational
Feasibility, Schedule Feasibility and Legal Feasibility.

3.2 Factors of Feasibility Study (TELOS)

There are many factors of feasibility study. But the ’TELOS’ is the some impor-
tant factors int the feasibility study. The acronym TELOS refers to the five areas
of feasibility - Technical, Economic, Legal, Operational, and Scheduling.

14
 Mwell Software Solution

3.2.1 Technology and System Feasibility

It is included the study of function, performance and constraints that may affect
the ability to achieve an acceptable system. For this feasibility study, we studied
complete functionality to be provided in the system, as described in the system Re-
quirement specification, and checked if everything was possible using different type
of frontend and backend platforms In this we determine whether it is possible to
develop the system within available equipment, available software technology and
manpower.

3.2.2 Financial and Economical Feasibility

In this the benefit of system are considered. Actually, cost benefit analysis is
done. Since, Visual Studio and SQL Server are easily available; development cost
can be kept minimum. Therefore the system is economically feasible.

3.2.3 Operational Feasibility

No doubt the proposed system is fully GUI based that that is very user friendly
and all inputs to be taken all self-explanatory even to a layman. Besides, a proper
training has been conducted to let know the essence of the system to the users
so that they feel comfortable with new system. As far our study is concerned the
clients are comfortable and happy as the system has cut down their loads and doing.

3.2.4 Legal Feasibility

In this operationally implementation cost of the system is considered. After

implementing it the cost of the training programs as well space requirement for im-
plementation of the system and the other assets are considered in it.

15
 Mwell Software Solution

In our system reviewer can easily understand the actual system so training is not
required and implementation is also easy. Therefore our system is operationally
feasible.

3.2.5 Schedule Feasibility

A project will fail if it takes too long to be completed before it is useful. Typically
this means estimating how long the system will take to develop, and if it can be
completed in a given time period using some methods like payback period. Schedule
feasibility is a measure of how reasonable the project timetable is. Given our techni-
cal expertise, are the project deadlines reasonable? Some projects are initiated with
specific deadlines. You need to determine whether the deadlines are mandatory or
desirable.

16
Chapter 4

Proposed System

4.1 Proposed System

The development of this system contains many proposed activities. Some of these
are following activities :
• This entire website is helping public to reach out the Grampanchayat easily.
• It also helping public to get the required data or documents as per their exact
need.
• All the data of the running projects is shown on the website.
• If there are any new schemes coming, then it will displayed it on the website.
• Relationship between grampanchayat and public is getting better by the web-
site.
Grampanchayat is also showing all their running projects and schemes, which they
are running for to help the public. So the public is know how the grampanchayat is
doing their work transparently and efficiently.

17
 Mwell Software Solution

4.2 User Privileges

A profile contains user permissions and access setting that control what users
can do within their organization. The user type determines the privileges that the
user has within E-Grampanchayat System.

• Login

• View Scheme Information.

• View Tax Details.

• View Citizen Information.

• Generate Reports.

• Mange Schemes.

• Village Profile/Portfolio Management.

4.3 Objective of the System

• Fast technology.
• Graphical user Interface.
• Extremely flexible.
• Efficient Performance.
• Easy and Simple to Handle.
• Easy integration and compatibility.

18
Chapter 5

Preliminary Design

A data-flow diagram is a way of representing a flow of data through a process or a

system (usually an information system). The DFD also provides information about
the outputs and inputs of each entity and the process itself. A data-flow diagram
has no control flow. There are no decision rules and no loops. Specific operations
based on the data can be represented by a flowchart. For each data flow, at least
one of the endpoints (source and / or destination) must exist in a process. The
refined representation of a process can be done in another data-flow diagram, which
subdivides this process into sub-processes.

5.1 Tools of data flow strategy

Data flow analysis makes use of the following tools:
Use Case Diagram
Data Flow Diagrams
Enity Relationship Diagram (ER-Diagram)

19
 Mwell Software Solution

5.2 Use Case Diagram

A use case diagram at its simplest is a representation of a user’s interaction with
the system that shows the relationship between the user and the different use cases
in which the user is involved.

Usecase Diagram :

5.3 Entity Relationship Diagram

Entity Relationship Diagram, also known as ERD, ER Diagram or ER model, is
a type of structural diagram for use in database design. An ERD contains differ-
ent symbols and connectors that visualize two important information: The major
entities within the system scope, and the inter relationships among these entities.
Common Entity Relationship Diagram Symbols Entities: It is represented by rect-
angles. An entity is an object or concept about which you want to store information.
Entity-Relationship model is a type of database model based on the notion of real

20
 Mwell Software Solution

world entities and relationship among them. We can map real world scenario onto
ER database model. ER Model creates a set of entities with their attributes, a set
of constraints and relation among them.

ERD

5.4 Data Flow Diagram

Data Flow Diagrams represent one of the most ingenious tools used for struc-
tured analysis. A Data Flow Diagram or DFD as it is shortly called is also known as
a bubble chart. It has the purpose of clarifying system requirements and identifying
major transformations that will become programs in System design.
A DFD consists of a series of bubbles joined by lines. The bubble represents data
transformation and lines represent data flow in the system. In the normal conven-
tion, a DFD has four major symbols:
Square, which defines source or destination of data

21
 Mwell Software Solution

Arrow,which shows data flow

Circle, which represents a process that transforms incoming data into outgoing flow
Open rectangle, which shows a data store

Fig. 0 Level DFD

22
 Mwell Software Solution

Fig. 1st Level DFD

23
Chapter 6

Detailed Design

Detailed design is the phase where the design is refined and plans, specifications
and estimates are created. Detailed design will include outputs such as 2D and 3D
models, cost build up estimates, procurement plans etc. This phase is where the full
cost of the project is identified.

6.1 Data Dictionary

Data dictionary is only collection of data element definition. Entries in a data
dictionary include the name of the data item and attributes.
A data dictionary is a file or a set of files that contains a databases metadata. In a
relational database, the metadata in the data dictionary includes the following:
• Names of all tables in the database and their owners.
• Names of all indexes and the columns to which the tables in those indexes relate.
• Constraints defined on tables, including primary keys, foreign-key relationships
to other tables, and not-null constraints.

24
 Mwell Software Solution

6.2 Input and Output Design

Input Design
It is the process of converting user inputs into computer-based format. The
project requires a set of information from the user to prepare a report. In order
to prepare a report, well-organized input data are needed. In the system design
phase, the expanded DFD identifies logical data flow, data stores and destination.
Input data is collected and organized into groups of similar data. The goal behind
designing input data is to make the data entry easy and make it free from logical
errors. The input entry to all type of clients is the user name and password only. If
they are valid the client is allowed to enter into the software.
Output Design
One of the most important features of a system for user is the output it produces.
Output design should improve the systems relationship with the user and help in
decision making. Computer output is a process that involves designing necessary
output that have to be given to various users according to their requirements. Ef-
ficient, intelligible output design should improve the system relationship with the
user and help in decision making. A major form of output is the hard copy from
the printer. The output devices are selected by considering the response time re-
quirements, print quickly etc. The print formats and editing for the final printout
are very much considered during output design.

25
 Mwell Software Solution

6.2.1 Screenshot

Homepage

Sign in Option

26
 Mwell Software Solution

User Login Form

User Dashboard

27
 Mwell Software Solution

View Application Details - User Side

View Application Details - User Side

28
 Mwell Software Solution

Certificate Detail - Birth Certificate

Birth Registration Menu

29
 Mwell Software Solution

Birth Registration Details

Print Birth Certificate

30
 Mwell Software Solution

6.3 Database structure

tbl user : This table stores all the basic information about users.

Field Name Data Type size Constraints

Id bigint 20 Primary Key,auto increment
first Name varchar 50 NOT NULL.
middle name char 50 NOT NULL.
last name char 50 NOT NULL.
address name varchar 50 NOT NULL.
email varchar 25 NOT NULL
mobile number varchar 25 NOT NULL.
dob date - NOT NULL.
is deleted enum(0,1) - 0.

Table 6.1: user table

tbl birth certi : This table stores all the basic information about birth certificate
details.

Field Name Data Type size Constraints

Application id bigint 20 Primary Key,auto increment
first name varchar 100 NOT NULL
middle name varchar 100 NOT NULL
last name varchar 100 NOT NULL
address email varchar 100 NOT NULL.
contact phone varchar 50 NOT NULL.
dob date - NOT NULL
is deleted enum(0,1) - 0.

Table 6.2: Birth Certificate Table

31
 Mwell Software Solution

tbl feedback: This table stores all the basic information about Feedback/complaint
details.

Field Name Data Type size Constraints

complaint Id bigint 20 Primary Key,auto increment
subject varchar 50 NOT NULL.
feedback varchar 200 NOT NULL.
post table int 50 NOT NULL.
user id int 50 NOT NULL.

Table 6.3: Feedback/Complaint Table

tbl death certi : This table stores all the basic information about Death Certifi-
cate details.

Field Name Data Type size Constraints

Application id bigint 20 Primary Key,auto increment
first name varchar 100 NOT NULL
middle name varchar 100 NOT NULL
last name varchar 100 NOT NULL
place death varchar 50 NOT NULL.
address email varchar 100 NOT NULL.
dod date - NOT NULL
is deleted enum(0,1) - 0.

Table 6.4: Death Certificate Table

32
 Mwell Software Solution

tbl tax pay : This table stores all the basic information about Tax payments.

Field Name Data Type size Constraints

bill id bigint 20 Primary Key,auto increment
bill no varchar 20 NOT NULL
Txn id varchar 20 NOT NULL
bill type varchar 20 NOT NULL
user id int - NOT NULL.
amount int - NOT NULL.

Table 6.5: Tax payment bill

33
Chapter 7

Testing

7.1 Introduction
Testing is a process of executing error. It is an important and critical stage in
software development. It plays an important role in determining the quality and
reliability of the application. With this process, several test cases are devised. A
test case means a set of data that the system will process as the normal input.
Testing also adds value to the product by conforming the user requirements. Testing
verifies that this software deliverable conforms precisely to the functional and design
specification that have been compiled during analysis and design phases. A good
test case is one that has a high portability of finding an undiscovered error. Testing
involves a series of operation of a system or application under controlled conditions
and subsequently evaluating results. The controller conditions should include both
normal and abnormal conditions. It is planned and monitors for each testing level.

7.1.1 White Box Testing

This testing reveals the internal working of the code i.e. each of the program-
ming elements is exercised properly. The white box testing for the proposed website
focuses on the control structure and it is also called clear box testing. Test cases

34
 Mwell Software Solution

for the proposed system are designed to ensure that all statements in the program
have executed at least once during testing and that all logical conditions have been
exercised. White box testing is small implying that this test is typically applied to
small components. White-box testing is the detailed investigation of internal logic
and structure of the code. White-box testing is also called glass testing or open-box
testing. In order to perform white-box testing on an application, a tester needs to
know the internal workings of the code.

7.1.2 Black Box Testing

It is the testing process in which tester can perform testing on an application

without having any internal structural knowledge of application. Usually Test En-
gineers are involved in the black box testing. In black box, the structure of the
program is not considered.Here, the tester only knows the inputs that can be given
to the system and what output the system should give. This form of testing is
called functional or behavioural testing. Tester give inputs to the form and check-
ing the reports that are generated as a output are proper or not. The technique
of testing without having any knowledge of the interior workings of the applica-
tion is called black-box testing. The tester is oblivious to the system architecture
and does not have access to the source code. Typically, while performing a black-
box test, a tester will interact with the system’s user interface by providing inputs
and examining outputs without knowing how and where the inputs are worked upon.

7.1.3 Validation Testing

Valid data must be in output i.e. report. At the culmination of black box testing,
website is completely assembled. Interfacing errors have been uncovered and cor-
rected and final series of test, i.e, validation test is defined with a simple definition
that validation succeeds when website functions in a manner that can be reasonably

35
 Mwell Software Solution

accepted by a customer. The proposed system validated as each entry by advo-

cate must be tested. Each control is tested by putting input in all the way and
determine what appropriate message given by system. Validation testing has been
implemented and successfully tested. This is conducted by the Quality Assurance
Team who will gauge whether the application meets the intended specifications and
satisfies the client’s requirement.

7.1.4 GUI Testing

The criterion of the user interface is graphical which is less time consuming for
user but more complexes for the programmer. GUI testing is defined as the process
of testing, In which the system’s Graphical User Interface is Under Testing. The
proposed system involves checking the screens with the controls like menus, buttons,
icons, and all types of bars - tool bar, menu bar, dialogue boxes, etc. A user does
not see the source code, Ony the user interface is visible to the user..

7.2 TESTING METHODOLOGY

To be truly robust, distributed applications require more than simple functional
testing before release into production. At least one and preferably all of the following
types of testing before releasing application to customers should be performed.
• Performance Testing
• Load Testing
• Stress Testing
• Endurance Testing

36
 Mwell Software Solution

7.3 TEST CASES

Purpose
The main purpose of test cases is that the system should flow as it has been
made, even if user puts inputs in a wrong manner the output generated will give
error. The flow of the system should go as it is defined by the developer.
Required Input
There are many inputs in the forms which cannot be explained here as it will be
too lengthy to give explanation of each and every input. But the expected validations
are kept so user will not be able to encounter any problem in the system.
Expected Result
The result would be expected as per the system is made by the developer. The
system is robust so even if user tries to put value other than expected value, vali-
dations are kept at each and every point so the output will be positive in each and
every case.

37
Chapter 8

Concluding Remarks

8.1 Strengths of System

• Platform independent. • Saves time and efforts. • Easy to maintain and
user-friendly. • Reduces paper work. • Reduces overload on PDO and public.
• Authenticated through username and password. • System is easy to use.
• System has a user friendly GUI.
• User satisfy to got various Reports as he want.
• Quickly find out information of Student, Staff, other details.
• Cost Reduction and secure.
• To provide easy and faster access information.

8.2 Limitations of system

The only limitation of the system is that the system is not fully automated. The
limited scope of current System doesn’t fully encompass the current system. If in
future the data set increases then this will affect the speed of the system.

38
 Mwell Software Solution

8.3 Scope for future development

There are future enhancement that can be made in the system.
• Public and PDO communication module can be implemented in this project. •
Indira Avas Yojana module can be implemented in this project. • Website cus-
tomization through GUI. • We can apply technologies like data mining, machine
learning to manage and sort data appropriately.

8.4 Conclusion
It has been a great pleasure for me to work on this exciting and challenging
project. This project proved good for us as it provided practical knowledge of
not only programming in J2EE and Oracle Server Developer working of web based
application, but also about all handling procedure related with Advance and new
technology. It also provides knowledge about the latest technology used in develop-
ing web enabled application and client server technology that will be great demand
in future. This will provide better opportunities and guidance in future in develop-
ing projects independently. Overall, the system is useful for all the users to maintain
information at various levels. It connects supervisor and employee and thus easy
to maintain. Now supervisor can easily set the schedule or any notifications to the
respective employees without having a person to send to employees.

39
 References

Books Referred
• PHP 6 and MySQL 5 : Larry Ullman
• Code Ignitor for Rapid PHP Application Development : David Upton
• Pressman, Rogers Software Engineering: A Practitioners Approach 6th Edition,
Mass: McGraw-Hill Publication
• MySQL Cookbook : Paul DuBois

Websites Visited
The following websites proved to be very helpful during the development of the
system :
• www.w3schools.com
• www.codeproject.com
• www.getbootstrap.com
• www.github.com