The CSIT Syllabus, Explained Simply: Credit Hours, Electives & Structure
Every CSIT student hears the same set of phrases early on: "126 credit hours", "electives", "project work", "internship". Usually nobody explains what they mean until you're already a year in and wondering why one semester feels heavier than another.
This article answers that. It is about the BSc CSIT course of study as Tribhuvan University (IOST) runs it, the official curriculum that every TU-affiliated college follows. You will finish with a clear picture of how the four years are arranged, what a credit hour actually means, and when the syllabus starts letting you choose what to study.
The short version: eight semesters, four years, 126 credit hours. Almost every course is 3 credits. There are five electives spread across the later semesters, one project, and one internship. Everything else follows a steady, predictable pattern.
The BSc CSIT degree in one paragraph
BSc CSIT is a four-year, eight-semester bachelor's program run by TU's Institute of Science and Technology. The curriculum was built by following the course patterns of accredited international computer science programs. Every undergraduate has to complete 126 credit hours, made up of foundation courses, core computer science and IT courses, plus elective courses added from the second half of the degree. There is a separate exam at the end of each semester, and each semester runs for about 90 working days. That's the whole skeleton.
What a credit hour actually is
A credit hour is a measure of course size, and in TU's system it maps directly to contact time. It tells you how much classroom time a course eats out of your week, not how hard the course is.
The curriculum defines it like this:
-
A 3-credit course with theory and lab = 3 lecture hours + 3 lab hours = 6 working hours per week.
-
A 3-credit theory-only course = 3 lecture hours + 2 tutorial hours = 5 working hours per week.
So a credit is roughly one lecture hour per week across the semester, with lab or tutorial time added on top. CSIT keeps this simple in practice: every core course is 3 credits, and almost every 3-credit course carries 100 full marks. The only exceptions are the project (3 credits, in semester VII) and the internship (6 credits, the largest single course in the degree, in semester VIII).
One thing to remember: credits measure workload, not difficulty. Mathematics I and C Programming are both 3 credits. Nobody would tell you they are equally hard. When someone says a semester is "15 credits", they mean five courses, not five easy weeks.
The shape of the 126 credits
Here is the semester-by-semester credit load:
| Semester | Credits | Full marks | What's in it |
|---|---|---|---|
| I | 15 | 500 | 5 subjects: IT, programming, digital logic, maths, physics |
| II | 15 | 500 | 5 subjects: discrete maths, OOP, microprocessors, maths, statistics |
| III | 15 | 500 | 5 subjects: data structures, numerical methods, architecture, graphics, statistics |
| IV | 15 | 500 | 5 subjects: theory of computation, networks, OS, databases, AI |
| V | 18 | 600 | 5 core subjects + Elective I (your first choice) |
| VI | 18 | 600 | 5 core subjects + Elective II |
| VII | 15 | 500 | 3 core subjects + Project Work + Elective III |
| VIII | 15 | 500 | Advanced Database + Internship (6 credits) + Electives IV & V |
Add it up: 15 + 15 + 15 + 15 + 18 + 18 + 15 + 15 = 126. The pattern is easy to see: the first four semesters are a steady five-courses-per-semester run, semesters V and VI get heavier because an elective is added, and the final two semesters trade classroom load for project, internship, and your last electives.
Full marks work the same way: most semesters total 500, semesters V and VI total 600, and the internship (200 full marks) is what pushes semester VIII to 500 despite only three taught courses.
Semester by semester: what you actually study
This is the map. Every course below is 3 credits unless stated otherwise. Where codes appear, they are the ones EasyCSIT uses on its subject pages (they follow the TU curriculum closely).
| Semester | Courses |
|---|---|
| I (15 cr) | CSC114 Introduction to Information Technology · CSC115 C Programming · CSC116 Digital Logic · MTH117 Mathematics I · PHY118 Physics |
| II (15 cr) | CSC165 Discrete Structure · CSC166 Object Oriented Programming · CSC167 Microprocessor · MTH168 Mathematics II · STA169 Statistics I |
| III (15 cr) | CSC211 Data Structures and Algorithms · CSC212 Numerical Method · CSC213 Computer Architecture · CSC214 Computer Graphics · STA215 Statistics II |
| IV (15 cr) | CSC262 Theory of Computation · CSC263 Computer Networks · CSC264 Operating Systems · CSC265 Database Management System · CSC266 Artificial Intelligence |
| V (18 cr) | CSC325 Design and Analysis of Algorithms · CSC326 System Analysis and Design · CSC327 Cryptography · CSC328 Simulation and Modeling · CSC329 Web Technology · Elective I |
| VI (18 cr) | CSC375 Software Engineering · CSC376 Compiler Design and Construction · CSC377 E-Governance · CSC378 NET Centric Computing · CSC379 Technical Writing · Elective II |
| VII (15 cr) | CSC409 Advanced Java Programming · CSC410 Data Warehousing and Data Mining · MGT411 Principles of Management · Project Work (3 cr) · Elective III |
| VIII (15 cr) | CSC475 Advanced Database · Internship (6 cr) · Elective IV · Elective V |
Read it as a story, not a list. The first two semesters build foundations: programming, maths, and how computers work. Semesters III and IV are the core of the degree: data structures and algorithms, operating systems, databases, networks: the subjects every CS student in every country studies. Semesters V and VI start applying that core to real software (web, compilers, software engineering, security) and introduce electives. Semesters VII and VIII are the finish line: a project, an internship, and your final electives.
Theory, lab, and what that means for your week
Nearly every CSIT course is Theory + Lab. That includes surprising ones like Physics and Statistics, which carry lab components too. Only a handful are theory-only: Mathematics I and II, Technical Writing, Principles of Management, and the management-oriented electives.
The marks pattern follows the nature of the course:
-
Theory + Lab (most courses): the written exam is 60 marks, and the remaining 40 marks are practical, made up of internal marking, attendance and lab reports. You need at least 24 marks in the 60-mark written exam to pass it, and the practical components carry their own minimums too.
-
Theory only: the same 60-mark written exam, with the other 40 marks coming from internal assessment.
-
Project Work: 100 full marks (80 + 20), assessed through your proposal, mid-term progress, and a final report and defense, not a written exam.
-
Internship: 200 full marks (160 + 40), assessed through your internship report and a final defense.
Electives: the part you get to choose
Electives are courses you pick from a list, rather than courses everyone takes. CSIT has five electives (one in each of semesters V, VI and VII, and two in semester VIII), at 3 credits each, for 15 credits total. That is more than ten percent of your degree; these are the courses where the syllabus is shaped around your interest instead of the other way around.
The curriculum fixes a list of options for each semester, and the college you study at decides which of those it can actually run. So treat the lists below as the full menu, and confirm with your campus which ones are offered in your year.
| When | You take | Options given by the curriculum |
|---|---|---|
| Semester V (Elective I) | 1 of 6 | Multimedia Computing (CSC319); Wireless Networking; Image Processing (CSC321); Knowledge Management; Society and Ethics in Information Technology; Microprocessor Based Design |
| Semester VI (Elective II) | 1 of 6 | Applied Logic; E-commerce; Automation and Robotics; Neural Networks; Computer Hardware Design; Cognitive Science |
| Semester VII (Elective III) | 1 of 6 | Information Retrieval; Database Administration; Software Project Management; Network Security; Digital System Design; International Marketing |
| Semester VIII (Electives IV & V) | 2 of 12 | Advanced Networking with IPv6; Distributed Networking; Game Technology; Distributed and Object-Oriented Database; Introduction to Cloud Computing; Geographical Information System; Decision Support System and Expert System; Mobile Application Development; Real Time Systems; Network and System Administration; Embedded Systems Programming; International Business Management |
How to think about choosing:
-
Pick by direction, not by the rumour of which is easy. These courses show up on your transcript and in interviews. If you want to work on mobile apps, Mobile Application Development and E-commerce beat a random pick. Interested in systems? Network and System Administration, Database Administration, or Network Security.
-
Your campus is the real list. The curriculum lists twelve options for semester VIII; a single campus will not run all of them. Ask seniors and the department what actually opens, and plan around that.
-
Combos matter. Your five electives can tell a coherent story (e.g., databases + cloud + distributed systems) or they can be five unconnected subjects. The syllabus lets you build a direction; it does not force one.
Project work and internship: where theory meets real work
These two courses do not look like the rest, because they are not taught like the rest. They are the closest the degree comes to work experience, and they are the two things that most often end up on a student's CV.
Project Work (semester VII, 3 credits). You develop a real application or system, in a group of at most three, working through analysis, design, implementation, and testing. There are three checkpoints built into the semester: a proposal you submit and present around the 3rd–4th week, a mid-term progress report around the 10th–11th week, and a final submission and defense: a viva and live demonstration in front of an evaluation committee that includes an external examiner from the university. Full marks split 80 external / 20 internal.
Internship (semester VIII, 6 credits). The biggest single course in the degree. It is an individual placement of at least 180 hours, or ten weeks, usually starting around the third week of the semester, at a software or hardware company, a telecom, an ISP, or a financial or health organisation. You get a mentor at the organisation and a supervisor at your campus, and you submit a report plus a final defense (160 external / 40 internal marks).
Two honest notes. First, the internship is individual: you cannot hide in a group, so start looking for a host organisation early. Second, both courses reward students who treat them as real work. A project you actually built and can talk about, and an internship report you can stand behind, are worth far more on a CV than the theory courses you barely passed.
How to use the structure instead of just reading it
Now that the shape is clear, here is how to make it useful:
- Count credits, not subjects. 15 credits is five courses; 18 is six. When you see a 15-credit semester, that is normal load, not a light week.
- Spread the hard subjects. Since credits do not measure difficulty, do not assume two semesters of 15 credits are equally heavy. If you know (from seniors, or from how a subject sits with you) that one course will eat your time, balance it against lighter ones when you plan group projects and lab submissions.
- Decide your elective direction by semester IV. The choices start in semester V. By the time you reach them, you should know roughly whether you lean web/mobile, systems, data, or management, which makes choosing from the lists fast and cuts the "easy elective" trap.
- Start the project proposal early. The rules put the proposal submission in the 3rd–4th week of semester VII. Students who treat that deadline as real get most of the semester to build; the ones who drift into it late end up defending whatever they can throw together in the last weeks.
- If you fail a course, the structure does not change. Backlogs are about retaking and passing exams, not about the layout of semesters. We cover how marks, pass thresholds and backlogs actually work in a separate article.
Where EasyCSIT fits
Because the syllabus is fixed by TU and shared across all affiliated colleges, the structure above is exactly what EasyCSIT is organised around. The site has a page for every semester from 1 to 8, and every subject has its own hub with Videos, Notes, Syllabus, Question Papers, and Discussions. The Syllabus tab of each subject shows the official course details (the units, the hour allocation, the credit hours, and whether the course is theory or theory + lab), so you are always looking at the syllabus the exam is based on, not a summary that drifted from it.
Start at your semester page or go straight to a subject, for example C Programming, and open its Syllabus tab to see exactly what the course covers. Everything is free.
What can change
This article describes the TU course of study that has been effective since academic year 2079, and it was checked in October 2026. Curricula do get revised. If TU issues a new course of study, the official document wins over anything written here. Two honest notes. First, where subject codes appear, they are the ones EasyCSIT uses on its subject pages, from the platform's syllabus data (which follows the TU curriculum). The official PDF itself does not use a single consistent code set. Advanced Java Programming, for example, appears as CSC409 in one section of the document and CSC419 in another, and unofficial sites add more variations. So treat course titles as the reliable identifier and codes as the everyday handle. Second, always confirm the elective list for your year at your own campus, since what is offered varies by college.