EVENT MANAGEMENT SYSTEM.docx EVENT MANAGEMENT SYSTEM.docx EVENT MANAGEMENT SYSTEM.docx

EVENT MANAGEMENT SYSTEM
This Project Report is submitted in partial fulfilment of the
requirements for the award of the degree of
Master of Computer Applications
Submitted by
SANNIDHI NAGA MACHARI KIRANMAI
2385351101
Under the Esteemed Guidance of
Mr. G. RAMESH KUMAR
Assistant Professor
B.V. RAJU COLLEGE
Vishnupur :: Bhimavaram
Submitted to
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
COLLEGE OF ENGINEERING
ADIKAVI NANNAYA UNIVERSITY
RAJAHMAHENDRAVARA
M 2024-2025

Vishnupur, Bhimavaram.
Accredited by NAAC With B++
Grade
(Affiliated to Adikavi Nannaya University)
DEPARTMENT OF MCA
CERTIFICATE
This is to certify that this project entitled “EVENT MANAGEMENT SYSTEM”
submitted in partial fulfilment of the degree of MASTER OF COMPUTER
APPLICATIONS to Adikavi Nannaya University from 7i Tech Solutions, Hyderabad
through B.V.Raju College, done by Ms. SANNIDHI NAGA MACHARI KIRANMAI,
2385351101 is an authentic work carried out by her during the Academic Year 2024-2025
under my guidance. The matter embodied in this project work has not been submitted
earlier for award of any degree or diploma to the best of my knowledge and belief.
Internal Guide Head of the Department
External Examiner Principal

ACKNOWLEDGEMENT
The satisfaction and euphoria that accompany the successful completion of any task
would be incomplete without the mention of people who made it possible, whose
constant guidance and encouragement crowned our efforts with success. It is a pleasant
aspect that I have now the opportunity to express my gratitude for all of them.
The first person I would like to thank Dr. I.R. KRISHNAM RAJU, Principal,
B.V. RAJU College, Bhimavaram. His wide knowledge and logical way of thinking
have made a deep impression on me. His understanding, encouragement and personal
guidance have provided the basis for this thesis. He is a source of inspiration for
innovative ideas and his kind support is well known to all his students and colleagues.
I wish to thank Dr. V. BHASKARA MURTHY, Professor & HOD, Dept. of MCA.
His support and valuable suggestions for the successful completion of this project.
I wish to thank my guide, Mr. G RAMESH KUMAR , Assistant Professor, Dept.
of MCA his support and valuable suggestions for the successful completion of this
Project.
SANNIDHI NAGA MACHARI KIRANMAI
2385351101

DECLARATION
This is to certify that the project report entitled “EVENT MANAGEMENT
SYSTEM” is done by me is an authentic work carried out for the partial fulfilment
of the requirements for the award of the degree of MASTER OF COMPUTER
APPLICATIONS under the guidance of the Mr. G. RAMESH KUMAR, Assistant
Professor. The matter embodied in this project work has not been submitted earlier
for award of any degree or diploma to the best of my knowledge and belief.
Signature of the
Student SANNIDHI NAGA MACHARI
KIRANMAI
2285351101
B.V. Raju College

INDEX
Chapter Page No.
1. INTRODUCTION 1-2
1.1 Specific Objectives 2
1.2 Scope of the study 2
2. LITERATURE SURVEY 3-4
3. SYSTEM ANALYSIS 5-9
3.1 Existing System 6
3.2 Proposed System 6
3.3 Feasibility Study 6-7
3.4 Requirements Analysis 8-9
3.4.1 System Requirements 8
3.4.2 Requirements Gathering Stage 8
3.4.3 Analysis stage 9
4. SYSTEM DESIGN 10-26
4.1 Designing Stage 11
4.2 Development Stage 12
4.3 Integration & Test Stage 12-13
4.4 System Architecture 14-15
4.5 UML Diagrams 20-21
4.5.1 Use Case Diagram 16
4.5.2 Class Diagram 17
4.5.3 Context Diagram 18
4.5.4 Flowchart Diagram 19
4.6 Input and Output Design 20-21
5. SYSTEM IMPLEMENTATION 22-30
6. SYSTEM TESTING 31-33

7. SCREENS 34-40
8. CONCLUSION 41-42
9. BIBILIOGRAPHY 43-44

LIST OF FIGURE
S.No Fig.No Fig.Name Pg.No
1 4.4.1 Architecture Flow 14
2 4.4.2 URL Pattern 15
3 4.5.1 Use-Case Diagram 16
4 4.5.2 Class Diagram 17
5 4.5.3 Context Diagram 18
6 4.5.4 Flowchart Diagram 19

1. INTRODUCTION
Event management system was web-based application that enhanced project management
to the creation and development of large scale events such as festivals, conferences,
ceremonies, weddings, formal parties, concerts, or conventions. It involved studying the
brand, identifying its target audience, devising the event concept, and coordinating the
technical aspects before actually launching the event. The Event management system (OEMS)
enabled customers/ clients view various packages/products about the event and make booking
through the platform. The process of plam1ing and coordinating the event is usually referred
to as event plam1ing and it included budgeting, scheduling, site selection, acquiring necessary
permits, coordinating 1;ransportation and parking, arranging for speakers or entertainers,
arranging decor, event security, catering, coordinating with third party vendors, and
emergency plans. Each event was different in its nature so process of planning & execution of
each event differed on basis of type of event.(https://www.wikipedia.com/ event-
managementsystem)
1.2 Problem Statement
CmTently Event Management system is manual and only accessible to staff. The
client has to travel to the company offices in order to schedule, book and organize an event
such as Birthday Party, Marriage, Reception, and Ring Ceremony. Clients pay cash to book
for an event which is inconveniencing when customers are many at the company. It takes lots
of time of customer because they have to search such event organizer and contact them
individually so an event management system is needed which will enable the customer make
booking, schedule events online at any preferred time.
1.3 Scope of the study
This includes physical scope which describes the physical area of application where
the project will be applied and technical scope describes the functionalities in proposed
system.

2. LITERATURE SURVEY
This section summarizes the contents of the literature review that is event
management systems defined; event management systems evolution and trend; event
management Architecture; Benefits of EMS (proposed system).
In the existing system customer contacts the company for event management. He
provides the details of the event and its requirements. He explains its aims, how long it will
last, its format (Presentation/Workshop and/or Exhibition etc.), expected number of
delegates/guests, equipment and furniture required, whether any delegate pack or promotional
material is to be distributed, and other facilities required.
The Event Manager studies the requirements of the event carefully and using the event
management system. The company offers some readymade packages to choose from.
If the customer agrees, the event is booked and the advance deposit is taken by the
company. According to the requirements of the event, different bookings are made. A
strategic schedule is prepared for smooth conduct of the event. The Event Management
System helps the manager in different tasks of planning, scheduling and Conducting the
event. This system provides instant access to event-related information. Thus, resources are;

3. SYSTEM ANALYSIS
3.1 Existing System
In the existing buying and selling of products is done manually. All the details of the
products to be sold or purchased is maintained manually.
3.2 Proposed System
The development of this system contains the following activities, which try to
automate the entire process keeping in the view of database integration approach. This system
maintains employee’s personal, address, and contact details. User friendliness is provided in
the application. To make an event successful event manager needs different service provider
like Sound systems services, Lighting providers, Canteen services, stage construction and so
on. In present system event company have to do all management work manually. They keep
all payment information on papers. There is no system to check the past expenses on any
event. To do this they have to check payment register and this task is very time consuming
and tiresome. Keeping all these problem in mind we have developed this system. This system
helps the event management company to manage their paper work online and they can also
retrieve report of last event they have completed.
3.3 Feasibility Study
The feasibility of the project is analyzed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates. During system analysis
the feasibility study of the proposed system is to be carried out. This is to ensure that the
proposed system is not a burden to the company. For feasibility analysis, some understanding
of the major requirements for the system is essential.
Three key considerations involved in the feasibility analysis are
♦ ECONOMIC FEASIBILITY
♦ TECHNICAL FEASIBILITY
♦ SOCIAL FEASIBILITY

Economic Feasibility
This study is carried out to check the economic impact that the system will have on
the organization. The amount of fund that the company can pour into the research and
development of the system is limited. The expenditures must be justified. Thus the developed
system as well within the budget and this was achieved because most of the technologies used
are freely available. Only the customized products had to be purchased.
Technical Feasibility
This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the
available technical resources. This will lead to high demands on the available technical
resources. This will lead to high demands being placed on the client. The developed system
must have a modest requirement, as only minimal or null changes are required for
implementing this system.
Social Feasibility
The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system
and to make him familiar with it. His level of confidence must be raised so that he is also able
to make some constructive criticism, which is welcomed, as he is the final user of the system.

3.4 Requirement Analysis
3.4.1 System Requirements
Hardware Requirements
⮚ System : Pentium Dual Core.
⮚ Hard Disk : 120 GB.
⮚ Monitor : 15’’ LED
⮚ Ram : 1 GB
Software Requirements
⮚ Operating system : Windows 7/10.
⮚ Coding Language : JAVA/J2EE
⮚ Tool : Net Beans.
⮚ Database : MYSQ
⮚
3.4.2 Requirements Gathering stage:
The requirements gathering process takes as its input the goals identified in the high-
level requirements section of the project plan. Each goal will be refined into a set of one or
more requirements. These requirements define the major functions of the intended
application, define operational data areas and reference data areas, and define the initial data
entities. Major functions include critical processes to be managed, as well as mission critical
inputs, outputs and reports. A user class hierarchy is developed and associated with these
major functions, data areas, and data entities. Each of these definitions is termed a
Requirement. Requirements are identified by unique requirement identifiers and, at minimum,
contain a requirement title andtextual description.
These requirements are fully described in the primary deliverables for this stage: the
Requirements Document and the Requirements Traceability Matrix (RTM). The requirements

document contains complete descriptions of each requirement, including diagrams and
references to external documents as necessary. Note that detailed listings of database tables
and fields are not included in the requirements document.

3.4.3 Analysis Stage:
The planning stage establishes a bird's eye view of the intended software product, and
uses this to establish the basic project structure, evaluate feasibility and risks associated with
the project, and describe appropriate management and technical approaches.
The most critical section of the project plan is a listing of high-level product
requirements, also referred to as goals. All of the software product requirements to be
developed during the requirements definition stage flow from one or more of these goals. The
minimum information for each goal consists of a title and textual description, although
additional information and references to external documents may be included. The outputs of
the project planning stage are the configuration management plan, the quality assurance plan,
and the project plan and schedule, with a detailed listing of scheduled activities for the
upcoming Requirements stage, and high level estimates of effort for the out stages.

4. SYSTEM DESIGN
4.1 Designing Stage:
The design stage takes as its initial input the requirements identified in the approved
requirements document. For each requirement, a set of one or more design elements will be
produced as a result of interviews, workshops, and/or prototype efforts. Design elements
describe the desired software features in detail, and generally include functional hierarchy
diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudo
code, and a complete entity-relationship diagram with a full data dictionary. These design
elements are intended to describe the software in sufficient detail that skilled programmers
may develop the software with minimal additional input.
When the design document is finalized and accepted, the RTM is updated to show that
each design element is formally associated with a specific requirement. The outputs of the
design stage are the design document, an updated RTM, and an updated project plan.

4.2 Development (Coding) Stage:
The development stage takes as its primary input the design elements described in the
approved design document. For each design element, a set of one or more software artifacts
will be produced. Software artifacts include but are not limited to menus, dialogs, data
management forms, data reporting formats, and specialized procedures and functions.
Appropriate test cases will be developed for each set of functionally related software artifacts,
and an online help system will be developed to guide users in their interactions with the
software.
The RTM will be updated to show that each developed artifact is linked to a specific
design element, and that each developed artifact has one or more corresponding test case
items. At this point, the RTM is in its final configuration. The outputs of the development
stage include a fully functional set of software that satisfies the requirements and design
elements previously documented, an online help system that describes the operation of the
software, an implementation map that identifies the primary code entry points for all major
system functions, a test plan that describes the test cases to be used to validate the correctness
and completeness of the software, an updated RTM, and an updated project plan.
4.3 Integration & Test Stage:
During the integration and test stage, the software artifacts, online help, and test data are
migrated from the development environment to a separate test environment. At this point, all
test cases are run to verify the correctness and completeness of the software. Successful
execution of the test suite confirms a robust and complete migration capability. During this
stage, reference data is finalized for production use and production users are identified and
linked to their appropriate roles. The final reference data (or links to reference data source
files) and production user list are compiled into the Production Initiation Plan.
The outputs of the integration and test stage include an integrated set of software, an
online help system, an implementation map, a production initiation plan that describes
reference data and production users, an acceptance plan which contains the final suite of test
cases, and an updated project plan.

♦ Installation & Acceptance Test:
During the installation and acceptance stage, the software artifacts, online help, and
initial production data are loaded onto the production server. At this point, all test cases are
run to verify the correctness and completeness of the software. Successful execution of the
test suite is a prerequisite to acceptance of the software by the customer.
After customer personnel have verified that the initial production data load is correct
and the test suite has been executed with satisfactory results, the customer formally accepts
the delivery of the software.
The primary outputs of the installation and acceptance stage include a production
application, a completed acceptance test suite, and a memorandum of customer acceptance of
the software. Finally, the PDR enters the last of the actual labor data into the project schedule
and locks the project as a permanent project record. At this point the PDR "locks" the project
by archiving all software items, the implementation map, the source code, and the
documentation for future reference.
Maintenance:
Outer rectangle represents maintenance of a project, Maintenance team will start with
requirement study, understanding of documentation later employees will be assigned work
and they will under go training on that particular assigned category.
For this life cycle there is no end, it will be continued so on like an umbrella (no ending point
to umbrella sticks).

4.4 SYSTEM ARCHITECTURE
Architecture flow:
`Below architecture diagram represents mainly flow of requests from users to database
through servers. In this scenario overall system is designed in three tires separately using
three layers called presentation layer, business logic layer and data link layer. This project
was developed using 3-tire architecture.
Request Response
Fig 4.4.1
User
Dat
a
Bas
SERVE
R

URL Pattern:
Response sent
from the
URL Request
sent through the
Reply from the
database
according to the
Verifying or
updating
the
database
through a
statement
Fig 4.4.2
URL pattern represents how the requests are flowing through one layer to another layer and
how the responses are getting by other layers to presentation layer through server in
architecture diagram.
DAT
E
SER
TS AT
SERV
P
enta
Lay

4.5 UML DIAGRAMS
4.5.1 Use-case Diagram

4.6 INPUT DESIGN & OUTPUT DESIGN
INPUT DESIGN
Input design is part of overall system design that requires special attention designing
input data is to make the data entered easy and free from errors. The input forms are designed
using the controls available in .NET framework. Validation is made for each and every data
that is entered. Help information is provided for the users during when the customer feels
difficult.
Input design is the process of converting the user originated inputs to a computer
based format. A system user interacting through a workstation must be able to tell the system
whether to accept the input to produce reports. The collection of input data is considered to be
most expensive part of the system design. Since the input has to be planned in such a manner
so as to get relevant information, extreme care is taken to obtain pertinent information.
This project first will entered to the input of allocation forms it will be created on
student details form and subject entry form, time table form .it will helps to calculate subject
wise attendance system. Next one if u wants any verification on your data’s also available in
details show forms. Attendance to entered single subject wise or all subject wise attendance
system available in this project

OUTPUT DESIGN
Output design this application “Student Attendance management system”generally
refers to the results and information that are generated by the system for many end-users;
output is the main reason for developing the system and the basis on which they evaluate the
usefulness of the application.
The output is designed in such a way that it is attractive, convenient and informative.
Forms are designed with various features, which make the console output more pleasing.
As the outputs are the most important sources of information to the users, better
design should improve the system’s relationships with us and also will help in
decisionmaking. Form design elaborates the way output is presented and the layout available
for capturing information.
One of the most important factors of the system is the output it produces. This system
refers to the results and information generated. Basically the output from a computer system
is used to communicate the result of processing to the user.
Attendance management system to show the report subject wise attendance
maintaining by staffs. Taken as a whole report obtain on a administrator privileges only. this
forms will show weekly report and consolidate report generated date, batch, and class wise to
our end user. we want to change our report to convert Excel format .if you want change any
modification.

5. SYSTEM IMPLEMENTATION
SOURCE CODE
Index.html
Event Management System.
● Home
● Admin
● Employee
● User
● Registration
About Event Management System
The development of this system contains the following activities, which try to
automate the entire process keeping in the view of database integration approach. This system
maintains employee’s personal, address, and contact details. User friendliness is provided in
the application. To make an event successful event manager needs different service provider
like Sound systems services, Lighting providers, Canteen services, stage construction and so
on. In present system event company have to do all management work manually. They keep
all payment information on papers. There is no system to check the past expenses on any
event. To do this they have to check payment register and this task is very time consuming
and tiresome. Keeping all these problem in mind we have developed this system. This system
helps the event management company to manage their paper work online and they can also
retrieve report of last event they have completed.
© 2022. All Rights Reserved. Designed by Venkat Java Projects
●
●
●

Admin Login.jsp
<%--
Document : Admin
Created on : Feb 15, 2022, 11:09:21
PM Author : Venkat
--%>
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title> Event Management System</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="Free HTML5 Website Template
freehtml5.co" />
<meta name="keywords" content="free website templates, free html5, free
template, free bootstrap, free website template, html5, css3, mobile first, responsive" />
<meta name="author" content="freehtml5.co" />

<meta property="og:title" content=""/>
<meta property="og:image" content=""/>

background-color:green;
}
table tr td
{
padding:15px
}
</style>
</head>
<body>
<div class="fh5co-loader"></div>
<div id="page">
<nav class="fh5co-nav" role="navigation">

<div class="container">
<div class="row">
<div class="col-xs-12 text-center logo-wrap">
</div>
<div class="col-xs-12 text-center menu-1 menu-wrap">
<ul>
<li class="active"><a href="index.html">Home</a></li>
<li><a href="Admin.jsp">Admin</a></li>

<li><a href="Employee.jsp">Employee</a></li>
<li><a href="User.jsp">User</a></li>
<li><a href="Register.jsp">Registration</a></li>
</ul>
</div>
<header id="fh5co-header" class="fh5co-cover js-fullheight" role="banner"
style="background-image: url(images/hero_1.jpeg);" data-stellar-
background- ratio="0.5">
<div class="overlay"></div>
<div class="container">
<div class="row">
<div class="col-md-12 text-center">
<div class="display-t js-fullheight">
<div class="display-tc js-fullheight animate-box" data-animate-effect="fadeIn">
<div class="row copyright">
<div class="col-md-12 text-center">
<p>
<small class="block">© 2022. All Rights Reserved.</small>
<small class="block">Designed<a href="" target="_blank">Java Projects</a>
</p>
<p>
<ul class="fh5co-social-icons">

6. SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the Software system meets its
requirements and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.
TYPES OF TESTS
Unit Testing
Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program inputs produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual software
units of the application .it is done after the completion of an individual unit before integration.
This is a structural testing, that relies on knowledge of its construction and is invasive. Unit
tests perform basic tests at component level and test a specific business process, application,
and/or system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined inputs and
expected results.
Integration Test
Integration tests are designed to test integrated software components to determine if
they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the components
were individually satisfaction, as shown by successfully unit testing, the combination of
components is correct and consistent. Integration testing is specifically aimed at exposing the
problems that arise from the combination of components.
Functional Test
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.

System Test
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing is
the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.
White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.
Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the
software under test is treated, as a black box .you cannot “see” into it. The test provides inputs
and responds to outputs without considering how the software works.
6.2 Integration Testing
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by interface
defects.
The task of the integration test is to check that components or software applications,
e.g. components in a software system or – one step up – software applications at the company
level – interact without error.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
6.3 Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

7. SCREENS
HOME PAGE
Admin Login Page

Admin Home Page
Create New Event

View Events List
Add New Event Location

Update Events
In above screen click on ‘Click Here’ link to update any record and to get below screen

8. CONCLUSION
This chapter contains the discussion of the research findings, the conclusions that the
researcher made from the findings of the research and also the recommendations made by the
researcher about the research topic. It is a summary of what was achieved by the researcher,
the challenges encountered as well as recommendations for future work on the developed
system
The project aim was automating the processes of booking at Fruitions Event Planners
through the Design and Development of an event management system.
The main objective of the research project was to design and develop an event 1;1-
anagement system. This objective was achieved and the developed system has the
functionalities that were proposed by the different system users.
The first specific objective was to review the current event managements system. This
was done in chapter two where a number of literatures relating to the research problem were
reviewed which helped in identifying the gaps in the related work that was already done by
other researchers.

9. BIBILIOGRAPHY
1. Amite Sharma et al. / International Journal of Engineering Science and Technology (IJEST)
2. ://www.wikipedia.com/ -event-management- https system
3. Ramsborg, G.C.; B Miller, D Breiter, BJ Reed & A Rushing (eds), Professional meeting
management: Comprehensive strategies for meetings, conventions and events, 2008, 5th ed,
Kendall/Hunt Publishing, Dubuque, Iowa. ISBN 0-7575- 5212-9
4. Bowdin, Glenn; Johnny Allen, William O'Toole, Rob Harris, Ian McDonnell, 2010. Events
Management (Events Management S.) ISBN 0-7506-6533-5
5. http:/ /www.wikipedia.com/ event+management+officail +version. pdf
6. https://www.finances.com/top-10-event-management-software
7. Ramsborg, G.C.; B Miller, D Breiter, BJ Reed & A Rushing (eds), Professional meeting
management: Comprehensive strategies for meetings, conventions and events, 2008, 5th ed,
Kendall/Hunt Publishing, Dubuque, Iowa. ISBN 0-7575- 5212-9
8. Roy Want, An Introduction to RFID Technology, IEEE Pervasive Computing, v.5 n.1,
p.25-33, January 2006
9. R.G. Mair, "Protocol-Independent Detection of Passive Transponders for NearField
Communication Systems. Instrumentation and Measurement". IEEE Trans. 59,814 (2010).
10. Nicolas T. Courtois. "The dark side of security by obscurity - and cloning MiFare
11. Classic rail and building passes. anywhere. anytime". In Proceedings of the International
Conference on Security and Cryptography, pages 331-338. INSTICC Press. 2009.

EVENT MANAGEMENT SYSTEM.docx EVENT MANAGEMENT SYSTEM.docx EVENT MANAGEMENT SYSTEM.docx

More Related Content

Similar to EVENT MANAGEMENT SYSTEM.docx EVENT MANAGEMENT SYSTEM.docx EVENT MANAGEMENT SYSTEM.docx (20)

More from spub1985 (20)

Recently uploaded (20)

EVENT MANAGEMENT SYSTEM.docx EVENT MANAGEMENT SYSTEM.docx EVENT MANAGEMENT SYSTEM.docx