Scribd
Upload
11 views3 pages

Assessment Project

Uploaded by

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

Assessment Project

Uploaded by

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

Task: Event Management System

An event management system is to be developed, enabling the management of events,


participants, and venues. The requirements are as follows:

1. Database:

o A MySQL/MariaDB database is provided and will be made available


separately.

o The MyISAM storage engine should be used, with UTF8MB4 as the


character encoding.

o The table structure must include at least: events, locations, participants,


and event_participants.

2. API Development:

o A RESTful API for CRUD operations (Create, Read, Update, Delete) on


events, locations, and participants is required.

o The API should process JSON data.

o Filtering and search functions must be integrated, e.g., displaying events by


date or listing participants.

o The venue capacity must be respected.

3. Dynamic Service:

o A blacklist should be integrated to protect the API from unauthorized or


abusive access.

o A whitelist logic is also required.

4. Frontend:

o A simple HTML frontend should display:

1. The number of registered participants per event.

2. A warning when a venue reaches 80% of its capacity.

3. The status of the blacklist, including the ability to unblock IPs.

o No libraries or frameworks should be used (only HTML, CSS, JavaScript, and


PHP).

o Venue capacity usage should be graphically represented, clearly showing


when a warning appears and when capacity is fully reached.

o The frontend should feature an appealing design.


5. Additional Requirements:

o External libraries or frameworks are not allowed.

o Clean documentation and a well-structured codebase are expected.

o UTF8MB4 support must be consistent throughout the application.

o Abuse protection of the API through blacklist and other methods is


mandatory.

Evaluation Criteria:

• Compliance with the Requirements: Use of the provided database and UTF8MB4
support.

• Code Quality and Documentation: Structure, readability, and comments.

• Error Handling and Security: Handling of invalid inputs.

• Frontend Functionality: Display of participant numbers and blacklist status.


Figure 1 Wireframe: View

You might also like