Scribd
Upload
7K views

Doctor Appointment System Data Flow PDF

The document provides an overview of data flow diagrams (DFDs) for a doctor appointment system at three levels - Level 0, Level 1, and Level 2. Level 0 shows the system interacting with users and data at a high level. Level 1 expands on this with more detail on four processes: customer information management, appointment records management, appointment status monitoring, and transactions management. Level 2 further breaks down the sub-processes and data flows in more detail, but this level is optional if the previous diagrams are clear.

Uploaded by

46-Numaan Nawaaz
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
7K views

Doctor Appointment System Data Flow PDF

The document provides an overview of data flow diagrams (DFDs) for a doctor appointment system at three levels - Level 0, Level 1, and Level 2. Level 0 shows the system interacting with users and data at a high level. Level 1 expands on this with more detail on four processes: customer information management, appointment records management, appointment status monitoring, and transactions management. Level 2 further breaks down the sub-processes and data flows in more detail, but this level is optional if the previous diagrams are clear.

Uploaded by

46-Numaan Nawaaz
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Doctor Appointment System Data

Flow Diagram (DFD)


A thorough explanation is provided for the example data flow diagram for doctor
appointment system. This example emphasizes the three DFD levels (DFD Levels 0, 1, and 2).

0 Level DFD for Doctor Appointment System


The context diagram is an alternative name for the Level 0 DFD Diagram for Doctor
Appointment System. Users, the main process, and data flow make up its parts. Also, the project
concept is demonstrated using the single process visualization.

DFD Level 0 shows the entities that interact with a system and defines the border between
the system and its environment. This diagram also depicts the doctor appointment system at a high
level.

The illustration presents the main process in a single node to introduce the project context.
This context explains how the project works in just one look. The user feeds data into the system
and then receives the output from it.

In addition to this, you will perceive through the diagram that there is already the presence
of data flow. Though the process is very general, the flow of data is clear. Nevertheless, just modify
this diagram to meet the other requirements and include other matters regarding doctor
appointment management.
Level 1 DFD for Doctor Appointment System
The "detonated view" of the context diagram is Doctor Appointment System DFD Level
1. Its function is to deepen the concept derive from the context diagram.

Specifically, level 1 shows the broader details of Doctor Appointment System DFD Level
0. This is to clarify the paths (flow) of data and its transformation from input to output.

The designed diagram portrays four different scenarios: customer information


management, appointment records management, appointment status monitoring, and transactions
management.

Firstly, the flow of data starts from the hospital admin, doctors, and patients. Then the
system caters to the transaction. This idea was based on appointment scheduling processes or
transactions.
You can also see the data store used or the database. The database is also used in storing
users' data inputs. Then it serves as the source of outputs.

DFD Level 2 for Doctor Appointment System


Level 2 DFD for Doctor Appointment System is also the highest abstraction of the data
flow diagram. This level also broadens the idea from the DFD level 1. It includes the sub-processes
from level 1 as well as the data that flows.

However, not all of the processes in the project must have sub-processes. Only provide this
diagram if needed. As long as your previous diagrams were clear and precise, this level is not
required.

You can add more to this and it is up to you how will you create your data flow diagram.
Also, consider the data flow included and be precise with your information.

You might also like