Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 1

Library Manager

You have been asked to create the UML models of a new application for a public library.

The library lends books and DVDs for its members. The books have a title, an author and an ISBN
number, while the DVDs also have a title and a director. A unique barcode identifies both items, and
they store their statuses too (i.e., borrowed, available).

When a member requests to lend an item, the system checks the item's status (i.e., it is available)
and whether the member has one or more expired loans. If the item is available and the member has
no expired loan, the system creates a new loan. The system registers for each new loan the date
when the item got borrowed (the current date) and the expected return date of the item, which is
two weeks from the borrowed date.

When a member brings back an item that was borrowed, the system checks whether the loan has
overdue (the current date is later than the expected return date). If so, the system creates a payment
request. Then in all cases, the system closes the loan.

The application should be able to:

- Manage users - add, remove and list active members.


- Manage books - add, remove, list, search books.
- Manage DVDs - add, remove, list, search DVDs.
- Manage Loans – create a new loan, close loan, list loans for a member, generate a payment
request

Tasks:

1. Create a UML Use-Case Diagram that depicts the application.


2. Create a UML Class Diagram about all the classes. Many of them are marked with bold
letters, but there can be more. The diagram should contain all the necessary classes and all of
their attributes and methods.
3. Create a UML Sequence Diagram that depicts the creation of a new loan.

You might also like