The kiosk ticket system is designed to allow users to purchase tickets from a self$-$service kiosk for events such as workshops, concerts, movies, public transportation, etc. The system should handle ticket selection, payment processing, and ticket printing.

Question $1.[20$ points$]$

Draw a UML use case diagram by identifying actors with associated functionalities. Select a use case and write a description for it$.$

$-$ Guidelines:

$-$ Identify all relevant actors, with at least three different types of actors.

$-$ Define the primary functionalities for each actor, with at least three different functionalities for each actor.

$-$ Write a use case description for one use case, including the use case ID$,$ name, actors, description, trigger, preconditions, postconditions, normal flow, alternative flows, exceptions, assumptions, and any notes and issues.

Question $2.[20$ points$]$

Draw a UML class diagram for the kiosk ticket system, identifying attributes and operations. Association links with multiplicities between classes need to be identified.

$-$ Guidelines:

$-$ Define the main classes involved.

$-$ Identify key attributes and operations for each class.

$-$ Show association links with appropriate multiplicities between classes.