Islamic University of Technology · B.Sc. Engg. (CSE) · AY 2017–18 onwards

The whole degree,
in plain English.

Every course in the IUT CSE syllabus, stripped of catalogue language: what it actually is, why it exists, and what you could build with it. Plus a ranked order to learn the ones that matter if you're building software right now.

8Semesters
~182Credit hours
—Courses mapped
—Build-critical
85%Attendance floor

The 20% that does 80% of the work

A four-year degree is padded with attendance, labs, and general education. If your goal is to build things rather than collect a transcript, this is the dependency order that actually matters — grouped into five blocks. Roughly 9–12 months of serious part-time study, versus four years.

How to use this. Work top to bottom. Each block assumes the one before it. Don't skip Block 1 because you already write code — Data Structures and Discrete Math are where most self-taught programmers have a hole, and everything after Block 2 quietly assumes both.

Block 1 — Foundations

≈ 12 weeks Goal: think in memory, structures, and proofs
1
CSE 4107 / 4108Structured Programming (C)

You know Python. C is the one that teaches you what Python was hiding: pointers, manual memory, the stack vs the heap, what a "string" really is. Six weeks of C makes every other language legible. Don't skip it for comfort.

2
CSE 4203Discrete Mathematics

The grammar of computer science: sets, logic, proofs, counting, graphs, recursion. This is the actual prerequisite for Algorithms, and the reason people bounce off Algorithms is almost always this gap, not the algorithms themselves.

3
CSE 4303 / 4304Data Structures

Arrays, linked lists, stacks, queues, trees, graphs, hash tables — plus the cost of each operation. The single highest-return course in the entire degree. Implement every one of them from scratch in C, then never again.

Block 2 — The Engineering Core

≈ 14 weeks Goal: design systems, not scripts
4
CSE 4301 / 4302Object Oriented Programming

Classes, inheritance, polymorphism, interfaces. Less about C++ syntax and more about where to put things so a 40-file codebase doesn't collapse. This is the vocabulary every team you hire will already speak.

5
CSE 4403 / 4404Algorithms

Divide-and-conquer, greedy, dynamic programming, graph search, and Big-O analysis. The course that separates "it works on my 10 rows" from "it works on 10 million." Also the entire content of most technical interviews.

6
CSE 4307 / 4308 / 4508Databases + SQL

Relational modelling, normalization, SQL, transactions, indexing. Nearly every product you'll build is a database with a UI stapled on. Learn normalization properly once and you'll avoid the data mess that kills v2 of most apps.

7
CSE 4851Design Patterns (elective, 8th sem — pull it forward)

Named solutions to problems you'll otherwise re-solve badly: Strategy, Observer, Factory, Adapter, Facade, State. Short course, enormous payoff. Officially final-year; there's no reason to wait.

Block 3 — How Machines Actually Work

≈ 12 weeks Goal: debug things you didn't write
8
CSE 4501 / 4502Operating Systems

Processes, threads, scheduling, deadlock, memory paging, file systems. Why your server hangs, why two threads corrupt the same variable, what "out of memory" really means. Deploying anything without this is guesswork.

9
CSE 4511 / 4512Computer Networks

TCP/IP, the layer model, IP addressing and subnets, DNS, HTTP, routing, congestion control. Every "the API is down" incident is somewhere in this course. Skip the older LAN material (token ring, FDDI) — it's history.

10
CSE 4513Software Engineering & Object-Oriented Design

Requirements, lifecycle models, UML, testing strategy, configuration management, team process. The syllabus is dated in places (heavy waterfall), but the modelling half — use cases, class and state diagrams — is exactly how you spec work for other people.

11
CSE 4510Software Development (Agile) — 0.75 cr, punches far above it

Unit testing frameworks, refactoring, build tools, iterative delivery. Tiny credit weight, but this is the day-to-day operating manual for shipping. Pair it with 4513 and treat them as one course.

Block 4 — The Math Under AI

≈ 14 weeks Goal: read an ML paper without flinching
12
Math 4341Linear Algebra

Vectors, matrices, rank, eigenvectors, SVD, projections. Machine learning is linear algebra with a loss function attached. Strang's book (already the listed text) is the single best resource in this entire syllabus.

13
Math 4441Probability & Statistics

Distributions, expectation, variance, Bayes, estimation, hypothesis testing. Needed for ML, for A/B tests, and for not being fooled by your own dashboards. The second half — confidence intervals, significance — is the business-critical part.

14
CSE 4621 / 4622Machine Learning

Supervised and unsupervised learning, regression, classification, clustering, neural networks, reinforcement learning. Broad, and the syllabus's neural-net section is pre-transformer — pair it with current material, but the fundamentals here are permanent.

15
CSE 4711 / 4712Artificial Intelligence

Search, heuristics, knowledge representation, planning, game playing. The classical-AI half of the field. Russell & Norvig is the text and it's genuinely worth owning. Ignore the LISP/PROLOG framing — the ideas transfer.

Block 5 — Shipping to the World

≈ 10 weeks Goal: run it in production, for money
16
CSE 4539 / 4635Web Programming & Web Architecture

HTML/CSS/JS, HTTP, forms, sessions and cookies, server-side rendering, database tiers. The syllabus's stack is dated (PHP, Flash, AJAX-era) — take the architecture, use a current toolchain for the code.

17
CSE 4749 / 4750Introduction to Cloud Computing

Virtualization, IaaS/PaaS/SaaS, scaling, distributed storage, map-reduce. This is where your app actually lives and where your monthly bill comes from. Directly commercial knowledge.

18
CSE 4743Cryptography & Network Security

Symmetric and public-key crypto, hashing, certificates, TLS, authentication, firewalls. You don't need to invent crypto — you need to stop misusing it. Covers exactly the mistakes that leak customer data.

19
CSE 4809 / 4810Algorithm Engineering

The graduate-level sequel to Algorithms: randomized algorithms, amortized analysis, network flow, NP-completeness, approximation. Take it when you want depth. Optional for shipping, essential for research.

20
CSE 4614Technical Report Writing

Structure, LaTeX, figures, citation, plagiarism. Undervalued at 0.75 credits. The ability to write a clear spec, a readable proposal, or a publishable paper compounds harder than almost any technical skill on this list.

What you're deliberately skipping, and the cost. Physics, Chemistry, Electronic Devices, VLSI, Digital Signal Processing, Microprocessor & Assembly, Peripherals & Interfacing. That's the hardware and electrical engineering spine. If you never touch embedded systems, robotics, or chip design, the cost is close to zero. If you do, come back for Digital Logic Design (4205) and Computer Organization (4305) first — they're the bridge.

Every course, semester by semester

Tick courses off as you learn them — progress saves in this browser. Use the filters to hide everything that isn't build-critical.

0 of 0 done

How you're actually scored

The mechanics from Part I of the syllabus — the parts that decide your transcript.

Marks per course

ComponentWeightWhat it really means
Quizzes & assignments20%Continuous. Cheap marks, easiest to lose by drifting.
Mid semester40%Half the exam weight, on half the material.
Semester final40%Cumulative. Attendance gates entry to this one.

Letter grades

GradePointsMarks
A+4.0080% and above
A3.7575 – below 80%
A−3.5070 – below 75%
B+3.2565 – below 70%
B3.0060 – below 65%
B−2.7555 – below 60%
C+2.5050 – below 55%
C2.2545 – below 50%
D2.0040 – below 45%
F0.00below 40%
The two rules that bite hardest.
1. Attendance. You need 85% of classes in every course. Below that you are barred from the semester final — the 40% you cannot recover. The Vice-Chancellor may condone 10% on documented medical grounds via the Head of Department, but that's a favour, not a right.

2. Credit maths. A theory course's credits = its weekly contact hours. A lab course's credits = half its contact hours. So a 3-hour lab is worth 1.5 credits — labs cost you double the time per credit. Budget your week accordingly.

Reading a course code

PositionMeaningExample: CSE 4107
LettersDepartment offering itCSE
1st digitProgram type (4 = B.Sc., 4 years)4
2nd digitSemester it's normally taken1 → first semester
Last 2 digitsCourse number — odd = theory, even = lab07 → theory

So CSE 4108 is the lab twin of CSE 4107. Once you see the odd/even rule, you can read the whole catalogue at a glance. Humanities, Math, Physics and Chemistry codes insert a department digit third — Math 4441 = B.Sc. · 4th semester · offered to dept 4 · course 1 (odd, theory).