Overview
A data flow diagram (DFD) shows how information flows within an
information system. A DFD is a representation of the data flow and does
not imply the activity order. A DFD is a model of a real-world business
system represented through a hierarchy of abstracts through leveling.
Lower levels of a DFD reflect more detail, and higher levels of a DFD
reflect less detail. A logical system diagram describes the business
events that take place and the data required for each business event,
focusing on what information is flowing and what information is
transmitted. A DFD will not go into technical (hardware and software)
aspects of the system; it will show inputs and outputs from external
sources, showing the path of data and how it flows through the system.
Prompt
For this activity, you need to create a data flow diagram reflective of the following:
Your experience registering for a course and then following the process through payment (or using financial aid).
Access course catalog
Review course options
Select course to register for
Complete registration
Pay for course
Your DFD must include the listed processes and at least two
subprocesses (levels) within two of the five main processes. Your
diagram can reflect up to three levels: zero (the context diagram), one
(subprocess), and two (functionality). The various levels of detail are:
Level zero: Represents the overview of the entire system you are critiquing
Level one: Breaks down the main functions of the system into smaller subprocesses
Level two: Further breaks down subprocesses of level one
Use the symbols from the Gane and Sarson symbol set needed to illustrate data flow within your diagram:
External entity = Square 
Data flow = Arrow →
Process = Rounded square ▢
Data stored = Rectangle ▭
Specifically, you must address the following rubric criteria:
Data Flow Diagram: Your diagram must be completed
without any missing components. It needs to show how information flows
within a system process. Remember: only DATA flows on data flows.
Hierarchical Leveling: Whether your diagram has one
or three levels, it needs to illustrate how each level is broken down
into smaller business events.
Data Flow Notation: Your diagram should include
accurate and appropriate data flow notation. Whenever you are referring
to a process, use a rounded square symbol. Whenever you are referring to
data that is being stored, use a rectangle. It depends on the business
process, but you may or may not have to use all Gane and Sarson symbols.
Logical System Functionality: Your diagram also needs to illustrate how business events are broken down into smaller subprocesses.
What to Submit
Upload a .doc, .pdf, or .jpeg file of your diagram. You can use a
tool of your choice to help you create the data flow diagram, but we
recommend using Lucidchart, draw.io, or Microsoft Visio.
Getting Started in Lucidchart: The Basics
Visio 2016 Tutorial
Microsoft Azure Dev Tools for Teaching (link to access Visio)
Draw.io Quick Start Video Tutorial (1:35)
Draw.io Diagram Software
Module Two Activity Rubric
Criteria Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value
Data Flow Diagram Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner Illustrates a complete data flow diagram by showing how information flows within a system process Shows progress toward
proficiency, but with errors or omissions; areas for improvement may
include more details of the complete process Does not attempt criterion 25
Hierarchical Leveling Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner Illustrates how each hierarchical level is broken down into smaller business events Shows progress toward
proficiency, but with errors or omissions; areas for improvement may
include more breakdown of information transmitted throughout system Does not attempt criterion 20
Data Flow Notation Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner Includes accurate data flow notation (processes, data stores, external entities, and data flows) based on the selected system Shows progress toward
proficiency, but with errors or omissions; areas for improvement may
include correcting inaccurate symbols to show the part of the data flow
(e.g., using a square to show a process instead of using a rounded
square) Does not attempt criterion 15
Logical System Functionality Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner Designs a diagram that shows business events broken down into subprocesses Shows progress toward
proficiency, but with errors or omissions; areas for improvement may
include showing both the business event and the associated subprocesses Does not attempt criterion 20
Articulation of Response Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner Clearly conveys meaning with correct
grammar, sentence structure, and spelling, demonstrating an
understanding of audience and purpose Shows progress toward
proficiency, but with errors in grammar, sentence structure, and
spelling, negatively impacting readability Submission has critical errors in grammar, sentence structure, and spelling, preventing understanding of ideas 10
Citations and Attributions Uses citations for ideas requiring attribution, with few or no minor errors Uses citations for ideas requiring attribution, with consistent minor errors Uses citations for ideas requiring attribution, with major errors Does not use citations for ideas requiring attribution 10
Total: 100%
