Discrete mathematics
1–2Discrete mathematics trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.
Computer Science · Algorithms, systems and software — how machines are made to reason, store and communicate.
Darker cells mean a higher score for this topic on that metric.
LessMore
Last reviewed Sources & creditsMedia creditsMethodology
Most bachelor pathways run about 4 years of full-time study, though professionally accredited or longer first degrees can exceed that, and some systems split into 3+2 Bologna structures.
Expect both. Foundations lean theoretical; later years push labs, project studios and code reviews. The balance depends on accreditation and department culture.
Math intensity on this site is scored 80/100 relative to other majors. That is a signal, not a gate — check the specific programme's calculus and statistics requirements.
Selectivity here is 78/100 relative to the other majors catalogued — a composite of typical grade barriers and competition, not a single exam cut-off.
Start with the departmental society, then look for national student chapters and one serious online forum where practitioners share primary sources rather than memes.
They are editorial composites grounded in common, checkable student and alumni patterns — attributed by role and place, not anonymous star ratings or fabricated celebrities.
A computer science curriculum is a sequence, not a shopping list. Early courses build shared vocabulary; middle years introduce methods; the final stretch demands a project that can fail in public.
Elective freedom varies: some systems lock professional accreditation hours; others allow wide minors. The courses below are the common spine, not every university's catalogue.
Discrete mathematics trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.
Data structures trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.
Algorithms trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.
Computer architecture trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.
Operating systems trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.
Databases trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.
Networks trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.
Software engineering trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.
A systems emphasis usually appears after foundations, when students choose seminars, labs or studios that deepen one problem family inside computer science.
A ai & ml emphasis usually appears after foundations, when students choose seminars, labs or studios that deepen one problem family inside computer science.
A security emphasis usually appears after foundations, when students choose seminars, labs or studios that deepen one problem family inside computer science.
A human–computer interaction emphasis usually appears after foundations, when students choose seminars, labs or studios that deepen one problem family inside computer science.
Algorithmic thinking is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.
Systems design is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.
Debugging is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.
Math modelling is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.
Collaboration is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.
Writing specs is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.
Large-group framing plus primary texts or problem sets that define the week's vocabulary.
Supervised practice where mistakes are expected and feedback is specific.
Small-group argument; silence is expensive because the group notices.
A public synthesis — defence, exhibition, clinic portfolio or engineered prototype.
Treat the catalogue as a map of practised skills, not a brand promise. The department that grades hard and returns work fast usually teaches more than the one that advertises prestige alone.
Circuits, fields and signals — powering, sensing and communicating the physical world.
Employability 88 🔧Forces, materials and machines — designing things that move, bear load and last.
Employability 86 🌉Infrastructure that societies stand on — bridges, water, roads, cities and codes.
Employability 84 ⚗️Turning reactions into plants — scale, safety and efficiency from molecule to factory.
Employability 82 🛰️Flight in air and vacuum — structures, propulsion, guidance and certification.
Employability 76 📊Statistics, computing and domain sense — turning messy data into decisions that hold up.
Employability 92 🧮Proof, structure and abstraction — the language that other sciences borrow.
Employability 70 ⚛️Matter, energy, space and time — from lab benches to the edge of the observable.
Employability 68 🧪Molecules and reactions — how substances change, bind and are made safely.
Employability 72 📉Uncertainty made usable — design, inference and the ethics of claiming a pattern is real.
Employability 88