Where the marks actually go
Unit A2 1, Systems Approaches and Database Concepts, is a single 100-mark paper in 2 hours, built around a pre-release case study you will have seen before the exam. That is about 72 seconds per mark, so a 10-mark question deserves 12 minutes and the 18-mark SQL question at the end deserves close to 22. The paper splits into two halves: Part 1 covers systems approaches, requirements, and project management across six questions worth 55 marks, and Part 2 covers relational databases, normalisation, and SQL across three questions worth 45 marks.
Structured Query Language and entity relationship modelling carry the largest concentrated blocks of marks in Part 2, worth 18 and 17 marks respectively in recent papers, with normalisation close behind. In Part 1, systems methodologies is the heaviest single topic. Because you have already seen the case study before the exam, the marks in both halves reward how precisely you apply your knowledge to the named characters and scenario in it, not how much general theory you can recall.
Paper structure and timing
Part 1: Systems Approaches, Requirements and Project Management (around 55 marks)
Six questions, each worth around 10 marks, mixing short answer and template completion with quality of written communication essays on prototyping, project management, testing and the V-model, and modelling with UML. Budget about 66 minutes across this half, roughly 11 minutes per question.
Part 2: Relational Database Concepts, Normalisation and SQL (around 45 marks)
Three questions: a 10-mark normalisation task taking a relation through 2NF and 3NF, a 17-mark question combining definitions with entity relationship diagram completion, and an 18-mark SQL scripting question covering insertion and multi-table aggregate queries. Budget around 54 minutes, weighted toward the SQL question since it carries the most marks.
Read the pre-release case study again on exam morning, and keep the named characters and business rules from it in front of you. Every extended answer in this paper is marked down when it stays generic instead of naming the specific scenario.
The highest-yield techniques
Normalisation questions are marked step by step, and the most common way to lose marks that have nothing to do with understanding 2NF or 3NF is bookkeeping: forgetting to underline or asterisk primary keys, and forgetting to carry foreign keys forward, at every stage of the decomposition. Mark every key at every step, from the unnormalised form through to 3NF, even when a table looks unchanged from the previous stage.
SQL questions reward precise syntax over approximate logic. When a query needs to find parent records with no matching child rows, for example clients who have never placed an order, use a LEFT JOIN with a null check on the child table's key, an inner join alone will silently exclude exactly the rows the question is asking for. When aggregating, for example summing booking durations by staff member, include every non-aggregate column you are grouping by in the GROUP BY clause, and use COUNT(DISTINCT ...) when a join could otherwise produce duplicate rows.
PERT network questions catch candidates on the backward pass specifically. When more than one activity depends on the same predecessor, the late finish time for that predecessor is the minimum, not the maximum, of the late start times of everything that follows it. Work backward from the project end date one activity at a time, and write down each late start and late finish as you go rather than trying to hold several branches in your head at once.
Quality of written communication questions, on Agile versus Waterfall, feasibility, or testing strategy, lose marks when the answer reads as a textbook definition with no reference to the case study. Name the business, the named characters, and the specific business rule the question is pointing at, and use that context in every paragraph, not just the introduction.
CCEA conventions worth knowing
This unit carries synoptic assessment: A2 questions can draw on material first covered at AS, object concepts, control structures, testing principles, so do not assume everything on this paper is new content from the A2 course alone. Quality of written communication is assessed inside the extended prose questions themselves and depends on specialist technical vocabulary, entity, functional dependency, join, exception, rather than everyday description, plus a logically ordered answer.
The three assessment objectives for this unit are knowledge (AO1), application (AO2), and analysis and evaluation (AO3), weighted at roughly 32%, 36%, and 32% within this paper. That is a more even split than many subjects, which is why both precise recall of syntax and applied problem solving matter equally here.
Exam day plan
Reread the pre-release case study before you open the question paper. For every normalisation step, mark primary and foreign keys as you go, do not leave it to the end. For every SQL query, check your JOIN type and your GROUP BY columns before you move on. For every QWC answer, open with the specific business context, not a general definition. Leave time at the end to check that every extended answer names the case study characters at least once.