$*$Create an Analysis class diagram based on the list of Canidate classes below, use the UML modeling techniques and heuristics.

$*$One big hint: You have to utilize the Specification Class heuristic. You need a Title class and an Audiobook class. You need it for the normalization of the information $($third normal form$).$ You will also need these two classes because Requests are linked to Titles while Reservations are linked to Audiobooks.

$*$Remember that both requests and reservations are three way relationships $($among Users, Audiobooks or Titles, and Kiosks$).$

$\backslash$table$[[$Candidate Class,$],[$Customer$,\backslash$table$[[$Account Class that stores customer details, including account ID$,$ name,$],[$current account status etc. Customer Class is needed because the$],[$audiobooks are reserved and borrowed by the customer.$]]],[\backslash$table$[[$Library$],[$Employee$]],\backslash$table$[[$Account Class that stores library employee details, including account ID$,],[$name etc. Library Employee is tasked with adding and removing$],[$audiobooks$.]]],[\backslash$table$[[$System$],[$Administrator$]],\backslash$table$[[$Account Class that stores system administrator details, including account$],[$ID$,$ name etc. A class for System Administrator is necessary, as it is$],[$responsible for adding audiobook titles and removing copies that are$],[$stolen or missing from the system.$]]],[$Report$,\backslash$table$[[$Class that stores report details, including report ID$,$ title, creator, kiosk ID$,],[$timestamp etc. Report Class is critical in this case, as it plays a key role in$],[$rebalancing books across all the kiosks.$]]],[$Kiosk$,\backslash$table$[[$Class that stores kiosk details, including its kiosk ID$,$ kiosk location, and$],[$associated audiobook data $($e$.$g$.,$ name, status, count, book location$).$ Kiosk$],[$Class showcases what audiobooks are available.$]]],[$Audiobook title,$\backslash$table$[[$Class that holds the title of an audiobook. This Audiobook title Class is what$],[$System Administrator will be adding and removing from the system.$]]],[$Audiobook$,\backslash$table$[[$Class that stores all the specifics around an audiobook, including its ID$,],[$title$,$ location, book status etc. This Audiobook class is what the Customer$],[$and Library Employee will borrow and manage, respectively.$]]],[$Reservation$,\backslash$table$[[$Class that holds reservation details, including reservation ID$,$ creator$],[$account ID$,$ creation time, status, associated loan ID etc. The Reservation$],[$Class is what the Customer set up$,$ prior to borrow books.$]]],[$Request$,\backslash$table$[[$Class that stores all request details, including request ID$,$ creator account$],[$ID$,$ creation time, status etc. The Request Class is necessary because the$],[$Customer needs to place a request, when the book of interest is not$],[$available$.]]],[$Loan$,\backslash$table$[[$Class that stores loan details, including loan ID$,$ creator account ID$,],[$creation time, due date, # of days overdue, status etc. The Loan Class$],[$tracks the status of the books borrowed by Customer.$]]]]$