Skip to content

Specialisation

Software Engineering & Development

Build software other people can trust, extend and keep running for years.

Writing something that works once is the easy part. This track is about the harder problem: designing systems that survive changing requirements, new team members and years of maintenance — from problem definition through architecture, testing, release and operations.

What you learn

You work in teams on codebases you did not start, under review. Architecture, design patterns, automated testing and delivery pipelines are taught as everyday practice rather than theory.

  • 01Requirements, domain modelling and architecture decisions
  • 02Design patterns and refactoring legacy code
  • 03Automated testing, CI/CD and release engineering
  • 04Web, mobile and cloud delivery, plus product management basics

The studio model

From the fifth semester the track runs as a studio: a real client brief, a fixed release date, code review by lecturers who ship software professionally, and a retrospective at the end.

After graduation

Where graduates go

  • Software engineer (backend, frontend, mobile)
  • QA / automation engineer
  • DevOps or platform engineer
  • Product or technical lead

Interested in this track?

You do not have to decide now — the choice is made at the end of semester four.