What is DFD(Data Flow Diagram)?

Last Updated: 26-05-2020

DFD is the abbreviation for Data Flow Diagram. The flow of data of a system or a
process is represented by DFD. It also gives insight into the inputs and outputs of each
entity and the process itself. DFD does not have control flow and no loops or decision rules
are present. Specific operations depending on the type of data can be explained by a
flowchart. Data Flow Diagram can be represented in several ways. The DFD belongs to
structured-analysis modeling tools. Data Flow diagrams are very popular because they help
us to visualize the major steps and data involved in software-system processes.

Components of DFD

The Data Flow Diagram has 4 components:

 Process
Input to output transformation in a system takes place because of process function.
The symbols of a process are rectangular with rounded corners, oval, rectangle or a
circle. The process is named a short sentence, in one word or a phrase to express its
essence
 Data Flow
Data flow describes the information transferring between different parts of the
systems. The arrow symbol is the symbol of data flow. A relatable name should be
given to the flow to determine the information which is being moved. Data flow
also represents material along with information that is being moved. Material shifts
are modeled in systems that are not merely informative. A given flow should only
transfer a single type of information. The direction of flow is represented by the
arrow which can also be bi-directional.
 Warehouse
The data is stored in the warehouse for later use. Two horizontal lines represent the
symbol of the store. The warehouse is simply not restricted to being a data file
rather it can be anything like a folder with documents, an optical disc, a filing
cabinet. The data warehouse can be viewed independent of its implementation.
When the data flow from the warehouse it is considered as data reading and when
data flows to the warehouse it is called data entry or data updation.
 Terminator
The Terminator is an external entity that stands outside of the system and
communicates with the system. It can be, for example, organizations like banks,
groups of people like customers or different departments of the same organization,
which is not a part of the model system and is an external entity. Modeled systems
also communicate with terminator.
Rules for creating DFD

 The name of the entity should be easy and understandable without any extra
assistance(like comments).
 The processes should be numbered or put in ordered list to be referred easily.
 The DFD should maintain consistency across all the DFD levels.
 A single DFD can have maximum processes upto 9 and minimum 3 processes.

Levels of DFD

DFD uses hierarchy to maintain transparency thus multilevel DFD’s can be created. Levels
of DFD are as follows:
DFD uses hierarchy to maintain transparency thus multilevel DFD’s can be created. Levels
of DFD are as follows:
 0-level DFD
 1-level DFD:
 2-level DFD:

Advantages of DFD

 It helps us to understand the functioning and the limits of a system.

 It is a graphical representation which is very easy to understand as it helps
visualize contents.
 Data Flow Diagram represent detailed and well explained diagram of system
components.
 It is used as the part of system documentation file.
 Data Flow Diagrams can be understood by both technical or nontechnical person
because they are very easy to understand.
Disadvantages of DFD


At times DFD can confuse the programmers regarding the system.
 Data Flow Diagram takes long time to be generated, and many times due to this
reasons analysts are denied permission to work on it.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory
concepts for SDE interviews with the CS Theory Course at a student-friendly price and
become industry ready.

DFD for Library Management System

Last Updated: 12-06-2020
Data Flow Diagram (DFD) 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:
 Book will be the output as the book demanded by the student will be given to
them. 
 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.


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.
Out of scope: 
Other activities like purchasing of new books, replacement of old books or charging a fine
are not considered in the above system.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory
concepts for SDE interviews with the CS Theory Course at a student-friendly price and
become industry ready.
Use Case Diagram for Library Management
System
Last Updated: 16-06-2020
Use case diagrams referred as a Behavior model or diagram. It simply describes and
displays the relation or interaction between the users or customers and providers of
application service or the system. It describes different actions that a system performs in
collaboration to achieve something with one or more users of the system. Use case diagram
is used a lot nowadays to manage the system.
Here, we will understand the designing use case diagram for the library management
system. Some scenarios of the system are as follows :
1. User who registers himself as a new user initially is regarded as staff or student
for the library system.
 For the user to get registered as a new user, registration forms are
available that is needed to be fulfilled by the user.
 After registration, a library card is issued to the user by the librarian. On
the library card, an ID is assigned to cardholder or user.
2. After getting the library card, a new book is requested by the user as per there
requirement. 
3. After, requesting, the desired book or the requested book is reserved by the user
that means no other user can request for that book. 
4. Now, the user can renew a book that means the user can get a new due date for
the desired book if the user has renewed them. 
5. If the user somehow forgets to return the book before the due date, then the user
pays fine. Or if the user forgets to renew the book till the due date, then the book
will be overdue and the user pays fine. 
6. User can fill the feedback form available if they want to. 
 7. Librarian has a key role in this system. Librarian adds the records in the library
database about each student or user every time issuing the book or returning the
book, or paying fine.
8. Librarian also deletes the record of a particular student if the student leaves the
college or passed out from the college. If the book no longer exists in the library,
then the record of the particular book is also deleted. 
9. Updating database is the important role of Librarian. 
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory
concepts for SDE interviews with the CS Theory Course at a student-friendly price and
become industry ready.
Recommended Posts:

Class Diagram for Library Management System

Last Updated: 08-07-2020
In Object-Oriented modeling, the main building block generally represents different objects
in a system, their attributes, their different functions, and relationships among objects.
These building blocks are known as Class Diagram. 
Class diagrams are generally used for conceptual modeling of static view of a software
application, and for modeling translating models into programming code in a detailed
manner. At time of developing or construction software systems, a class diagram is widely
used. They are also used for data modeling. It is used to show classes, relationships among
them, interface, association, etc. Class in a class diagram simply is a blueprint of an object.
It simply describes and explains different type of objects in system, and different types of
relationships that exist between them.
Class Diagram for Library Management System :
Aggregation and Multiplicity are two important points that need to take into consideration
while designing a Class Diagram. Let us understand in detail.
1. Aggregation –
Aggregation simply shows a relationship where one thing can exist independently
of other thing. It means to create or compose different abstractions together in
defining a class. Aggregation is represented as a part of relationship in class
diagram. In diagram given below, we can see that aggregation is represented by an
edge with a diamond end pointing towards superclass. The 

1 The “Library Management System” is superclass that

consists of various classes. These classes are User,
Book, and Librarian as shown in diagram. Further, for
“Account” class, “User” is a superclass. All of these,
share a relationship and these relationships are known
as aggregate relationships.
2 Ad
3

4
5 #1 Flowchart
Software
6 Easy to use. Collaborative. Hundreds of templates. No download needed. Free

7-day trial. LucidchartSign Up

7 Multiplicity –
8 Multiplicity means that number of elements of a class is
associated with another class. These relations can be
one-to-one, many-to-many, and many-to-one or one-to-
many. For denoting one element we use 1, for zero
 elements we use 0, and for many elements we use *.
We can see in diagram; many users are associated
with many books denoted by * and this represents a
many-to-many type of relationship. One user has only
one account that is denoted by 1 and this represents a
one-to-one type of relationship. Many books are
associated with one librarian and this represents many-
to-one or one-to-many type of relationship. All these
relationships are shown in diagram.
Class Diagram for Library Management System simply
describes structure of Library Management System class,
attributes, methods or operations, relationship among
objects.
Classes of Library Management System :
• Library Management System class –
• It manages all operations of Library Management System.
It is central part of organization for which software is
being designed.
• User Class –
• It manages all operations of user.
• Librarian Class – It manages all operations of Librarian.
• Book Class –
• It manages all operations of books. It is basic building block
of system.
• Account Class –
• It manages all operations of account.
• Library database Class –
• It manages all operations of library database.
• Staff Class –
• It manages all operations of staff.
• Student Class –
• It manages all operations of student.
Attributes of Library Management System :
• Library Management System Attributes –
• UserType, Username, Password
• User Attributes –
• Name, Id
• Librarian Attributes –
• Name, Id, Password, SearchString
• Book Attributes –
• Title, Author, ISBN, Publication
• Account Attributes –
• no_borrowed_books, no_reserved_books,
no_returned_books, no_lost_books fine_amount
• Library database Attributes –
• List_of_books
• Staff Class Attributes –
• Dept
• Student Class Attributes –
• Class
Methods of Library Management System :
• Library Management System Methods –
• Login(), Register(), Logout()
• User Methods –
• Verify(), CheckAccount(), get_book_info()
• Librarian Methods –
• Verify_librarian(), Search()
• Book Methods –
• Show_duedt(), Reservation_status(), Feedback(),
Book_request(), Renew_info()
• Account Methods –
• Calculate_fine()
• Library database Methods –
• Add(), Delete(), Update(), Display(), Search()
Class Diagram of Library Management System :
Attention reader! Don’t stop learning now. Get hold of all the
important CS Theory concepts for SDE interviews with the
CS Theory Course at a student-friendly price and become
industry ready.
Recommended Posts:
• Use Case Diagram for Library Management System
• DFD for Library Management System
• Use Case Diagram for Bank ATM System
• State Transition Diagram for an ATM System
• Difference between Project Management and Operation
Management
• Difference between General Management and Project
Management
• Difference between Project Management and Construction
Management
• Difference between Project Management Software and
Product Management Software
• Difference between Project Management and Program
Management
• Difference between Project Management and Portfolio
Management
• Difference between Program Management and Portfolio
Management
• Difference between Logistic Management and Operation
Management
• Difference between Logistic Management and Inventory
Management
• Difference between Logistic Management and Material
Management
• Difference between Project Management and Service
Management
• Difference between Project Management and Warehouse
Management
• Difference between Project Management and Distribution
Management
• Difference between Project Management and Transport
Management
• Difference between Project Management and Material
Management
• Difference between Logistic Management and Transport
Management
madhurihammad
Check out this Author's contributed articles.