TEMPLE MANAGEMENT

SYSTEM
SUBMITTED To:

SRCMBMM SANCHALIT
SMT K.S.KAPASHI B.C.A
COLLEGE PALITANA
GUIDED BY: Mr. Divyesh
Narigara
PREPARED BY:
Vala Kunjal & Chauhan Krupali
PROJECT YEAR : 2023-24
 1.1  Background

Chapter 1 1.2  Objectives

1.3  Purpose
1. Introduction
1.4 1.4 scop
1.4

 Applicability
1.5
 1. Introduction
 A temple is place of worship often dedicated to a specific deity or religious tradition.

 Multiple Temples can be added or removed in our project.

 Multiple Festivals can be added in our project.

 News show of more than one temple can be done.

 Users can book Darshan from our website in advance of available temples.
  Background
 User can pre-register the available temple from our website

 Festival of multiple temples can be added , removed and managed

 User News of more than one temple can be published and that news can also be managed

 Earlier , if you want to see information about the festival or temple , then you can see it easily from
this website.
  Objectives
 In future it well be used for online darshan booking

 Online payment method is also available in this website so that any donar can donate easily.

 The objective of temple management is to create a conducive and enriching environment for
devotees To worship.

 Easy information will also be available from this website for those who are interested in learning
more about religion.
  Purpose
 Ultimately , the purpose is to facilitate the religious and cultural practices associated with the temple
and provide a space for people to connect with their faith.

 More than one temple can be managed in easily in this website

 Religious scriptures , sermons and literary information related to temple tradition will be easily
available
  Scope
 Live filming of worship services or events will be shown for those unable to attend in person.

 Calendar of upcoming events , festivals , and special religious observances , details about how These
events are celebrated at the temple.
  Applicability
 Facilitate the promotion and organization of temple event , festivals , and special ceremonies.

 Temple management ensures that the temple functions smoothly and provides a positive and fulfilling
experience for devotees who visit this website.
 2.1  Problem definition

Chapter 2 2.2
 Requirement Specification

 Hardware and Software

Requirement And Specification 2.3 Requirement

 Hardware and software

2.4 requirement
 2.1 Problem definition

 Many temple management tasks are still handled manually, leading to inefficiencies,
errors, and delays.

 Lack of effective communication channels between temple authorities, staff, and devotees,
resulting in misinformation and confusion.

 Inconsistent and suboptimal visitor experiences due to long waiting times, inadequate
facilities, and insufficient crowd management.

 Insufficient use of technology for administrative tasks, communication, and enhancing

visitor experiences. Lack of an effective online presence and digital platforms for
donations and information dissemination.
 2.2 Requirement And Specification

Lack of effective communication channels between temple authorities, staff, and

devotees, resulting in misinformation and confusion.

Inconsistent and suboptimal visitor experiences due to long waiting times, inadequate
facilities, and insufficient crowd management.

Insufficient use of technology for administrative tasks, communication, and enhancing

visitor experiences. Lack of an effective online presence and digital platforms for
donations and information dissemination.
2.3 Hardware & Software Specification

1.Hardware Requirements.
Processor Intel(R) Core(TM) i7-4810MQ CPU @
2.80GHz 2.80 GHz

Ram Min 2 GB, 4GB, 8GB

Hard Disk Min 250 GB,500 GB, 1 TB

Monitor Window Compatible Monitor

Keyboard Window Compatible Keyboard

Mouse Window Compatible Mouse

2.3 Hardware & Software Specification

2.Software Requirements
Processor Intel(R) Core(TM) i7-4810MQ CPU @
2.80GHz 2.80 GHz
Ram Min 2 GB, 4GB, 8GB

Hard Disk Min 250 GB,500 GB, 1 TB

Monitor Window Compatible Monitor

Keyboard Window Compatible Keyboard

Mouse Window Compatible Mouse

 2.4 Planning and Scheduling

 Function of project Planning

 This stage is best for risk management.

 Planning include information’s related to cost, time lines, budgets etc.

 Planning is needed to identify desired goals, reduce risk, service or result.

 2.5 Planning and Scheduling
 Scheduling - Chartt
 3.1  Over all System Design
Using Designing Tools.

Chapter 3
3.2  Data Dictionary
System Design

3.3  Input/Output Design

3.1 Over all System Design Using

3.1.1)Data Flow Diagram

3.1.4) Sequence Diagram

3.1.2) Use-case Diagram

3.1.5) E-R Diagram

3.1.3) Activity Diagram

Data Flow Diagram
Data Flow Diagram Admin
Data Flow Diagram
Visitor
Use-case Diagram
Admin
Use-case Diagram
Visitor
Activity Diagram
(Admin)
Activity Diagram
Visitor
Sequence Diagram (Visitor)
Sequence Diagaram
(Admin)
E-R Diagram
  Data Dictionary
 List of Tables
Table No Name of Table Purpose
1 About_us Table Store Temple Information

2 Booking_user Table Store Booking user information

3 Contact_us Table Store visitor contact information

4 Darshan_booking Table Store Darshan booking user information

5 Festival Table Store festivals information
6 Gallery Table Store Gallery information

7 Reports Table Store Donar information

8 Services Table Store Temple Service information

9 Temple Table Store Temple information

10 Temple_registration Table Store Temple registration information

11 View donation Table Store player trials information
  About-us Table

Field Name Data type Size Constraint Description

Id Int 5 Primary key Auto increment

Title Varchar 500 --- Store title of

temple

Description Varchar 500 --- Store

Description of
about us
Img Varchar 500 --- Image of about
us
  Booking-user Table

Field Name Data type Size Constraint Description

Ref-id Int 10 Primary key Auto increment

Amount Int 10 --- Amount of booking
Total_person Int 10 --- Total_person of
booking
Book date Varchar 500 --- Booking date
Time Varchar 100 --- Booking of time
Temple title Varchar 500 --- Booking temple title

Status Varchar 50 --- Status of user

  Contact_Us Table

Field Name Data type Size Constraint Description

id Int 100 Primary key Auto increment

User_name Varchar 500 --- User name

Gmail Varchar 500 --- User Gmail

Subject Varchar 50 --- Description of

Subject

Message Varchar 500 --- Description of

message
  Darshan_booking Table

Field Name Data type Size Constraint Description

Id Int 10 Primary key Auto increment

User_name Varchar 50 --- Name of user

Temple name Varchar 50 --- Name of temple

Booking date Varchar 50 --- Date of booking

Amount Int 100 --- Amount of user

Ref_id Varchar 50 --- Refer id number

  Festivals Table

Field Name Data type Size Constraint Description

Id Int 5 Primary key Auto increment

Title Varchar 500 --- Store title of

temple
Description Varchar 500 --- Store
Description of
about us
Img Varchar 500 --- Image of about
us
  Gallery Table

Field Name Data type Size Constraint Description

id Int 100 Primary key Auto

increment

title Varchar 100 --- Image title

Image Varchar 500 --- Gallery of

image
  Report Table

Field Name Data type Size Constraint Description

id Int 10 Primary key /auto Auto increment

increment

Type Varchar 50 --- Store report type

Title Varchar 50 --- Store report title

File Varchar 90 --- Store report file

Date Varchar 20 --- Store date

  Service Table

Field Name Data type Size Constraint Description

id Int 100 Primary key Auto

/auto increment increment

Title Varchar 500 --- Store service

title
Image Varchar 500 --- Store service
image
Description Varchar 500 --- Store service
description
  Temple Table

Field Name Data type Size Constraint Description

id Int 10 Primary key Auto increment

Title_of_temple Varchar 50 --- Store temple

title
Description Varchar 90 --- Store temple
description
Post_date Varchar 50 --- Store date
Update_date Varchar 50 --- Store date
Image Varchar 100 --- Store temple
image
  Temple_registration Table

Field Name Data type Size Constraint Description

id Int 10 Primary key Auto increment

User_name Varchar 50 --- Store user name
Gmail Varchar 30 --- Store user email
Password Varchar 20 --- Store user
password
Profession Varchar 50 --- Store user
profession
About_us Varchar 50 --- Store about_us
information
Image Varchar 100 --- Store user image
  View_donation Table
Field Name Data type Size Constraint Description

id Int 10 Primary key Auto increment

Donar_name Varchar 50 --- Store donar name
Description Varchar 50 --- Donar description
Photo Varchar 100 --- Donar photo
Donar_amount Int 50 --- Paid amount
Donar_post_date Timestamp --- --- Store date
Donar_ref Varchar 20 --- Donar refrence
Donar_phone Int 50 --- Donar number
Donar_gmail Varchar 40 --- Donar email
Proof_no Varchar 50 --- Store photo
Message Varchar 50 --- Store message of
donar
Status Varchar 50 --- Store status of donar
 Home Page
 Gallery
 Services
 Donation
 Donation Archive
 Donation Archive
 Payment
 Payment
 Payment
 Payment
 Donation
 View Temple
 Somnath Temple Description
 View Temple
 Badrinath Temple Description
 View Temple
 Kedarnath Temple Description
 View Temple
 Jain Temple Description
 View Temple
 Prem Temple Description
 View Temple
 Dwarka Temple Description
 View Temple
 Ambaji Temple Description
 View Temple
 Salangpur Temple Description
 View Temple
 Tirupati Balaji Temple Description
 About_us
 About_us
 Festivals
 Darshan Booking
 Darshan Booking
 Payment
 Payment
 Payment
 Ticket
 Ticket
 Contact Us
 Contact Us
 Log in
 Log in
 Wrong Password
 Forget Password
 Forget Password
 Forget Password
 Change Password
 Admin Dashboard
 Add Temple
 Add Temple
 Successfully Temple Add
 Temple List
 Update Temple
 Update Temple
 Successfully Update Temple
 Successfully Delete Temple
 Add Service
 Add Service
 Successfully Add Service
 Service List
 Service Update
Update Service
 Successfully Update Services
 Successfully Delete Service
Add Festivals
Add Festivals
Successfully Add Festivals
 Festivals List
 Festivals Update
 Festivals Update
 Successfully Festivals Update
 Successfully Delete Festivals
Add Gallery
Add Gallery
 Successfully Add Gallery
 Gallery List
 Successfully Delete Gallery
View Donation
 Successfully Delete Donor
 Donar Balance Sheet Report
 Update About_us
 Update About_us
 Successfully Update About_us
 Update Admin Profile
 Feedback Page
 Successfully Delete Feedback
 Update Admin Profile
 Change Password
 Successfully Change Password
 4.1  Testing Approaches used

4.2  Testing Technique

Chapter-4
 Strategies
Testing and
Implementations: 4.3 1  Test Case
1.4

 Implementation Approaches
4.4
  Testing Approach
 Testing is executing a system in order to identify any gaps, errors, or missing requirements in contrary
to the actual requirements.

 A test approach is the test strategy implementation of a project, defines how testing would be carried
out.

 Testing Techniques and Strategies:

 There are two strategies available:

1. Top-Down Testing
2. Bottom-Up Testing
1.Top-Down Testing
2.Bottom Up Testing
  Type of Testing
1. Black Box Testing:
 Black box testing, also known as Behavioral testing, is a software method in which the internal
design/implementation of the item being tested is not known to the later.

 The technique of testing without having any knowledge of the interior workings of the applications 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.
 Advantage of Black-Box Testing:

 It becomes very easy to find out which type of data can help testing the application effectively.

 It helps in optimizing the code.

 Extra lines of code can be removed which can be bring in hidden effects.

 Due to the tester’s knowledge about the code maximum coverage attained during testing scenario
writing.
 Black-Box Testing:

Figure 4.1.3
 2.White Box Testing:

 White box testing is a software testing method in which the internal structure /design / implementation
of the item being tested is known to the tester.

 White box testing is the detailed investigation of internal logic and structure of the code.

 The tester needs to have a look inside the source code and find out which unit/chunk of the code is
behaving inappropriately.

 White box testing techniques:

 Statement Coverage.
 Branch Coverage.
 Path Coverage.
  Advantage of White-Box Testing:

 Forces test developer to reason carefully about implementation.

 Reveals errors in “hidden” code.

 Spots the dead code or other issues with respect to best programming practices.
  Grey Box Testing:

 Grey Box testing is testing technique performed with limited information about the Internal
functionality of the system.

 Grey Box testers have access to the detailed design documents along with information about
requirements.

 Grey Box tests are generated based on the state-based models, UML Diagrams or architecture diagrams
of the target system.

 Grey-box testing Techniques:

 Regression testing
 Pattern Testing
 Orthogonal array testing
 Matrix testing
  Advantages:

 Grey-box testing provides combined benefits of both white-box and black-box testing

 It is based on functional specification, UML Diagrams, Database Diagrams or architectural view.

 Grey-box tester handles can design complex test scenario more intelligently
 The added advantage of grey-box testing is that it maintains the boundary between independent
testers and developers.
 Grey-box testing

4.2 Test Case

Figure 4.1.5
  Test Cases
 Test Case: - 1 Login
Test Id Test Steps Test Input Expected Actual Status Comments
Results Results
1 1.Enter User Name Admin Admin Admin Pass No issues found
2.Enter Password admin Password : Dashboard Dashboard
3.Click on login admin
2 1.Enter Name Admin Login Failed Login Failed Pass No issues found
2.Enter Password admin Password :
3.Click on login admin
3 1.Enter Name Admin Error As Expected Pass No issues found
2.Enter Password Admin Password: Message:
3.Click on login admin ”Please
Enter valid
Email”
 5.1  Conclusion

Chapter 5 2.2
 Limitation Of System

 Future Scope Of System

 Conclusions 2.3

 Bibliography
2.4
  Conclusion
 Temple Management System project aims to provide In conclusion, the implementation of a temple
management system has proven to be beneficial in streamlining various administrative processes and
enhancing the overall efficiency of temple operations. By digitizing tasks such as donation management,
event scheduling, and visitor registration, the system has enabled temple staff to devote more time and
resources to spiritual and community-focused activities

 Overall, the project has been successful in achieving its objectives and delivering a high quality system. The
project has worked diligently to design and develop the system, taking into account the requirements and
feedback from various user. The system has undergone rigorous testing and quality assurance to ensure that it
is free from bugs and performs optimally under different scenarios

 Moving forward, the project can continue to improve the system by incorporating new features and
functionalities based on the evolving needs of the Temple management System. They can also explore
opportunities to integrate the system with other platforms and technologies to enhance its capabilities and
reach a broader audience. Finally, the project can continue to provide ongoing support and maintenance to
ensure that the system remains up-to date and reliable for its users
  Limitation Of System

 There are some limitations for the current system to which solutions can be provided as a future development.

 Not available in multiple language.

 Device must be requires.

 System Used only for specific temple.

  Future Scope Of System :

 Digital Transformation: Temples will increasingly adopt digital platforms for various operations,
including online donations, ticketing for events and ceremonies, virtual tours, and digital archives of
religious texts and artifacts. We have decided to change our previous traditional system with a fully
functionality which include new features that are not available in existing system.

 Convert this application to Mobile application.

 SMS alert for aarti notification

  Bibliography :
 Bibliography means take reference to prepare any project. Here I concern the website takes reference is as under.

 Website:
 https://www.stackoverflow.com/
 https://getbootstrap.com/
 https://www.github.com/
 https://www.codepen.io/
 https://www.w3schools.com
 https://www.tutorialspoints.com/
 https://www.youtube.com/
 https://www.free-css.com/
  Reference Website:

 https://phpgurukul.com/online-temple-management-system-using-php-and-mysql/

 https://mayurik.com/source-code/P2556/-online-temple-management-system-project-in-php-and-mysql

 https://www.studentprojects.live/vb-net-projects/temple-management-system/
THANK
YOU