DFD (Data Flow Diagram) :

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.

Level 0 DFD :
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.
Level 1 DFD :

As described previously, context diagrams (level 0 DFDs) are diagrams

where the whole system is represented as a single process. A level 1 DFD notates
each of the main sub-processes that together form the complete system. We can
think of a level 1 DFD as an “exploded view” of the context diagram.

DFD Level 1 provides a more detailed breakout of pieces of the Context

Level Diagram. You will highlight the main functions carried out by the system,
as you break down the high-level process of the Context Diagram into its
subprocesses.
Level 2 Diagram :
2-level DFD goes one step deeper into parts of 1-level DFD. It can be used
to plan or record the specific/necessary detail about the system’s functioning.

This level two data flow diagram (DFD) template can map out information
flow, visualize an entire system, and be shared with your stakeholders.
Use Case Diagram :
A use case diagram is a graphical depiction of a user's possible interactions
with a system. A use case diagram shows various use cases and different types of
users the system has and will often be accompanied by other types of diagrams as
well. The use cases are represented by either circles or ellipses. The actors are
often shown as stick figures.

The purpose of use case diagram is to capture the dynamic aspect of a system.
However, this definition is too generic to describe the purpose, as other four
diagrams (activity, sequence, collaboration, and Statechart) also have the same
purpose. We will look into some specific purpose, which will distinguish it from
other four diagrams.

Use case diagrams are used to gather the requirements of a system including
internal and external influences. These requirements are mostly design
requirements. Hence, when a system is analyzed to gather its functionalities, use
cases are prepared and actors are identified.

When the initial task is complete, use case diagrams are modelled to present the
outside view.

In brief, the purposes of use case diagrams can be said to be as follows −

Used to gather the requirements of a system.

Used to get an outside view of a system.

Identify the external and internal factors influencing the system.

Show the interaction among the requirements are actors.

Use Case Diagram for Hungrezy :

Registration

Login

Navigate Menu

Select Items

Add Items to Cart

Remove Item from

Cart
CUSTOMER

Table Booking RESTAURANT

Pay for order

Receive for order

Update Cart

Receive Confirmation
Check-out