Skip to content · ⁨דלג לתוכן⁩

Browse · ⁨דפדף⁩

A-Level Computer Science · ⁨מדעי המחשב A-Level⁩

Browse past papers, syllabus content, handouts, and vocabulary for every subject. · ⁨דפדף במבחנים קודמים, תוכן הלימודים, חומרי עזר וצירי מילים לכל נושא.⁩

Past papers · ⁨מבחנים ישנים⁩Handouts · ⁨חומרי עזר⁩Exercise sheets · ⁨דפי תרגילים⁩Vocabulary · ⁨מילון מונחים⁩

No PDFs in this folder. · ⁨אין קבצי PDF בתיקיה זו.⁩

Study A-Level Computer Science · ⁨מדעי המחשב A-Level⁩ · ⁨לימוד A-Level Computer Science · ⁨מדעי המחשב A-Level⁩⁩
Revise a topic · ⁨לחזור על נושא⁩

Got a question wrong? Open the notes for that topic. · ⁨טעית בשאלה? פתח את ההערה לנושא הזה.⁩

Teaching this subject? Everything for the classroom in one place · ⁨מורה לנושא זה? הכל לחצר הלימודים במקום אחד⁩ →

Tips · ⁨טיפים⁩

Split these papers by half. Theory questions suit short, frequent sessions — they test recall of precise definitions, and precision decays fast. Programming questions need long, uninterrupted sittings, because the skill is holding a whole solution in your head.

Write the code by hand, then type it in and run it. Past papers are the one place you can discover that what you "would have written" does not compile — much cheaper to find out now than in the exam hall.

When marking theory, compare your wording to the scheme word by word, not by meaning. This subject's schemes are unusually literal, and the right idea in the wrong words often scores zero. Keep a list of the phrasings you keep missing.

Browse all subjects · ⁨דפדפו בכל הנושאים⁩

Log in or create account · ⁨היכנס או צור חשבון⁩

IGCSE, A-Level & AP