Skip to content

2. Interpreting Requirements and Designing Solutions

This section moves students from a problem description to a planned solution.

Combines

  • functional requirements
  • non-functional requirements
  • constraints
  • scope
  • mock-ups
  • input-process-output charts
  • flowcharts and pseudocode

Why these belong together

Students should practise reading a teacher-provided case study, deciding what the solution must do, and then choosing the best design tools to represent the intended solution before coding begins.

Good folio-style tasks

  • classify statements from a case study as functional or non-functional requirements
  • identify constraints and scope boundaries
  • produce an IPO chart and pseudocode for a short solution
  • create a simple mock-up for a text-based or graphical solution

Key skills supported

  • interpret solution requirements
  • select and use appropriate design tools to represent solution designs