A Project Report On
Church Management System
Submitted by
Mr. Tshering Namgyal Sherpa [20IT103010]
Under the supervision and guidance of
Ms. Hema Malini S
Assistant Professor
School Of Information Technology
SRM University Sikkim
Under the supervision and internship guidance of
Mr. Madhav Bhattarai
DemiSolution, Gangtok
In the partial fulfilment of requirements for the award of Degree in
Master of Computer Application
Batch 2020-2022
Submitted to the
SCHOOL OF INFORMATION TECHNOLOGY
SRM UNIVERSITY SIKKIM
Tandong, Gangtok, East Sikkim - 703102
DECLARATION
I
hereby
declare
that
the
work
recorded
in
this
project
report
entitled
Church
Management
System
in
partial
fulfilment
for
the
requirements
for
the
award
of
Degree
in
Master
of
Computer
Applications
from
SRM
University
Sikkim,
is
a
faithful
and
bonafide
work
carried
out
under
the
supervision
and
guidance
of
Ms.
Hema
Malini
S
Assistant
professor
from
4
May
2022
to
4th
August
2022.
The
results
of
this
investigation
reported
in
this
project
have
so
far
not
been
reported
for
any
other
Degree
or
other
technical
forum.
The
assistance
and
help
received
during
the
investigation
have
been
duly
acknowledged.
Mr.
Tshering
Namgyal
Sherpa
Reg.
No.
201T103010
CERTIFICATE OF ACCEPTANCE
This
is
to
certify
that
Mr.
Tshering
Namgyal
Sherpa
bearing
Registration
No.
201T103010
of
School
of
Information
Technology,
SRM
University
Sikkim
has
worked
on
the
project
entitled
Church
Management
System
under
the
supervision
of
Ms.
Hema
Malini
S
Assistant
professor,
School
of
Information
Technology,
Shri
Ramasamy
Memorial
University
Sikkim.
The
project
was
carried
out
from
4h
May
to
4n
August.
The
project
is
hereby
accepted
by
the
School
of
Information
Technology,
SRM
University
Sikkim,
in
partial
fulfilment
of
the
requirements
for
the
award
of
Degree
in
Master
of
Computer
Application.
Dr.
Om
Prakash
Sharma
HODIT)
School
of
Information
Technology
SRM
University
Sikkim
HEAD
OF
DEPARTMENT
SCHOOL
OF
INFORMATION
TECHNOLOGY
SRM
UNIVERSITY
SIKKIM
Certified
that
this
project
report
titled
Church
Management
System
is
the
bonafide
work
of
Mr.
Tshering
Namgyal
Sherpa
(201103010)
who
carried
out
the
research
under
my
supervision.
Certified
further,
that
to
the
best
of
my
knowledge
the
work
reported
herein
is
not
part
of
any
other
project
report
or
dissertation
based
on
which
a
degree
or
award
was
conferred
on
an
earlier
occasion
to
this
or
any
other
candidate.
BONAFIDE
CERTIFICATE
Submitted
for
the
viva-voce
examination
held
on
23d
August
2022
HOD-School of
IT
HEAD
OF
DEPARTMENT
SCHOOL
OF
INFORMATION
TECHNOLOGY
SRM
UNIVERSITY
SIKKIM
INTERNAL
EXAMINER
ASSOCIATE DEAN
GUIDE
EXTEKNAL
EXAMINER
ABSTRACT
Church Management System is developed for the Evangelical Presbyterian
Church of Sikkim (EPCS), to keep a record of all the EPCS church’s branches
scattered all over the Sikkim and members of every church (EPCS). Church
Management System helps the council of EPCS to keep trace of Churches
details and the member’s details. This web application is designed using PHP,
and MySQL as backend. HTML, CSS, Bootstrap, and JavaScript for Frontend.
It contains various modules. The expected outcome of this management system
is that the council members can easily keep the record of everyone that is a
member of the church under EPCS.
ACKNOWLEDGEMENT
First of all, I would like to thank my guide Assistant professor Ms. Hema Malini.
S for her invaluable patience and feedback who generously provided knowledge
and expertise in this journey of completion of this dissertation.
Secondly, I would also like to show gratitude to SRM University Sikkim and
the School of Information Technology, HOD Dr. Om Prakash Sharma R,
Project Coordinator Ms. Sabna Sharma Assistant Professor for giving me such
an opportunity and encouraging us.
Thirdly I would also like to acknowledge my intern company (DemiSolution)
for boarding me in, Mr. Madhav Bhattarai who supported me relentlessly and
motivated me under his supervision throughout the intern period. Relentlessly
Last but not least I must express my very profound gratitude to friends, family
and everyone involved throughout this journey who supported me financially
and emotionally.
TABLE OF CONTENT
TITLE
Title
Page No
Chapter 1 Introduction
1
Overview
1
About the company
1
Training undergone
2
Existing System
2
Chapter 2 Literature Review
3
Web-based Church Management system for
Asokwa Pentecost,
Mercy Vicentia Nazzar, Kwame Nkrumah
University of Science and Technology,
2018
3
Church Management System, Capstone, 2020
3-4
The Design and Assessment of a Church
Records and Information Management System,
Cris Norman P. Olipas , Romabelle Cheline M.
Sawit , Rubelyn M. Esperon, 2021
4-5
Chapter 3 Problem Statement
6
Problem Statement
6
Motivation
6
Objective
6-7
Chapter 4 Methodology
8
Existing system
8
Proposed system
9
Waterfall model
9-10
ER Diagram
10
Use case Diagram
11
Chapter 5. Results Discussion
12
Description of Findings
12-47
Chapter 6. Conclusion
48
Chapter 7. Reference
49
LIST OF FIGURES
Fig. No
Fig. Name
Title
Page No
1
Waterfall model
9
2
ER Diagram
10
3
Use case Diagram
11
4
Admin dashboard
12
5
Login form for admin and sub admin.
12-13
6
User interface
13
1
CHAPTER 1
1.1 Overview
INTRODUCTION
The church management system is the system for the Evangelical Presbyterian
Church of Sikkim (EPCS). The Authorities of the church will use this system
for the better performance of the work. This system will provide online facilities
for the members of the church and also for the Administrator. “My Church,” the
thesis project is a system that will allow church groups to automate the process
of establishing and administering church members and events. The technology
in question makes it simple for churches to plan events and handle essential
elements for occasions.
Features of the systems are:-
1. Online member registration.
2. Online church registration.
3. Members can check the announcement from the council.
4. Members can send their prayer requests.
1.2. Company Profile
Welcome to de.mi, a community of successful, innovative, smart minds. Established
in 2013, de.mi’s main aim is to increase wealth & benefit its community of
stakeholders, by promoting a culture of innovation and competitiveness of its
products, solutions and services. At de.mi we support the growth of innovative
ideas, people, process & technology across sectors such as Education, Mobility,
Cloud Computing, BIGData, 3D Printing, Robotics, Biosciences, Green
Technologies and Sustainable Agriculture.
We aim to:
• Build you perfect for Corporate World
• Make you capable to handle the regular work flow of client
• Fulfil the difference between theoretical knowledge and practical knowledge
2
1.2.1. Training Undergone
1. Learned to use Bootstrap.
2. Researched how to show image from database to user-interface.
3. Learned to add image from database to user-interface.
1.3 Existing System
The management of the church is currently following a manual procedure. The
user has to check the availability of the required item by querying the
management. The management has to check the availability from the register
manually. After getting the availability status the user has to fill up the
membership and other forms manually. The management then checks the
validity of the forms and after checking it books the item against the respective
request. The information about the item is kept in a temporary register. When
the user submits the entire necessary document, the management enters the
details of the request in the main register of item details.
Currently, each member has a file in which vital data or information about a
member or management is kept in. Apart from this the member information or
data is also written papered and in booklets which are then stored in shelves.
Other documents such as transfer sheets report forms and registration forms are
also kept in files and stored in shelves. Therefore the council has several
problems with their record keeping. Since their records can be destroyed at any
time by natural environmental hazards or conditions which comes from
nowhere. It then causes the church to lose a large amount of resources and
required more management staffs.
3
CHAPTER 2
LITERATURE REVIEW
2.1. Web-based Church Management system for Asokwa Pentecost, Mercy
Vicentia Nazzar, Kwame Nkrumah University of Science and Technology, 2018
2.1.1. Introduction
Church management software is a specialized software that assists churches and
other religious organizations in the organization and automation of daily
operations. These packages typically assist in the management of membership
and mailings, fundraising, events, and report generation. Churches use the
packages to reduce the cost of operations and track the growth in their
congregations. The growth in the church management software business
coincides with the growing trend of using computers for religious activity.
2.1.2. Problems
The system wasn’t fully in systematic order and lacked of organizing
announcements.
2.1.3. Methodology
Prototyping: iterative framework type
Spiral: the combination of linear and iterative framework type
Waterfall: linear framework type.
2.2 Church Management System, Capstone, 2020
2.2.1. Introduction
The capstone project, “Church Event Management System” is a system that
will allow church organizations to automate the process of creating and
managing church events. The said project makes it easy for the churches to
schedule events and organize the important details for the events. Church
organizations conduct events to help the people of the church create moments
for fellowship and growth. Church events were usually attended by many people
under the church and it requires a lot of work for the assigned committee from
preparation up to the registration processes. Without having an effective system
4
of organizing the event, the organizer may encounter a lot of difficulties in
harmoniously managing all aspects needed for the event. The conventional
method of managing church events may encounter physical barriers and time
constraints in completing the preparations needed.
2.2.2. Problems
The system was fully focused only on events.
2.2.3. Methodology
They used Automated Management, Records Management,Report Generation.
2.3 The Design and Assessment of a Church Records and Information
Management System, Cris Norman P. Olipas , Romabelle Cheline M. Sawit ,
Rubelyn M. Esperon, 2021
2.3.1. Introduction
The advent of new technologies has brought significant impacts on people's
lives, which is evident in the different technological solutions present from
society's different areas and industries. This significant impact was caused by
computer technology, resulting in the information revolution (Deitel and Deital,
1986). Kamalov (2016) asserts that the information revolution has brought
people in the age of the internet in which a massive amount of data is
continuously transmitted over a communication network to different areas of the
globe. The ability to quickly transfer data from one point to another had opened
new possibilities, including improving the different services, capabilities, and
features of the establishments, institutions, and organizations that can be found
on the internet.
2.3.2 Problems
CRIMS fails to meet the standard of making software. Major changes are
required.
2.3.3 Methodology
Quantitative method,
Descriptive-developmental method.
5
CHAPTER 3
PROBLEM STATEMENT, MOTIVATION AND
OBJECTIVES
3.1. Problem Statement
The problem definition for the system is to launch the online system for the
Evangelical Presbyterian Church of Sikkim (EPCS). The whole church process
is carried out in a manual order. Since it’s a manual system it has the drawbacks
such as time consumption, and inefficient resource utilization. Some of the
drawbacks of the current system are:
1. The members have to collect the membership and other forms by hand from the
church premises. This consumes a valuable amount of time for the church
management.
2. An unmanageable tangle of papers within the office.
3. Wasted clerical effort searching for information.
4. Loss of important operating information.
5. Extravagant use of high-cost office space and equipment.
6. Loss of valuable historical records through destruction or neglect.
7. Difficulties in finding members and churches information when needed.
8. A lot of time is spent on the generation of reports since they are using the old
system.
9. A lot of time is spent collecting data about members and churches.
3.2 . Motivation
1. New members registration is cumbersome process
2. To go paperless office and curbing pilferage and duplication
6
3.3 . Objective
The main objective of this system is to overcome the drawbacks of the existing
system.
The prime benefits are:
1. To create a comprehensive database that provides the information on the
availability details and the issue details along with the member details.
2. Development and implementation of an information retrieval system for the
members and the management of the church.
3. To automate the entire range of activities or processes that needs to be performed
by the management before a request.
4. To put the information on the internet for easy access not only for the
management but also for the members from various places.
5. To make the system more user-friendly and easy to use.
6. Utilize IT to increase efficiency/productivity.
7
CHAPTER 4
METHODOLOGY
4.1. Existing System
The management of the church is currently following a manual procedure. The
user has to check the availability of the required item by querying the
management. The management has to check the availability from the register
manually. After getting the availability status the user has to fill up the
membership and other forms manually. The management then checks the validity
of the forms and after checking it books the item against the respective request.
The information about the item is kept in a temporary register. When the user
submits the entire necessary document, the management enters the details of the
request in the main register of item details.
Currently, each member has a file in which vital data or information about a
member or management is kept in. Apart from this the member information or
data is also written papered and in booklets which are then stored in shelves.
Other documents such as transfer sheets report forms and registration forms are
also kept in files and stored in shelves. Therefore the council has several problems
with their record keeping. Since their records can be destroyed at any time by
natural environmental hazards or conditions which comes from nowhere. It then
causes the church to lose a large amount of resources and required more
management staffs.
4.2. Proposed System
From earlier system the members have to keep in touch with the management about the
availability of the items. The proposed system is a web based online system. The user can apply
online from any place and also at any time. The main base of the proposed system is the
database, which keeps all the information about the availability status of the church. Based on
this information the user can easily get the availability status at any time without coming to the
church premises. The software also allows user to fill up the membership form and submit it
online which will save a lot of user’s valuable time. Along with the availability status the
database also keeps the information of the Issue details and the transaction details against the
respective request .This database also keeps the information of user’s personal details, based
on which the management can check the validity of the user and it’s request. Based on all the
above information the management can efficiently respond all the user queries.
8
The main activities will be performed by the system are.
1. Online submission of the membership.
2. Automation of the procedure performed by the management.
4.3. Waterfall model
The waterfall model is a sequential development process, in which development
is seen as flowing steadily downwards (like a waterfall) through the phases of
requirements analysis, design, implementation, testing (validation), integration,
and maintenance. The first formal description of the waterfall model is often
cited to be an article published by Winston W. Royce in 1970 although Royce
did not use the term “waterfall” in this article.
The principal stages of the model map onto fundamental development activities:
1. Requirements analysis and definition: The system's services, constraints, and
goals are, established by consultation with system users. They are then defined
in detail and serve as a system specification.
2. System and software design: The systems design process partitions the
requirements to either hardware or software systems. It establishes an overall
system architecture. Software design involves identifying and describing the
fundamental software system abstractions and their relationships.
3. Implementation and unit testing: During this stage, the software design is
realized as a set of programs or program units. Unit testing involves verifying
that each unit meets its specification.
4. Integration and system testing: The individual program units or programs are
integrated and tested as a complete system to ensure that the software
requirements have been met. After testing, the software system is delivered to
the customer.
5. Operation and maintenance: Normally (although not necessarily) this is the
longest life-cycle phase. The system is installed and put into practical use.
Maintenance: involves correcting errors that were not discovered in earlier
stages of the life cycle, improving the implementation of system units, and
enhancing the system’s services as new requirements are discovered.
9
Fig 1: waterfall model process.
To follow the waterfall model, one proceeds from one phase to the next in a
sequential manner. For example, one first completes requirements
specifications, which after sign-off are considered "set in stone." When the
requirements are fully completed, one proceeds to design. The software in
question is designed and a blueprint is drawn for implementers (coders) to
follow — this design should be a plan for implementing the requirements given.
When the design is fully completed, an implementation of that design is made
by coders. Towards the later stages of this implementation phase, separate
software components produced are combined to introduce new functionality and
reduced risk through the removal of errors.
Thus the waterfall model maintains that one should move to a phase only when
its preceding phase is completed and perfected. However, there are various
modified waterfall models (including Royce's final model) that may include
slight or major variations in this process.
10
4.4. Entity Relation Diagram
An entity relationship diagram (ERD), also known as an entity-relationship
model, is a graphical representation that depicts relationships among people,
objects, places, concepts, or events within an information technology (IT)
system. An ERD uses modeling techniques that can help define business
processes and serve as the foundation for a relational database.
Fig 2. Entity Relation diagram for Church management system.
11
4.5. Use case diagram
Use-case diagrams describe the high-level functions and scope of a system.
These diagrams also identify the interactions between the system and its actors.
The use cases and actors in use-case diagrams describe what the system does
and how the actors use it, but not how the system operates internally.
Fig 3. Use case diagram for Church management system
12
CHAPTER 5
RESULT AND DISCUSION
1.1 Admin dashboard where admin is able to add sub admin, adds announcement,
can add church, views members.
1.2 login form for admin and sub admin
13
1.3 form for adding sub admins
5.4. User interface contains events, about us, contact us and more.
14
5.4. Source codes
<?php
include("include/connection.php");
?>
<!DOCTYPE html>
<!-- Designined by CodingLab | www.youtube.com/codinglabyt -->
<html lang="en" dir="ltr">
<head>
<meta charset="UTF-8">
<title> </title>
<link rel="stylesheet" href="admin/css/style.css">
<!-- Boxicons CDN Link -->
<link href='https://unpkg.com/[email protected]/css/boxicons.min.css'
rel='stylesheet'>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="viewport" content="width=device-width, initial-scale=1">
<script src="https://code.iconify.design/2/2.2.1/iconify.min.js"></script>
</head>
<body><style>
/* This style sets the width of all images to 100%: */
img {
width: 100%;
}
</style>
<a href="request.php">
<i class='bx bx-message-alt-detail' ></i>
15
<span class="links_name">prayer request </span>
</a>
</li>
<li>
<?php
$query = "SELECT gender, count(*) as number FROM household GROUP BY
gender";
$result = mysqli_query($conn, $query);
?>
<head>
<script type="text/javascript"
src="https://www.gstatic.com/charts/loader.js"></script>
<script type="text/javascript">
google.charts.load('current', {'packages':['corechart']});
google.charts.setOnLoadCallback(drawChart);
function drawChart()
{
var data = google.visualization.arrayToDataTable([
['Gender', 'Number'],
<?php
while($row = mysqli_fetch_array($result))
{
echo "['".$row["gender"]."', ".$row["number"]."],";
}
?>
]);
var options = {
16
title: 'Percentage of Male and Female Members',
//is3D:true,
pieHole: 0.4
};
var chart = new
google.visualization.PieChart(document.getElementById('piechart'));
chart.draw(data, options);
}
</script>
</head>
<body>
<div style="width:900px;">
<div id="piechart" style="width: 500px; height: 0px;"></div>
</div>
</body>
<div class="grid-container">
<div class="item1"><h3>Evangelical Presbyterian Church of
Sikkim</h3></div>
<div class="item3"><h6>
<?php
$query = "SELECT presbyterian, count(*) as number FROM church GROUP
BY presbyterian";
$result = mysqli_query($conn, $query);
?>
17
<head>
<script type="text/javascript"
src="https://www.gstatic.com/charts/loader.js"></script>
<script type="text/javascript">
google.charts.load('current', {'packages':['corechart']});
google.charts.setOnLoadCallback(drawChart);
function drawChart()
{
var data = google.visualization.arrayToDataTable([
['presbyterian', 'Number'],
<?php
while($row = mysqli_fetch_array($result))
{
echo "['".$row["presbyterian"]."', ".$row["number"]."],";
}
?>
]);
var options = {
title: 'churches in each presbyterian',
//is3D:true,
pieHole: 0.4
};
var chart = new
google.visualization.PieChart(document.getElementById('piechart'));
chart.draw(data, options);
}
</script>
18
</head>
<body>
<br /><br />
<div style="width:500px;">
<br />
<div id="piechart" style="width: 500px; height: 0px;"></div>
<script src="https://code.iconify.design/2/2.2.1/iconify.min.js"></script>
<script>
let sidebar = document.querySelector(".sidebar");
let sidebarBtn = document.querySelector(".sidebarBtn");
sidebarBtn.onclick = function() {
sidebar.classList.toggle("active");
if(sidebar.classList.contains("active")){
sidebarBtn.classList.replace("bx-menu" ,"bx-menu-alt-right");
}else
sidebarBtn.classList.replace("bx-menu-alt-right", "bx-menu");
}
</script>
</body>
</html>
19
DATABASE
-- phpMyAdmin SQL Dump
-- version 5.0.2
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Jul 12, 2022 at 05:27 PM
-- Server version: 10.4.11-MariaDB
-- PHP Version: 7.4.6
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
START TRANSACTION;
SET time_zone = "+00:00";
/*!40101 SET
@OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT
*/;
/*!40101 SET
@OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULT
S */;
/*!40101 SET
@OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION
*/;
/*!40101 SET NAMES utf8mb4 */;
--
20
-- Database: `hms`
--
--
-- Table structure for table `contactdata`
--
CREATE TABLE `contactdata` (
`id` int(255) NOT NULL,
`user` varchar(255) NOT NULL,
`mobile` varchar(255) NOT NULL,
`msg` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `contactdata`
--
INSERT INTO `contactdata` (`id`, `user`, `mobile`, `msg`) VALUES
(66, 'ftgyuhjik', 'tgyuhjiok', 'tgyhujiko'),
(67, 'rguyhji', 'fghjuki', 'ghjk');
21
--
-- Table structure for table `doctor`
--
CREATE TABLE `doctor` (
`id` int(255) NOT NULL,
`name` varchar(255) NOT NULL,
`address` varchar(255) NOT NULL,
`spclist` varchar(255) NOT NULL,
`mobile` varchar(255) NOT NULL,
`pwd` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `doctor`
--
INSERT INTO `doctor` (`id`, `name`, `address`, `spclist`, `mobile`, `pwd`)
VALUES
(6, 'Dr Bandana', 'Bering', 'Brain', '7845895612', 'bhalu');
--
-- Table structure for table `loginform`
--
22
CREATE TABLE `loginform` (
`id` int(255) NOT NULL,
`user` varchar(255) NOT NULL,
`pass` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `loginform`
--
INSERT INTO `loginform` (`id`, `user`, `pass`) VALUES
(1, 'admin', 'admin');
--
-- Table structure for table `patient`
--
CREATE TABLE `patient` (
`id` int(255) NOT NULL,
`name` varchar(255) NOT NULL,
`address` varchar(255) NOT NULL,
`mobile` varchar(255) NOT NULL,
`symtoms` varchar(255) NOT NULL,
23
`doctor` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Table structure for table `staff`
--
CREATE TABLE `staff` (
`id` int(255) NOT NULL,
`username` varchar(255) NOT NULL,
`mobile` varchar(255) NOT NULL,
`address` varchar(255) NOT NULL,
`gender` varchar(255) NOT NULL,
`shift` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `staff`
--
INSERT INTO `staff` (`id`, `username`, `mobile`, `address`, `gender`, `shift`)
VALUES
(3, 'Abikeser', '7589658458', 'Ranipool', 'Male', 'Day'),
(11, 'Bandu', '7845123659', 'pakyong', 'Female', 'Evening'),
24
(12, 'uday', '852147963', 'ranipool', 'Male', 'Night');
--
-- Table structure for table `subadmin`
--
CREATE TABLE `subadmin` (
`id` int(255) NOT NULL,
`name` varchar(255) NOT NULL,
`address` varchar(255) NOT NULL,
`mobile` varchar(255) NOT NULL,
`username` varchar(255) NOT NULL,
`password` varchar(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Dumping data for table `subadmin`
--
INSERT INTO `subadmin` (`id`, `name`, `address`, `mobile`, `username`,
`password`) VALUES
(3, 'Abikeser', 'Ranipool', '7845123692', 'abikeser', 'kelvinrux'),
(15, 'Asha', 'lol', '987654321', 'asha', 'admin'),
(17, '', '', '', '', '');
25
--
-- Indexes for dumped tables
--
--
-- Indexes for table `contactdata`
--
ALTER TABLE `contactdata`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `doctor`
--
ALTER TABLE `doctor`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `loginform`
--
ALTER TABLE `loginform`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `patient`
--
26
ALTER TABLE `patient`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `staff`
--
ALTER TABLE `staff`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `subadmin`
--
ALTER TABLE `subadmin`
ADD PRIMARY KEY (`id`);
--
-- AUTO_INCREMENT for dumped tables
--
--
-- AUTO_INCREMENT for table `contactdata`
--
ALTER TABLE `contactdata`
MODIFY `id` int(255) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=68;
27
--
-- AUTO_INCREMENT for table `doctor`
--
ALTER TABLE `doctor`
MODIFY `id` int(255) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=10;
--
-- AUTO_INCREMENT for table `loginform`
--
ALTER TABLE `loginform`
MODIFY `id` int(255) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=2;
--
-- AUTO_INCREMENT for table `patient`
--
ALTER TABLE `patient`
MODIFY `id` int(255) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=3;
--
-- AUTO_INCREMENT for table `staff`
--
ALTER TABLE `staff`
MODIFY `id` int(255) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=13;
28
--
-- AUTO_INCREMENT for table `subadmin`
--
ALTER TABLE `subadmin`
MODIFY `id` int(255) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=18;
COMMIT;
/*!40101 SET
CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET
CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET
COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
29
DELETION CODE
<?php
include("../include/connection.php");
$id=$_GET['ok'];
$query = "delete from subadmin WHERE name ='$name'";
$data=mysqli_query($conn,$query);
if($data)
{
header('location:details.php');
}
else
{
echo "<script>alert('Record Not Deleted')</script>";}
?>
header('location:announcement.php');
?>
30
ADDING CODE
<?php
include("../include/connection.php");
$Date =$_POST['Date'];
$Announcement =$_POST['Announcement'];
$query="INSERT into Announcement(date,Announcement)
VALUES('$date','$Announcement')";
mysqli_query($conn,$query);
31
CSS
/* Googlefont Poppins CDN Link */
@import
url('https://fonts.googleapis.com/css2?family=Poppins:wght@200;300;400;50
0;600;700&display=swap');
*{
margin: 0;
padding: 0;
box-sizing: border-box;
font-family: 'Poppins', sans-serif;
}
.sidebar{
position: fixed;
height: 100%;
width: 240px;
background: #0A2558;
transition: all 0.5s ease;
}
.sidebar.active{
width: 60px;
}
.sidebar .logo-details{
height: 80px;
display: flex;
align-items: center;
}
32
.sidebar .logo-details i{
font-size: 28px;
font-weight: 500;
color: #fff;
min-width: 60px;
text-align: center
}
.sidebar .logo-details .logo_name{
color: #fff;
font-size: 24px;
font-weight: 500;
}
.sidebar .nav-links{
margin-top: 10px;
}
.sidebar .nav-links li{
position: relative;
list-style: none;
height: 50px;
}
.sidebar .nav-links li a{
height: 100%;
width: 100%;
display: flex;
align-items: center;
text-decoration: none;
33
transition: all 0.4s ease;
}
.sidebar .nav-links li a.active{
background: #081D45;
}
.sidebar .nav-links li a:hover{
background: #081D45;
}
.sidebar .nav-links li i{
min-width: 60px;
text-align: center;
font-size: 18px;
color: #fff;
}
.sidebar .nav-links li a .links_name{
color: #fff;
font-size: 15px;
font-weight: 400;
white-space: nowrap;
}
.sidebar .nav-links .log_out{
position: absolute;
bottom: 0;
width: 100%;
}
.home-section{
34
position: relative;
background: #f5f5f5;
min-height: 100vh;
width: calc(100% - 240px);
left: 240px;
transition: all 0.5s ease;
}
.sidebar.active ~ .home-section{
width: calc(100% - 60px);
left: 60px;
}
.home-section nav{
display: flex;
justify-content: space-between;
height: 60px;
background: #fff;
display: flex;
align-items: center;
position: fixed;
width: calc(100% - 240px);
left: 240px;
z-index: 100;
padding: 0 20px;
box-shadow: 0 1px 1px rgba(0, 0, 0, 0.1);
transition: all 0.5s ease;
}
35
.sidebar.active ~ .home-section nav{
left: 60px;
width: calc(100% - 60px);
}
.home-section nav .sidebar-button{
display: flex;
align-items: center;
font-size: 24px;
font-weight: 500;
}
nav .sidebar-button i{
font-size: 35px;
margin-right: 10px;
}
.home-section nav .search-box{
position: relative;
height: 50px;
max-width: 550px;
width: 100%;
margin: 0 20px;
}
nav .search-box input{
height: 100%;
width: 100%;
outline: none;
background: #F5F6FA;
36
border: 2px solid #EFEEF1;
border-radius: 6px;
font-size: 18px;
padding: 0 15px;
}
nav .search-box .bx-search{
position: absolute;
height: 40px;
width: 40px;
background: #2697FF;
right: 5px;
top: 50%;
transform: translateY(-50%);
border-radius: 4px;
line-height: 40px;
text-align: center;
color: #fff;
font-size: 22px;
transition: all 0.4 ease;
}
.home-section nav .profile-details{
display: flex;
align-items: center;
background: #F5F6FA;
border: 2px solid #EFEEF1;
border-radius: 6px;
37
height: 50px;
min-width: 190px;
padding: 0 15px 0 2px;
}
nav .profile-details img{
height: 40px;
width: 40px;
border-radius: 6px;
object-fit: cover;
}
nav .profile-details .admin_name{
font-size: 15px;
font-weight: 500;
color: #333;
margin: 0 10px;
white-space: nowrap;
}
nav .profile-details i{
font-size: 25px;
color: #333;
}
.home-section .home-content{
position: relative;
padding-top: 104px;
}
.home-content .overview-boxes{
38
display: flex;
align-items: center;
justify-content: space-between;
flex-wrap: wrap;
padding: 0 20px;
margin-bottom: 26px;
}
.overview-boxes .box{
display: flex;
align-items: center;
justify-content: center;
width: calc(100% / 4 - 15px);
background: #fff;
padding: 15px 14px;
border-radius: 12px;
box-shadow: 0 5px 10px rgba(0,0,0,0.1);
text-align: center;
}
.overview-boxes .box-topic{
font-size: 20px;
font-weight: 500;
}
.home-content .box .number{
display: inline-block;
font-size: 35px;
margin-top: -6px;
39
font-weight: 500;
}
.home-content .box .indicator{
display: flex;
align-items: center;
}
.home-content .box .indicator i{
height: 20px;
width: 20px;
background: #8FDACB;
line-height: 20px;
text-align: center;
border-radius: 50%;
color: #fff;
font-size: 20px;
margin-right: 5px;
}
.box .indicator i.down{
background: #e87d88;
}
.home-content .box .indicator .text{
font-size: 12px;
}
.home-content .box .cart{
display: inline-block;
font-size: 32px;
40
height: 50px;
width: 50px;
background: #cce5ff;
line-height: 50px;
text-align: center;
color: #66b0ff;
border-radius: 12px;
margin: -15px 0 0 6px;
}
.home-content .box .cart.two{
color: #2BD47D;
background: #C0F2D8;
}
.home-content .box .cart.three{
color: #ffc233;
background: #ffe8b3;
}
.home-content .box .cart.four{
color: #e05260;
background: #f7d4d7;
}
.home-content .total-order{
font-size: 20px;
font-weight: 500;
}
.home-content .sales-boxes{
41
display: flex;
justify-content: space-between;
/* padding: 0 20px; */
}
/* left box */
.home-content .sales-boxes .recent-sales{
width: 95%;
background: #fff;
padding: 10px 20px;
margin: 0 20px;
border-radius: 52px;
box-shadow: 0 5px 10px rgba(0, 0, 0, 0.1);
}
.home-content .sales-boxes .sales-details{
display: flex;
align-items: center;
justify-content: space-between;
}
.sales-boxes .box .title{
font-size: 24px;
font-weight: 500;
/* margin-bottom: 10px; */
}
.sales-boxes .sales-details li.topic{
font-size: 20px;
42
font-weight: 500;
}
.sales-boxes .sales-details li{
list-style: none;
margin: 8px 0;
}
.sales-boxes .sales-details li a{
font-size: 18px;
color: #333;
font-size: 400;
text-decoration: none;
}
.sales-boxes .box .button{
width: 100%;
display: flex;
justify-content: flex-end;
}
.sales-boxes .box .button a{
color: #fff;
background: #0A2558;
padding: 4px 12px;
font-size: 15px;
font-weight: 400;
border-radius: 4px;
text-decoration: none;
transition: all 0.3s ease;
43
}
.sales-boxes .box .button a:hover{
background: #0d3073;
}
/* Right box */
.home-content .sales-boxes .top-sales{
width: 35%;
background: #fff;
padding: 20px 30px;
margin: 0 20px 0 0;
border-radius: 12px;
box-shadow: 0 5px 10px rgba(0, 0, 0, 0.1);
}
.sales-boxes .top-sales li{
display: flex;
align-items: center;
justify-content: space-between;
margin: 10px 0;
}
.sales-boxes .top-sales li a img{
height: 40px;
width: 40px;
object-fit: cover;
border-radius: 12px;
margin-right: 10px;
44
background: #333;
}
.sales-boxes .top-sales li a{
display: flex;
align-items: center;
text-decoration: none;
}
.sales-boxes .top-sales li .product,
.price{
font-size: 17px;
font-weight: 400;
color: #333;
}
/* Responsive Media Query */
@media (max-width: 1240px) {
.sidebar{
width: 60px;
}
.sidebar.active{
width: 220px;
}
.home-section{
width: calc(100% - 60px);
left: 60px;
}
.sidebar.active ~ .home-section{
45
left: 220px;
width: calc(100% - 220px);
overflow: hidden;
}
.home-section nav{
width: calc(100% - 60px);
left: 60px;
}
.sidebar.active ~ .home-section nav{
width: calc(100% - 220px);
left: 220px;
}
}
@media (max-width: 1150px) {
.home-content .sales-boxes{
flex-direction: column;
}
.home-content .sales-boxes .box{
width: 100%;
overflow-x: scroll;
margin-bottom: 30px;
}
.home-content .sales-boxes .top-sales{
margin: 0;
}
}
46
@media (max-width: 1000px) {
.overview-boxes .box{
width: calc(100% / 2 - 15px);
margin-bottom: 15px;
}
}
@media (max-width: 700px) {
nav .sidebar-button .dashboard,
nav .profile-details .admin_name,
nav .profile-details i{
display: none;
}
.home-section nav .profile-details{
height: 50px;
min-width: 40px;
}
.home-content .sales-boxes .sales-details{
width: 560px;
}
}
@media (max-width: 550px) {
.overview-boxes .box{
width: 100%;
margin-bottom: 15px;
}
.sidebar.active ~ .home-section nav .profile-details{
47
display: none;
}
}
@media (max-width: 400px) {
.sidebar{
width: 0;
}
.sidebar.active{
width: 60px;
}
.home-section{
width: 100%;
left: 0;
}
.sidebar.active ~ .home-section{
left: 60px;
width: calc(100% - 60px);
}
.home-section nav{
width: 100%;
left: 0;
}
.sidebar.active ~ .home-section nav{
left: 60px;
width: calc(100% - 60px);
}}
48
CHAPTER 6
CONCLUSION
The web-enabled system “church management system” on successful
completion enables the CEPCS to view the status of the Churches and members
of EPCS. It will also provide the facility to the user so that they can send their
prayer request online. The Authority of the church will be also benefited from
the proposed system, as it will automate the whole registration procedures,
which will reduce the workload for the Authority.
Since every system has some limitations, so the proposed system is also not
untouchable in this regard. Although it includes many features still it would not
be sufficient as the user requirement are not always same. The change in the
requirements will need some changes in the system to fulfill the requirements.
The security of the system will be one of the prime concerns once it will be
made online.
This program would enhance the running of the church information. The
existing system will be used alongside the new system to ensure that the church
does not loose valuable information when switching to the new system.
FUTURE SCOPE
The future developer can add chats features where the members can be able to
chat with each other. They can add live location of each churches where other
can see the location when they go to visit that particular church.
49
CHAPTER 7
REFERENCES
1.
Mercy Vicentia Nazzar, “Web-based Church Management system for Asokwa Pentecost”
Kwame Nkrumah University of Science and Technology 2018.
2.
Capstone “Church Management System” 2020
3.
Cris Norman P. Olipas , Romabelle Cheline M. Sawit , Rubelyn M. Esperon “The Design and
Assessment of a Church Records and Information Management System ” 2021.
4.
"Software manages while pastors minister.". Church Central.
5.
"Software manages while pastors minister.". Church Central. Retrieved 2008-04-11. "Church
Management Software (ChMS) allows a congregation to keep tabs on information related to
activities of the church. It uses a database to store information and typically includes a set of
programs or modules to manipulate the stored data."
6.
"Software solutions for growing churches". Church Central. July 5, 2005. Retrieved 2008-04-
04. "With more than 7,000 members and an office staff of 75, Asbury United Methodist Church
of Tulsa, Okla., relies on church management software to help run the administrative side of the
church."
7.
"What can church management software do?". Church Central. 21 February 2015. Retrieved
2018-04-04.
8.
David Gonzalez (July 24, 1994). "The Computer Age Bids Religious World to Enter". The New
York Times. 0. Retrieved 2008-04-04. "Specially-designed software for church management, to
track contributions and membership, can be used by savvy pastors to minister to their
congregants, said Pat Faudree, a spokeswoman for Shelby Systems, which is a leading church
management software company."
9.
The Complete Reference Java J2SE 5
th
Edition—Herbert Schildt (Tata McGraw Hill 2005).
10.
Java How To Program—Deitel & Deitel(PHI—2004).
11.
Mastering SQL Server 2000—Mike Gunderly, Joseph L Jordan.
50