A-Level CS NEA: The Interactive Master Guide

Assessment Overview

The NEA is a systems development project accounting for ~20% of your A-level. It is not just about code; the documentation is critical. Below is the breakdown of where your marks come from.

Marking Scheme Breakdown

Hover over segments to see details.

Why Documentation Matters

⚠

The 20% Rule: The NEA is often 20% of your grade. Implementation (Coding) is only ~15% of that. A perfect code with bad docs fails; buggy code with great docs can succeed.

📋

Systems Development: You are being assessed on the lifecycle: Analysis -> Design -> Build -> Test -> Evaluate.

"The code itself is only a small part. A 'buggy' program with a fantastic report (that documents the bugs!) can score higher than a 'perfect' program with a terrible report."

Choosing Your Project

The most critical first step. You need a project that hits the "Goldilocks Zone" of complexity—not too simple, not too hard.

The "Goldilocks" Complexity Check

Click a project idea to see if it's viable for A-Level.

📅

Basic Calculator / Quiz

📊

Booking System / Data Tool

🎮

3D MMORPG

Does your idea have...?

✓ A Real Client (End User)
✓ Data Structures (Lists, Trees, Hash Tables)
✓ Complex Algorithm (Sorting, Pathfinding, Minimax)
✓ Persistence (Database or File Handling)

The 5 Pillars of Development

Navigate the lifecycle stages. Use the buttons below to explore the specific documentation requirements for each phase.

The Golden Thread

How to get the A*. Examiners look for a single thread linking all stages. A requirement defined in Analysis must be traced all the way to Evaluation.

Trace a Requirement

EXAMPLE: USER LOGIN