TEMPLE MANAGEMENT SYSTEM

 

INTRODUCTION OF TEMPLE MANAGEMENT SYSTEM

Are you looking for Temple management system for your final year project? We are here to help you. You can contact us 

Everyone is born into this world for some reason, but they never know the same, but search for that thing, it is believed by everyone that that god is the one who makes everyone and resides with all to give them the path to pursue the life.

People believe that God lives in their house or their existence can be felt and everyone should go there to get touched by the god grace. there are many religions in the world, everyone has different ways worshipping God, one of them is temples were mainly Hindus believe to worship.

There are many temples but few temples are such that their grace is known to be much than the other so few people there in n numbers. Due to that, the darshans become very difficult as people maybe wanted to get darshans at their time and have some work or proper management can also be managed.

So we come up with a system where users are required to register for the darshans for the given time as they can book the devotional aartis at a particular time. they require to fill the details about it and timing and then they will get the token after giving a nominal amount of payment.

The arrangements will be done by the temple management to do the required worship apart from the queue.They need to show the token to get the special entry. Finally, they will get the darshans without any hesitation and without difficulty at their time.

MODULES OF TEMPLE MANAGEMENT SYSTEM

The system is made of the combination of modules which work with collaboration with each other and make it beneficial to accomplish the main aim of the system.

REQUEST MAKING :

Users make a request through the interface for booking the aartis at a particular time. they have the option to choose the temple like Vaishno Devi, Chamunda Devi, Mansa Devi and few more temples they select the one from them all.

After selecting temple they have the option to select the task they want to do like they want to do the aartis, darshans or seva, according to that they will select the items they want the temple management to get managed prior to the arrival for the purpose they note that down in the interface finally, they confirm the request .

PAYMENTS:

After confirming the request they will be prompt for the payment to the management for the organization of the facilities to arrange.

They have the option to pay through the interface in the form of a debit card they can pay.After doing successful payment they will be doing the necessary print of token.

TOKEN:

The token interface is available to the both user and the temple management they will receive token and arrange the requirement according to that before time, this token will be checked by them at the time of entrance to the temple for the users.To confirm the legal token.

WORSHIP:

Finally, they get the chance of doing the worship according to that and make the status of worship done in the interface confirmed and done by the users and the management both hence they will complete the system task.

REGISTRATION:

Users information have to be compelled to be registered within the system thus on establish every of them unambiguously and do the required group action as simple potential .like on the name of the bill are issued.

on the far side, this plenty of things require measure there wherever we will reference him. Without registration, there are few options and pages one user can see which are landing on the home page and taking the features read but he won’t be allowed to use those.

For use, he will have to register. One person needs to put his all the details properly and precisely as it will be helpful in identifying them and believing that he is the real person who has booked for the same.

It also includes driver license for them who is driving and parameter too.

LOGIN:

After registration one will log within the system because the operator of the system either on the behalf of user. when this he has the opposite helpful interfaces accessible for any actions.

Here either bride or groom both have to log in with their unique identity and passwords. After this, they will be directed to the main user interface from where they have further options.

FORGOT PASSWORD:

This is quite often that people tend to forget the password they keep for the login. So this could be very tedious and hectic to recover the password manually in case if one needs to login in the emergency.

So to overcome this problem we have this module named ass forgot the password and using this module user can recover their password in seconds. So here we need to only put our registered email Id and hit the enter.

than one confirmation email will go to the email where he has the option to reset the password. In seconds one can use this module and get rid of forgetting password problem.

ADMIN:

Admin has the official powers to control the flow of the data from one part of the system to the other. He has the power to manipulate the access of the users to the data.

The main purpose of this account is to make the user data relevant and then giving the inputs to the other interface module and make it work optimistically and get the timetable according to the wish we want to create for a particular type of inputs.

Hence all the data will be reflected with clean and well data in the interfaces.

SYSTEM REQUIREMENTS OF TEMPLE MANAGEMENT SYSTEM

Now, this method is intended in such the way that it takes fewer resources to figure out work properly. it’s its own type of minimum needs that we’d like to require care of :

The system wants a minimum of two GB of ram to run all the options sleek and unforeseen.

It wants a minimum 1.3 gigahertz processor to run sleek as else which will produce issues.

The system must be operated by some approved person as wrong hands will build it happy-go-lucky.

Rest is all up to the user’s usage can take care of hardware

For security opposing anti-virus is suggested.

The system is made properly and all the testing is done as per the requirements. So, the rest of the things depend on the user and no one can harm the data or the software if the proper care is done.

All the attributes are working perfectly and if any error is found then it can be removed easily.

SYSTEM DESIGN OF TEMPLE MANAGEMENT SYSTEM

ENTITY REQUEST:

PRIMARY KEY REQUEST:

This is system generated and unique, which can be referenced in any other entity.

TEMPLE_ID:

Reference to the temple

TYPE OF REQUEST:

The purpose of the request like aartis, darshans, seva.

THE TIMING OF ARRIVAL:

At what time they want to visit

COST:

The cost of the request is mentioned here.

ENTITY TEMPLE:

PRIMARY KEY TEMPLE_ID:

This is system generated and unique, which can be referenced in any other entity.

NAME:

The name of the temple.

OPENING TIME:

The time at which it opens.

CLOSING TIME:

The time it will close.

ENTITY MANAGER

PRIMARY KEY MANAGER_ID:

This is system generated and unique, which can be referenced in any other entity.

NAME:

The name is taken from the user and fed into this it is properly validated so that no mistake happens.

QUALIFICATION:

Qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

NUMBER:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

EMAIL:

email is taken to make member aware of new offers new events and for future reference, it is also relevant.

TYPE:

the type of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

ADDRESS:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

ENTITY PAYMENT:

PRIMARY KEY PAYMENT_ID:

This is system generated and unique, which can be referenced in any other entity.

FOREIGN KEY USER_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

FOREIGN KEY REQUEST_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

STATUS:

Is the payment is done or not is given here.

ENTITY STAFF:

PRIMARY KEYSTAFF_ID:

This is system generated and unique, which can be referenced in any other entity.

STAFF NAME:

Staff name is taken from the user and fed into this it is properly validated so that no mistake happens.

QUALIFICATION:

qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

NUMBER:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

EMAIL:

email is taken to make member aware of new offers new events and for future reference, it is also relevant.

TYPE:

the type of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

ADDRESS:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

FOREIGN KEY MANAGER_ID:

Reference to the manager entity is given through the system.

ENTITYUSER:-

User data have to be saved in this entity and all fields are required for this purpose which taken from the user .proper validation is checked and the attributes are as follows:

PRIMARY KEYUSER_ID:

This is system generated and unique, which can be referenced in any other entity.

USERNAME:

Username is taken from the user and fed into this it is properly validated so that no mistake happens.

QUALIFICATION:

qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

NUMBER:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

EMAIL:

email is taken to make member aware of new offers new events and for future reference, it is also relevant.

TYPE:

the type of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

ADDRESS:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

ENTITY ADMIN:

PRIMARY KEY ADMIN:

This is the main supervisor of all task happening in the system for long. It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities. It has all the power to make changes in the field of other tables. It grants the privileges to other users of the system that what kind of operations they can perform.

LOGS:

The logs are saved here to analyze the system accordingly. The changes occur. For necessary changes.

PASSWORD:

A Strong password is recommended for this account as no one wants to get hacked and lose the sophisticated data.

DESCRIPTION:

Any important info. Regarding this account is attributed in this.

USE CASE DIAGRAM OF TEMPLE MANAGEMENT SYSTEM

In this system mainly we have three actors. First is the user who is eager to get the darshan of the temple at the time and want to do the specific task at the venue. He specifies the materials they want get managed by the organization.

As he confirms after doing the necessary payment it will be forwarded to the management of the temple they get the token to clear and they do the same with the arrangements done.User comes up to the temple at a time get the darshans done.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF TEMPLE MANAGEMENT SYSTEM

FUNCTIONAL REQUIREMENTS OF TEMPLE MANAGEMENT SYSTEM:-

The functional requirements are those requirements which are necessary to the eye of the user and the client. Here we try to make the module possible to accomplish the need of the desired function. few of its functional requirements are as follows-

NON-FUNCTIONAL REQUIREMENTS OF TEMPLE MANAGEMENT SYSTEM:-

These requirements needs unit among the style of “system shall be “, associated overall property of the system as a full or of a particular aspect and not a particular operation. The system’s overall properties remarkably mark the excellence between whether or not the event project has succeeded or unsuccessful.

NON-FUNCTIONAL OF TEMPLE MANAGEMENT SYSTEM NEEDS –

unit of measurement usually divided into 2 main categories:

Execution qualities, like security and quality, that unit evident at the runtime.

Evolution qualities, like liabilities, maintainability, flexibility and quantitative, that unit embodied among the static structure of the code.

Non-functional of temple management system needs place restrictions on the merchandise being developed, the event technique, and specify external constraints that the merchandise has to be compelled to meet

Our project qualifies all the factors of helpful and not helpful consequently and the system is up to mark performance device.Here we’d prefer to need the care of few lots of things before heading towards the system.

the many sensible intuitive interfaces are usually created. that ultimately build interface easy to use for a lengthy time. in distinction to ancient vogue wherever the goal is to create the difficulty or application physically enticing, the goal of interface vogue is to create the user’s interaction expertise as simple and intuitive as double – what’s typically mentioned as user-centred vogue.

where smart graphic/industrial vogue is daring and eye-catching, smart interface vogue is sometimes delicate and invisible.

Keep things simple and consistent:-Simple and Harmonic means that making u i is extraordinarily intuitive and needs to followed

OBSERVE THE USE OF TYPOGRAPHY:-

The typography is taken care really strictly as the wish of the system.

USE COLOUR AND DISTINCTION PROPERLY:

Color band of skin and dark is sweet means that stress and done well throughout this method

CONSIDER FEEDBACK MESSAGES:-

feedback sort may well be an excellent means that taking feedback of forms and rising the system.

SIMPLIFIED FORMS:-

The form is made simple to fill with a clean program.

CONCLUSION OF TEMPLE MANAGEMENT SYSTEM

Finally in temple management system, we have a system where we can a user who is eager to get the darshan of the temple at the time and want to do the specific task at the venue. He specifies the materials they want get managed by the organization.

As he confirms after doing the necessary payment it will be forwarded to the management of the temple they get the token to clear and they do the same with the arrangements done.User comes up to the temple at a time get the darshans done.