CMS

Rajagiri College of Social Sciences, Kalamassery
Department of Computer Application
Church Management System

MINI PROJECT INTERIM REPORT
Submitted By,
Eldho P Joy
MCA
Roll No. 13
Software Requirement Specification
TABLE OF CONTENTS
Abstract
Part A
1. Introduction to the Project---------------------------------------------------04
2. About the Organization------------------------------------------------------04
3. Objective of the Project------------------------------------------------------06
4. System Study------------------------------------------------------------------07
4.1.
Existing System
4.2.
Proposed System
5. Functional Specifications(Modules)---------------------------------------09
6. User Characteristics----------------------------------------------------------10
7. Software Interfaces-----------------------------------------------------------11
8. Specific Hardware Requirements-------------------------------------------11
Part B
1. UML Diagrams----------------------------------------------------------------13
1.1.
Use Case Diagram----------------------------------------------------14
1.2.
Activity Diagram------------------------------------------------------15
1.3.
Class Diagram---------------------------------------------------------16
1.4.
Sequence Diagram----------------------------------------------------17
2. E-R Diagram------------------------------------------------------------------18
3. Database Design--------------------------------------------------------------19
4. Form Design-------------------------------------------------------------------23
5. Report Design-----------------------------------------------------------------30
2
Part-A
SOFTWARE REQUIREMENT
SPECIFICATION (SRS)
1. INTRODUCTION TO THE PROJECT

Church management System is used to provide the facility to automate the
official functionalities of a church. The system is also using technologies to organize, automate
and synchronize the interaction process. The system enables users from across the region to utilize
the church facilities and ensure easy functioning.
The overall goal of the system is to manage the details of the parish members
of the church. The users will be able to get familiarize with the parish members of the church along
with their contact details. It saves time and paper work.
The main functions of this project are
Save the details of parish members.

Marriage Registrations.
Baptism Registrations.
Provide certificates for Parish members like marriage, baptism, community and death.
There are two types of users, admin and other users. Admin have the
privilege to enter the details and the right to generate certificates. The other users can apply for
certificates and the admin checks the request and take necessary actions for the request.
In future the project can be incorporated with other sites like matrimonial
website and family tree application. The application provides an interface using PHP for
applying management logic and MySQL for establishing connection with the database.
2. ABOUT THE ORGANISATION

The St. Marys (Martha Mariam) Church at Pallikkara is one of the most
ancient churches of the Jacobite Syrian Orthodox Christians in Malankara. The 'Kol-Tamil'
inscription on a granite slab found in the northern premises of the Church indicates the year of its
establishment as 905 A.D. Pallikkara is situated near Ambalamugal, 20 km from Kochi. This
ancient parish belongs to the Angamali diocese of the Malankara Church.
Legend has it that when the body of a child was brought to the Edappally
Church for burial, an altercation broke out between two groups, and as a result, the body had to be
taken back. The aggrieved family then took permission from a prominent Nair landlord, and the
body was laid to rest in an uninhabited place. The site was marked off with a Cross, and it was
here that the Pallikkara Church was built.
The Pallikkara parish has been an active participant in all the historical
developments of the Malankara Syrian Orthodox Church. A large group of its members
participated in the Koonen Cross pledge of 1653 A.D. On return to Pallikkara, they took to
celebrating the death anniversary of His Holiness Ignatius Ahatulla Bava with great zeal and
fervor.
Metropolitans Yuyakim Mor Kurillos (who was laid to rest in the
Mulanthuruthy MarThoman Church) and Mathews Mar Athanasius had stayed in this Church for
a very long time. All the Patriarchs who visited Malankara from time to time have also visited and
blessed the Church.
The five altars (THRONOS) in the church are dedicated to St. Mary, St.
Thomas, St. George, St. Baselios Yeldho of Kothamangalam and St. Gregorios of Parumala The
churches that branched off from the Pallikkara Church are many: St.Mary's Church, Vengola; St
Mary's Church, Thamarachal; St Peter's St Paul's Church, Kizhakkambalam; St Thomas Church,
Vadavukode; St Mary's Church, Pazhathottam and St George's Church, Kutta. Also majority of
the parishioners of St Georges' Church, Veloor; St George's Church, Cheruthottukunnel; St Mary's
Church, Thengod; and St Thomas Church, Kakkanad; were earlier members of the Pallikkara
Church.
The Pallikkara parish presently consists of over 1200 families in its
congregation. The chapel at East Morakkala consecrated on 1st February 1995 is one of the three
chapels of this church. Besides there are eight kurishupalli (Shrines) under the Pallikkara church;
at Chanthakurissu, Angadikurissu, Chakalamukal, Chittanadu, Vempilli, Oothikkara, Perunthira
and at East Morakkala.
The Church runs its Sunday school very diligently, and the Youth Association
and Vanitha Samajam have excellent programs. In 2001 a monthly promoted by St. Marys Youth
Association, Pallikkara, started publication under the patroonship of the Vicar and other office
bearers of the parish & the youth wing. The annual convention that started in 1990 under the
patronage of Rev. Fr. E C Varghese & the youth Association has now grown into the largest
spiritual meeting in the area.
The St. Marys Higher Secondary School run by the Church has on its rolls
about 2000 students with more than 60 teachers and office staff. There is also an English medium
L.P. school functioning under the management.
The Pallikkara St Mary's Church can rightfully claim an enviable record in
humanitarian and social activities, having been in the forefront of many social, cultural and
ameliorative activities. The Church has offered financial assistance to a large number of deserving
cases. Further, a housing fund is also set aside on a yearly basis. All the inmates of the Vaaikkoli
Leprosy Hospital are provided meals many times a year. The parish has also made substantial
financial contribution in the construction of the Malankara Syrian Orthodox Theological Seminary
at Vettickal.
3. OBJECTIVE OF THE PROJECT

The main objective behind the project Church management System is it to
be used to provide the facility to automate the official functionalities of a church. The system is
also using technologies to organize, automate and synchronize the interaction process. The system
enables users from across the region to utilize the church facilities and ensure easy functioning.
The overall goal of the system is to manage the details of the parish members of the church. The
users will be able to get familiarize with the parish members of the church along with their contact
details. The system gave privilege to the parish members to add their details and request for some
necessary certificates for any purposes like marriage certificate, death certificate, community
certificate, baptism certificate etc.
4. SYSTEM STUDY
4.1 Existing System
The existing system is manually data entering paper bind records, which
is a very slow process and error prone. The information about the parish member details and
registration details are stored manually, which is time consuming and errors. The existing
system does not provide any security for storing the details.to keep these records take a lot of
room space.
Here registration details are entered manually. This leads to error and also
causes lot of manual work. In the manual system to produce reports many records should be
replaced and hence the time required will be very high. Moreover the quality of details may
not be good enough.
Drawback of the existing system
Man power is required to maintain records.
Does not provide any security for details
While preparing the reports manually, it takes lot of time and effort
It is very slow process
It needs more human works
Searching for details is very difficult.
4.2 Proposed System

The existing system is a manual system and this will cause several problems.
It is not very easy to maintain and changes in details can cause errors to occur at any level of this
system. So it is better to adopt another system, which removes all these problems. Thus we
introduced a computerized system, which gives more physical security to the details of the
application forms. Retrieval and storage of data is easier in this system. Since the proposed system
is error free, less time consuming and more users friendly.
The proposed system has been developed by using the front end tool
used in this Project is PHP (PHP Hypertext Pre-processor). The back end tool used is MySql. The
proposed system is computerized system that keeps tables and database for maintaining the details
of the whole process. The tables are maintained for keeping different details so that each details is
accessed quickly with accurate values. The proposed system is user friendly in which everyone
can understand the transactions. Even an end user can understand the system. It gives accuracy
and neat presentation of results with high speed. The proposed system enables good interface over
the existing system. It should automate the activities that are being done manually in the existing
system.
BENEFITS OF PROPOSED SYSTEM
The proposed system is developed in PHP as front end so that we can
take advantage of the graphical user interface, which increase user interaction. The back end for
this proposed system is MySql. The proposed system has provisions for storing and maintaining
all the parish members details.
Advantages of proposed system
Stores the information about members and the user can view their profile.
Easier search options.
Provision for editing user details.
Portable and feasible for further development.
User friendly screens to enter data and to view existing data.
Printable reports & Certificates.
5. FUNCTIONAL SPECIFICATIONS (MODULES)

Admin Login Module
In this module, Members logins are managed. Admin adds students by allocating unique
username and password and some basic details about each member which will be stored in member
table. Only those members who has valid username and password are allowed to use the system.
Members Login Module
In this module, Members details are managed. The registered members are able to login to
the system and they can add their profile and manage their profile. They are able to request for the
certificates of services offered by the system. They can also check for the request status.
Marriage Registration Module
In this module, marriage registrations are generated by admin which will be stored in
marriage table. Each marriage has a unique id. Marriages are registered based on the parish
member details in the member table and also specifying bride details, groom details, date of
marriage, name of priest, etc. Marriage certificate will be generated based on the user request.
Baptism Registration Module
In this module, baptism registrations are generated by admin which will be stored in
baptism table. Each baptism has a unique id. Baptisms are registered based on the parish member
details in the member table and also specifying childs original name, date of birth, date baptism,
name of priest, etc. Baptism certificate will be generated based on the user request.
Death Registration Module
In this module, death registrations are generated by admin which will be stored in death
table. Each death has a unique id. Death are registered based on the parish member details in the
member table and also specifying date of funeral, name of the person, name of priest, etc. Death
certificate will be generated based on the user request.
Certificate Generation Module

In this module, admin checks the request from the members for any certificates. Check the
availability of the certificate and generate certificate for the same. Also changes the request status
of the member to grant.
6. USER CHARACTERISTICS
There are three users who can use the system.
6.1 Admin
The admin is the user who create the system and has full control over the system.
Admin has the following privileges on the system.
View Parish members Details
Add New family
Update family Details
Delete Existing family
Marriage Registration
Baptism Registration
Death Registration
Search
Generate Certificates
6.2 Members
The members are the user who is actually going to use the system for his benefit.
Student has the following privileges on the system:
Add personal profile
Apply for certificates
Check status
Change password
Search
10
7. SOFTWARE INTERFACES
7.1 Development
Client Machine
Google Chrome
Server Machine
SQL Server, IIS Server
Client Machine
Google Chrome
Server Machine
SQL Server, IIS Server
7.2 Implementations
8. SPECIFIC HARDWARE REQUIREMENTS

8.1 Development Configuration
Client Machine
Server Machine
Processor
Intel Dual Core i3 or above.
Hard Disk
40 GB or Above
RAM
4 GB or Above
Processor
Hard Disk
40 GB or Above
RAM
4 GB or Above
Processor
Hard Disk
40 GB or Above
RAM
4 GB or Above
Processor
Hard Disk
40 GB or Above
RAM
4 GB or Above
8.2 Implementation Configuration

Client Machine
Server Machine
11
Part B
SOFTWARE DESIGN
DESCRIPTION (SDD)
12
UML DIAGRAMS
13
USE CASE DIAGRAM
14
ACTIVITY DIAGRAM
15
CLASS DIAGRAM
16
SEQUENCE DIAGRAM
17
E-R DIAGRAM
18
DATABASE DESIGN
19
Table1: login_details
Field Name
username
password
utype
Data Type
varchar
varchar
varchar
Size
50
50
50
Description
user id, Primary Key
password
User type
Table 2: registeration_details
Field Name
Parishid
Househead
housename
Address1
Address2
photo
No_of_mem
Data Type
varchar
varchar
varchar
varchar
varchar
blob
int
Size
50
50
50
50
50
20
Description
parish id, primary key
House head name
House name
Street name
City name
Family photo
No. of members
Table 3: member_details
Field Name
Memid
Data Type
varchar
Size
50
Parishid
varchar
50
Name
Dob
Occupation
Contact
relation
varchar
date
varchar
varchar
varchar
50
50
50
50
Description
member id,
Primary key
parish id,
Foreign key
name
Date of birth
occupation
Contact no
Relation with family
Table 4: marriage_details
Field Name
marid
Data Type
varchar
Size
50
Parishid
varchar
50
Memid
varchar
50
Bname
varchar
50
20
Description
marriage id,
Primary key
Parish id ,
Foreign key
Member id ,
Foreign key
Bride name
Gname
Date
Priest
Bimage
Gimage
varchar
date
varchar
Blob
Blob
50
50
50
50
Groom name
Marriage date
Priest name
Bride image
Groom image
Table 5: baptism_details
Field Name
baptid
Data Type
varchar
Size
50
Parishid
varchar
50
Orgname
Fname
Pname
Dob
Baptdate
godfather
varchar
varchar
varchar
date
date
varchar
50
50
50
50
Description
baptism id,
Primary key
Parish id ,
Foreign key
Original name
father name
priest name
Date of birth
Baptism date
godfather name
Table 6: death_details
Field Name
Death_id
Data Type
varchar
Size
50
Parish_id
varchar
50
Member_id
varchar
50
dod
Funeral_date
Preist name
Vault_id
date
date
varchar
varchar
20
20
21
Description
Death id,
Primary key
Parish id,
Foreign key
Member id,
Foreign key
Date of death
Date of funeral
Priest name
Vault id
Table 7: subscription_details
Field Name
Sub_id
Data Type
Varchar
Size
50
Parish_id
varchar
50
amount
lpd
Due_amount
Due_date
integer
date
integer
date
22
Description
Subscription id,
Primary key
Parish id,
Foreign key
Subscription amount
Last paid date
Due amount
Due date
FORM DESIGN
23
Home
About us
Contact
Login
Login
Username
Password
Login
Login
Admin Home
Home
Add New
Welcome,
Register
Requests
ADMIN
24
Logout
Home
Register
Add New
Requests
Logout
Parish id
House head
House Name
Street
City
Personal Details
Register
Home
Register
Marriage
Add New
Requests
Baptism
Death
Parish Id
Bride Name
Address 1
Address2
Groom Name
Address 1
Address2
Date
Priest name
Register
25
Logout
Home
Register
Marriage
Add New
Requests
Logout
Baptism
Death
Parish Id
Original Name
Fathers name
God Father
Date of birth
Baptism Date
Priest name
Register
Home
Add New
Register
Marriage
Requests
Baptism
Death
Parish Id
Name
Fathers name
Date of Death
Funeral Date
Priest name
Register
26
Logout
Home
Register
Add New
Sl no.
Parish id
Logout
Requests
Certificate of
Date
Status
User home
Home
Update Profile
Requests
Welcome, USER
27
Status
Logout
Home
Update Profile
Requests
Status
Logout
Requests
Status
Logout
Name
Date of birth
Occupation
Contact no.
Add
Home
Update Profile
Marriage Certificate
Request
28
Home
Update Profile
SL no
Requests
Applied for
Status
Status
Refresh
29
Logout
REPORT DESIGN
30
This is certify that

.....
Was baptized in the name of the father, the son of the Holy Spirit
At ..
On ..
By
Date:
Place:
Seal
Sign
Photo
groom
Photo
bride

... & ..
Were wed on the..day of in the year..
By ..
At ..
Date:
Place:
Seal
31
Sign

...
Son of Mr..... ..is a parish member
of this church since .
Date:
Place:
Seal
Sign
Photo
This is to acknowledge the death of
... ..
On the..day of in the year..
By ..
At ..
Date:
Place:
Seal
32
Sign

CMS

Uploaded by

Copyright:

Available Formats

CMS

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CMS

Uploaded by

Copyright:

Available Formats

What are the main functions of the Church Management System?

What are the main functions of the Church Management System?

What are the different types of users in the system?

What are the different types of users in the system?

Rajagiri College of Social Sciences, Kalamassery

Department of Computer Application

Church Management System

Church Management System

Software Requirement Specification

Use Case Diagram----------------------------------------------------14

Church Management System

Software Requirement Specification

Church Management System

Software Requirement Specification

1. INTRODUCTION TO THE PROJECT

Save the details of parish members.

2. ABOUT THE ORGANISATION

Church Management System

Software Requirement Specification

Church Management System

Software Requirement Specification

3. OBJECTIVE OF THE PROJECT

Church Management System

Software Requirement Specification

4.2 Proposed System

Church Management System

Software Requirement Specification

Church Management System

Software Requirement Specification

5. FUNCTIONAL SPECIFICATIONS (MODULES)

Church Management System

Software Requirement Specification

Certificate Generation Module

View Parish members Details

Add New family

Update family Details

Delete Existing family

Add personal profile

Apply for certificates

Church Management System

Software Requirement Specification

SQL Server, IIS Server

SQL Server, IIS Server

8. SPECIFIC HARDWARE REQUIREMENTS

Intel Dual Core i3 or above.

Intel Dual Core i3 or above.

Intel Dual Core i3 or above.

Intel Dual Core i3 or above.

8.2 Implementation Configuration

Church Management System

Software Requirement Specification

Church Management System

Software Requirement Specification

Church Management System

Software Requirement Specification

USE CASE DIAGRAM

Church Management System

Software Requirement Specification

Church Management System