Scribd
Upload
5K views4 pages

DFD For Library Management System: Data Flow Digram

The document describes a data flow diagram (DFD) and entity relationship (ER) diagram for a library management system. The DFD shows the flow of book requests, library cards, books being output, and book information being displayed. It also describes three levels of the DFD that provide more processing details. The ER diagram models the relationships between entities like staff, readers, books, publishers and attributes. It tracks things like book catalog information, reader registration details, and book reservations/returns.

Uploaded by

Ayush
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
5K views4 pages

DFD For Library Management System: Data Flow Digram

The document describes a data flow diagram (DFD) and entity relationship (ER) diagram for a library management system. The DFD shows the flow of book requests, library cards, books being output, and book information being displayed. It also describes three levels of the DFD that provide more processing details. The ER diagram models the relationships between entities like staff, readers, books, publishers and attributes. It tracks things like book catalog information, reader registration details, and book reservations/returns.

Uploaded by

Ayush
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
You are on page 1/ 4

DFD for Library Management System

Data Flow Digram - Depicts the flow of information and the transformation applied when a data moves in and out
from a system. The overall system is represented and described using input, processing and output in the DFD. The inputs can
be:

Book request -when a student requests for a book.

Library card - when the student has to show or submit his/her identity as a proof.

The overall processing unit will contain the following output that a system will produce or generate:

1) Book will be the output as the book demanded by the student will be given to them.

2) Information of demanded book should be displayed by the library information system that can be used by the student while
selecting the book which makes it easier for the student.

1) Level 0 DFD –

2) Level 1 DFD – At this level, the system has to show or exposed with more details of processing.
The processes that are important to be carried out are:

 Book delivery
 Search by topic

List of authors, List of Titles, List of Topics, the bookshelves from which books can be located are some information that is
required for these processes. Data store is used to represent this type of information .
3) Level 2 DFD –
ER diagram of Library Management System
ER Digram is known as Entity-Relationship Diagram, it is used to analyze to the structure of the Database. It shows
relationships between entities and their attributes. An ER Model provides a means of communication.

The Library Management System database keeps track of readers with the following considerations –

•The system keeps track of the staff with a single point authentication system comprising login Id and password.

•Staff maintains the book catalog with its ISBN, Book title, price(in INR), category(novel, general, story), edition,
author Number and details.

•A publisher has publisher Id, Year when the book was published, and name of the book.

•Readers are registered with their user_id, email, name (first name, last name), Phone no (multiple entries allowed),
communication address. The staff keeps track of readers.

•Readers can return/reserve books that stamps with issue date and return date. If not returned within the prescribed
time period, it may have a due date too.

•Staff also generate reports that has readers id, registration no of report, book no and return/issue information.
This Library ER diagram illustrates key information about the Library, including entities such as staff, readers, books,
publishers, reports, and authentication system. It allows for understanding the relationships between entities.

 Entities and their Attributes – It has authno,, title, edition, category, price. ISBN is the Primary Key for
Book Entity .
 Reader Entity - It has UserId, Email, address, phone no, name. Name is composite attribute of firstname
and lastname. Phone no is multi valued attribute. UserId is the Primary Key for Readers entity.
 Publisher Entity : It has PublisherId, Year of publication, name. PublisherID is the Primary Key.
 Authentication System Entity : It has LoginId and password with LoginID as Primary Key.
 Reports Entity : It has UserId, Reg_no, Book_no, Issue/Return date. Reg_no is the Primary Key of reports
entity.
 Staff Entity : It has name and staff_id with staff_id as Primary Key.
 Reserve/Return Relationship Set : It has three attributes: Reserve date, Due date, Return date.

You might also like