The ApprenticeRouteDTS

Inside the course: what you actually study

Prospectuses describe DTS in outcomes ("industry-relevant skills"). This page is the concrete version: the actual module map of the four-year programme I completed, lightly genericised, with honest notes on what each part was like.

Two caveats. This is one university's programme — every provider maps the same ST0119 standard onto its own modules, so treat this as a representative example, not a syllabus you'll receive. And I don't name my university or employer anywhere on this site, so module names here are the generic versions of what mine were called.

How the study actually happens

My programme ran on a residential block model: normal weeks were full-time work with study wrapped around the job, punctuated by intensive weeks on campus — lectures, labs and group work, staying in student accommodation. Other universities do day release (one day a week on campus) or mostly-online delivery. The funding rules guarantee the study time either way: for this standard that's a minimum of 1,022 off-the-job training hours across the programme, which in practice feels like roughly a day a week plus the block weeks.

Year 1 — Foundations

Learning to program from zero alongside starting the job. Python, SQL and the web, plus the professional-skills groundwork that later feeds the portfolio.

Business Organisation and Professional Skills

How organisations actually work, and how to operate inside one

Organisational structures, business processes, professional communication and workplace conduct. Sounds soft next to the programming modules, but it lands in your first months of full-time work — when it is suddenly, practically relevant. Assessed through case studies, presentations and written assignments, including group project work.

Web Programming and Information Architecture

First contact with HTML, CSS and JavaScript

Building and structuring real web pages: markup, styling, client-side JavaScript and how to organise information so people can find it. Assessed through practical web projects that become the first entries in a growing portfolio of work.

  • HTML
  • CSS
  • JavaScript

Information and Data

Relational databases and SQL, properly

Database design and normalisation, entity-relationship modelling, then a lot of SQL — joins, aggregations, stored procedures — on a full SQL Server instance. The assessment is designing and implementing a complete database from a realistic scenario. One of the most directly job-useful modules of the whole degree.

  • SQL
  • SQL Server
  • SSMS

System Development 1

Python programming fundamentals

The first programming module: Python syntax, data structures, file handling and algorithmic thinking, taught through progressive hands-on exercises. For a chunk of the cohort this is their first line of code ever; the module assumes nothing and builds quickly. Assessed by practical programming assignments.

  • Python

Reflective Practice

Writing about your own development — the portfolio habit starts here

Reflective writing about what you are learning at work and how it connects to the academic side. Easy to dismiss at the time, but this is where you learn the evidence-collection habit that the end-point assessment portfolio depends on three years later. Assessed by reflective reports and development documentation.

Year 2 — Building depth

From writing code to building software: object-oriented programming, testing, a first web framework, and the project-management vocabulary the workplace runs on.

Programming and Software Development

From scripts to structured software

Advanced programming concepts on top of the Year 1 foundations: code organisation, software design, debugging discipline and version control with Git. The bridge between writing code that runs and writing code someone else can maintain.

  • Python
  • Git

Systems Fundamentals

What is actually happening under the hood

Computer architecture, operating systems, memory, processes, file systems and networking basics. Mostly exam-assessed theory, and the module people underestimate — it quietly pays off later in debugging, performance work and the security module.

IT Project Management

Agile, Scrum, Kanban, risk and estimation

Project planning, Agile frameworks, risk management and stakeholder communication. Unusually for a university module, most of the cohort are living this at work in parallel — sprint boards and stand-ups stop being abstract very fast. Assessed through planning exercises and case-study analysis.

System Development 2

OOP, unit testing and a first full web application — the hardest module so far

Object-oriented Python, design patterns, unit testing with pytest, REST APIs and a first real web framework (Flask), plus professional documentation. The coursework is a complete database-backed web application with a test suite, linted code and generated docs — the first time the degree demands an end-to-end, professional-standard build. Widely considered the toughest and most valuable module of the first two years.

  • Python
  • Flask
  • pytest
  • SQLite
  • Sphinx
  • Git

Enterprise Computing

How big organisations run technology at scale

Enterprise architectures, system integration, middleware, ERP, cloud concepts and the security considerations of large estates. Especially relevant if your employer is exactly this kind of organisation — the module gives names to systems you are already working around. Assessed by exams and technical reports.

Year 3 — Working like an engineer

Agile delivery for real, design patterns and software quality, an integrated team project, and a step back to look at the industry you are now three years into.

Agile Software Development

Scrum and TDD practised, not just described

Sprints, stand-ups, retrospectives, user stories, estimation, and test-driven development's red-green-refactor cycle, run as actual team project work with CI/CD. The overlap with the day job is the point: you notice which parts of the textbook version your employer actually does.

  • Python
  • pytest
  • CI/CD

Integrated IT Projects

End-to-end delivery of a realistic multi-technology project

Requirements gathering, solution design, build, test, document, present — one project through the whole lifecycle, integrating databases, interfaces and APIs. The closest the academic side gets to a real work assignment, and strong raw material for the EPA portfolio.

  • Python
  • SQL

Industry Studies

The IT industry from above: sectors, careers, ethics

Industry structure, business models, professional ethics, certifications and career pathways, taught through case studies of real projects that succeeded and failed. Lands differently as an apprentice — you analyse the industry while being employed in it. Assessed through research reports and presentations.

Software Engineering 1

Design patterns, SOLID and software quality

The classic design patterns, SOLID principles, refactoring, architecture patterns like MVC, and code-quality metrics, applied in a substantial agile development exercise. The module that moves you from making things work to designing things that stay workable.

  • Python
  • UML

Year 4 — Specialisation and the finish line

Security, a second web framework at production standard, and the synoptic project — all while the end-point assessment approaches.

Cyber Security 1

Thinking like an attacker to build like a defender

The CIA triad, cryptography, authentication, OWASP-style web vulnerabilities, threat modelling, network security and compliance, with hands-on capture-the-flag workshops alongside a formal exam. Changes how you write code regardless of which specialism you follow.

  • Security tooling
  • Cryptography

Synoptic Project

The capstone: one substantial, self-directed build

A significant independent project — scoped, researched, designed, built, evaluated and presented, with supervisor support. Usually rooted in a genuine workplace problem, which is exactly what the EPA's project method wants to see. The single biggest piece of work in the degree.

  • Your choice

Software Engineering 2

Django and production-grade web engineering

A full-featured web framework (Django) on top of the Flask foundations: ORM and data modelling, authentication, forms, media handling, REST APIs and deployment, assessed through both an architecture-and-design coursework and an exam. The culmination of the programming thread that started with week one Python.

  • Python
  • Django
  • PostgreSQL
  • Git

The technology thread

One language carried the whole programme: Python, from first-week fundamentals to Django in the final year, with SQL as the constant second string. That's a deliberate design — depth in one stack teaches transferable engineering better than a tour of six languages. The core toolkit by graduation:

Your employer's stack will differ (mine did) — and that turns out to be fine. Learning Flask at university while writing something else at work is exactly the kind of transfer the programme is quietly training.

How it's assessed

Mostly coursework: substantial practical builds with test suites and documentation, plus written reports, group projects and presentations, and a handful of formal exams (systems theory and security, in my case). The final year is dominated by the synoptic project — one large self-directed build, usually rooted in a real workplace problem — which then feeds naturally into the end-point assessment. Deadlines don't move for your day job, and hand-in weeks are the hardest weeks of the whole programme; plan leave around them.