EVENT MANAGEMENT SYSTEM

SOFTWARE ENGINEERING

SUBMITTED BY:
 LARAIB HAMID 22011598-112
 IZMA SHOAIB 22011598-115
 SAMAVIA TANVEER 22011598-131
 RAMEEN FATIMA 22011598-149
DOCUMENT

Contents
1 INTRODUCTION: ............................................................................................................................. 2
1.1 EXISTING SYSTEMS: .............................................................................................................. 2
2 SYSTEM MODULES:........................................................................................................................ 3
2.1 STAKEHOLDERS AND ACTORS: .......................................................................................... 3
2.2 ROLES AND RESPONSIBILITIES ......................................................................................... 3
3 REQUIREMENT ENGINEERING: ................................................................................................. 4
3.1 Questionnaire/ Elicitation Technique ........................................................................................ 4
3.2 FUNCTIONAL REQUIREMENTS AND NON-FUNCTIONAL REQUIREMENTS: ........ 5
3.3 USE CASE DIAGRAM: ............................................................................................................. 7
3.4 USE CASE DESCRIPTION: ..................................................................................................... 8
4 DOMAIN DIAGRAM: ..................................................................................................................... 13
5 CLASS DIAGRAM: ......................................................................................................................... 14
6 SEQUENCE DIAGRAM: ................................................................................................................ 15
7 RESEARCH TRENDS IN SOFTWARE ENGINEERING: ......................................................... 19
8 IMPROVING QUALITY: ................................................................................................................ 21
9 VISUAL REPRESENTATION: ....................................................................................................... 23

1
DOCUMENT

EVENT MANAGEMENT SYSTEM

1 INTRODUCTION:

a) What is an event management system?

Event management system software is primarily business software, it consists of several
interconnected modules that together fulfill the functional requirements. The process of
organizing, administering, and carrying out an event is automated. Its streamers the event
preparation process.

b) Who will use the event management system?

The event management system provides a user-friendly interface that allows users to carry
out tasks. The system is specifically designed for the admin.
Admin: Admin refers to a user role with privileged access and is in charge of managing
and supervising various components of the system.

c) What are the problems addressed by the event management system?

Data Disorganization: EMS frequently handles a lot of physical documentation, like
registration forms that result in disarray, which makes it challenging to track down and
retrieve information when required. This system organizes the data orderly.
Time-consuming Procedures: Managing many duties manually, such as registration,
needs a lot of time and effort.
Data security risks: Compared to secure digital systems, physical documents, and
spreadsheets are more vulnerable to theft, damage, and illegal access.
Manual Booking Issue: Manual processes are time-consuming in traditional booking
techniques that involve phone calls, actual tickets, and paperwork. This system streamlines
these procedures and accelerates their speed and effectiveness.

1.1 EXISTING SYSTEMS:

Before the planned system was implemented, the current event management system
covered the current strategy. The outdated systems were ineffective due to manual booking
issues, accessibility issues, and data security issues. The suggested online solution
transforms events by streamlining easy registration and event management. It improves
user experience with an intuitive interface, eliminates paperwork, saves time, and makes
accessing event information simpler.

2
DOCUMENT

2 SYSTEM MODULES:

a) REGISTRATION MODULE:
The registration form contains the following functions;
 Login
 Logout
b) VENUE MANAGEMENT MODULE:
Venue management includes the following functions;
 View venue
 Add venue
 Update venue
 Delete venue

c) FOOD MANAGEMENT MODULE:

It includes the following functionalities:
 View food
 Add food
 Update food
 Delete food

d) EQUIPMENT MODULE:
It includes the following functionalities;
 View equipment
 Add equipment
 Update equipment
 Delete equipment
2.1 STAKEHOLDERS AND ACTORS:

In an event management system, stakeholders and actors are;

 Admin: A person who is responsible for managing the whole system.

2.2 ROLES AND RESPONSIBILITIES

a) USER ROLE
ADMIN: The admin is the person who will have checks and balances on the whole system.

b) USER RESPONSIBILITY

3
DOCUMENT

ADMIN

 REGISTRATION: Admin will have access to the whole registration module which
includes the log-in and log-out functions.
 VIEW FUNCTION: The admin will have access to view functions so that he can view all
the data that is entered in that module.
 FOOD MANAGEMENT: The admin will have access to all the functions of this module.
 VENUE MANAGEMENT: The admin will have access to all the functions of this
module.
 EQUIPMENT MANAGEMENT: The admin will have access to all the functions of this
module.

3 REQUIREMENT ENGINEERING:

3.1 Questionnaire/ Elicitation Technique

OPEN-ENDED QUESTIONS
 What are the primary objectives of the registration module?
 How would you describe the ideal user experience during the registration process?
 How would you define the user experience for adding and updating events?
 Are there any specific requirements that should be considered during the registration process?
 Can you provide any examples of additional options that the user may want to select during adding
process?
CLOSE-ENDED QUESTIONS
 Should the system validate the entered username for registration?
 Is this service available 24/7?
 Will users have the ability to update their event?
 Is the registration process easy to use?
 Is user registration required for adding or updating events?
 Are there any restrictions on the number of events a user can add?
 Can users update or cancel their events?

4
DOCUMENT

3.2 FUNCTIONAL REQUIREMENTS AND NON-FUNCTIONAL

REQUIREMENTS:

FUNCTIONAL REQUIREMENTS:
Functional requirements describe the specific features and functionalities of the system.
REGISTRATION MODULE:
1. The admin shall log in to the system by providing a username and password.
2. The system shall store the registered user's information securely.
3. The system shall enforce secure authentication practices, such as password hashing.
4. The system shall provide a log-out function that allows users to securely and effectively end their
session, to make sure that no unauthorized access or activity can occur.
VENUE MANAGEMENT MODULE:
1. The system shall allow the admin to enter the venue.
2. The system shall allow the admin to update the venue.
3. The system shall allow the admin to view the venue.
4. The system shall allow the admin to delete the venue.
FOOD MANAGEMENT MODULE:
1. The system shall allow the admin to enter the food.
2. The system shall allow the admin to update the food.
3. The system shall allow the admin to view the food.
4. The system shall allow the admin to delete the food.
EQUIPMENT MANAGEMENT MODULE:
1. The system shall allow the admin to enter the equipment.
2. The system shall allow the admin to update the equipment.
3. The system shall allow the admin to view the equipment.
4. The system shall allow the admin to delete the equipment.

NON-FUNCTIONAL REQUIREMENTS:
Non-functional requirements describe the overall quality attributes and constraints of the system. They
focus on areas such as performance, security, reliability, and usability.
PERFORMANCE:
1. The system shall respond to user actions within 2 seconds, providing a smooth and responsive user
experience.
2. The system shall support a minimum of 50 concurrent users without significant performance
degradation.
SECURITY:
1. The system shall store user passwords securely using industry-standard encryption algorithms.

5
DOCUMENT

2. The system shall protect sensitive user data, such as personal information using encryption during
transmission and storage
RELIABILITY:
1. The system shall maintain a minimum uptime of 99.9% to ensure its availability for users.
2. The system shall implement regular data backups to prevent data loss in case of system failures.
USABILITY:
1. The system shall provide a user-friendly interface with intuitive navigation and clear instructions

6
DOCUMENT

3.3 USE CASE DIAGRAM:

REGISTRATION

LOGIN LOGOUT

MANAGE
VENUE

ADD
DELETE

UPDATE
VIEW

MANAGE FOOD

ADD
ADMIN DELETE DATA-
BASE
VIEW
UPDATE

MANAGE
EQUIPMENT

ADD DELETE

UPDATE VIEW

7
DOCUMENT

3.4 USE CASE DESCRIPTION:

( 01 )

UC ID: 01 DEVELOPER: XYZ

UC NAME: REGISTRATION DATE: 21-07-2023

ACTOR: ADMIN

PRE-CONDITIONS:

The admin must have correct username and password to get logged in to the system.

MAIN SCENARIO:

ACTOR’S ACTION SYSTEM RESPONSE

The admin enters the correct username and The dashboard will get opened where bu ons
password then presses the OK or log-in for different modules are placed.
bu on.

POST CONDITIONS:

The admin will be prompted or the admin will have an op on to log out of the system

8
DOCUMENT

( 02 )

UC ID: 02 DEVELOPER: XYZ

UC NAME: ADD VENUE DATE:21-07-2023

ACTOR: ADMIN

PRE-CONDITIONS:

The actor must be registered to perform this func on.

MAIN SCENARIO:

ACTOR’S ACTION SYSTEM RESPONSE

1.The actor will select the Add Venue bu on

1. The Add Venue page will get opened.
2. The actor will now enter the desired
2. The venue will be added.
venue.
3. The price of the venue will be added.
3. The actor will enter the price of the venue.
4. Then all the details will get entered and
4. The actor will click the OK bu on.
actor can go back from Back bu on.

POST CONDITIONS:

The actor moves to the next func on.

9
DOCUMENT

( 03 )

UC ID: 03 DEVELOPER: XYZ

UC NAME: UPDATE VENUE DATE: 21-07-2023

ACTOR: ADMIN

PRE-CONDITIONS:

The actor must be registered and should have entered the venue to perform this func on.

MAIN SCENARIO:

ACTOR’S ACTION SYSTEM RESPONSE

1. The actor will select the update venue
bu on
2. The actor will now enter the string of the
desired venue to be updated.
3. The actor will now enter the venue name
and price.
4. The actor will click the OK bu on.
1. The update venue page will get opened.
2. That string in the database will get selected
to be uploaded.
3. The previous data will be replaced.
4. Then all the changes will be done and the
actor can go back from the Back bu on.

POST CONDITIONS:

The actor moves to the next func on

10
DOCUMENT

( 04 )

UC ID: 04 DEVELOPER: XYZ

UC NAME: DELETE VENUE DATE: 21-07-2023

ACTOR: ADMIN

PRE-CONDITIONS:

The actor must be registered and should have added a venue to perform this func on.

MAIN SCENARIO:

ACTOR’S ACTION SYSTEM RESPONSE

1. The actor will first enter the string of the 1. The string will be entered into the system.
venue which is to be deleted.
2. The desired venue will be deleted from the
2. The actor will now click on the Delete
system.
Venue bu on to delete the desired venue.

POST CONDITIONS:

The actor moves to the next func on.

11
DOCUMENT

( 05 )

UC ID: 05 DEVELOPER: XYZ

UC NAME: VIEW VENUE DATE: 21-07-2023

ACTOR: ADMIN

PRE-CONDITIONS:

The actor must have log-in access to the system to view all the venues that are added.

MAIN SCENARIO:

ACTOR’S ACTION SYSTEM RESPONSE

1. The actor will select the view venue 1. The view venue page will get opened.
bu on.
2. A er viewing the actor can go back by
2. The actor can see the list of all the venues clicking on the BACK bu on
that are added.

POST CONDITIONS:

The actor can move to the func on he wants to work on or can log-out of the system by clicking log-out bu on

12
DOCUMENT

4 DOMAIN DIAGRAM:

ADMIN

Username

Password

MANAGE FOOD MANAGE VENUE MANAGE EQUIPMENT

Name Id Name
Number of items Name Number of items
Cost Loca on Cost

Cost

13
DOCUMENT

5 CLASS DIAGRAM:

ADMIN

Username

Password

Log-in ()

Log-out ()

Add event ()

Update event ()

View event ()

Delete event ()

MANAGE FOOD MANAGE VENUE MANAGE EQUIPMENT

Name Id Name
Number of items Name Number of items
Cost Loca on Cost
Add food () Cost Add equipment ()
Update food () Add venue () Update equipment ()
View food () Update venue () View equipment ()
Delete food () View venue () Delete equipment ()
Delete venue ()

14
DOCUMENT

6 SEQUENCE DIAGRAM:

: ADMIN : REGISTRATION : DATABASE

User select login requests for login sent

The registration page shows request for approval

user enters a username and password request to store in the database

and selects login

show the message “successfully login” request approved

selects “ok”

15
DOCUMENT

: ADMIN : MANAGE FOOD : DATABASE

Selects add venue requests to display add venue page

Venue page shows request for approval
Enter venue name and cost and select request to store in database
Add
Show message “ add successfully” request approved
Select update venue request to display page
Page shown request approval
Enter string to update venue name request to store in database
,cost then select update
Message displayed request approved
Selects view venue request to display venue
Venue page shown request approval
Select delete venue request to delete venue
Venue deleted successfully request approved

16
DOCUMENT

: ADMIN : MANAGE : DATABASE

FOOD

Selects add food requests to display add food page

page shown request approval
Enter food name and cost and select request to store in database
Add
Show message “ add successfully” request approved
Select update food button request to display page
Page shown request approval
Enter string to update food name request to store in database
quantity and cost then select update
Message displayed request approved
Selects view food button request to display food
Food page shown request approved
Select delete food request to delete food
food deleted successfully request approved

17
DOCUMENT

: ADMIN : DATABASE
: EQUIPMENT
MANAGMENT

Selects add equipment requests to display add equipment

page shown request approved
Enter equipment name and cost and request to store in database
Select Add
Show message “ add successfully” request approved
Select update equipment request to display page
Page shown request approval
Enter equipment to update name request to store in database
Quantity and cost then select update
Message displayed request approved
Selects view equipment request to display equipment
page shown request approval
Select delete equipment request to delete equipment
equipment deleted successfully request approved

18
DOCUMENT

7 RESEARCH TRENDS IN SOFTWARE ENGINEERING:

1. SOFTWARE ENGINEERING AND EDUCATION:

 Education may be performed through a variety of means, such as dialogues, lectures,
information dissemination through social networking, and so on.
 Mobile learning is a type of presenting learning approach.
 Pair programming practice has a considerable influence on students' efficiency and
satisfaction.
 T-Test is utilized in the research to accept or reject various elements used to evaluate
the generated application.
 When compared to traditional instructional strategies, using mobile gaming
applications as an educational strategy has a greater influence on student
performance.
 A web portal that provides adequate testing tools is employed (WTLAP).

2. SOFTWARE ENGINEERING AND MACHINE LEARNING:

 Creating modules that assist developers in identifying defective modules or classes
early in the development life cycle.
 It is done in order to increase the quality.
 Support vector machine (SVM) integration with genetic algorithm (GA) and particle
swarm method for software failure prediction.
 The model is further tested utilizing ensemble approaches such as boosting, bagging,
and decorating, as well as Naive Bayes, Bayes Net, J48, Decision Table, and Random
Tree learner classifiers.
 System for triaging bugs that are automated.
 Machine learning hybrid approach.

3. TECHNIQUES AND SOFTWARE TESTING:

 Important tasks for detecting and correcting problems.
 To detect flaws before they are discovered by customers.
 Using K-means clustering methods to save costs.
 The Information Retrieval (IR) approach was used to reduce the number of test cases.
 Software metrics for selecting test cases.
 A comprehensive examination of the literature to classify the present testing
procedures.
 To categorize test suite reduction strategies in order to offer software testers a
guideline for selecting the most relevant techniques.

19
DOCUMENT

4. ALGORITHMS FOR SOFTWARE ENGINEERING AND DEEP LEARNING:

 Deep learning for learning from multi-layer neural networks
 Deep learning methods include Convolutional Neural Networks (CNNs) and
Multilayer Perceptrons (MLPs), which are utilized in domains such as speech
recognition, computer vision, and natural language processing.
 The fault detection rate is measured.
 Dataset gathered from 15 participants.

5. BIG DATA ANALYTICS AND DATA SCIENCE:

 Big Data is a technology for data storage, processing, and analysis. Large corporations
worry about big data.
 Hadoop is a piece of software that can sort massive amounts of data.
 The use of big data improves agility.
 Private and public networks are used in cloud computing and data analytics.
 OWASP, which aims to cover the majority of known security threats.
 To eliminate dangers.

6. STUDIES ON OPEN SOURCE SYSTEMS (OSS):

 Open-source software is free software or source code that may be used and modified.
 They are created in order to enhance and test the systems.
 It is inexpensive and occasionally free.
 Software maintenance operations may cost 60-77% of the total cost of developing a
software system.
 Mutation testing coverage, code coverage, and test suite LOC are all measured to
evaluate the relationship between code coverage, fault detection, and test suite size.
 Several software versions are used to assess the link between LOC, nesting levels, and
cyclomatic complexity indicators.

7. DESIGN AND MODELLING:

 A class diagram combines the presentation of the component, and it demands
considerably more time and emphasis to build.
 The technique based on meta-models, test models, and structured models is being used as
a backbone in software design to minimize the number of test cases in the regression
testing process for generating system models.
 To map the structural modifications in autonomic software, a model-driven method was
utilized, and a metamodel and a workflow were developed to assist the approach.
 A prototype of a reductive shift to an autonomic, service-oriented healthcare application
was also created.
 The system is made up of heat sensors that detect the presence of humans as well as DC
LED lamps.

20
DOCUMENT

 Traceability of design and code.

8 IMPROVING QUALITY:
Improving software quality is an important part of software development since it leads
to greater performance, fewer defects, and increased customer happiness. Here are a few pointers
to help you improve the quality of your software:
1) Define specific requirements: Before beginning development, ensure that you have a
thorough knowledge of the project requirements. In order to minimize misunderstandings
and misinterpretations, include stakeholders, collect feedback, and develop extensive
documentation.
2) Adopt a strong development process: Use a well-known software development
approach such as Agile, Scrum, or Kanban. These approaches encourage cooperation,
ongoing feedback, and iterative development, which can aid in the detection of flaws and
the delivery of a higher-quality product.
3) Conduct extensive testing: Implement a stringent testing procedure that includes unit
testing, integration testing, system testing, and user acceptability testing. Automated
testing frameworks are very handy for running tests on a regular basis and detecting
regressions.
4) Encourage your development team to do frequent code reviews. Peer reviews can help
team members detect errors, enhance code readability, enforce coding standards, and
exchange information.
5) Adopt version control tools such as Git to track changes in the software. Version control
helps developers to successfully communicate, roll back changes as needed, and maintain
a stable codebase.
6) Set security as a top priority: Implement security practices throughout the development
process. Identify possible flaws and implement security best practices such input
validation, authentication, and encryption.
7) Performance optimization is identifying and addressing bottlenecks in software in order
to increase its performance. Profiling tools may be used to discover resource-intensive
portions of code and optimize them accordingly.
8) Documentation: Keep thorough and up-to-date program documentation. Not just code
comments, but also user manuals, API documentation, and architectural overviews are
included.
9) User input and usability testing: Seek feedback from end users actively, and undertake
usability testing to understand their pain areas and preferences. Utilize this data to
enhance the customer experience and overall product quality.
10) Tracking and resolving bugs: Set up a sophisticated bug-tracking system to keep track
of reported issues and their status. Prioritize and address problems as soon as possible to
provide a stable and dependable software product.
11) Continuous integration and deployment: Use continuous integration and continuous
deployment (CI/CD) pipelines to automate the build, testing, and deployment processes.

21
DOCUMENT

This method ensures that updates are properly tested and delivered on a regular basis,
lowering the likelihood of mistakes.
12) Training and professional development: Invest in your development team's training and
continual learning. Keeping up with the newest technologies and best practices
guarantees that your team can effectively produce high-quality software.

22
DOCUMENT

9 VISUAL REPRESENTATION:

23
DOCUMENT

24
DOCUMENT

25
DOCUMENT

26
DOCUMENT

27