Nepal SEE Computer Science study materials
Nepal SEE Computer Science study resources

Nepal SEE Computer Science exam-day guide

Nepal SEE Computer Science · Prepare for the day ahead.

Your checklist

Admit card / exam identity document

Carry the admit card issued through your school along with a school-issued student ID if you have one. Rules on what counts as acceptable ID differ by examination centre, so confirm with your subject teacher or the school examination committee which documents are accepted before the exam day.

Two or more blue or black ballpoint pens

Practical answer sheets are handwritten. Bring at least two working pens plus one spare so a single failure does not cost writing time. Avoid gel pens that smudge when the sheet is folded.

Pencil, eraser and sharpener

A HB pencil is useful for rough work, flowcharts, truth tables and diagrams before you commit them in ink. Confirm whether rough work must be crossed out or left on a separate sheet.

Simple scientific calculator (if permitted)

Number-system conversions, binary arithmetic and logic problems usually need no calculator, but a basic non-programmable calculator helps with checking. Confirm with the provider whether calculators are allowed in your centre; do not assume.

Know your practical syllabus scope

Revise the practical skills your course lists - typically writing and debugging simple programs in a language such as QBASIC, C or Python as taught in your school, drawing flowcharts and algorithms, number-system conversion, and basic database or spreadsheet tasks. Confirm the exact language and tool set with your teacher, since schools vary.

Written program logic you can reproduce from memory

Memorise the skeleton of common programs (input, processing, output, loop, condition) and the syntax for opening files or printing output in the language your school teaches. You should be able to write a short program without notes.

Hand-drawn practice of flowcharts and truth tables

Practise drawing standard flowchart symbols (terminal, process, decision, input/output, connector) neatly by hand and completing truth tables for AND, OR, NOT, NAND, NOR and XOR. Neatness and correct symbols earn marks.

A watch or silent timekeeping method

Many centres do not have a visible clock. A plain analogue or digital watch without smart features is usually acceptable; confirm that smartwatches and phones are not allowed inside the hall.

Water bottle and light snack for after the exam

Keep these outside the hall unless the invigilator permits them. Practical sessions can run long, so plan hydration and food for before and after, not during.

Sleep and a normal breakfast

Do not stay up late the night before revising syntax. Rested recall of program structure is worth more than one more hour of cramming.

Confirm reporting time and centre location

Ask your school for the exact reporting time, gate-closing rule and centre address. Arrive early; late entry rules vary and are set by the examination authority, so confirm with the provider rather than guessing.

Plan transport and backup

Decide how you will travel and identify one backup route or person to call. Traffic and weather can delay you on exam morning.

Plan the day

72 hours before

List every practical topic your syllabus names and rate your confidence from 1 to 5. Spend most remaining time on the two weakest areas, especially the programming language your school uses and flowchart drawing.

72 hours before

Write three or four short programs by hand, without looking at notes, covering input/output, a conditional, a loop and an array or simple calculation. Then check them against your textbook and correct your own errors.

48 hours before

Practise number-system conversions (binary, decimal, octal, hexadecimal) and binary addition/subtraction on paper. Do ten conversions and check each answer by converting back.

48 hours before

Draw five flowcharts and three truth tables by hand under light time pressure. Focus on correct symbols, labelled arrows and clear decision branches.

24 hours before

Do one full timed mock: pick a past-style practical task, set a timer matching the real duration your school confirms, and complete it in one sitting without notes. Mark it yourself against the syllabus.

24 hours before

Pack your admit card, ID, pens, pencil, eraser, sharpener and watch in one bag. Place the bag by the door. Confirm reporting time and centre with your school.

24 hours before

Review only summaries: syntax skeletons, flowchart symbols, truth-table patterns and common debugging errors. Stop studying at a reasonable hour and sleep.

Morning of the exam

Eat breakfast, recheck the bag against the checklist, and leave with enough buffer to arrive well before the reporting time. Do not attempt to learn new syntax on the way.

During the test - first minutes

Read all instructions and questions before writing. Note the marks for each part and the total time, then allocate minutes per question and leave 5–10 minutes for checking.

During the test - answering

Start with the questions you are most confident about to secure marks early. For programs, write the algorithm or logic first, then the code, then a short comment or output sample if asked. For flowcharts, sketch in pencil, then finalise.

During the test - debugging and checking

If a program has an error, trace variables line by line rather than rewriting blindly. Check brackets, indentation, variable names and loop bounds. Verify number-system answers by converting back.

During the test - final minutes

Make sure every question number is attempted, rough work is clearly marked, and your name and roll number are filled in as instructed. Hand over the answer sheet only when the invigilator says so.

Rules to check

  • Carry only the admit card, ID and permitted stationery into the hall. Phones, smartwatches and any smart device must be switched off and left outside; confirm the centre's exact device policy with the provider.

  • Follow the invigilator's instructions on seating, filling in the answer sheet and the timing of the session. Do not start writing before you are told and stop immediately when time is called.

  • Ask the invigilator, not a neighbour, if a question is unclear or a page is missing. Raise your hand and wait.

  • Do not communicate with other candidates, exchange materials or look at another answer sheet during the exam. Suspected malpractice is handled under the examination authority's rules; confirm the consequences with the provider.

  • If you need to leave the hall for water or a toilet break, raise your hand and follow the invigilator's direction. Rules on breaks differ by centre, so confirm beforehand.

  • Marks are awarded for correct logic, correct syntax and clear presentation. Show your working for number-system and logic questions, because partial credit may be given for a correct method even when the final answer is wrong.

  • Write legibly in ink for final answers and use pencil only for rough work or diagrams if instructed. Ambiguous handwriting can lose marks.

  • Do not remove question papers, answer sheets or any centre material from the hall unless the invigilator explicitly permits it.