System Model
1. Context Model
Definition:
A Context Model represents the system as a whole
and how it interacts with external entities like users,
other systems, or environments.
Key Features:
Defines system boundaries.
Identifies external entities (users, hardware,
software).
Shows high-level interactions.
Diagram Used:
Context Diagram (Data Flow Diagram - Level 0)
Example:
A library management system's context diagram would
include entities like students, librarians, and book
databases, showing interactions such as issuing books,
returning books, and updating records.
2. Behavioral Model
Definition:
A Behavioral Model describes how a system responds
to inputs and how it transitions from one state to
another.
Types of Behavioral Models:
1. Data Flow Model (DFD) – Shows how data moves
within the system.
2. State Machine Model – Defines system states
and transitions.
3. Use Case Model – Represents interactions
between users and the system.
Diagrams Used:
State Transition Diagram
Sequence Diagram
Use Case Diagram
Example:
A state diagram for an ATM system:
1. Idle → Card Inserted → Validating
2. Validating → PIN Entered → Transaction
Processing
3. Transaction Processing → Cash Dispensed →
Idle
3. Data Model
Definition:
A Data Model represents how data is structured,
stored, and related within the system.
Key Concepts:
Entities: Objects in the system (e.g., Student,
Book).
Attributes: Characteristics of entities (e.g.,
Student ID, Book Title).
Relationships: Connections between entities
(e.g., A Student borrows a Book).
Types of Data Models:
1. Entity-Relationship (ER) Model – Represents
data relationships.
2. Relational Model – Uses tables for data
representation.
3. Object-Oriented Model – Uses objects and
classes.
Diagrams Used:
ER Diagram
Class Diagram
Example:
An ER diagram for a Student and Course relationship:
Entity: Student (Student_ID, Name)
Entity: Course (Course_ID, Course_Name)
Relationship: "Enrolls in" (Many-to-Many)
4. Object Model
Definition:
An Object Model represents a system in terms of
objects, classes, and their interactions.
Key Concepts:
Objects: Instances with properties and behaviors.
Classes: Blueprints for objects.
Inheritance: Sharing of properties between
classes.
Encapsulation: Data hiding within objects.
Diagrams Used:
Class Diagram
Object Diagram
Example:
A Class Diagram for an Online Shopping System:
Class: Customer (Attributes: Name, Email)
Class: Order (Attributes: Order_ID, Date)
Class: Product (Attributes: Product_ID, Price)
Relationships: A Customer places multiple
Orders.
Model Focus Example
Type Area Diagram
Context System boundaries
Context Diagram
Model & interactions
Behavioral System's reaction State Diagram, Use
Model to inputs Case Diagram
Data storage & ER Diagram, Relational
Data Model
relationships Model
Object Objects, classes, Class Diagram, Object
Model and interactions Diagram
