Software Engineering › Notes › Answer skeletons for every question type
Answer skeletons for every question type
Skeleton: 3-mark 'Outline / Describe / Explain'
- Identify: Name the term or feature (1 mark).
- Outline: Say what it is or does in one clear sentence (2 marks).
- Describe/Explain: Add how or why, with a consequence or example from the scenario (3 marks).
- Count the verbs: 'Outline TWO' means two separate ideas, each with a short reason. Do not write a list of names.
Skeleton: 'Compare' and 'Distinguish'
- Both: One thing the two have in common.
- A only: A feature of A in the context of the scenario.
- B only: The matching contrasting feature of B.
- So what: One consequence for the user or the scenario.
- Link words: Both... whereas... however... in contrast...
Skeleton: 5-mark 'Discuss / Assess / Explain with scenario'
- Topic sentence: Name the technology/issue and the scenario in one sentence.
- Point 1 (positive): Feature -> effect -> scenario example.
- Point 2 (negative or limitation): Feature -> effect -> scenario example.
- Point 3: Another distinct angle (security, privacy, workers, cost, users).
- Judgement: One sentence that weighs it up (overall, ... because ...).
- Check: Both sides? Used scenario words? Used syllabus terms?
Skeleton: 6-mark extended response
- Thesis: Direct answer to the question in the first sentence, using its keywords.
- Concept: Define the key concept in one line (e.g. human bias, privacy by design).
- Paragraph 1: Point + explanation of mechanism + stimulus evidence.
- Paragraph 2: Second point (different stage or group) + evidence.
- Paragraph 3: Effect on the user/society/environment, with a positive AND negative where asked.
- Close: Mitigation or evaluative conclusion. Aim for 150-200 words; a 6 mark answer needs 'explain', not 'list'.
- Stimulus: If a video, image or scenario is given, refer to it by name at least twice (2025 Q27 needed 'with reference to the video').
Technique: Python, SQL and pseudocode questions
- Read the task into a checklist: Underline each requirement (e.g. unique, random, 5 by 5, descending order). The criteria are literally that list.
- Plan: Write the inputs, processes and outputs first.
- Code: Use the constructs asked for (selection AND loop), correct indentation, sensible names, and inbuilt functions where suitable (len, sum, range, random).
- Run it in your head: Trace with a small example. Check off-by-one in range(), indexes from 0, and boundaries (> v >=).
- Output format: Match the output asked (prints, separators, end=" ").
- Call your function: Marker feedback: some students defined a function but never called it.
- SQL: SELECT, FROM, WHERE, GROUP BY, ORDER BY in order; quote text values; use AS for names; GROUP BY the non-aggregated fields; COUNT/SUM for totals; DESC for highest first.
- Pseudocode: Capital keywords, paired BEGIN/END and IF/ENDIF, indent, initialise variables before loops, show output.
- Partial marks: Always write something: correct selection OR correct loop OR correct output earns marks.
Technique: drawing questions (DFD, flowchart, structure chart, class diagram, decision tree, storyboard, UI, ERD)
- Use the exact symbols: Course-spec symbols (see Diagram rules). Label every flow, process, decision arrow and relationship.
- Boundaries: DFD level 0: one process, no data stores.
- Read the scenario for nouns and verbs: Nouns become entities/data stores/classes; verbs become processes/methods.
- Completeness: Every input has a process; every process has an output; every decision has two labelled exits.
- Neatness: Boxes big enough, no crossing lines, readable text. Do not run out of time: spend marks-based time.
Technique: objective items (multiple choice, multi-select, drag-and-drop, fill in blanks, matching)
- Eliminate: Cross out options that are clearly wrong, using keywords (e.g. 'Ensuring parties are who they claim to be' = authentication).
- Multi-select: Read how many to choose; each correct tick matters.
- Ordering: Sequences you must know: SDLC steps, Waterfall phases, DFD/ML training cycle (forward propagation, loss, backpropagation).
- Matching tables: Match each statement to ORM, SQL or both (2025 Q9).
- Time: 16 marks in 2025 for Q1-14; aim for under 20 minutes, then bank the time for written items.