2.2.1 Strategies for problem solving (top-down design, stepwise refinement)

• Top-down design:

  • Start with a broad problem statement and recursively break it down.

  • Produces a hierarchy of subproblems.

• Stepwise refinement:

  • Continuously refine each subproblem until it’s detailed enough to solve directly in code.

• Purpose:

  • Improves clarity, reduces complexity, and helps create structured solutions.

2.2.2 Writing and following pseudocode and flowcharts

• Pseudocode:

  • A language-independent notation for designing algorithms.

  • Common keywords: IF, THEN, ELSE, WHILE, FOR, REPEAT, UNTIL.

• Flowcharts:

  • Visual diagrams showing the flow of control in an algorithm.

  • Standard shapes: oval (start/end), parallelogram (input/output), rectangle (process), diamond (decision).

• Importance:

  • Clarifies logic before coding.

  • Facilitates collaboration and review.

2.2.3 Programming best practices (naming conventions, commenting, modularity)

• Naming conventions:

  • Use descriptive names for variables, functions, classes.

  • Improves readability and maintainability.

• Commenting:

  • Explains why something is done, not just what.

  • Helps future maintainers (and your future self) understand logic.

• Modularity:

  • Splitting code into functions, procedures, or modules.

  • Encourages reusability and simplifies debugging.

2.2.4 Testing (black box, white box, alpha, beta)

• Black box testing:

  • Tester sees only inputs and outputs.

  • Internals of the system are not considered.

• White box testing:

  • Tester examines the internal structure and flow of code.

  • Ensures every path in the code is tested.

• Alpha testing:

  • Done in-house by the development team or dedicated test team.

• Beta testing:

  • Done by a limited external group of potential end-users before final release.