Scribd
Upload
9K views7 pages

Library Management System: A. Use Case Diagram

The document describes a library management system that aims to simplify the process of renting books. It involves applicants logging into the system and submitting details that are stored in a database. An administrator then verifies the details and allows the applicant to rent books. UML diagrams including use case, activity, sequence, collaboration, class, component, and deployment diagrams are used to describe the system's processes. The system is intended to improve efficiency by streamlining administrative tasks like book searches, check-ins/outs, and calculating due dates.

Uploaded by

Nirvana Maharjan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Topics covered

  • Software Architecture,
  • Troubleshooting,
  • Design Relationships,
  • UML Diagrams,
  • Database Management,
  • Book Rental Process,
  • Communication Diagram,
  • System Architecture,
  • Book Management,
  • Forward Engineering
9K views7 pages

Library Management System: A. Use Case Diagram

The document describes a library management system that aims to simplify the process of renting books. It involves applicants logging into the system and submitting details that are stored in a database. An administrator then verifies the details and allows the applicant to rent books. UML diagrams including use case, activity, sequence, collaboration, class, component, and deployment diagrams are used to describe the system's processes. The system is intended to improve efficiency by streamlining administrative tasks like book searches, check-ins/outs, and calculating due dates.

Uploaded by

Nirvana Maharjan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Topics covered

  • Software Architecture,
  • Troubleshooting,
  • Design Relationships,
  • UML Diagrams,
  • Database Management,
  • Book Rental Process,
  • Communication Diagram,
  • System Architecture,
  • Book Management,
  • Forward Engineering

Library Management System

AIM:
To draw the diagrams (use case, activity, sequence, collaboration , class ,components,
deployment, state chart) for the Library Management System.

PROJECT DESCRIPTION:
To simplify the process of renting books, software has been created by designing through
visual paradigm too. Initially the applicant login the library management system and submits
the details. These details are stored in the database and verification process done by
administrator and then allows to rent a book.
PURPOSE:
The Library Management System improves efficiency by filling in the gaps in a library’s struggles.
The LMS can cut down time spent on administrative tasks, such as searching for books, checking in
or checking out books, and handling books as well as calculating the time.

PROBLEM STATEMENT:
Library Management System used for effective searching and easy access to renting books to the
applicants. This system adopts a comprehensive approach to minimize the time for task and checking
books.

UML DIAGRAMS
The following UML diagrams describe the process involved in the Library Management system.

A. USE CASE DIAGRAM:


This diagram will contain the actors, use cases which are given below
Actors: Librarian, Member.
Use case: Register Member, Enquiry, verify member, issue book, Check availability of the book,
Return book, Calculate time, Maintaining book.
Figure: Use Case Diagram
B. ACTIVITY DIAGRAM:
The activity diagram denotes the structural flow of the activities in the form of the flow chart
with decision boxes enhanced and hence is also used for troubleshooting like raising
exceptions when a particular action is done and the alternative to be done when smoothing
abnormal is done. This diagram will have the activities as Start point, End point, Decision
boxes as given below
C. SEQUENCE DIAGRAM:
This diagram consists of the objects, messages and return messages.
Object: Members, Librarian, Librarian DB, Operation

Figure: Sequence Diagram


D. CLASS DIAGRAM:

Class diagram shows the classes in a system, attributes and operations of each class and the
relationship between each class. It visualizes, specifies and helps in documenting the models
through backward and forward engineering.

E. COLLABORATION DIAGRAM:
This diagram contains the objects and actors. A collaboration diagram is similar to sequence
diagram but the message in number format. In a collaboration diagram sequence diagram is indicated
by the numbering the message. A collaboration diagram, also called a communication diagram or
interaction diagram, A sophisticated modelling tool can easily convert a collaboration diagram into a
sequence diagram and the vice versa.
Figure: Collaboration Diagram

F. COMPONENT DIAGRAM:
The component diagram is represented by figure dependency and it is a graph of design of
figure dependency. The component diagram's main purpose is to show the structural relationships
between the components of a systems. It is represented by boxed figure. Dependencies are represented
by communication association.
Figure: Component Diagram

G. DEPLOYMENT DIAGRAM:

You might also like