Skip to content Skip to a section

💻Curriculum & Skills

Computer Science · Algorithms, systems and software — how machines are made to reason, store and communicate.

At a glance
Score intensity

Darker cells mean a higher score for this topic on that metric.

Last reviewed Sources & creditsMedia creditsMethodology

Quick answers

How long does a typical Computer Science degree take?

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.

Is Computer Science mostly theoretical or practical?

Expect both. Foundations lean theoretical; later years push labs, project studios and code reviews. The balance depends on accreditation and department culture.

Do I need strong mathematics?

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.

How selective is entry?

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.

What communities should I join?

Start with the departmental society, then look for national student chapters and one serious online forum where practitioners share primary sources rather than memes.

Are the "voices" real reviews?

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.

Core courses

Discrete mathematics

1–2

Discrete mathematics trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.

Data structures

1–2

Data structures trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.

Algorithms

1–2

Algorithms trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.

Computer architecture

2–3

Computer architecture trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.

Operating systems

2–3

Operating systems trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.

Databases

2–3

Databases trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.

Networks

3–4

Networks trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.

Software engineering

3–4

Software engineering trains the habits computer science depends on — not trivia for exams, but reusable technique for later studios, labs or clinics.

Common tracks

Systems

A systems emphasis usually appears after foundations, when students choose seminars, labs or studios that deepen one problem family inside computer science.

AI & ML

A ai & ml emphasis usually appears after foundations, when students choose seminars, labs or studios that deepen one problem family inside computer science.

Security

A security emphasis usually appears after foundations, when students choose seminars, labs or studios that deepen one problem family inside computer science.

Human–computer interaction

A human–computer interaction emphasis usually appears after foundations, when students choose seminars, labs or studios that deepen one problem family inside computer science.

Skill map

948890786270
Algorithmic thinking
94
Systems design
88
Debugging
90
Math modelling
78
Collaboration
62
Writing specs
70

Algorithmic thinking

Algorithmic thinking is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.

Systems design

Systems design is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.

Debugging

Debugging is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.

Math modelling

Math modelling is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.

Collaboration

Collaboration is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.

Writing specs

Writing specs is practised weekly in computer science programmes; the percentage is relative strength among skills on this page, not a grade.

How you learn

Lectures & readings

Large-group framing plus primary texts or problem sets that define the week's vocabulary.

Labs / studios / clinics

Supervised practice where mistakes are expected and feedback is specific.

Seminars

Small-group argument; silence is expensive because the group notices.

Capstone / thesis

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.

Keep exploring

More in STEM & Engineering