BSEH SS Computer Science exam-day guide
BSEH SS Computer Science · Prepare for the day ahead.
Your checklist
Admit card or hall ticket
Print or download the admit card issued for your BSEH SS Computer Science practical. Carry more than one copy if the board permits; keep one in your bag as a spare. Confirm the exact document name and whether a printed copy is mandatory with your school coordinator or the provider, since formats change between sessions.
Valid photo ID
Bring the original photo identification your school or board requires for practical exams. A school-issued ID card is commonly accepted, but the accepted list can vary by centre. Confirm with the provider which originals are accepted and whether photocopies are allowed.
School uniform or prescribed dress
Most Haryana board exam centres expect candidates in school uniform for practicals. If your school has a different instruction, follow the written notice from your coordinator rather than guessing.
Stationery kit
Carry two blue or black ballpoint pens, a pencil, an eraser, a sharpener, and a scale. For Computer Science practicals you may also need rough sheets for dry runs of code or SQL. Do not rely on borrowing from neighbours.
Practical file, record book, and project report
Bring your completed practical record and any project documentation your school has instructed you to submit. Ensure your name, roll number, and class are written on the cover. Confirm the required contents and submission format with your subject teacher in advance.
Know your syllabus practical components
Revise the practical list your school follows: typically Python programming with file handling, a small SQL section, and a project demonstration. Ask your teacher which textbook or reference the school uses so your preparation matches the assessed tasks.
Practise writing code on paper
During the practical you may be asked to write or explain code before typing it. Practise writing short, correct programs by hand: input and output, conditionals, loops, functions, and file read/write. Check indentation and syntax mentally as you write.
Rehearse your project demo aloud
Be ready to explain what your project does, which data structures or files it uses, and how you tested it. Prepare to answer two or three viva questions on your own code, not on general theory.
Report on time, well before the slot
Reach the centre early so you can complete any verification and settle in. Exact reporting time is set by the centre; confirm it with your coordinator rather than assuming.
Water bottle and a light snack
Practical sessions can run long with batches. Carry water and something simple to eat if the centre allows it. Confirm any restrictions on bringing items into the lab with your coordinator.
No prohibited electronic devices
Leave smartphones, smartwatches, and any storage devices out of the lab unless the examiner explicitly permits them. If you need a calculator, ask beforehand whether it is allowed for the practical.
Backup of your project files
If your project is submitted digitally, keep a copy on a pen drive and, where allowed, in your school account. Ask your teacher whether the centre provides machines or expects you to bring your own media, since lab setups differ.
Plan the day
List every practical topic your school covers and rate your confidence from 1 to 5. Spend the remaining time on the two weakest areas. Write at least one complete program by hand each day and trace its output line by line.
Finish and proofread your practical file and project report. Check that every program has a problem statement, code, and sample output, and that page numbers and the index match. Get your teacher to confirm the submission format.
Run your project once end to end on the machine you will use, or on a similar setup. Fix any path or file-location issues now, not in the lab. Note the exact steps to start it.
Do a timed mock practical: pick two programs and one SQL query, write them in 30 minutes, then explain each aloud in two minutes as if to an examiner. This trains both coding and viva fluency.
Pack your bag: admit card, ID, stationery, practical file, project report, and any permitted media. Lay out your uniform. Check the reporting time and travel route with your coordinator.
Do a light revision only: syntax for file handling, common SQL commands, and the main points of your project. Sleep early. Cramming new topics the night before tends to hurt accuracy in the lab.
Eat a proper meal, arrive early, and re-read your project summary once. Keep the mood calm; do not attempt to learn new programs in the final hour.
Read the full question or task sheet before starting. Write code in small steps, test each part, and keep rough work tidy. If a program fails, debug methodically rather than rewriting everything.
For the viva, answer in short clear sentences. If you do not know something, say so and explain how you would find out. Examiners generally value honest reasoning over bluffing.
Watch the clock and reserve the last few minutes to save files, check output, and confirm your name and roll number are on everything you submit.
Rules to check
Carry only the documents and items the centre permits. Ask your coordinator in advance about phones, smartwatches, calculators, and pen drives, because lab rules vary and an unapproved device can be treated as misconduct.
Follow the examiner's instructions at all times inside the lab. Do not touch another candidate's machine, files, or answer sheet, and do not share code or answers during the session.
Keep your admit card and ID with you until the session ends. If an invigilator asks for verification, cooperate immediately and quietly.
Ask before leaving the lab for water or a break. Movement during a practical is usually restricted; confirm the centre's break policy with the provider rather than assuming you can step out.
Submit exactly what is asked: your written answers, saved program files, and practical record as directed. Confirm with the examiner that your files are saved and your record is received before you leave.
Marks for the practical are awarded by the examiner against the board's scheme, which typically covers program writing, execution or output, the practical record, and the viva. The exact split and pass requirements should be confirmed with the provider or your teacher.
If something goes wrong, such as a machine failure or a missing document, tell the examiner or your coordinator immediately. Do not try to fix equipment yourself or borrow another candidate's work.