A-Level Computer Science project ideas (NEA) and how to pick a good one
7 min readUpdated
The A-Level Computer Science programming project (often called the NEA) rewards a solution to a real problem for a real user, with enough technical complexity to show advanced skills. These ideas are starting points: the best project is one where you know the user and can test with them. Always follow your exam board's specification and your teacher's guidance.
What makes a project score well
- A real end user you can interview, show prototypes to and test with.
- Clear, measurable success criteria agreed in the analysis.
- Technical complexity, such as object-oriented design, a relational database with SQL, recursion, a graph or tree algorithm, or a simulation.
- Evidence of testing against every success criterion, with screenshots or test tables.
- An honest evaluation: what works, what does not and what you would improve.
Project ideas with built-in complexity
| Idea | Possible user | Where the complexity comes from |
|---|---|---|
| School timetable or room booking system | A teacher or office manager | Relational database, clash detection, SQL queries |
| Revision quiz with spaced repetition | Students in a younger year group | Scheduling algorithm, user accounts, statistics |
| Route planner for a campus or town | New students or visitors | Graph data structure and Dijkstra's shortest path |
| Sports club manager | A coach | OOP design, fixtures generation, league tables |
| Stock and order system for a small shop | A local business owner | Database design, reports, data validation |
| Physics or traffic simulation | A science teacher | Numerical simulation, OOP, visual output |
| Puzzle game with a computer opponent | Friends or a games club | Minimax search, recursion, game-state trees |
A plan from start to finish
| Stage | What to produce |
|---|---|
| Analysis | User interviews, research into existing solutions, success criteria |
| Design | Data structures, database tables, algorithms in pseudocode, interface sketches |
| Development | Iterative prototypes with testing evidence at each stage |
| Testing | A test plan mapped to every success criterion, plus user feedback |
| Evaluation | How well each criterion was met, limitations and future improvements |
Common mistakes to avoid
- Choosing a project that is too big to finish; a smaller, complete, well-tested project scores better.
- No real user, which makes analysis and evaluation weak.
- Writing the documentation at the end instead of as you go.
- Complexity that is claimed but not shown in the code.
Frequently asked questions
Which language is best for the A-Level Computer Science project?
Python, Java and C# are all common. Choose the language you are most fluent in, because the project rewards a working, well-tested solution.
Can I make a game for my A-Level project?
Yes, if it has real technical complexity, such as an AI opponent using search or a physics simulation, and a real user to test it with.
How long should the project take?
Most students work on it across several months. Plan stages with deadlines and keep the documentation up to date as you go.
Learn it step by step
Practise this, step by step
Short lessons with quizzes, practice and interview questions, from your first program to job-ready.