Library Management System - Usecase Diagram: Actors:-Member, Librarian
Library Management System - Usecase Diagram: Actors:-Member, Librarian
UML Use Case diagram for Library Management System is shown below. The various
participants of the same are detailed below:-
Actors:- Member, Librarian
The corresponding use cases for these actors are:-
Member: Inquiry For Membership, Search Book, Book Issue, Book Return, Pay Fine
Librarian: Search Book, Issue Membership Card, Cancel Membership, Issue Book,
Return Book, Charge Fine In Case of Late Return, Maintain the Book Records, Add Books,
Remove Books, Add Members, Remove Members, Update Member Details
Here we have some dependencies also like Request For Book Return <<extends>>Pay
Fine. Also Maintain Book Records <<includes>> Add Book, Remove Book and Update Book.
Again Return Book <<extends>> Charge Fine in case of late return.
The Use Case UML diagram for Library Management System is shown below:-
Library Management System - Class Diagram
UML Class diagram for Library Management System is shown below. The various Classes
involved in the system are:
Class: Books, Librarian, User, Publisher, Reference Book, General Book, Book Bank,
Student, Faculty.
Here, in this system there could be two types of users: Student and Faculty. Both use to
share many of the properties and methods. So, we defined a new class that is user and from
it both student and faculty class inherits properties and methods. Hence, User is basically an
abstract class whose object directly can't be created.
Similarly, Reference Book, General Book and Book Bank all three classes share many of its
attributes so, we generalized all the three classes with super class Books and from it all the
other three classes inherits methods and properties. Unlike User class, Books class is not an
abstract class. We can create as well as instantiate its objects directly.
The Class diagram for Library Management System is shown below:-