Overview
Undergraduate computing is a first degree with a final project. Online students are not charged tuition. Students in Durham follow the campus fee. The modules are the ones listed, and the credits are their sum.
BSc (Hons) Computer Science is taught as one award, not a list of unrelated modules. The published length is 3 years full-time, and the credit total is 360. Students move from Programming Fundamentals through Programming Fundamentals; Mathematics for Computing; Computer Systems & Architecture; Web Development; Object-Oriented Software Design; Database Fundamentals, and finish on Honours Computing Project & Dissertation.
Each course has a question, a method, and a submission. In this field, students specify a small system, show how it was tested, and state how it fails. Reading is a specification, a test note, and an incident or post-mortem. The artefact a marker expects is a specification or reviewed component with tests and a trade-off note.
The award is built so that a graduate can do the following in practice: Program and test Explain systems Review code
Teaching assumes the student can read a source, attempt a problem before the seminar, and revise after feedback. Attendance at live seminars is part of the design. The capstone or final course must use the methods of the earlier courses; a project that ignores them does not pass.
The pages for each course name the topics that are examined. Those topics are the syllabus. A brochure line is not a substitute for them.
The credit total equals the modules listed. Online tuition is covered. Examination or administrative fees may still apply. Campus study, where it is offered, is priced separately.
Who This Programme Is For
- ✦Applicants starting a first degree
- ✦Adults returning to study while working
- ✦Students who want a campus route, an online route, or both where both are offered
- ✦Applicants who can meet the published entry standard
Faculty spotlight
The department of computer science at Durham University teaches the undergraduate modules.
Programme Structure & Delivery
Coursework
Interactive modules, weekly readings, recorded and live seminars, and collaborative discussions with peers worldwide.
Assessment
Module assignments, proctored examinations, and capstone projects designed to demonstrate mastery of the field.
Learning Outcomes
- ✦Program and test
- ✦Explain systems
- ✦Review code
- ✦Complete a project
Career Pathways
- ✦Junior developer
- ✦IT analyst
- ✦Further study
Assessment
Modules are assessed through a published mix of coursework, applied projects, and examinations. Exam windows are announced in advance so students in other time zones are not forced into overnight sittings. Alternative arrangements are available where documented.
Curriculum
Year 1 — Foundations
CS101Programming Fundamentals- CS101-M1 · Users, components, and the interface between parts — Programming Fundamentals
- CS101-M2 · Build, test, failure, and fix — Programming Fundamentals
- CS101-M3 · Deployment, logs, and recovery — Programming Fundamentals
- CS101-M4 · Trade-offs the designer must defend — Programming Fundamentals
- CS101-M5 · Security and failure in ordinary operation — Programming Fundamentals
- CS101-M6 · A supervised build or design with a defence — Programming Fundamentals
20 creditsCS102Mathematics for Computing- CS102-M1 · Users, components, and the interface between parts — Mathematics for Computing
- CS102-M2 · Build, test, failure, and fix — Mathematics for Computing
- CS102-M3 · Deployment, logs, and recovery — Mathematics for Computing
- CS102-M4 · Trade-offs the designer must defend — Mathematics for Computing
- CS102-M5 · Security and failure in ordinary operation — Mathematics for Computing
- CS102-M6 · A supervised build or design with a defence — Mathematics for Computing
20 creditsCS103Computer Systems & Architecture- CS103-M1 · Users, components, and the interface between parts — Computer Systems & Architecture
- CS103-M2 · Build, test, failure, and fix — Computer Systems & Architecture
- CS103-M3 · Deployment, logs, and recovery — Computer Systems & Architecture
- CS103-M4 · Trade-offs the designer must defend — Computer Systems & Architecture
- CS103-M5 · Security and failure in ordinary operation — Computer Systems & Architecture
- CS103-M6 · A supervised build or design with a defence — Computer Systems & Architecture
20 creditsCS104Web Development- CS104-M1 · Users, components, and the interface between parts — Web Development
- CS104-M2 · Build, test, failure, and fix — Web Development
- CS104-M3 · Deployment, logs, and recovery — Web Development
- CS104-M4 · Trade-offs the designer must defend — Web Development
- CS104-M5 · Security and failure in ordinary operation — Web Development
- CS104-M6 · A supervised build or design with a defence — Web Development
20 creditsCS105Object-Oriented Software Design- CS105-M1 · Users, components, and the interface between parts — Object-Oriented Software Design
- CS105-M2 · Build, test, failure, and fix — Object-Oriented Software Design
- CS105-M3 · Deployment, logs, and recovery — Object-Oriented Software Design
- CS105-M4 · Trade-offs the designer must defend — Object-Oriented Software Design
- CS105-M5 · Security and failure in ordinary operation — Object-Oriented Software Design
- CS105-M6 · A supervised build or design with a defence — Object-Oriented Software Design
20 creditsCS106Database Fundamentals- CS106-M1 · The question, the unit of analysis, and data quality — Database Fundamentals
- CS106-M2 · Features, baselines, and error — Database Fundamentals
- CS106-M3 · Validation, leakage, and what the model must not decide — Database Fundamentals
- CS106-M4 · Monitoring, drift, and human review — Database Fundamentals
- CS106-M5 · Interpretation for a non-technical decision maker — Database Fundamentals
- CS106-M6 · A supervised project with method, result, and limitation — Database Fundamentals
20 creditsYear 2 — Core Systems
CS201Data Structures & Algorithms- CS201-M1 · The question, the unit of analysis, and data quality — Data Structures & Algorithms
- CS201-M2 · Features, baselines, and error — Data Structures & Algorithms
- CS201-M3 · Validation, leakage, and what the model must not decide — Data Structures & Algorithms
- CS201-M4 · Monitoring, drift, and human review — Data Structures & Algorithms
- CS201-M5 · Interpretation for a non-technical decision maker — Data Structures & Algorithms
- CS201-M6 · A supervised project with method, result, and limitation — Data Structures & Algorithms
20 creditsCS202Database Systems- CS202-M1 · The question, the unit of analysis, and data quality — Database Systems
- CS202-M2 · Features, baselines, and error — Database Systems
- CS202-M3 · Validation, leakage, and what the model must not decide — Database Systems
- CS202-M4 · Monitoring, drift, and human review — Database Systems
- CS202-M5 · Interpretation for a non-technical decision maker — Database Systems
- CS202-M6 · A supervised project with method, result, and limitation — Database Systems
20 creditsCS203Software Engineering Practice- CS203-M1 · System boundary, constraint, and actors — Software Engineering Practice
- CS203-M2 · Indicators, sources of error, and a better measure — Software Engineering Practice
- CS203-M3 · Two options on cost, time, and downside — Software Engineering Practice
- CS203-M4 · Safety, environmental limit, and who bears the risk — Software Engineering Practice
- CS203-M5 · A site, grid, or product decision — Software Engineering Practice
- CS203-M6 · A recommendation with evidence and residual risk — Software Engineering Practice
20 creditsCS204Computer Networks & Security- CS204-M1 · Assets, trust boundaries, and the adversary model — Computer Networks & Security
- CS204-M2 · Threat modelling and attack paths — Computer Networks & Security
- CS204-M3 · Identity, logging, and segmentation — Computer Networks & Security
- CS204-M4 · Detection, containment, and evidence — Computer Networks & Security
- CS204-M5 · Residual risk and what a control does not stop — Computer Networks & Security
- CS204-M6 · Defensive design, test plan, and after-action review — Computer Networks & Security
20 creditsCS205Operating Systems & Concurrency- CS205-M1 · Users, components, and the interface between parts — Operating Systems & Concurrency
- CS205-M2 · Build, test, failure, and fix — Operating Systems & Concurrency
- CS205-M3 · Deployment, logs, and recovery — Operating Systems & Concurrency
- CS205-M4 · Trade-offs the designer must defend — Operating Systems & Concurrency
- CS205-M5 · Security and failure in ordinary operation — Operating Systems & Concurrency
- CS205-M6 · A supervised build or design with a defence — Operating Systems & Concurrency
20 creditsCS206Human-Computer Interaction- CS206-M1 · Users, components, and the interface between parts — Human-Computer Interaction
- CS206-M2 · Build, test, failure, and fix — Human-Computer Interaction
- CS206-M3 · Deployment, logs, and recovery — Human-Computer Interaction
- CS206-M4 · Trade-offs the designer must defend — Human-Computer Interaction
- CS206-M5 · Security and failure in ordinary operation — Human-Computer Interaction
- CS206-M6 · A supervised build or design with a defence — Human-Computer Interaction
20 creditsYear 3 — Advanced & Honours
CS301Distributed Systems & Cloud Computing- CS301-M1 · Users, components, and the interface between parts — Distributed Systems & Cloud Computing
- CS301-M2 · Build, test, failure, and fix — Distributed Systems & Cloud Computing
- CS301-M3 · Deployment, logs, and recovery — Distributed Systems & Cloud Computing
- CS301-M4 · Trade-offs the designer must defend — Distributed Systems & Cloud Computing
- CS301-M5 · Security and failure in ordinary operation — Distributed Systems & Cloud Computing
- CS301-M6 · A supervised build or design with a defence — Distributed Systems & Cloud Computing
20 creditsCS302Artificial Intelligence & Machine Learning- CS302-M1 · The question, the unit of analysis, and data quality — Artificial Intelligence & Machine Learning
- CS302-M2 · Features, baselines, and error — Artificial Intelligence & Machine Learning
- CS302-M3 · Validation, leakage, and what the model must not decide — Artificial Intelligence & Machine Learning
- CS302-M4 · Monitoring, drift, and human review — Artificial Intelligence & Machine Learning
- CS302-M5 · Interpretation for a non-technical decision maker — Artificial Intelligence & Machine Learning
- CS302-M6 · A supervised project with method, result, and limitation — Artificial Intelligence & Machine Learning
20 creditsCS303Cybersecurity Principles- CS303-M1 · Assets, trust boundaries, and the adversary model — Cybersecurity Principles
- CS303-M2 · Threat modelling and attack paths — Cybersecurity Principles
- CS303-M3 · Identity, logging, and segmentation — Cybersecurity Principles
- CS303-M4 · Detection, containment, and evidence — Cybersecurity Principles
- CS303-M5 · Residual risk and what a control does not stop — Cybersecurity Principles
- CS303-M6 · Defensive design, test plan, and after-action review — Cybersecurity Principles
20 creditsCS304Advanced Software Architecture- CS304-M1 · Users, components, and the interface between parts — Advanced Software Architecture
- CS304-M2 · Build, test, failure, and fix — Advanced Software Architecture
- CS304-M3 · Deployment, logs, and recovery — Advanced Software Architecture
- CS304-M4 · Trade-offs the designer must defend — Advanced Software Architecture
- CS304-M5 · Security and failure in ordinary operation — Advanced Software Architecture
- CS304-M6 · A supervised build or design with a defence — Advanced Software Architecture
20 creditsCS305Honours Computing Project & Dissertation- CS305-M1 · Users, components, and the interface between parts — Honours Computing Project & Dissertation
- CS305-M2 · Build, test, failure, and fix — Honours Computing Project & Dissertation
- CS305-M3 · Deployment, logs, and recovery — Honours Computing Project & Dissertation
- CS305-M4 · Trade-offs the designer must defend — Honours Computing Project & Dissertation
- CS305-M5 · Security and failure in ordinary operation — Honours Computing Project & Dissertation
- CS305-M6 · A supervised build or design with a defence — Honours Computing Project & Dissertation
40 creditsAdmission requirements
Academic entry
- A-levels BBB (or equivalent) in relevant subjects, or an Access to HE Diploma with Merit profile
- International Baccalaureate 28 points, or high school diploma with GPA 3.0/4.0 minimum
English language
- English proficiency: IELTS 5.5, TOEFL 46, or equivalent (waived for prior English-medium study)
Documents
- Personal statement (400–600 words) explaining your academic interests and career goals
- One academic reference from a teacher, tutor, or school counsellor
Research & interview
- Optional: portfolio or interview for creative and professional programmes
Programme questions
How long is the BSc (Hons) Computer Science?+
The published duration is 3 years full-time. Teaching language: English. Actual time-to-complete depends on mode and any recognised prior learning.
Can I study this from my country?+
This is a fully online award. You study from your country. No student visa and no campus relocation are required.
What does it cost?+
Degree tuition for this award is published as £0 / tuition-free on the online pathway. Examination or administrative fees may apply at checkout — never an annual tuition invoice. Check the Fees page for any extras.
What are the entry requirements?+
Requirements are grouped on this page (academic, English, documents). Equivalent qualifications are considered. English may be waived after prior English-medium study.
How is the programme assessed?+
Assessment is typically a mix of coursework, projects, and examinations. Doctoral awards include a thesis or dissertation and an oral examination. Details sit in the programme specification and module outlines.
Will this award be recognised where I live?+
Recognition of the award for local employment, professional licence, or ministry attestation is decided by your employer or regulator. Durham University publishes verification pages for certificates. We do not claim automatic equivalence in every country.
How do I apply?+
Start an application on this website. Progress is saved from the first step. Admissions: admissions@durhm.co.uk.
