How To Pass Tu Bsc Csit Exams

Study strategy

How to pass TU BSc CSIT semester exams, the honest guide

A practical guide to passing TU BSc CSIT semester exams: what to study, in what order, and the mistakes that cost marks.

2026-07-03 | notesharu team

Most students who fail a BSc CSIT paper did not fail because the subject was too hard. They failed because they studied it in the wrong order, or they wrote correct content in a form the marker could not award marks for.

This is what actually works, in order.

Start from the paper, not the syllabus

  1. Open the last five years of the paper first. Before reading a single page of notes. All 2,766 solved questions are on the past questions page.
  2. Mark which units repeat. In most TU papers, a small number of units account for most of the marks. The syllabus treats every unit equally. The examiner does not.
  3. Rank your units by marks per hour. A unit that appears every year and takes two hours to learn beats a unit that appeared once and takes six.
  4. Only then open the notes, and only for the units you ranked.

Write answers the way they are marked

  • Match the length to the marks. A 10 mark question answered in four lines cannot score 10, no matter how correct it is. Answers on this site come at 1, 5 and 10 mark depth for exactly this reason.
  • Show every step on numericals. Method marks are awarded for the working, not the result. A correct final answer with no steps often scores less than a wrong answer with correct method.
  • Draw the diagram. In Operating Systems, Networks and DBMS, a labelled diagram is frequently worth marks on its own.
  • Define before you explain. Most theory questions carry a mark for the definition. It is the cheapest mark on the paper.
  • Do not pad. Markers do not award marks for volume, and long answers cost you time on later questions.

The mistakes that cost the most

  1. Leaving numericals for last. They take the longest and carry the most method marks. Do them while you are fresh.
  2. Studying subjects in timetable order. Study them in order of how weak you are, not in the order the exams fall.
  3. Reading solutions instead of writing them. Reading a worked numerical feels like learning and is not. Cover the solution and write it out.
  4. Ignoring the theory papers until the night before. Papers like Society and Ethics or Technical Writing are easy marks, but only if you have seen the question format once.
  5. Skipping the previous semester's core paper. Data Structures assumes C. Computer Architecture assumes Digital Logic. A gap behind you costs marks in front of you.

A realistic four week plan

WhenWhat
Weeks 4 to 3 beforePast papers for every subject. Rank units by frequency. Do not study yet.
Week 3The two subjects you are weakest in. Numericals first.
Week 2The remaining core subjects. Write full answers, timed.
Week 1Theory and lighter papers. Re-do the numericals you got wrong.
Last 2 daysOnly the repeated questions. No new material.

Adding new material in the last two days is how students lose marks on topics they already knew.

Where the degree gets hard

Semester III and Semester VI are the two that catch people out, for different reasons. Semester III has the hardest concepts, led by Data Structures. Semester VI has the heaviest volume at seven subjects and 57 units. Both need planning a month earlier than feels necessary. The semester roadmap lays out all eight semesters and where the difficulty sits.

Before the next exam

Pick your weakest paper from the full subject list, open its past questions, and find the three units that repeat most. That is your next week decided.

Put it into practice

Browse all subjects