Draw the LMS STATE DIAGRAM *not the code* for the following class diagram, where an object can change its state depending on certain events and guard conditions.

Thx

Cl After determining the actors, the second step in use case analysis is to determine the tasks that each actor will need to do with the system. Each task is called a use case because it represents one particular way the system will be used. In other words, only those use cases are listed that actors will need to do when they are using the system to solve the customer's problem. Borrower: - JSearch for items by title. - ... by author. - ... by subject. - JPlace a book on hold if it is on loan to somebody else. - JCheck the borrower's personal information and list of books currently borrowed. Checkout Clerk: - J All the Borrower use cases, plus - JCheck out an item for a borrower. - JCheck in an item that has been returned. - JRenew an item. - I Record that a fine has been paid. - JAdd a new borrower. - J Update a borrower's personal information (address, telephone number etc.). Librarian: - JAll of the Borrower and Checkout Clerk use cases, plus - J Add a new item to the collection. - I Delete an item from the collection. - J Change the information the system has recorded about an item