📚 Understanding System Modeling Methods
System modeling is a way to create a graphical representation of a system to understand its
components and how they interact. There are three main types: process, data, and object
modeling. Each has a different focus.
1. Differences Among Process, Data, and Object Modeling
Modeling Type Focus What it Represents
Process Modeling Processes The flow of data and the
sequence of business
activities. It shows what a
system does.
Data Modeling Data The structure of a system's
data and how it relates to
other data. It shows what a
system stores.
Object Modeling Objects The system as a collection
of interacting objects,
which have both data
(attributes) and behaviors
(methods). It combines
data and process
modeling.
2. Components of Modeling Methods
Data Flow Diagrams (DFDs)
DFDs are used in process modeling to show the flow of information through a system. Its
components are:
● Process: A function or activity that transforms incoming data into outgoing data. It's
represented by a circle or a rectangle with rounded corners.
● External Entity: A source or destination of data, outside the system's control. It's
represented by a rectangle. Examples include a customer or a bank.
● Data Flow: The path data takes between components. It's represented by an arrow.
● Data Store: A place where data is stored for later use. It's represented by two parallel
lines or a rectangle open on one side.
Entity-Relationship Diagrams (ERDs)
ERDs are used in data modeling to show the relationships between data entities.1 Its
components are:
● Entity: A person, place, or thing about which data is collected. It's represented by a
rectangle. For example, a "Student" or a "Course."
● Attribute: A characteristic or property of an entity. It's represented by an oval. For a
"Student," attributes might be "Name" and "ID."
● Relationship: An association between two or more entities. It's represented by a
diamond. For example, a "Student" enrolls in a "Course."
3. Usage of Modeling Methods
● Process Modeling (DFDs): DFDs are used to create a logical model of a system. They
help developers and analysts visualize how data moves and is transformed. They're great
for showing business processes, like how an order is processed from a customer to
shipping.
● Data Modeling (ERDs): ERDs are used to design databases. They ensure that all
necessary data is captured and that the relationships between different pieces of data
are clearly defined.2 This helps avoid data redundancy and inconsistencies.
4. Common Errors in DFDs
Common mistakes in DFDs include:
● Data flows with no process: An arrow connecting two external entities or two data
stores without a process in between is an error because data must be transformed by a
process.
● Black hole process: A process that has input data flows but no output data flows. This
means the data goes in but never comes out.
● Miracle process: A process that has output data flows but no input data flows. This
means data is created out of nothing.
5. Applying Process and Data Modeling
Scenario: A University Course Registration System
Let's apply process and data modeling to a simple university course registration system or
Student Information System.
Process Modeling (DFD)
A DFD would show the flow of information.
● External Entities: Student, Registrar's Office.
● Processes: Check Course Availability, Register for Course, Generate Schedule.
● Data Stores: Course Catalog, Student Records.
● Data Flows: The arrows would show data like "Course Request" from the Student to the
"Check Course Availability" process, and "Registered Courses" from the "Register for
Course" process to the "Student Records" data store.
Data Modeling (ERD)
An ERD would show the data structure.
● Entities: Student, Course, Instructor.
● Attributes:
○ Student: StudentID, Name, Major.
○ Course: CourseID, Title, Credits.
○ Instructor: InstructorID, Name, Department.
● Relationships:
○ A Student enrolls in a Course.
○ An instructor teaches a Course.