Web app development is complex. In fact, it involves so many different tasks that it is highly unlikely that a single person can carry out each of them on a professional level. Ordinarily, a web development project is made up of a team of specialists who are experts in their own field. So$,$ is this unit attempting to achieve the impossible? No$.$ Whilst it is inevitable that you will not gain the skills to develop a professional application by yourself, you will learn enough to understand each of the key areas involved and be able to produce a small prototype application. This understanding across all the relevant areas will be extremely useful to you, especially if working in a multidisciplinary team in the industry.

In this assignment, you will design an Event Management System as a web application. The genre of events is your own choice $($e$.$g$.$ Seminar, Music, Business, etc.$)$ and you will scope the design for your application. So$,$ be creative.

What is an Event Management System? It is an application that will allow users to post events of a given type, book tickets for events, comment on those events $$ take a look at EventbriteLinks to an external site. for example $($however$,$ we recommend that your design has a single focus$/$genre$).$

In this individual assignment, you will:

Describe the type of event management application you want to design and develop $($e$.$g$.$ event management web application for seminars, food festivals, or music events etc.$)$

Design the details of your web application $($user stories, conceptual model, data model, web$-$page wireframes$).$

NB: Generative AI tools are not allowed in this assessment task.

The Event Management web application must support a specific list of requirements so please keep these in mind when you come up with your design.

Project Requirements

User registration

The site has one type of user. This user can see all events, comment on all events, but only edit$/$update their own events.

A name, email address, password and mobile phone number should be obtained when registering with the system.

Creating an event

A logged in user can create an event. Since your web application is specific to an event type, the user should provide relevant information when creating an event. For example, for a music event web app, the user might be asked to provide an artist$/$s name$/$s$,$ location or venue, date and time in addition to a description, image, number of tickets available etc.

An event can have one of the following status: Open, Inactive $($event date in the past$),$ Sold Out, or Cancelled.

The creator of an event $($and only the creator$)$ should be able to update the details of the event. For example, if something about an event changes, the event creator should be able to change the description, image, start time or date, venue etc or cancel an event entirely. No user should be able to change the event's status however $($the controller$/$application should do this$).$

Viewing events

Anybody can view all events $($e$.$g$.,$ site visitors who are not logged in$).$

The events can be different categories $($e$.$g$.,$ Jazz, Country, Classical etc for a music event management app$).$ A user should be able to view all upcoming open events belonging to a category.

Any user should be able to select an event and view the details of it$.$

Buy a ticket for an event, post or read comments

A user can view the details of the event and book tickets for the event. To buy tickets, the user should be logged in$.$ The user should provide the number of tickets to be booked. An order is generated by the application and an order confirmation is shown to the user for reference.

If the user buys tickets equal to the tickets available, the event will be labeled as $$Sold Out$.$

If the user enters a number of tickets that exceeds the tickets available, the application should inform the user that the order cannot be placed.

A user can post a comment on the event if they are logged in$.$ The user$$s name, the comment and the posted date of the comment can be seen by all users.

Anybody can view the comments posted by other users on the event.

Unit Learning Outcomes assessed:

ULO #$1$: Analyse client requirements and design a web application in preparation for the software development process

ULO #$2$: Apply existing frameworks to implement model, view, and controller aspects of web applications

ULO #$4$: Evaluate the use of web applications in relation to different computer systems $($hardware$,$ software, and networks$)$