Diocese Management software provides seamless integration of all parishes with the diocese. Diocese can communicate with parishes and institutions effortlessly through this software. The software integrates all the functions of diocese particularly designed for Syro Malabar, Latin, Malankara rites. It can also be easily adapted for any Catholic Diocese management.

1. DIOCESE MANAGEMENT SYSTEM
Submitted by:Libin M
E mail:mlibin89@gmail.com

2. Introduction
 Diocese Management software provides
seamless integration of all parishes with the
diocese. Diocese can communicate with parishes
and institutions effortlessly through this
software. The software integrates all the
functions of diocese particularly designed for
Syro Malabar, Latin, Malankara rites. It can also
be easily adapted for any Catholic Diocese
management.
 Administrator is the main user of this web
application.

3. ABSTRACT
Diocese management system software is designed to
do this task by evaluating, communicating and managing a
diocese administration from diocese directly.
Administrator: The administrator of the company is allowed
to access all the services in the system. The username and
password for the sub user is given by the administrator.
Authorized people: It include archbishops secretary, parish
priest, Sunday schools, organization, parish member etc.
Visitors: Visitors can view the notification without logging in
the website.

4. COMPANY PROFILE
TEENA COMPUTERS,Anchal
Software Solutions is an IT solution provider for a
dynamic environment where business and technology
strategies converge. Their approach focuses on new ways of
business combining IT innovation and adoption while also
leveraging an organization’s current IT assets. Their work
with large global corporations and new products or services
and to implement prudent business and technology
strategies in today’s environment.
TEENA COMPUTERS is an ISO 9001:2008 certified
institution with a long experience in this field.

5. SYSTEM STUDY
EXISTING SYSTEM
 Existing system is a manual one in which
authorized people is maintaining books to
store the information. It is very difficult to
maintain historical data.
 The existing system is done in manual works.
 Lots of human resources is needed.

6. Disadvantages
 More manual hours need to generate
required reports.
 It is difficulty to maintain important
information in books.
 Time management not accurate.
 Communication is not effective.
 It is not useful to keeping touch with diocese
every time.

7. PROPOSED SYSTEM
The online diocese management
system is a software application which
avoids more manual hours that need to
spend in record keeping and generating
reports. This tool increases performance
by reducing manual hours spending for
normal things. It is very easy to record the
information in the database.

8. Advantage
 Proposed system is fully computerized
system.
 It is easy to store and retrieve information.
 View the notification through online.
 Online message or email passing through .

9. Tools used
Front End: .net mvc
.net is used to develop the graphical environment and
networking features where forms and controls can be
visually designed
Back End: sql
SQL Server which is one of the most powerful
database management systems is used for data storage
and manipulation of datas.
Editor:Dreamweaver
Dreamweaver is very simple to handle
HTMLprograms
and it is very efficient to create styles

10. Diocese management system modules
 Administrator: He can create new foranes, parishes, priests
, organizations and Sundays schools. And also he can view
the details of the above.
 Archbishops Secretary: He can arrange the programs of the
archbishops. He can view and allow the programmes
requests from the parishes and parish members.
 Parish Priest: He can enter the details of parishes and
members. Also he can enter the details of all activities of
institutions and organizations related to that church.

11.  Sunday Schools: can view the schedules and
programmes created by the administrator. Also
can edit and enter the details of students and
staffs.
 Organizations: can view the schedules and
programmes created by the administrator. Also
can edit and enter the details of members and
leaders.
 Parish Member : Can book the archbishops
program online. Also he can view the details of
parishes, foranes and priests in the diocese.

12. HARDWARE REQUIREMENT
System: core i3
Hard disk:300gb
Processor:2.4ghz
Ram:2gb

13. TABLES
1.Log in
FIELD DATA TYPE CONSTRAINT DESCRIPTION
User_id Varchar(10) Primary key User id for a user
password Varchar(20) Not null password
User_type Varchar(20) Not null Type of user

14. 2.parish
FIELD DATA TYPE CONSTRAINT DESCRIPTION
parish_id Varchar(10) Primary key Parish id for a parish
name Varchar(25) Not null Name of parish
address Varchar(100) Not null Address of parish
place Varchar(20) Not null Place of parish
pin Int(6) Not null Pin number
phone Int(11) Not null Phone number
email Varchar(30) Not null Email address
Land_mark Varchar(30) Not null To identify location
Forane_id Varchar(10) Foreign key
Ref:forane
Code for identify
forane
type Varchar(20) Not null Type of church

15. 3.priest
FIELD DATA TYPE CONSTRAINT DESCRIPTION
Priest _id Varchar(10) Primary key Priest id for a priest
Priest_name Varchar(50) Not null Official name ofpriest
name Varchar(30) Not null Name of priest
address Varchar(100) Not null Address of priest
pin Int(6) Not null Pin number
phone Int(11) Not null Phone number
mobile Int(15) Not null Mobile number
email Varchar(40) Not null Email address
Parish_id Varchar(10) Foreign key
Ref:parish
Parish id for parish
Mother_parish Varchar(30) Not null Nameof mother parish
D_ordination date Not null Ordination date
D_birth date Not null Date of birth
qualification Varchar(30) Not null qualification

16. 4.forane
FIELD DATA TYPE CONSTRAINT DESCRIPTION
Forane_id Varchar(10) Primary key Id for a forane
Forane_name Varchar(30) Not null Name of forane
Forane_president Varchar(30) Not null Name of president
Forane_secretary Varchar(30) Not null Name of secretary

17. 5.Sunday school
FIELD DATA TYPE CONSTRAINT DESCRIPTION
ss_id Varchar(10) Primary key Id for sundayschool
sname Varchar(30) Not null Name of Sunday
school
Parish_id Varchar(10) Not null
Ref:parish
Parish id for parish
No_student Int(5) Not null No. of student
No_teacher Int(5) Not null No. of teacher
S_president Varchar(30) Not null Name of president
S_secretary Varchar(30) Not null Name of secretary

18. 6.Faith organization
FIELD DATA TYPE CONSTRAINT DESCRIPTION
F_id Varchar(10) Primary key Id for faith
organisation
f_o_name Varchar(30) Not null Name of organisation
no_member Int(5) Not null No.of members
president Varchar(30) Not null Name of president
secretary Varchar(30) Not null Name of secretary
Parish_id Varchar(10) Foreign key
Ref:parish
Id of a parish
Forane_id Varchar(10) Foreign key
Ref:forane
Id of forane

19. 7.Donation
FIELD DATA TYPE CONSTRAINT DESCRIPTION
D_id Varchar(10) Primary key Id for donation
date date Not null Date
name Varchar(30) Not null Name of donator
address Vrchar(100) Not null address
Parish_id Varchar(10) Foreign key
Ref:parish
Id of a parish
amount Int(8) Not null Amount details
purpose Varchar(200) Not null Purpose of donating
etc

20. 8.curia
FIELD DATA TYPE CONSTRAINT DESCRIPTION
curia_id Varchar(10) Primary key Id of curia member
name Varchar(30) Not null Name of member
position Varchar(20) Not null Position in diocese
Parish_id Varchar(20) Not null Id of parish

21. 9.Institution
FIELD DATA TYPE CONSTRAINT DESCRIPTION
In_id Varchar(10) Primary key Id for a institute
Parish_id Varchar(10) Foreign key
Ref:parish
Id of a parish
In_name Varchar(30) Not null Name of institute
address Varchar(100) Not null Address of institute
phone Int(11) Not null Phone number
email Varchar(30) Not null Email address
lanmark Varchar(40) Not null Land mark

22. 10.Bishop program
FIELD DATA TYPE CONSTRAINT DESCRIPTION
Pro_id Varchar(10) Primary key Id for a bishop
program
Date date Not null Program date
time time Not null Program time
Pro_name Varchar(40) Not null Program name
venue Varchar(30) Not null Venue of program
description Varchar(200) Not null Detail of the program

23. 11.Employee
FIELD DATA TYPE CONSTRAINT DESCRIPTION
Emp_id Varchar(10) Primary key Id for employee
name Varchar(30) Not null Name of employee
position Varchar(30) Not null Position of employee
address Varchar(100) Not null Address of employee
mob Int(10) Not null Mobile number

24. 12.Daily news
FIELD DATA TYPE CONSTRAINT DESCRIPTION
News_title Varchar(50) Primary key Title of news
news Varchar(1000) Not null News content
Date date Not null Date of news
time time Not null time

25. 13.Church budget& report
FIELD DATA TYPE CONSTRAINT DESCRIPTION
cb_id Varchar(10) Primary key Id for church budget
Parish_id Varchar(10) Foreign key
Ref:parish
Id of a parish
Fian_year date Not null Financial year
Income Int(10) Not null Total income
expense Int(10) Not null Total expence
Dioce_per Int(10) Not null Diocese percentage
Report_gen Varchar(1000) Not null Report of program

26. 14.Diocese budget&report
FIELD DATA TYPE CONSTRAINT DESCRIPTION
Db_id Varchar(10) Primary key Id for diocese budget
Fin_year date Not null Financial year
Income Int(10) Not null Total income
expense Int(10) Not null Total expence
Report_gen Varchar(1000) Not null Report of program

27. 15.Parish members
FIELD DATA TYPE CONSTRAINT DESCRIPTION
Mem_id Varchar(10) Primary key Id for member of
parish
Parish_id Varchar(10) Foreign key
Ref:parish
Id of parish
ward varchar(30) Not null Ward of parish
Mem_name Varchar(30) Not null Name of member
address Varchar(100) Not null Address of member
phone Int(11) Not null Phone no. of member
mob Int(10) not null Mob no. of member

28. 16.certificate
FIELD DATA TYPE CONSTRAINT DESCRIPTION
App_id Varchar(10) Primary key Applicant id
parish_id Varchar(10) Foreign key
Ref:parish
Id of parish
mem_id Varchar(10) Foreign key
Ref:parish member
Id of membership
cata Varchar(20) Not null Category of certificate
App_name Varchar(30) Not null Applicant name
date date Not null date
status Varchar(30) Not null Status of certificate

29. DATA FLOW DIAGRAM
Context Level

30. Level 1.1(Admin)
Level 1

31. Employee(Level 1.2)

32. Bishop secretary(Level 1.3)

33. Priest(Level 1.4)

34. Forane(Level 1.5)

35. Admin(Level 2.1)
Level 2

36. Employee(Level 2.2)

37. Bishop Secretary(Level 2.3)

38. Priest(Level 2.4)

39. Forane(Level 2.5)

40. ER-Diagram

41. ER-diagram

42. Conclusion
The new system has overcome most of
the limitations of the existing system and
according to the design specification given.
The newly developed system consumes less
processing time and all the details are
updated and processed immediately. In
future we can modify this project to suit the
requirements of the time and modules can be
added to it.

43. Thank you