Seat No: 18-9603

Name of Student: Abhishek S. Beloshe

Seat no: 18-9603
Topic Name: Library Management System
Class: S.Y. Bsc CS
Year: 2018-19

1|Page
Seat No: 18-9603

INDEX

Sr. No. Diagrams Pg no.

1. Use case diagram 3

2. Class diagram 4

3. Sequence diagram 5

4. StateChart diagram 6

5. Activity diagram 7

6. Event Table 8

7. Context Level DFD 9

2|Page
Seat No: 18-9603

1. Use case diagram:

With a UML use case diagram, you can create a broad, high-level view of the relationship
between use cases, actors involved, and systems being performed. As you can see from the
examples below, use cases are represented by oval shapes, and the lines then show at which point
an actor participates and interacts with their corresponding use case. You can see where each
actor is involved within the entire process (and where they're excluded). For instance, the
following is a use case diagram for library management system:

3|Page
Seat No: 18-9603

2. Class diagram:
The class diagram is one of the most commonly used diagrams in UML. Software engineers
and business professionals often choose class diagrams to map the structure of particular systems
because they clearly display the various classes, attributes, operations, and relationships between
objects. In our example below, each class shape is labeled with its name in the first row, the
second row displays each attribute of the class on a separate line, and the third row displays each
operation on a separate line. From there, additional UML symbols are used to model the various
interactions and objects involved within the process.

4|Page
Seat No: 18-9603

3. Sequence diagram:

Sequence diagrams are a popular dynamic modeling solution in UML because they
specifically focus on lifelines, or the processes and objects that live simultaneously, and the
messages exchanged between them to perform a function before the lifeline ends. Here,
Librarian Issues a book to member: whenever a member asks for a book, the librarian checks the
availability of book, if the book is available then the rack number of that book will be returned to
librarian. librarian then checks the validity of member by verifying the library card if member is
valid then the number of books issued to him is less then maximum allowed ,books issued to him
and transaction is created, librarian then update the number of books issued to member and status
of book.

5|Page
Seat No: 18-9603

4. State chart diagram:

State chart diagram are used to help the developers better understand any complex
functionalities or business flow of specialized area of system. It depict the dynamic behavior of
the entire system. A state chart diagram shows a state machine. state chart diagram can be used
to graphically represent finite state machine.

State chart diagram contain following states.

1) student / faculty login
2) search book
3 )request book
4) receive book
5) calculating fine
6) profile update

6|Page
Seat No: 18-9603

5. Activity diagram:
Activity diagram is one of the important uml diagram which describes the flow of activity in a
system. Activity diagram is basically a flowchart which shows connection between one activity
of system to another activity. Activity diagram of library management system may defer
according to users such as administrator, customer etc.
Activity of Issuing books to member: The librarian checks the availability of book. If the
book is not available, then an error message will be displayed else the check the rack no were the
book is placed will be displayed. The member is validated. depending upon the type of member
if more books can be issued to member, the transaction will be created and issue details are
added to the transaction. The book and member details are updated accordingly.

7|Page
Seat No: 18-9603

6. Event Table:

Event analysis works especially well for specifying real-time control systems. To identify
events, consider all the states associated with the object you are analyzing, and identify any
events that might transition the object into those states. Review for any external entities that
might initiate an action (trigger an event) or require an automatic response (need a temporal
event triggered).
An event-response table that defines every possible combination of event, state, and response,
including exception conditions, can serve as part of the functional requirements for that portion
of the system. Depending on how far down you detail the event descriptions and their
corresponding responses, you can employ event-response analysis as a system scoping tool, as a
way to understand user requirements. The following is a Event Table for Library Management
System.

Event Trigger Source Activity Response Destination

Librarian Request Librarian Validate Confirmation Librarian
login Username & Username saved
Password &
Password
Create Enter user User Librarian Account Librarian
account details verify User created
User Login Request User Validate Confirmation User
Username & Username saved
Password &
Password
Add Books Book details Librarian / Add book Information Librarian/
and Add to User to saved User
inventory inventory
Update Update Librarian / Update Information Librarian/
inventory Book User book in saved User
inventory
Generate User User Confirm Book issued User
book issue request
request
Save Save details Librarian / Save Details saved Librarian /
Details User details User
Logout Librarian / Librarian / Logout Logged out Librarian /
User User User

8|Page
Seat No: 18-9603

7. Context Level DFD:

A context diagram gives an overview and it is the highest level in a data flow diagram,
containing only one process representing the entire system. It should be split into major
processes which give greater detail and each major process may further split to give more detail.
DFD Level 0 is also called a Context Diagram. It’s a basic overview of the whole system or
process being analyzed or modeled. It’s designed to be an at-a-glance view, showing the system
as a single high-level process, with its relationship to external entities. The following is a
Context Level for Library Management System.

9|Page