Year 1 Semester 1 IT at SLIIT: Modules, Study Routine and How to Prepare
The first semester sets the tone for your whole degree. The modules are not the hardest you will take, but the jump from school-style learning to university pace catches many students out. This guide explains what each module is really about and how to build a routine that keeps you ahead instead of catching up.
1. The four modules
Module names and codes can change between intakes, so check your own timetable. These are the modules Study Hub organises for Year 1 Semester 1 IT.
Introduction to Programming (IT1120)
Your first Java module: variables, data types, operators, selection, loops, arrays and methods. It is the most practical module of the semester, and the only way to get good is to write code yourself every week. Watching tutorials without typing along gives a false sense of progress.
Mathematics for Computing (IT1130)
Number systems and base conversion, Boolean algebra and logic gates, sets, functions and relations, matrices, partial fractions and an introduction to derivatives. It rewards steady practice more than last-minute cramming: do a few problems after every lecture while the method is fresh.
Fundamentals of Computing (IT1140)
How computers actually work: domains of computing, computer architecture, data representation, digital logic and processor components, along with practical lab skills. Many questions are conceptual, so make short notes in your own words and test yourself on definitions and diagrams.
Data Communication & Networks (IE1030)
Protocol architecture (OSI and TCP/IP models), the physical layer and transmission media, the link layer, the network layer and IP addressing. Draw the layer models until you can sketch them from memory, and practise subnetting and addressing calculations; they appear often and are easy marks once understood.
2. A weekly routine that works
Aim for a routine you can actually keep. Two focused hours on most days beats one exhausting all-nighter.
| When | What to do |
|---|---|
| Same day as a lecture | 20–30 minutes reviewing the slides and writing a one-page summary. |
| Twice a week | Programming practice: rewrite lab and lecture examples, then change them. |
| Twice a week | Maths problems: 5–10 questions on the latest topic. |
| Weekend | One lesson quiz per module to check what actually stuck. |
| Every Sunday | Plan the coming week: deadlines, lab tests and quizzes. |
3. Mids, labs and finals
Lab tests check that you can produce working code or complete practical tasks under time pressure. Practise in the same conditions: a timer, no copy-paste and no notes, unless the test allows them.
Mid exams usually cover the first half of the lessons. Start practice papers at least two weeks early, and treat every wrong answer as a topic to revise, not just a question to memorise.
Final exams cover the full syllabus and carry the most weight. If you kept summaries and a mistake log through the semester, final revision becomes a matter of re-reading and practising instead of learning from scratch.
4. Habits that make the difference
- Keep a mistake log for every module. Reviewing your own errors is the highest-value revision there is.
- Use active recall: close the notes and explain the topic out loud, or answer questions without looking.
- Study with one or two serious friends. Explaining a concept to someone else shows you whether you really understand it.
- Track your marks as they come in, so you always know where your GPA stands and which module needs attention.
- Sleep before exams. Memory consolidates during sleep; an all-nighter usually costs more than it gains.