DRAW THE DOMAIN CLASS MODEL ON VISUAL PARADIGMS AND UPLOAD THAT I JUST NEED THE MODEL PLEASE SHOW THE RELATIONSHIPS FOR EXAMPLE

$1$

$-$

$0$

$1$

$-$

$1$

$$AND SO ON AND PLEASE EXPLAIN IT

Assignment Description

In this assignment, you will analyze the following scenario and create four UML diagrams: a Use Case Diagram, Domain Model, Activity Diagram, and System Sequence Diagram. These diagrams will help visualize the system

$$

s functionality, structure, and interactions.

Scenario: Online Movie Ticket Booking System

The Online Movie Ticket Booking System allows users to browse available movies, select showtimes, choose seats, make payments, and manage their bookings. The system also provides administrators with functionality to manage movies and showtimes.

Functional Requirements:

$1$

$.$

$$User Registration and Login:

o Users must be able to register for an account by providing personal details such as name, email, and phone number.

o Users can log in to the system using their credentials

$($

email and password

$)$

$.$

$2$

$.$

$$Browse Movies:

o Users should be able to view a list of available movies, which includes information such as title, genre, duration, and rating.

o Movies can be filtered based on criteria such as genre, language, or cinema location.

$3$

$.$

$$Select Movie and Showtime:

o Once a user selects a movie, they can choose from available showtimes and cinemas.

o Showtimes for each cinema should be displayed based on the selected date.

$4$

$.$

$$Seat Selection:

o After selecting a showtime, users should be able to view a seat map of the cinema and select available seats.

o Users can select one or multiple seats depending on the availability.

o The system should mark seats as available, reserved, or booked.

$5$

$.$

$$Make Payment:

o Once the seats are selected, the user is directed to the payment page.

o Users can choose from multiple payment options, including credit

$/$

debit card, PayPal, or a wallet system

$($

if implemented

$)$

$.$

o The system must validate the payment and either confirm the booking or notify the user of a failure.

$6$

$.$

$$Booking Confirmation:

o After a successful payment, users receive a booking confirmation that includes the movie details, showtime, cinema location, seat numbers, and a QR code or reference number for ticket collection.

o The system should send a confirmation email to the user with the booking details.

$7$

$.$

$$View and Manage Bookings:

o Users should be able to view their past and upcoming bookings under their profile.

o For upcoming bookings, users should have the option to cancel their booking. Cancellations are allowed up to a specified time before the showtime

$($

e

$.$

g

$.$

$,$

$2$

$$hours before the show

$)$

$.$

$8$

$.$

$$Cancel Booking:

o Users can cancel their booking, and the system will release the reserved seats and initiate a refund process based on the system's refund policy.

o A confirmation of the cancellation will be sent to the user via email.

$9$

$.$

$$Administrator Features:

o Manage Movies: Administrators should be able to add, edit, and remove movie details such as title, description, genre, and duration.

o Manage Showtimes: Administrators can add, update, and delete showtimes for each movie in specific cinemas.

o View Reports: Administrators can view booking reports, including total sales, movie popularity, and user activity.

Non

$-$

Functional Requirements:

$$

$$Usability: The system should have an intuitive interface that provides easy navigation for both users and administrators.

$$

$$Performance: The system should be capable of handling multiple users accessing the site simultaneously, especially during peak times

$($

e

$.$

g

$.$

$,$

$$popular movie releases

$)$

$.$

$$

$$Security: The system must ensure secure handling of user information, particularly payment details. Sensitive data must be encrypted, and user authentication should follow best practices.

$$

$$Availability: The system should be available

$2$

$4$

$/$

$7$

$,$

$$with minimal downtime for maintenance.

$$

$$Scalability: The system should be able to scale with the number of users and bookings during high

$-$

demand periods.

Create a Domain Model showing key classes and their relationships.