Back to A-Level
H446/03

Programming Project (NEA)

70 marks • 20% of A-Level

Important Notice

This guidance provides high-level advice only. Your project must be your own original work. Copying solutions or using excessive external help may constitute malpractice.

Analysis

9 marks
  • Identify a suitable problem requiring computational solution
  • Define clear stakeholder requirements through investigation
  • Document specific, measurable objectives
  • Research existing solutions and identify limitations
  • Justify chosen computational approach

Design

12 marks
  • Create detailed data structures with justification
  • Design algorithms using appropriate notations (pseudocode/flowcharts)
  • Plan modular structure with clear interfaces
  • Design user interface mockups with usability considerations
  • Include file structures and database schemas where relevant
  • Demonstrate decomposition of complex problems

Development

25 marks
  • Implement solution following design documentation
  • Use appropriate programming paradigms (OOP where suitable)
  • Write clean, well-commented code
  • Apply good coding practices and conventions
  • Implement input validation and error handling
  • Use advanced techniques appropriate to A-Level (recursion, file handling, etc.)

Testing

8 marks
  • Create comprehensive test plan before testing
  • Test with normal, boundary, and erroneous data
  • Document expected vs actual results with evidence
  • Include user acceptance testing
  • Show iterative testing during development

Evaluation

6 marks
  • Evaluate against original objectives systematically
  • Analyse effectiveness of solution for stakeholders
  • Identify genuine limitations and constraints
  • Suggest meaningful improvements with technical detail
  • Reflect on development process and lessons learned

General Tips

  • Choose a project you're genuinely interested in - you'll spend significant time on it
  • Start early and work incrementally - don't leave everything until the deadline
  • Document as you go - it's easier than writing everything at the end
  • Ensure your project has enough complexity to demonstrate A-Level skills
  • Back up your work regularly - losing work is not an acceptable excuse