Actor: A10-Administrator

This is the basic concrete direct and primary actor representing the user of the library management subsystem.

The A10-Administrator actor represents the librarian which interacts with the book, loan and user management subsystems.

Author: Rossi Nicola

Use-Case UC10-ManageBooks

This use case describe the abstract process of using the management subsystem for books.

<<Book>>

Depends on the concrete use-case

Depends on the concrete use-case

A10-Administrator

1. The administrator provide data to the CLI specifying the operation
2. The CLI performs the operation
3. Data is being returned to the administrator

Rossi Nicola

Use-Case UC20-FindBooks

This use case describe the concrete process of using the management subsystem for books to actually look for books according to the specified input data.

<<Book>>

No preconditions required to execute the process

No side effects so no postconditions either: no state is being altered being a read-only process

A10-Administrator

1. The administrator provide data to the CLI specifying the filter and the information to look for the book
2. The CLI performs a fetch in the database to obtain books matching the given filter.
3. A possibly empty list of books is being returned.

Rossi Nicola

Use-Case UC30-AddBooks

This use case describe the concrete process of adding a book to the system.

<<Book>>

No preconditions required

A new book is being persisted

A10-Administrator

1. The administrator provide data to the CLI specifying the book data to be added
2. The CLI performs the operation, persisting the book(E1)
3. Data of the book added is being returned.

E1 - The book is already present with the same address (Cutter Number) in the database. The operation cannot continue and system will prompt for new data.

Rossi Nicola

Use-Case UC40-RemoveBook

This use case describe the concrete process of removing a book from database

<<Book>>

The book being deleted must exist

The book is being removed

A10-Administrator

1. The administrator provide data to the CLI specifying address of the book to delete
2. The CLI performs the operation of deleting the book from database (E1)
3. Data of the book deleted is being returned.

E1 - If the book doesn't exist, the CLI will complain and ask again for information, outputting the input data provided

Rossi Nicola

Use-Case UC50-UpdateBooks

This use case describe the concrete process of updating the data of an already existing book

<<Book>>

The book must exist

Data associated with the book is being modified

A10-Administrator

1. The administrator provide data to the CLI specifying the id of the book and then the changes to make
2. The CLI performs the operation of update(E1)
3. Data of the book is being returned to the administrator

E1 - If the book doesn't exist or the address has been changed and it is not unique, the CLI will complain asking for new data

Rossi Nicola