Thinking Procedurally: Importance of Identifying Problem Components

Key Concepts

• Real-World Problem Complexity

  • Trivial problems can be solved by individual programmers.
  • Complex problems, like developing software for modern smartphones, require breaking down the task due to the complexity of operating systems.

• Procedural Thinking

  • Involves breaking down large problems into smaller, manageable parts.
  • Essential for tackling complex tasks.

Problem Solving with Top-Down Modular Design

Stepwise Refinement

• Top-Down Design

  • Split the main task into smaller subtasks.
  • Further split subtasks into more granular tasks if needed.
  • Goal: Create subtasks that perform single functional tasks, manageable independently.

• Structure Diagram

  • Visual representation of task breakdown.
  • Example: Wage Calculation Program
    • Top layer includes obtaining employee details, calculating gross pay, deductions, net pay, and outputting a wage slip.
    • Subtasks further broken down:
      • Gross Pay: Normal wages + Overtime
      • Deductions: Tax + National Insurance

Benefits of Top-Down Modular Design

• Allows assignment of lowest level tasks to individuals or small teams.
• Facilitates writing and testing modules in isolation.
• Modules can be integrated into the overall solution efficiently.

Additional Resources

• Cheat Sheet on Computational Thinking
  • Available from student.craiganddave.org
  • Features a basic poster and detailed explanation on computational thinking.
  • Download from A-Level Revision section under OCR AS and A-Level, includes two versions of the computational thinking cheat sheet.