Green University of Bangladesh
Department of Computer Science and Engineering (CSE)
Faculty of Sciences and Engineering
Semester: (Fall Year:2024), B.Sc. in CSE (Day)
Assignment
Course Title: IDP-1
Course Code: CSE 324 Section:221 D2
Student Details
Name ID
1. Hasimunnahar Shanta 221002585
Submission Date : 15/10/2024
1
Use Case Diagram for library management system:
Explanation: The diagram is Use Case Diagram for a library system. It shows
how two main users Student and Librarian interact with the system to perform
different tasks.
Users:
1. Student: The student uses the library system to borrow books, return books,
pay fines and give feedback.
2.
3. Librarian: The librarian manages the system. They can add or delete student
records, manage book records, and update the database.
Use Cases (Tasks the users can do):
1. Registration:
○ Students must register in the library system before using it.
○ Once registered, they receive a Library Card.So I included library card
for every use case purpose of authentication.
2
2. Receive Library Card:
○ After registering, the student gets a library card, which allows them to
borrow books.
3. Request Book:
○ If the student wants a book, they can request it through the system.
4. Reserve Book:
○ If the book is not available, the student can reserve it for future use.
5. Renew Book:
○ If a student needs more time with a borrowed book, they can renew it
to extend the borrowing period.
○ There is an invalid renew option if the system doesn’t allow them to
renew example someone else reserved the book.
6. Return Book:
○ When the student finishes using the book, they return it to the library.
○ There is an invalid return option if the return doesn’t go through
properly if the book is damaged.
7. Pay Fine:
○ If a student returns a book late, they need to pay a fine.
8. Feedback:
○ Students can give feedback about their library experience.
Tasks for the Librarian:
1. Add User Record:
○ The librarian adds new students to the system, giving them access to
library services.
2. Delete User Record:
○ The librarian can remove a student from the system such as after
graduation.
3. Delete Book Record:
○ The librarian can remove books from the system that are no longer
available.
4. Update Database:
○ The librarian updates the system’s database with any changes to
student or book records.
Relationships:
● <<include>>: Some actions depend on others. For example:
○ To Request a Book, the student needs a library card.
3
○ For every use cases, library card is must for security purposes for both
students and librarians. So , I included library card for every users
interactions
○ To Return a Book, the student might need to pay a fine first if the
book is overdue.
● <<exclude>>: Some actions have conditions where they might not be
allowed, such as invalid renewals or returns. It can be invalid or not .
