A Library Management System made using the concepts of Object Oriented Analysis and Design. Minimal Code is written in the GUI and the entities are decoupled as well. The interface is console based. This project was designed during the course "4136 Application Development using Java" with Munshid V
The actors include the following:
- Librarian
- Checkout Clerk
- Borrower
- Administrator
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.
- ❏ Search for items by title.
- ❏ ... by author.
- ❏ ... by subject.
- ❏ Place a book on hold if it is on loan to somebody else.
- ❏ Check the borrower’s personal information and list of books currently borrowed.
- ❏ All the Borrower use cases, plus
- ❏ Check out an item for a borrower.
- ❏ Check in an item that has been returned.
- ❏ Renew an item.
- ❏ Record that a fine has been paid.
- ❏ Add a new borrower.
- ❏ Update a borrower’s personal information (address, telephone number etc.).
- ❏ All of the Borrower and Checkout Clerk use cases, plus
- ❏ Add a new item to the collection.
- ❏ Delete an item from the collection.
- ❏ Change the information the system has recorded about an item.
- ❏ Add Clerk.
- ❏ Add Librarian.
- ❏ View Issued Books History.
- ❏ View All Books in Library.