CHSE Odisha Elective Computer Science exam-day guide
CHSE Odisha Elective Computer Science · Prepare for the day ahead.
Your checklist
Admit card / hall ticket
Carry the original admit card issued through your school plus one photocopy kept separately in your bag. Without it you may be denied entry; if it is lost, contact your school head immediately rather than arriving at the centre without it.
School identity card and one photo ID
Bring your school ID card and, if issued, an Aadhaar or other government photo ID. Invigilators may ask for a second identifier during verification; confirm with your school which documents the centre expects.
Practical record book / laboratory file
Bring the completed and teacher-signed practical record with all indexed programs, output screenshots or printouts, and SQL query sheets. Unsigned or incomplete records are commonly penalised during evaluation, so get signatures before the exam day.
Project report or case-study file (if your school assigned one)
Some schools assign a mini project or case study with source code and output. Carry the bound copy and the source file on a pen drive only if your centre allows it; confirm with your teacher whether external storage is permitted at the centre. (needs_review)
Blue or black ballpoint pens and a pencil, eraser, sharpener, scale
Use blue or black ink for written answers and rough work as instructed. Carry a spare pen and a spare pencil; do not rely on borrowing from neighbours, since talking during the exam can be treated as malpractice.
Written program sheets or rough paper approved by the centre
Most centres supply answer sheets and rough sheets. If your school has told you to bring your own, carry only unmarked blank paper; loose notes, printed code listings or textbooks inside the hall are usually treated as unfair means.
Printed or copied syllabus and practical question pattern
Keep a one-page summary of the practical syllabus (program categories and SQL topics) in your bag for last-minute revision outside the hall, not inside it. Confirm the exact practical question pattern with your teacher, since it varies by centre.
Water bottle and a light snack for the waiting period
Practical batches often wait a long time before their turn. Carry water in a transparent bottle and something small to eat outside the hall; keep it in your bag, not at the machine or desk.
Centre location, reporting time and batch number
Confirm with your school the exact centre address, your batch, and the reporting time at least two days ahead. Visit or map the route in advance so you are not deciding logistics on the morning of the exam.
Knowledge of your roll number and registration details
Memorise or note your roll number, registration number and subject code; you will write them on answer sheets, output printouts and the record file. A small chit with these numbers kept in your pocket saves time and errors.
Any prescribed stationery or toolchain instructions from your school
If the centre uses a specific editor, IDE or DBMS, your teacher may ask you to practise on it beforehand. Confirm with the provider which environment will be available, since you may not install or change software during the exam. (needs_review)
Plan the day
List every program category in your practical syllabus and write one program from each from memory, without looking at your record book. For each, note the input, expected output and the one line you most often get wrong. Spend the last session on SQL queries if your syllabus includes a database component, since query syntax errors are easy to make under time pressure.
Complete and get signed anything still pending in your record book: index page, teacher signature against each program, output listings and the viva question list. Photocopy or photograph the index page so you can revise the program list while waiting at the centre.
Do one timed rehearsal: pick two unseen problems, write the code on paper in about fifteen minutes, then type and run them on a computer in another fifteen. Practise producing clean output and being able to explain each line aloud, since viva questions usually start from your own submitted code.
Prepare your viva answers for standard areas: the difference between compiled and interpreted execution, data types and type conversion, control-flow constructs, functions and parameters, list and string operations, file handling, and basic database concepts such as keys, primary key versus foreign key, and the SELECT with WHERE, ORDER BY and aggregate functions.
Pack your bag: admit card, ID, pens, pencil, eraser, scale, signed record book and project file. Keep everything in one envelope or folder so nothing is searched for in the morning. Re-confirm the reporting time and centre with a classmate or your teacher.
Revise only from your own record book and one-page syllabus summary. Do not attempt new topics. Read each program's logic and write down the three most common runtime errors you have made - indentation, unclosed brackets, wrong data type, off-by-one indexing - so you actively avoid them.
Sleep at a normal hour. Practical exams reward careful typing and calm debugging more than last-minute memorisation, and a tired candidate makes syntax errors that cost more marks than an unknown topic.
Eat a proper breakfast, carry water, and reach the centre well before the reporting time so you can absorb delays without stress. Keep your bag light and do not carry textbooks, printed code or mobile phones into the hall unless the centre explicitly permits them.
Read the whole question paper or problem set before choosing. Pick the problem you can implement most completely rather than the one that looks most impressive; a working simple program with correct output scores better than an ambitious half-finished one. Write the algorithm or rough logic on the rough sheet first, then code.
Type carefully and run the program with a small, clear set of test inputs, including one boundary case. Print or write the output as instructed and label it with your roll number. Keep a short comment or note explaining the logic, which also helps you in the viva.
In the viva, answer briefly and honestly. If you do not know something, say so and reason from what you do know rather than guessing wildly. If you get stuck during programming, ask the invigilator only procedural questions, such as how to use the printer or which drive to save to; do not ask for help with the solution.
Rules to check
Carry the original admit card and produce it on demand. If you have lost it, inform your school immediately; do not enter the centre on someone else's documents or on a promise to produce it later. Confirm the exact documentary requirement with your school or the provider. (needs_review)
Do not carry mobile phones, smart watches or any communication device into the examination hall unless the centre explicitly permits it. Even a switched-off phone in your pocket can be treated as unfair means, so leave it with a parent or outside the hall.
Do not talk to, signal to or exchange material with other candidates once the exam begins, and do not look at another candidate's screen or sheet. Sharing a program is malpractice even if the other candidate does not use it.
Use only the answer sheets, stationery and storage locations the invigilator specifies, and label every printout or output sheet with your roll number as instructed. Unlabelled work may not be credited to you.
Leave the hall only with the invigilator's permission; practical exams often run in batches with supervised breaks, so ask before stepping out. Confirm the centre's break and toilet policy when you arrive rather than assuming. (needs_review)
Marks are awarded for a working program with correct output, a properly completed and signed record file, and a reasonable viva performance. Do not neglect the record file assuming the program alone will carry your score; clarify the exact mark distribution for each component with your teacher. (needs_review)
Follow the centre's instructions on rebooting or re-running a program if the system fails. Report a hardware or software fault immediately and let the invigilator decide on extra time or a change of system; do not attempt to repair or reconfigure the machine yourself.