CHSE Odisha Elective Computer Science

Expect a written paper with an objective or very short answer section followed by short-answer and descriptive questions, including program-writing, tracing and SQL/HTML items. It is answered on paper, not on a computer. The Council publishes the current section-wise mark distribution and duration on its site; check that before you build a revision plan.

Moderate. Fundamentals, number systems and HTML are usually scored well. Candidates lose marks in C pointers and file handling, in dry-running loops, and in stack/queue operations written by hand. If you practise writing complete programs on paper, the difficulty drops sharply.

The Council sets the compartmental, improvement and repeat rules and revises them from time to time, so the accurate answer changes by session. Read the current notification on the official CHSE Odisha website, and ask your school's examination coordinator, who receives the circulars directly.

Duration is fixed by the Council for each session and is printed on the admit card and the official timetable. Since the figure is not constant across years, do not plan around a rumoured number: confirm it from the Council's site, then practise full papers under that exact timing.

Start with fundamentals and number systems, since Boolean algebra and logic gates build on them. Then commit most of your time to C, because it carries the largest weight and reappears inside data structures. Take DBMS/SQL, networks and HTML next, and revise data structures last, once you can already write C code comfortably.

Incomplete programs with no headers or declarations, forgetting to initialise pointers, confusing pre- and post-increment, writing SQL without a WHERE clause, mixing up stack and queue operations, and skipping the lab record. Handwriting quality and labelled diagrams also matter, because examiners mark what they can read.

No advanced mathematics is needed. Number-system conversion, binary arithmetic, Boolean simplification using K-maps, and basic counting for complexity are the mathematical parts, and all are procedural. Regular short practice beats long study sessions; most errors come from carelessness, not conceptual gaps.

It is assessed separately from theory and usually involves writing and running programs, a viva, and evaluation of your lab record and project work, alongside the school's internal assessment. Your school conducts preparatory practicals; keep the record written up as you go rather than filling it in the week before.

C, as prescribed by the syllabus. Do not answer in C++, Java or Python even if you know them better, because syntax-specific marks are awarded for C constructs such as scanf/printf, stdio.h, pointer notation and file modes. Practise the exact C syntax your textbook uses.