UNIVERSIDAD DE MANILA

COLLEGE OF ENGINEERING AND TECHNOLOGY

ITE222 - SYSTEMS ANALYSIS AND DESIGN

ACITIVITY #2

TOOLS OF A SYSTEMS ANALYST – DATA FLOW DIAGRAM

Belmonte, Wilfred

Crisostomo, Maria Erlyn

Estrada, Kian Lance

Gamit, Cris Lorenz

Inosanto, Jiamae

Luciñada, Angelic Heri

Padilla, Mark Andrew

Valenzuela, Kobe Andrei

BSIT-21

Semester: 2nd | 2021-2022

DEFINITION OF TERMS

 Data flow diagram - maps out the flow of information for any process or system.

 Data flow chart - visually represents the systems and the processes.

 Logical Diagrams - display the theoretical process of moving information through a system.

 Physical diagrams - display the practical process of moving information through a system

 Data - individual facts and statistics collected together for reference or analysis.

 Process - a series of actions or steps taken in order to achieve a particular end.

 System – a collection of elements or components that are organized for a common purpose.

 Notation - a series or system of written symbols used to represent numbers, amounts, or elements in

something such as music or mathematics.

 Input - information fed into a data processing system or computer.

 Output - the amount of something that is produced or the process in which something is delivered.

USES

Data flow diagrams provide a graphical representation of how information moves between processes in a

system. Data flow diagrams follow a hierarchy; that is, a diagram may consist of several layers, each unique to a

specific process or data function. The primary use of a diagram is to map out an existing system and make it better

or to plan out a new system for implementation. Visualizing each element makes it easy to identify inefficiencies

and produce the best possible system.

PARTS

Entity, process, data store, and data flow are the four main components of all data flow diagrams.
TYPES/ CLASSIFICATION

 Logical diagrams display the theoretical process of moving information through a system, like where the

data comes from, where it goes, how it changes, and where it ends up.

 Physical diagrams show you the practical process of moving information through a system, like how your

system’s specific software, hardware, files, employees, and customers influences its flow of information.

SYMBOLS AND USES/ MEANING OF EACH SYMBOL

Data Flow Diagram symbols are standardized notations, like rectangles, circles, arrows, and short-text

labels, that describe a system or process’ data flow direction, data inputs, data outputs, data storage points, and its

various sub-processes. There are four common methods of notation used in DFDs: Yourdon & De Marco, Gene &

Sarson, SSADM and Unified. All use the same labels and similar shapes to represent the four main elements of a

DFD — external entity, process, data store, and data flow.

External Entity
An external entity, which are also known as terminators, sources, sinks, or actors, are an outside system or process

that sends or receives data to and from the diagrammed system. They’re either the sources or destinations of

information, so they’re usually placed on the diagram’s edges. External entity symbols are similar across models

except for Unified, which uses a stick-figure drawing instead of a rectangle, circle, or square.

Process

Process is a procedure that manipulates the data and its flow by taking incoming data, changing it, and producing

an output with it. A process can do this by performing computations and using logic to sort the data, or change its

flow of direction. Processes usually start from the top left of the DFD and finish on the bottom right of the diagram.

Data Store

Data stores hold information for later use, like a file of documents that’s waiting to be processed. Data inputs flow

through a process and then through a data store while data outputs flow out of a data store and then through a

process.

Data Flow

Data flow is the path the system’s information takes from external entities through processes and data stores.

With arrows and succinct labels, the DFD can show you the direction of the data flow.

RULES AND PROCEDURE

EXAMPLES
Bank transaction Diagram

The design is very simple, when the users inserted their cards, the system will ask for their credentials to

validate the possible transaction, after key-ing in their information and validation is success, the User will be

prompted on what type of account for the transaction it would like to use, after selection of account type the

system will proceed on the screen of transaction type. All this data will be visible to the user’s perspective when

using the application.

Simple FOS Diagram:

We are already familiar with some App for ordering food or items, with this type of transaction the

customer will send an Order to the app where the order from the app itself will be sent to 2 different destination,

the Kitchen and the Bill receipt maker, the Receipt maker will produce 2 types of receipt, the receipt for the

customer and the receipt to be sent for the customer, the only thing that the customer had to do after placing

order is waiting for his/her order to arrive at their respective doorstep.