Lecture 4 - Database Design DFD
Lecture 4 - Database Design DFD
User/developer
misunderstanding
a system.
System as a whole
is represented as a
bubble, and the
external entities are
shown as squares
from which input
flows and to which
output is directed
By: Mazhar Javed
14
Guidelines for designing a Context
data flow diagram
Online
Examination
System
By: Mazhar Javed
17
Problem Statement
Online
Examination
System
Online
Student Examination Faculty
System
In our case
(For Student)
1- Student Logins to the system
2- Student is asked questions
3- Student answers the questions
4- Student is displayed his/her result
(For Faculty)
1- Faculty enters number of questions in the system
2- Faculty is told about the result of particular students who
took the exam.
(For System)
1- Save the questions entered by faculty
2- Check and save the result.
By: Mazhar Javed
23
Context Diagram
Login
Question Online Question
Student Answers Examination Faculty
Result
Result System
Faculty Student
Enter login
Generate Process exam
and
questions Question
Validate Q
Quest results
Process Questions
Result for Process
Results Result for
Faculty
Student
By: Mazhar Javed
26
Some observations and hints
All data flows should be labeled. (These are the most common
labeling omissions.)
If you can’t name a data flow, re-evaluate it’s existence -- is it really
a data flow?
External entities (or agent) are outside the system: sources or sinks
of data.
Individuals performing functions within the system are NOT entities
-- their functions are captured as processes.
If you find yourself naming a data flow a verb -- take another look --
it may be a process! Data flows should be noun clauses.
All external entities shown on sub-diagrams (Level 0+) should be
on the context level diagram.
Make certain your labels are meaningful
By: Mazhar Javed
30