Scribd
Upload
21 views6 pages

Synopsis EMS PHP

The document outlines the development of an Event Management System aimed at centralizing event-related data and improving user registration and profile management. It highlights the shortcomings of the existing system and proposes a new solution that includes user authentication, online help, and a user-friendly interface. The feasibility study covers operational, technical, and economic aspects, while detailing functional requirements and system modules for both admin and registered users.

Uploaded by

sanketbucche123
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
21 views6 pages

Synopsis EMS PHP

The document outlines the development of an Event Management System aimed at centralizing event-related data and improving user registration and profile management. It highlights the shortcomings of the existing system and proposes a new solution that includes user authentication, online help, and a user-friendly interface. The feasibility study covers operational, technical, and economic aspects, while detailing functional requirements and system modules for both admin and registered users.

Uploaded by

sanketbucche123
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

1.

INTRODUCTION

1.1. Scope of The Project


The objective of this application is to develop a system that effectively manages all the data
related to the various events that take place in an organization. The purpose is to maintain a
centralized database of all event related information. The goal is to support various functions
and processes necessary to manage the data efficiently.

1.2. Existing System

This existing system is not providing secure registration and profile management of all the users
properly. This system is not providing on-line Help. This system doesn’t provide tracking of
users activities and their progress. This manual system gives us very less security for saving data
and some data may be lost due to mismanagement. This system is not providing event
management through internet. This system is not providing proper events information. The
system is giving manual information through the event management executer.

1.3. Proposed System


The development of this new system contains the following activities, which try to automate the
entire process keeping in the view of database integration approach. This system maintains
user’s personal, a and contact details. This system will provide on line help and search
capabilities. User friendliness is provided in the application with various controls provided by
system rich user interface. Authentication is provided for this application only registered users
can access. event information files can be stored in centralized database which can be
maintained by the system. This system provides the users to manage the events systematically.
2. SYSTEM ANALYSIS

2.1 FEASIBILITY STUDY


A feasibility study is a high-level capsule version of the entire System analysis and Design
Process. The study begins by classifying the problem definition. Feasibility is to determine if it’s
worth doing. Once an acceptance problem definition has been generated, the analyst develops a
logical model of the system. A search for alternatives is analyzed carefully. There are 3 parts in
feasibility study.

2.1.1 Operational Feasibility


Question that going to be asked are Will the system be used if it developed and implemented.
If there was sufficient support for the project from the management and from the users.
Have the users been involved in planning and development of the Project.

2.1.2 Technical feasibility

Does the necessary technology exist to do what is been suggested Does the proposed equipment have
the technical capacity for using the new system? Are there technical guarantees of accuracy,
reliability and data security? The project is developed on Pentium III with 128 MB RAM.
The environment required in the development of system is any windows platform.
The observer pattern along with factory pattern will update the results eventually.
The language used in the development is PHP, Apache Server and database as MySQL.

2.1.2 Economical Feasibility

To decide whether a project is economically feasible, to consider various factors as cost benefit
analysis, long-term returns and maintenance costs.
2.2 FUNCTIONAL REQUIREMENTS
Functional requirement defines a function of a software system or its component. A function is
described as a set of inputs, the behaviour, and outputs. Functional requirements may be
calculations, technical details, data manipulation and processing and other specific functionality
that define what a system is supposed to accomplish. Behavioural requirements describing all
the cases where the system uses the functional requirements are captured in use cases.

NUMBER OF MODULES

The system after careful analysis has been identified to be presented with the following
modules:

Event Management System Module


In EMS project we use PHP and MySQL database. It has two modules.
1.Admin Module
2.User Module

Admin Module

1. Dashboard: In this section, admin can see all detail in brief like listed categories,
Sponsors, Total Events, Total Registered Users, Total Booking, Total New Booking,
Total Confirmed Booking and Total Cancelled Booking.
2. Category: In this section, admin manage event category (add and update).
3. Manage Sponsors: In this section, admin can add sponsors and manage sponsors details
(Add/Update/Delete).
4. Events: In this section, admin manage events (add and update).
5. Manage Users: In this section, admin can update details of registered users and also block
them.
6. Manage Booking: In this section, admin can manage booking by cancel and confirm it.
7. News: In this section admin manage news (add and delete).
8. Website Setting: In this section, admin can update about us and another general website
setting.

Admin can also update his profile, change password and recover password.
User Module

In this module there is two types of user guest user and registered user.
Guest User: In this guest user can see only general information like about us, event details,
contact details and new about events.

Registered users can do following activity

1.Books the events.

2.Update his/her own profile.

3.Change Password.

4.Users can also cancel booking which is not confirmed.

5.Registered user can also recover his/her own password.


REQUIREMENT

4.1 HARDWARE REQUIREMENT :-


Processor : Pentium IV and latest
Hard Disk : 40GB
RAM : 512MB or more.

4.2 SYSTEM REQUIRMENT:-


APPLICATION SOFTWARE:-
Operating System : Windows95/ 2000/XP.
User Interface : HTML, CSS.
Client-side Scripting : JavaScript.
Server-side Scripting : PHP.
IDE : visual studio Editor
Database : My SQL 5.0(Backend)
Server Deployment : XAMMP Server
FRANTEND Software : HTML,PHP
BACKEND SOFTWARE : MY SQL 5.0
CONCLUSION

The “Event Management System” was successfully designed and is tested for accuracy
and quality.During this project we have accomplished all the objectives and this project
meets the needs of the organization. The developed will be used in searching, retrieving
and generating information for the concerned requests.

GOALS ACHIVIED
 Reduced entry work
 Easy retrieval of information
 Reduced errors due to human intervention
 User friendly screens to enter the data
 Portable and flexible for further enhancement
 Web enabled.
 Fast finding of information request

You might also like