
π Student Projects (College Reports) Β· Use Case
Who uses a college library system and what each of them can do: members, the librarian and the system administrator.
Drawing diagramβ¦
Use case diagram for a library management system: a member can search the catalogue, reserve a book, borrow and return books and pay fines; the librarian can add and update books, issue and return books, manage members and see overdue reports; the admin manages librarian accounts and settings. Paying a fine extends returning a book; issuing a book includes checking member eligibility.
flowchart LR
member(["π€ Member"])
librarian(["π§βπΌ Librarian"])
admin(["π‘οΈ Administrator"])
subgraph SYS ["π Library Management System"]
UC1(["Search catalogue"])
UC2(["Reserve book"])
UC3(["Borrow book"])
UC4(["Return book"])
UC5(["Pay fine"])
UC6(["Add or update books"])
UC7(["Issue book"])
UC8(["Check member eligibility"])
UC9(["Manage members"])
UC10(["View overdue report"])
UC11(["Manage librarian accounts"])
end
member --> UC1
member --> UC2
member --> UC3
member --> UC4
librarian --> UC6
librarian --> UC7
librarian --> UC9
librarian --> UC10
admin --> UC11
UC7 -.->|"includes"| UC8
UC5 -.->|"extends"| UC4The database of a library system: books and their copies, authors, members, loans, reservations and fines, with keys and cardinality.
How data moves through a library system: members and the librarian, the main processes, and the data stores they read and write.
The main classes of a library system with attributes, methods and UML relationships.
The steps when a member borrows a book: checks, loan record and the copy status update.
What students, examiners and the administrator do in an online examination system.
Database design for online exams: courses, exams, questions and options, attempts, answers and results.