BSEB Inter Computer Science

In four parts: a descriptive written theory paper containing very short, short and long-answer questions; a practical laboratory examination in the computer lab; a viva voce conducted with that practical; and internal assessment or project work graded by your school. BSEB publishes the current paper pattern, marks distribution and duration in its official notification, so check that rather than a coaching handout.

Moderate for a well-prepared student. Most of the paper rewards accurate definitions, labelled diagrams and stepwise explanations rather than clever problem-solving. The parts that separate candidates are number-system conversions, dry-running C code on paper and writing correct SQL queries by hand. If you can produce code and queries without an IDE, the paper feels routine.

C. Data types, operators, control structures, functions, arrays, strings, pointers, structures and file handling are all taught and examined in C. Practise writing complete programs on paper, including header files, main(), declarations and output statements, because the theory paper gives you no compiler to hide syntax errors.

BSEB runs a compartmental examination for candidates who fail a small number of subjects, with the application window announced after results are declared. Eligibility, the number of permitted attempts and the fee are revised from session to session, so confirm the current procedure on the official BSEB website or with your school's examination coordinator before planning a retake.

Those figures are set by BSEB for each examination session and printed on the question paper itself. They are not stable across years, which is why this page does not quote a count or a duration. Get the current pattern from the official BSEB notification, your admit card instructions or your subject teacher.

Start with computer fundamentals, number systems and Boolean logic: they are quick, heavily scoring and underpin later topics. Move to C, because data structures build directly on arrays, pointers and functions. Then take DBMS and SQL, followed by networking and web technology, which are largely descriptive and can be consolidated closer to the exam. Update the practical file throughout.

Use a one-line definition, then a labelled diagram or comparison table where the topic allows it, then a worked example or short code fragment, then advantages and limitations. Examiners award marks point by point, so numbered headings and short paragraphs score better than dense prose. Attempt every sub-part of a multi-part question; a partial answer still earns partial credit.

Leaving the practical and project file until the final week, never writing C programs or SQL queries by hand, confusing DELETE with DROP or WHERE with HAVING, skipping number-system conversion practice, and leaving long-answer questions blank instead of writing a definition and a diagram. These are preparation habits rather than ability problems, which means they are fixable.

Questions come from your own practical file and project: why you chose a particular loop, what a pointer actually holds, the difference between a stack and a queue, what a primary key enforces, how your HTML page links to a stylesheet. Be ready to explain your own code line by line and to name the software you used. An honest "I don't know" beats an invented answer.