Abstract Models in Computational Thinking

Overview

An abstract model is a simplified representation of a real-world system, focusing on the key components and their relationships while ignoring unnecessary details. In computational thinking, abstract models help break down complex problems, making them easier to analyse and solve. These models form the foundation for designing algorithms and systems.

Understanding how to devise abstract models is essential for applying computational thinking to a variety of scenarios.

Steps to Devise an Abstract Model

1. Identify Key Entities: Determine the main components involved in the problem.
2. Determine Relationships: Define how the entities interact with each other.
3. Focus on Essentials: Include only the details necessary to solve the problem, omitting irrelevant specifics.
4. Represent the Model: Use diagrams (e.g., entity-relationship diagrams) or structured descriptions to illustrate the abstract model.

Benefits of Abstract Models

1. Improved Problem Solving: Helps break down complex problems into simpler, solvable parts.
2. Clarity and Focus: Provides a clear understanding of the problem and its essential elements.
3. Reusability: Abstract models can be adapted for similar problems in different contexts.
4. Efficiency: Reduces the cognitive load by simplifying complex systems.

Devise Abstract Models for Different Situations

A School Timetable System

Real-World Scenario:

• Involves managing teachers, students, classrooms, and subjects. Abstract Model:

• Entities: Teacher, Student, Classroom, Subject.

• Relationships:

  • Each teacher teaches one or more subjects.
  • Each student is enrolled in multiple subjects.
  • Each subject has a fixed classroom and time slot.

• Essential Components: Focus on scheduling constraints like teacher availability and classroom occupancy.

A Traffic Light Control System

Real-World Scenario:

• Manages vehicle and pedestrian flow at an intersection. Abstract Model:

• Entities: Traffic Light, Timer, Vehicle Sensor, Pedestrian Button.

• Relationships:

  • Traffic lights change based on a timer or sensor input.
  • The pedestrian button overrides the timer to allow pedestrian crossing.

• Essential Components: Ignore specifics like the exact number of vehicles and focus on the sequence of light changes.

An Online Shopping System

Real-World Scenario:

• Manages products, customers, orders, and payments. Abstract Model:

• Entities: Product, Customer, Order, Payment.

• Relationships:

  • Customers place orders containing one or more products.
  • Each order is associated with a payment method.

• Essential Components: Focus on the process of ordering and payment, ignoring inventory storage details.

A Weather Forecasting System

Real-World Scenario:

• Collects and analyses weather data to predict future conditions. Abstract Model:

• Entities: Weather Station, Sensor Data, Forecast Model.

• Relationships:

  • Weather stations collect sensor data (temperature, humidity, pressure).
  • Forecast models use this data to predict weather.

• Essential Components: Ignore geographical distribution and focus on data inputs and model outputs.

A Banking System

Real-World Scenario:

• Handles customer accounts, transactions, and loans. Abstract Model:

• Entities: Account, Customer, Transaction, Loan.

• Relationships:

  • Customers have one or more accounts.
  • Transactions (deposits/withdrawals) are linked to accounts.
  • Loans are associated with specific customers.

• Essential Components: Concentrate on transaction processing and loan management, ignoring details like branch locations.

Note Summary