Fyp Areeba Fayyaz S22-045

THE SUPERIOR UNIVERSITY, LAHORE
ASSOCIATE DEGREE PROGRAMS
Final Year Project

PROJECT REPORT
Event Management System
Project ID: FYP-ADP-S22-045
Project Team
Student Name Student ID Program Contact Number Email Address
Fatima Aslam ADCS-S22-001 ADP-CS 03286778745 adcs-s22-001@gmail.com
Areeba Fayyaz ADCS-S22-045 ADP-CS 03284042904 adcs-s22-045@gmail.com
Ammar Abdul Saboor ADCS-S22-046 ADP-CS 03024588078 adcs-s22-046@gmail.com
[Project Supervisor]
Sir Rauf Bhatti.
(Lecturer)
Project Report: Event Management System
Project Report
Event Management system
Change Record
Author(s) Version Date Notes Supervisor’s Signature
Areeba Fayyaz 1.0 16/8/2023 Event Management

system is used to
manage all the
activity related to
event for providing
many services at
work.
Sir Rauf 1.1 04/9/2023 Advised to create a

better Event
Management system
experience.
Fatima Aslam 1.2 07/10/2023 Advised to separate

Services rather than
difficulty
Areeba Fayyaz 1.3 21/10/2023 Final draft where
every system is
working as intended.
Ammar Abdul Saboor 1.4 21/10/2023 Final draft where
every system is
working as intended
Sir Muhammad 1.5 10/1/2024 Final Every system is
Qasim Shah & working Good
Sir Rauf Bhatti Advised some
changes on
Documentation
Faculty of CS&IT, Superior University Lahore, Pakistan ii

APPROVAL
PROJECT SUPERVISOR
Comments:
Name:
Date: Signature:
PROJECT MANAGER
Comments:
Date: Signature:
HEAD OF THE DEPARTMENT

Comments:
Date: Signature:
Faculty of CS&IT, Superior University Lahore, Pakistan iii

Dedication
This final project report is devotedly dedicated to Allah Almighty, The Holy
Prophet Muhammad (S.A.W.W), our respective Parents and Teachers who
have been our constant source of inspiration. They have given us the drive and
discipline to tackle any task with enthusiasm and determination. Without their
love and support this project would not have been made possible.
Faculty of CS&IT, Superior University Lahore, Pakistan iv

Acknowledgements
It is incumbent upon us to express our fervent gratitude to almighty ALLAH the most
compassionate and merciful for giving us the courage to achieve this task in the field of
Game Development.
We are indeed respectfully grateful to the Holy Prophet Muhammad (S.A.W.W) who is
forever a source of guidance and idea for all mankind.
We would like to express our immense gratitude to our instructor Sir Rauf bhatti for his
regular support and motivation that has encouraged us to come up with this project as well
as our project supervisor Sir Rauf Bhatti
We are also thankful to our teachers and friends who have provide their whole-hearted
support at all times for the successful completion of our project “Interactive Traffic Lights.
May GOD almighty Allah infuse us, with the energy to fulfill their gracious objectives and
expectations and to further enlighten our competence!
Faculty of CS&IT, Superior University Lahore, Pakistan v

Executive Summary
An event management system provides campus event planners a flexible, fully integrated solution to
simplify the event management process and keep your customers, faculty and student happy, while
maintaining important reports and data for making real estate and future planning decisions.
Faculty of CS&IT, Superior University Lahore, Pakistan vi

Table of Contents
Dedication....................................................................................................................................... iv
Acknowledgements.......................................................................................................................... v
Executive Summary.........................................................................................................................vi
Table of Contents........................................................................................................................... vii
List of Figures....................................................................................................................................x
List of Tables.................................................................................................................................... xi
Chapter 1..........................................................................................................................................1
Introduction......................................................................................................................................2
1.1. Background........................................................................................................................2
1.2. Motivations and Challenges.............................................................................................. 2
1.3. Goals and Objectives......................................................................................................... 2
1.4. Literature Review/Existing Solutions.................................................................................2
1.5. Proposed Solution............................................................................................................. 3
1.6. Gap Analysis.......................................................................................................................3
1.7. Project Plan........................................................................................................................4
1.7.1. Work Breakdown Structure........................................................................................... 4
1.7.2. Roles & Responsibility Matrix........................................................................................ 5
1.7.3. Gantt Chart.................................................................................................................... 6
1.8. Report Outline................................................................................................................... 7
Chapter 2..........................................................................................................................................8
Software Requirement Specifications.............................................................................................. 9
2.1. Introduction.......................................................................................................................9
2.1.1. Purpose.......................................................................................................................... 9
2.1.2. Document Conventions................................................................................................. 9
2.1.3. Intended Audience and Reading Suggestions................................................................9
2.1.4. Product Scope.............................................................................................................. 10
2.1.5. References................................................................................................................... 10
2.2. Overall Description.......................................................................................................... 10
2.2.1. Product Perspective..................................................................................................... 10
2.2.2. Product Functions........................................................................................................ 10
2.2.3. User Classes and Characteristics.................................................................................. 10
2.2.4. Operating Environment............................................................................................... 10
2.2.5. Design and Implementation Constraints..................................................................... 11
2.2.6. Assumptions and Dependencies.................................................................................. 11
2.3. External Interface Requirements.....................................................................................11
2.3.1. User Interfaces.............................................................................................................11
2.3.2. Hardware Interfaces.................................................................................................... 12
2.3.3. Software Interfaces......................................................................................................12
2.3.4. Communications Interfaces......................................................................................... 13
2.4. System Features.............................................................................................................. 13
2.4.1. Opening the initial UI...................................................................................................... 13
2.4.1.1. Description and Priority............................................................................................13
2.4.1.2. Stimulus/Response Sequences.................................................................................13
2.4.1.3. Functional Requirements......................................................................................... 13
2.4.2. Driving.......................................................................................................................... 13
Faculty of CS&IT, Superior University Lahore, Pakistan vii

2.4.2.1. Description and Priority..........................................................................................133

2.4.2.2. Stimulus/Response Sequences................................................................................ 14
2.4.2.3. Functional Requirements......................................................................................... 14
2.4.3. Consequense System...................................................................................................14
2.5. Other Nonfunctional Requirements................................................................................14
2.5.1. Performance Requirements.........................................................................................14
2.5.2. Safety Requirements....................................................................................................14
2.5.3. Security Requirements.................................................................................................15
2.5.4. Buisness Rules..............................................................................................................15
2.6. Other Requirements........................................................................................................ 15
2.6.1. Cloud Ready................................................................................................................. 15
2.6.2. Loosely Typed.............................................................................................................. 15
2.6.3. Open Source.................................................................................................................15
2.6.4. Platform Independent..................................................................................................16
Chapter 3........................................................................................................................................17
Use Case Analysis........................................................................................................................... 18
3.1. Use Case Model............................................................................................................... 18
3.2. Use Case Descriptions......................................................................................................19
Chapter 4........................................................................................................................................25
System Design................................................................................................................................ 26
4.1. Architecture Diagram...................................................................................................... 27
4.2. Domain Model................................................................................................................. 28
4.3. Class Diagram.................................................................................................................. 29
4.4. Sequence / Collaboration Diagram..................................................................................30
4.5. Component Diagram....................................................................................................... 31
4.6. Activity Diagram.............................................................................................................. 32
4.7. State Transition Diagram................................................................................................. 33
4.8. Deployment Diagram.......................................................................................................34
Chapter 5........................................................................................................................................35
Implementation..............................................................................................................................36
5.1. Components, Libraries, Web Services and stubs.............................................................36
5.2. Deployment Environment............................................................................................... 36
5.3. Tools and Techniques...................................................................................................... 36
5.4. Best Practices / Coding Standards................................................................................... 37
5.5. Version Control................................................................................................................38
Chapter 6........................................................................................................................................39
Testing and Evaluation................................................................................................................... 39
6.1. Use Case Testing..............................................................................................................40
6.2. Data flow testing............................................................................................................. 40
6.3. Equivalence partitioning..................................................................................................40
6.4. Boundary value analysis.................................................................................................. 40
6.5. Unit testing...................................................................................................................... 41
6.6. Integration testing........................................................................................................... 41
6.7. Performance testing........................................................................................................ 41
6.8. Stress Testing...................................................................................................................41
Chapter 7........................................................................................................................................42
Summary, Conclusion and Future Enhancements......................................................................... 43
Faculty of CS&IT, Superior University Lahore, Pakistan viii

7.1. Project Summary............................................................................................................. 43

7.2. Achievements and Improvements...................................................................................43
7.3. Critical Review................................................................................................................. 43
7.4. Lessons Learnt................................................................................................................. 43
7.5. Future Enhancements/Recommendations...................................................................... 43
Reference and Bibliography........................................................................................................... 45
Index...............................................................................................................................................47
Faculty of CS&IT, Superior University Lahore, Pakistan ix

List of Figures
1.1 Gantt Chart 5

2.2 Use Case Model 17
4.1 Architecture Diagram 26
4.2 Domain Model 27
4.3 Entity Relationship Diagram 28
4.3 Entity Relationship Diagram 28
4.4 Class Diagram 29
4.5 Sequence / Collaboration Diagram 30
4.6 Component Diagram 31
4.7 Activity Diagram 32
4.8 State Transition Diagram 33
4.9 Deployment Diagram 34
Faculty of CS&IT, Superior University Lahore, Pakistan x

List of Tables
1.1 Roles & Responsibility Matrix 3

3.1 Use Case Table 1 18
Faculty of CS&IT, Superior University Lahore, Pakistan xi

Chapter 1
Introduction
Project Report: Event Management system
Chapter 1: Introduction
1.1. An event management system provides campus event planners a flexible, fully integrated
solution to simplify the event management process and keep your customers, faculty and
student happy, while maintaining important reports and data for making real estate and future
planning decisions.
1.2. Background
An event management system (or event management software) is a digital tool that streamlines the
planning, organization, and execution of events. It encompasses a range of features such as event
registration, ticketing, venue selection, scheduling, attendee engagement, and post-event analysis.
By using event management software, event organizers can simplify their tasks and more efficiently
manage logistics, communicate with participants, and analyze data to enhance future events. Not to
mention, event management software offers a centralized platform for coordination, reducing
manual efforts and increasing precision, ultimately enhancing the overall success and efficiency of
events
1.3. Motivations and Challenges

Our motivation for choosing this particular idea as our project was to educate people on the
uses of Event Management System, what the various different mean and why they are
important for safe driving by highlighting the consequences of not following them in a
family-friendly manner. The only challenge we are facing is the lack of expertise in Game
Development but with the help of our Instructor we are making good progress.
1.4. Goals and Objectives

A huge number of people, especially the younger generation, are unaware of the many
types of Events. Events such as the “Birthday” and the “Wedding” are often easy to
manage events
1.5. Literature Review/Existing Solutions
An event management system provides campus event planners a flexible, fully integrated solution to simplify
the event management process and keep your customers, faculty and student happy, while maintaining
important reports and data for making real estate and future planning decisions.
Faculty of CS&IT, Superior University Lahore, Pakistan 2

contain some game-like elements like UI and a “Health System” but other than that it has no
resemblance to our product much less a real game.
1.6. Proposed Solution

Our solution is to teach people the meaning as well as the importance of these signs
through the use of an interactive 3D game. The game will be comprised of multiple levels
with each level made up of different tracks. The tracks would be similar to roads that a
person may encounter in the real world and along the sides of the tracks would be various
traffic signs. Each time the driver/player encounters a new sign he/she would be told its
meaning and importance. The next time the player encounters that sign he must act
accordingly. Keeping check of the signs the player must reach his/her destination.
1.7. Gap Analysis

Gap Analysis for the Interactive Traffic Signs Game Project:
1. Current State Assessment:
Current traffic sign education lacks interactive and engaging methods for learners to
understand and effectively apply knowledge. Traditional methods such as textbooks
and still images may not fully capture the dynamic nature of real-world driving
scenarios.
2. Learning Experience Gap:
Current learning experiences fail to provide an engaging and practical environment
for learners to develop a comprehensive understanding of traffic signs. Lack of
opportunity to apply theoretical knowledge in real driving situations. The lack of
interactive feedback systems and real-time assessment hinders the ability to assess
learner progress and identify areas for improvement.
3. Technological Gap:
Current educational resources and tools cannot fully utilize the potential of
technology to enhance the learning experience. The lack of interactive, immersive
and visually appealing platforms limits learner engagement and motivation.
4. Integration Gap:
There is a gap between existing traffic information and its integration into simulated
driving. Students often find it difficult to bridge the gap between theoretical

knowledge and practical applications. This difference is heightened by the lack of

games that integrate traffic awareness, interpretation, and appropriate responses.
5. Comprehensive Content Gap:
Existing solutions may not include all traffic signs, including less obvious or region-
specific signs.
1.8. Project Plan

The Project is to be completed as we are learning about Game Development in our class so
the project must be planned accordingly.
1.8.1. Work Breakdown Structure
1. Scripting
1.1. Coding.
1.2. Testing.
1.3. Simulation.
2. Assets
2.1. Asset Collection
2.2. Sign Design
2.3. Home Page Design
3. Models
3.1. Services
3.2. Designing
3.3. Quality Check

1.8.2. Roles & Responsibility Matrix

WBS WBS Deliverable Activity # Activity to Duration Responsible Team
Complete the (# of Days) Member(s) & Role(s)
#
Deliverable
1 Coding. 7 14 Fatima Aslam
2 Testing. 8 50 Areeba Fayyaz
3 Simulation. 9 21 Ammar Abdul Saboor
4 Asset Collection 3 5 Fatima Aslam
5 Sign Design 4 7 Areeba Fayyaz
6 home Design 5 21 Ammar Abdul Saboor
7 Services 1 10 Fatima Aslam
8 Designing 2 20 Areeba Fayyaz
9 Quality Check 6,10 2 Ammar Abdul Saboor

1.8.3. Gantt Chart

1.9. Report Outline

This report consists of the following main points:
 Partnerships
 Establish a budget
 Planning and event timeline
 Promotion
 Capture the event with photos and video
 Essential to quality
 Process control

Chapter 2
Software Requirement Specifications

Chapter 2: Software Requirement Specifications
2.1. Introduction
An event planning organizational chart outlines the structure of roles within an event planning team or
company. It typically includes departments such as Event Management, Creative, Sales and Marketing,
Logistics, Finance, Client Relations, Technical Support, Vendor Management, Catering, Entertainment,
and Decoration. The hierarchy varies based on the organization's size and event complexity.
2.1.1. Purpose
An event management system provides campus event planners a flexible, fully integrated solution to
simplify the event management process and keep your customers, faculty and student happy, while
maintaining important reports and data for making real estate and future planning decisions.
2.1.2. Document Conventions

In this document we used Calibri(body) style with 12 fount size for paragraph and 14 for
heading text alignment justified and line spacing is 1.5 and we used different kinds of shapes
for diagrams.
2.1.3. Intended Audience and Reading Suggestions

This SRS is Intended for product developers and the university committee. The university
committee, representing the academic institution, will review the SRS to assess whether the
project meets educational goals, adheres to university guidelines, and evaluates potential
educational impact. They evaluate the scope, purpose, and specifications outlined in the SRS
to ensure that the project meets academic standards and aligns with the university's
mission.
2.1.4. Product Scope

The scope of the project encompasses the design, development, and implementation of a
fully functional E v e n t m a n a g e m e n t S y s t e m collection of Events.
2.2. Overall Description

2.2.1. Product Perspective
This product does not exist in the market and is a completely new concept. The only product

that seeks to educate on the peoples events management system.
2.2.2. Product Functions

Some of the functions that the project must provide are:
 The management system will provide good Services & entertainment.
 Save user time
 The event management system will provide various Services with various challenges.
2.2.3. User Classes and Characteristics
 Consultation with all parties directly involved in the program

 Calculating the time of each and every activity
 Ensuring that the program has time for “ceremonial” activities
 Opening and closing ceremonies
 Speeches The presentation of awards, entertainment

ULTIMATE PHASES TO CHECKLIST:
 Defining your events purpose and setting objectives.

 Securing event venue (for in-person events) or event virtual platform
 Choosing an ideal event date and time
 Create an event master plan
 Estimate an event budget
 Event branding
IMPORTANT PIECES OF INFORMATION:

 Size
 Capacity
 Location
 Lighting
 Price
PLAN FOR EVENT MANAGEMENT:

Maintaining through records will support you: plan and implement your event. Meet legal
requirements. Evaluate your event.
STRUCTURE IN EVENT MANAMEMENT SYSTEM:

The work involved in planning, organizing and conducting a major event can be sufficiently great to
require the recruitment of a large team of people.
EVENT PLANNING SHEET:

 Select the date
 Identify venue details
 Develop an event master plan
 Get cost estimates
 Create an event budget
 Recruit an event committee
 Brand your event

Chapter 3
Use Case Analysis

Chapter 3: System Analysis

3.1. Use Case Model

Chapter 4
System Design

Chapter 4: System Design

Use Case Diagram:
Create a Use Case Diagram to identify the various actors interacting with the system. Actors can
include Event Organizers, Clients, Attendees, and Suppliers.
Define use cases for different functionalities such as "Create Event," "Manage Guest List," "Book
Venue," "Manage Budget," and "Generate Event Report." Connect actors to relevant use
cases to show their interactions.
Class Diagram:
Develop a Class Diagram to represent the static structure of the system.

Identify key classes like "Event," "Client," "Venue," "Supplier," "Budget," and "Guest."
Define attributes and methods for each class. For example, the "Event" class may have attributes like
"EventName" and "EventDate" and methods like "calculateBudget" and
"generateEventReport."
Establish relationships between classes, such as associations, aggregations, or compositions, to show
how they are related.
Sequence Diagram:
Create Sequence Diagrams to illustrate the dynamic behavior of the system during specific scenarios.
For instance, create a sequence diagram for the "Booking Venue" use case to show the interactions
between actors and the system components (e.g., Client, Venue Manager, Booking System).
Use lifelines to represent objects and actors, and draw arrows to depict the flow of messages and
interactions between them.
Activity Diagram:
Develop Activity Diagrams to model the workflow or processes within the system.
For example, create an activity diagram for "Event Planning Process" to show steps like "Client
Requirements Gathering," "Budgeting," "Vendor Selection," and "Event Execution."
Use actions, decision nodes, and control flows to represent the flow of activities.
State Machine Diagram:
Use State Machine Diagrams to model the states and transitions of key objects or components.
For instance, represent the "Event" object's states such as "Planned," "In Progress," and
"Completed" and define transitions between them triggered by events like "Start Event" and
"End Event."
Component Diagram:
Create a Component Diagram to illustrate the system's architectural components and their
dependencies.
Identify components like "Event Management System," "Database," "Payment Gateway," and
"Reporting Module."
Show how these components interact and depend on each other.
Deployment Diagram:
Develop a Deployment Diagram to depict the physical deployment of the system's software
components onto hardware nodes.
Show nodes like "Web Server," "Database Server," and "Client Devices" and how components are
deployed on these nodes.
These UML diagrams can provide a comprehensive view of your Event Management System,
covering its structure, behavior, interactions, and deployment. Depending on the system's
complexity and your specific requirements, you can create additional diagrams or tailor these
diagrams to suit your modeling needs.

ERD
Entity: An entity represents a real-world object, concept, or thing in the system. In an ERD, entities are typically
represented by rectangles. Each entity corresponds to a table in a database.
Attribute: Attributes describe the properties or characteristics of an entity. They are depicted as ovals
connected to their respective entity with lines. Attributes correspond to columns in database tables.
Primary Key: The primary key uniquely identifies each record (row) within an entity. It is usually underlined in an
attribute or set of attributes within an entity.
Relationship: Relationships define how two or more entities are related or connected in the database.
Relationships are represented by lines connecting entities, with optional labels to indicate the nature of the
relationship.

One-to-One (1:1): A single record in one entity corresponds to a single record in another entity.
One-to-Many (1:N): A single record in one entity can relate to multiple records in another entity.
Many-to-One (N:1): Multiple records in one entity can relate to a single record in another entity.
Many-to-Many (N:N): Multiple records in one entity can relate to multiple records in another entity.
Cardinality: Cardinality represents the minimum and maximum number of instances of one entity that can be
associated with another entity in a specific relationship. Common notations include "1" for one, "0..1" for zero
or one, "0..N" for zero to many, and "1..N" for one to many.
Weak Entity: A weak entity is an entity that cannot be uniquely identified by its attributes alone and relies on a
related strong entity for identification. It is represented by a double rectangle.
Relationship Attribute: A relationship attribute is an attribute associated with a relationship, not an entity. It is
used when additional information needs to be stored about the relationship itself.
Inheritance/Generalization: In some ERDs, you may see a "Generalization" or "Inheritance" relationship

symbolized by a triangle pointing to the parent entity. This represents an inheritance hierarchy where child
entities inherit attributes and relationships from a parent entity.
Chapter 5
Implementation

Chapter 5: Implementation
FUNCTIONAL WEADING MEANAGMENT SYSTEM
Guest List Management: The system can help create and maintain a guest list, including RSVP tracking
and meal preferences.
Budget Tracking: It allows users to set and manage their wedding budget, track expenses, and generate
reports to ensure they stay within their budget.
Vendor Management: Users can search for and contact vendors such as venues, photographers, florists,
caterers, and DJs. The system may also help with vendor contracts and payments.
Task and Checklist Management: Users can create to-do lists and checklists for various wedding-
related tasks and set deadlines for completion.
Event Timeline: It can create a detailed timeline for the wedding day, including the schedule of events,
ceremony, reception, and other activities.

Seating Arrangement: Helps in planning the seating arrangements for guests at the reception.
Invitation and RSVP Management: Users can design and send digital invitations, track RSVPs, and
manage guest responses.
Gift Registry: Provides a platform for creating and managing a wedding gift registry.
RSVP Tracking: Allows for easy tracking of RSVPs and meal preferences.
Menu Planning: Helps in selecting and customizing the wedding menu, considering dietary restrictions and
preferences.
Decor and Theme Planning: Provides tools for selecting and organizing decorations and themes for the
wedding.
Weather Updates: Some systems may include weather forecasting to help plan for outdoor weddings.
Expense Reports: Generates reports to provide an overview of wedding expenses.
Communication Tools: Offers communication features like email or chat for interacting with vendors and
guests.
Data Security: Ensures the security and privacy of personal information and financial data.
Mobile Accessibility: Most systems are accessible via mobile apps for on-the-go planning and updates.
Collaboration: Allows for collaboration between the couple and their wedding planner or other family members
involved in the planning process.
Payment Processing: May include features for making and tracking payments to vendors.
Photo and Video Sharing: Offers a platform for sharing and collecting photos and videos from the wedding.
Post-Wedding Features: Some systems include features for sending thank-you notes and managing post-
wedding tasks.
Chapter 6
Testing and Evaluation

Chapter 6: Testing and Evaluation

NON FUNCTIONAL MANAGEMENT SYSTEM
Non-functional requirements (NFRs) in the context of a management system, whether it's a wedding
management system or any other type of system, refer to the qualities or attributes that describe how
the system should perform, rather than specific functionalities. Non-functional requirements focus on
aspects such as performance, security, usability, reliability, and scalability. Here are some non-
functional requirements that may apply to a management system:
Performance:
Response Time: The system should respond to user actions within a specified time frame.
Throughput: It should handle a certain number of simultaneous users or transactions per unit of time.

Scalability: The system should be able to scale up to accommodate increased load.

Authentication and Authorization: Implement user authentication and authorization mechanisms to
ensure data security.
Data Encryption: Sensitive data should be encrypted during transmission and storage.
Access Control: Specify who has access to different parts of the system and what actions they can
perform.
Audit Trails: Maintain logs of system activities for auditing and forensic purposes.
User Interface (UI): The user interface should be intuitive and user-friendly.
Accessibility: Ensure that the system is accessible to users with disabilities.
Internationalization and Localization: Support multiple languages and regions if required.
Reliability:
Availability: The system should be available for use as per defined service level agreements (SLAs).
Fault Tolerance: It should continue to operate even in the presence of hardware or software failures.
Backup and Recovery: Implement regular data backups and establish procedures for data recovery.
Scalability:
The system should be able to handle an increasing number of users, data, or transactions without a
significant drop in performance.
Maintainability:
The system should be easy to maintain and update.

Code Quality: Ensure that the codebase follows best practices and coding standards.
Compatibility:
Ensure compatibility with various browsers, devices, and operating systems.

Integration: The system should integrate seamlessly with other systems and services if needed.
Performance Testing and Tuning:
Conduct performance testing to ensure the system meets performance requirements.

Optimize system performance based on test results.
Data Management:
Data Integrity: Ensure the accuracy and consistency of data.

Data Privacy: Comply with data privacy regulations and protect sensitive user data.
Documentation:
Provide comprehensive documentation for system users, administrators, and developers.

Disaster Recovery:
Develop and maintain a disaster recovery plan to minimize downtime in the event of a catastrophic
failure.
Compliance:
Ensure compliance with relevant industry standards and regulations.
Chapter 7
Summary, Conclusion and Future
Enhancements

Chapter 7: Summary, Conclusion & Future

Enhancements
7.1. Project Summary
Conclusion: In conclusion, the Event Management System project has demonstrated the
importance of meticulous planning and technological solutions in enhancing the event management
process. By addressing the needs outlined in the planning task list and implementing a robust system
with comprehensive features, the project team has contributed to the efficiency and effectiveness of
event planning. Challenges were met with innovative solutions, and the successful completion of this
project signifies a milestone in the realm of event management technology.
7.2. Future Enhancements/Recommendations
The Event Management System fulfills the outlined requirements, several avenues for future
enhancements exist. These may include the integration of artificial intelligence for automated task
management, the incorporation of virtual reality for immersive event visualization, and enhanced data
analytics for more informed decision-making. Additionally, user feedback and evolving industry
standards will be valuable in guiding future updates to ensure the system remains cutting-edge and
adaptable to changing event management needs

Index

Index
Home Page: Welcome message Event highlights Quick links to popular events
About Us: Company history Mission and values Team members
Services: Event planning Venue selection Catering Entertainment Registration and ticketing
Events: Upcoming events Past events Event details and descriptions
Booking and Registration: Booking process Registration forms Ticketing information
Venue Management: Venue options Facilities and amenities Booking availability
Catering Services: Catering packages Menu options Dietary accommodations
Gallery: Photos from past events Videos
Testimonials: Client feedback and reviews
Blog/News: Updates on industry trends Tips for successful events
Contact Us: Contact information Inquiry form
FAQs: Frequently asked questions and answers

Fyp Areeba Fayyaz S22-045

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fyp Areeba Fayyaz S22-045

Uploaded by

Copyright:

Available Formats

THE SUPERIOR UNIVERSITY, LAHORE

ASSOCIATE DEGREE PROGRAMS

Final Year Project

Event Management System

Project ID: FYP-ADP-S22-045

Areeba Fayyaz 1.0 16/8/2023 Event Management

Sir Rauf 1.1 04/9/2023 Advised to create a

Fatima Aslam 1.2 07/10/2023 Advised to separate

Faculty of CS&IT, Superior University Lahore, Pakistan ii

HEAD OF THE DEPARTMENT

Faculty of CS&IT, Superior University Lahore, Pakistan iii

Faculty of CS&IT, Superior University Lahore, Pakistan iv

Faculty of CS&IT, Superior University Lahore, Pakistan v

Faculty of CS&IT, Superior University Lahore, Pakistan vi

Faculty of CS&IT, Superior University Lahore, Pakistan vii

2.4.2.1. Description and Priority..........................................................................................133

Faculty of CS&IT, Superior University Lahore, Pakistan viii

7.1. Project Summary............................................................................................................. 43

Faculty of CS&IT, Superior University Lahore, Pakistan ix

1.1 Gantt Chart 5

Faculty of CS&IT, Superior University Lahore, Pakistan x

1.1 Roles & Responsibility Matrix 3

Faculty of CS&IT, Superior University Lahore, Pakistan xi

1.3. Motivations and Challenges

1.4. Goals and Objectives

1.5. Literature Review/Existing Solutions

Faculty of CS&IT, Superior University Lahore, Pakistan 2

1.6. Proposed Solution

1.7. Gap Analysis

Faculty of CS&IT, Superior University Lahore, Pakistan 3

knowledge and practical applications. This difference is heightened by the lack of

1.8. Project Plan

Faculty of CS&IT, Superior University Lahore, Pakistan 4

1.8.2. Roles & Responsibility Matrix

2 Testing. 8 50 Areeba Fayyaz

3 Simulation. 9 21 Ammar Abdul Saboor

4 Asset Collection 3 5 Fatima Aslam

5 Sign Design 4 7 Areeba Fayyaz

6 home Design 5 21 Ammar Abdul Saboor

7 Services 1 10 Fatima Aslam

8 Designing 2 20 Areeba Fayyaz

9 Quality Check 6,10 2 Ammar Abdul Saboor

Faculty of CS&IT, Superior University Lahore, Pakistan 5

1.8.3. Gantt Chart

Faculty of CS&IT, Superior University Lahore, Pakistan 6

1.9. Report Outline

Faculty of CS&IT, Superior University Lahore, Pakistan 7

Faculty of CS&IT, Superior University Lahore, Pakistan 8

Chapter 2: Software Requirement Specifications

2.1.2. Document Conventions

2.1.3. Intended Audience and Reading Suggestions

2.1.4. Product Scope

2.2. Overall Description

Faculty of CS&IT, Superior University Lahore, Pakistan 9

that seeks to educate on the peoples events management system.

2.2.2. Product Functions

2.2.3. User Classes and Characteristics

 Consultation with all parties directly involved in the program

Faculty of CS&IT, Superior University Lahore, Pakistan 10

ULTIMATE PHASES TO CHECKLIST:

 Defining your events purpose and setting objectives.

IMPORTANT PIECES OF INFORMATION: