CCEA A-Level Computer Science
Explore your course, one topic at a time.
Explore your topics
9 topics
Course topics9 topics
- Programming Concepts and Paradigms11 objectives
- Software Development Process16 objectives
- Mathematics6 objectives
- Databases and SQL13 objectives
- Data Types, Structures and Algorithms7 objectives
- Systems Software and Networking7 objectives
- Systems Software and Security6 objectives
- Web Technologies9 objectives
- Networking and Web Technologies6 objectives
About this course
About CCEA A-Level Computer Science
The CCEA A-Level Computer Science specification provides students across Northern Ireland with a rigorous grounding in computing theory, software engineering principles, and practical problem-solving. Structured across two distinct tiers, the qualification divides into AS units covering system development lifecycles and core computational fundamentals, before advancing to A2 units that delve into enterprise information systems and complex programming.
Throughout the course, learners explore how hardware architecture, data representation, and networking underpin contemporary digital technologies. Students build significant technical proficiency by translating theoretical algorithms into functional, high-level code, culminating in a substantial software development project that mirrors real-world industry practices.
Assessment Structure
The CCEA A-Level is assessed through four mandatory units split equally across AS and A2 stages. At AS level, students sit two written examinations: Unit AS 1 (Approaches to System Development, 1 hour 30 minutes, 20% of total A-Level) and Unit AS 2 (Fundamentals of Computing, 1 hour 30 minutes, 20% of total A-Level). At A2 level, students complete Unit A2 1 (Information Systems, 2 hours 30 minutes, 40% of total A-Level), alongside Unit A2 2 (Application Development, 20% of total A-Level), which is a teacher-assessed, externally moderated practical programming project providing 100 marks.
Why Choose CCEA?
- CCEA maintains a true modular structure where AS marks directly contribute 40% towards the final overall A-Level grade, reducing end-of-course exam pressure compared to purely linear English boards.
- The specification places an exceptional focus on formal software engineering methodologies, agile practices, and enterprise systems, equipping students with directly transferable industry workflows.
- The Unit A2 2 practical project allows students significant flexibility to design, code, and test an authentic software solution for a real client using their preferred programming language.
Frequently Asked Questions
Does the CCEA AS-Level grade still count towards the full A-Level?
What programming languages are permitted in the CCEA A2 2 coursework?
How much mathematics is required for CCEA A-Level Computer Science?
What is the difference between Unit AS 1 and Unit A2 1?
Can I use external libraries and frameworks in my A2 programming project?
Assessment and exam guidance
What Gets Top Grades
Knowledge & Understanding
Demonstrates comprehensive and accurate knowledge
- Uses correct subject-specific terminology
- Shows detailed understanding of concepts
- Makes accurate connections between topics
- Demonstrates depth beyond surface-level knowledge
Application
Applies knowledge effectively to new contexts
- Selects relevant knowledge for the question
- Adapts understanding to unfamiliar scenarios
- Uses examples appropriately
- Shows awareness of context
Analysis & Evaluation
Develops sophisticated analytical arguments
- Constructs logical chains of reasoning
- Considers multiple perspectives
- Weighs evidence to reach justified conclusions
- Acknowledges limitations and nuances
Key Command Words
Give a single fact or term
Name, select, or recognise
Set out main features briefly
Give an account of what something is like or what happens
Give reasons with developed cause→effect chains
State similarities AND differences (both required)
Examine in detail showing cause→effect→consequence chains
Weigh up BOTH sides, reach JUSTIFIED conclusion
Make judgments about importance with justification
Show formula→substitution→calculation→answer with units
Tips and common mistakes
Common Exam Mistakes
Pitfalls to avoid in your exams
- •Confusing a class with an object, treating a class as if it were a single instance rather than a template.
- •Assuming that inheritance automatically provides unlimited access, failing to recognize visibility modifiers and the need for proper encapsulation.
- •Misunderstanding polymorphism, often confusing method overloading (compile-time) with overriding (run-time) and not using dynamic binding effectively.
- •Confusing black-box and white-box testing techniques, for example, applying code-coverage criteria when conducting black-box tests, or failing to consider internal logic during white-box testing.
- •Producing test plans with vague expected outcomes or with test cases that only check normal scenarios, neglecting edge cases and invalid inputs.
- •Misusing debugging tools, such as setting breakpoints indiscriminately rather than at strategic points near suspected errors, or completing trace tables without reflecting actual variable value changes through each step.
- •Omitting integration testing from the test plan entirely, assuming that unit testing alone is sufficient to ensure modules work together.
- •Confusing the order of digits when converting between bases
Top Examiner Tips
Expert advice for exam success
- •Always explicitly indicate the intended access level for each member (private, protected, public) and justify design choices in coursework.
- •Practice drawing UML class diagrams to visualize inheritance hierarchies and interface implementations, as this often helps in planning and answering design questions.
- •When designing test plans, always align test cases directly to specification requirements and justify the choice of testing technique (black-box or white-box) for each case.
- •In debugging questions, explicitly reference tool use: state where a breakpoint would be set and why, describe what watch variables indicate, and present trace tables with clear step-by-step state changes.
- •For high marks, include both typical and extreme/erroneous test data in black-box examples, and when using white-box techniques, illustrate coverage by referencing specific code paths or statements.
- •Practice conversions regularly to build speed and accuracy
- •Always show working for arithmetic operations to gain method marks
- •Memorize key Boolean algebra laws and practice applying them
Ready for a little practice?
Create your account to start practising Computer Science.
7 days Premium · Then free forever · No card, no charge