How to Score Higher in SQA National 5 Computing Science ()

• •Draw a variable trace table with one column per variable and one row per loop iteration before writing your answer
• •Do not skip iterations — update every variable that changes on each pass through the loop
• •Watch for off-by-one errors: check whether the loop condition uses < or <=
• •If the question says 'state the output', write only what appears in the PRINT/OUTPUT statement — do not include intermediate values
• •For nested loops, track both the outer and inner loop counters in your table

• •Identify the standard algorithm first (input validation = conditional loop; running total = initialise to 0 then add in loop; linear search = loop + conditional check)
• •Use the variable names and data structures specified in the question — do not introduce your own names if the question provides them
• •For input validation, ensure the structure is: get input BEFORE the loop, WHILE invalid DO ask again
• •For running total, initialise the accumulator to 0 before the loop, then add inside the loop, and output after the loop ends
• •Write each step on a separate line to make the structure clear to the marker

• •Always check whether you need fields from one or two tables — if two, you must include a JOIN
• •Write the JOIN before the WHERE clause; the correct order is SELECT → FROM → INNER JOIN … ON → WHERE → ORDER BY
• •For multiple conditions, use AND when both must be true; use OR when either can be true
• •For INSERT, the order of values must exactly match the order of field names: INSERT INTO table (field1, field2) VALUES (value1, value2)
• •For UPDATE, always include a WHERE clause to target the correct record, not the entire table

• •Use the correct technical term every time: 'floating point' not 'decimal', 'Boolean' not 'true/false variable', 'concatenation' not 'joining strings'
• •For 'describe' questions, state what happens — no reason required
• •For 'explain' questions, add 'because' or 'so that' to link the action to its effect
• •Tie your answer to the specific scenario in the question — generic answers about RAM or CPU that do not mention the context score no marks
• •For two-mark questions, make two distinct points — repeating the same point in different words does not earn the second mark

Name the correct item, term, or feature from the code, diagram, or scenario provided. Usually one or two words or a short phrase. No elaboration is required.

Give a concise factual answer. Similar to 'identify' but may require a short sentence. No explanation of why is needed.

State what happens, what a feature does, or how something works. For code, state what each line or section does. For a concept, explain its properties. Do not give reasons — that is 'explain'.

State what happens AND give the reason or mechanism using 'because' or 'so that'. The marking instructions will have an observation mark and a reason mark — both are needed for full credit.

Fill in the missing part of code, a table, a flowchart, or an SQL statement that is partially provided. Use the structure already given as a template.

Write syntactically correct code in your chosen programming language (or the language specified in the question) to implement the stated functionality. The answer must be executable code, not pseudocode unless the question allows it.

Produce a step-by-step solution using either pseudocode or a design technique (e.g. structure diagram, flowchart). The design must show the correct logic — loop type, condition, data structure, and sequence of steps.

Perform a numerical computation — for example, converting between number systems, working out the number of bits required, or computing a file size. Show your working.

Give a brief summary of the key points or stages of a process. Less detail is required than for 'describe', but the answer must go beyond just naming something.