The “Update Book Status”, on the other hand, is only done when needed. The processes with “include” are included in validating and recording book information. This use case diagram presents the included processes for book information management. Library Management System Use Case Diagram Book Information Management Use Caseīook information management includes the sub-use cases that are part of completing the task. This use case is focused on “Managing Users’ Information.” In the diagram, the use case is shown as a step that must come before user information management can be done. The label “include” implies that the use cases are required to complete the task, while “extend” declares otherwise. Include and extend are indications used to describe the following library system use case diagrams. These use cases will be discussed in the following diagrams.įor example: draw use case diagram for library management system Library Management System General Use Case Include and Extend in Use Case Diagram This diagram is made up of the system’s main use cases and primary users. General Use Case Diagram for Library Management The library management has different processes and they were discussed here one by one. This simple use case diagram for library management system section clarifies the use case diagrams shown. Library Management System Use Case Diagram with Explanation This is done when there’s a serious scenario or problem. School Admin: He/she can access all of the library’s information.They will also have access to the system. Book Borrowers: Book borrowers were not just the students but also the professors or instructors.School Librarian: The school librarians will be the ones to use the system most of the time.It works best with other UML diagrams, including activity, class, sequence, deployment, and component diagrams.

Furthermore, the diagram serves as a system analysis that can identify, clarify, and organize the project’s needs.

Use case diagram for online bookstore