Abstraction and automation exam tips

Exam tips

• Use brackets to show the intended logic

  When an expression contains both AND and OR, use brackets to make the order of evaluation explicit.

  Clear grouping helps prevent changing the meaning of the problem and makes your reasoning easier to follow when checking a solution.

• Trace systematically

  Make a table showing the important variable values before and after each iteration.

  A systematic trace reduces skipped steps and gives clear evidence for the final output and the algorithm's termination.

• Use the defining phrases

  For representational abstraction, mention removing unnecessary details. For generalisation or categorisation, mention common characteristics and the 'is a kind of' hierarchy.

  These phrases directly state the distinctions required by the specification and help make an answer precise.

• Use the essential-characteristics test

  For each detail, ask whether it contributes to the object's essential characteristics. If it does not, it is a candidate for hiding.

  This directly applies the specification definition and helps distinguish information hiding from removing important characteristics.

• Separate values from methods

  When explaining procedural abstraction, explicitly state which particular values have been removed and what general method remains.

  This directly addresses both parts of the specification requirement and avoids describing only a single example.

• Use the specification wording

  When explaining functional abstraction, explicitly mention that the particular computation method is hidden or disregarded.

  This directly addresses the defining distinction in the specification and helps separate functional abstraction from procedural abstraction.

• Use the two-part definition

  In an explanation, mention both that the representation is hidden and that use is isolated from construction.

  Including both ideas directly addresses the specification and helps avoid an incomplete definition of data abstraction.

• State both stages clearly

  For an abstraction or reduction question, mention the removal of unnecessary details and the aim of reaching a solvable representation. For reduction, also mention the already-solved problem.

  These points directly address the specification requirement and help distinguish abstraction from general simplification.

• Use the specification wording

  When defining procedural decomposition, include the ideas of sub-problems, identifiable tasks and possible further subdivision.

  These are the central points in the requirement and help ensure that a definition or explanation is complete.

• Identify what is being combined

  When answering a composition question, first decide whether the question concerns procedures or data objects.

  This lets you accurately distinguish a composition abstraction based on a compound procedure from a data abstraction based on compound data.