Loading…
Loading…
A first degree in computing, online or in Edinburgh
Online or on campus
The undergraduate computing degree at the University of Brigant takes a student from first principles to a project they can explain. Teaching uses problems from ordinary organisations in the UK, not a tour of fashion. Online students follow the same modules as campus students at Lady Lawson Street. The credit total on this page is the sum of those modules. 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: Write and test a small program Explain how data is stored and retrieved Describe a simple network or web system 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.
Faculty spotlight
The school of computing at the University of Brigant teaches the undergraduate modules.
Study online
Online tuition is free. Online examinations are free. There is no exam fee for online study.
On-campus study
Prefer to learn at our Edinburgh campus? Campus tuition and campus examinations are charged. The published campus price is on each programme page.
| Code | Course | Credits · hours |
|---|---|---|
| CS101 | Programming Fundamentals Programming Fundamentals (CS101) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Programming Fundamentals as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS102 | Mathematics for Computing Mathematics for Computing (CS102) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Mathematics for Computing as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS103 | Computer Systems & Architecture Computer Systems & Architecture (CS103) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Computer Systems & Architecture as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS104 | Web Development Web Development (CS104) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Web Development as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS105 | Object-Oriented Software Design Object-Oriented Software Design (CS105) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Object-Oriented Software Design as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS106 | Database Fundamentals Database Fundamentals (CS106) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can define a measurable question, fit a method that can be checked, and report where it fails, using Database Fundamentals as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a dataset description, a methods note, and one published evaluation. Seminar time is for the decision, not for reading the materials aloud. Assessment is a project note with the question, the method, the result, and the limitation. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| Code | Course | Credits · hours |
|---|---|---|
| CS201 | Data Structures & Algorithms Data Structures & Algorithms (CS201) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can define a measurable question, fit a method that can be checked, and report where it fails, using Data Structures & Algorithms as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a dataset description, a methods note, and one published evaluation. Seminar time is for the decision, not for reading the materials aloud. Assessment is a project note with the question, the method, the result, and the limitation. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS202 | Database Systems Database Systems (CS202) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can define a measurable question, fit a method that can be checked, and report where it fails, using Database Systems as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a dataset description, a methods note, and one published evaluation. Seminar time is for the decision, not for reading the materials aloud. Assessment is a project note with the question, the method, the result, and the limitation. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS203 | Software Engineering Practice Software Engineering Practice (CS203) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Software Engineering Practice as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a system description, an indicator note, and a project option paper. Seminar time is for the decision, not for reading the materials aloud. Assessment is a recommendation for one decision, with the evidence and the downside. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone. This course does not confer a professional engineering licence.
| 20 · 200 h |
| CS204 | Computer Networks & Security Computer Networks & Security (CS204) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can map one named system, write a threat model, and specify the controls that would stop the most likely path, using Computer Networks & Security as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses control catalogues, incident write-ups, and a short technical standard. Seminar time is for the decision, not for reading the materials aloud. Assessment is a defensive design with a test plan and a statement of residual risk. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS205 | Operating Systems & Concurrency Operating Systems & Concurrency (CS205) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Operating Systems & Concurrency as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS206 | Human-Computer Interaction Human-Computer Interaction (CS206) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Human-Computer Interaction as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| Code | Course | Credits · hours |
|---|---|---|
| CS301 | Distributed Systems & Cloud Computing Distributed Systems & Cloud Computing (CS301) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Distributed Systems & Cloud Computing as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS302 | Artificial Intelligence & Machine Learning Artificial Intelligence & Machine Learning (CS302) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can define a measurable question, fit a method that can be checked, and report where it fails, using Artificial Intelligence & Machine Learning as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a dataset description, a methods note, and one published evaluation. Seminar time is for the decision, not for reading the materials aloud. Assessment is a project note with the question, the method, the result, and the limitation. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS303 | Cybersecurity Principles Cybersecurity Principles (CS303) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can map one named system, write a threat model, and specify the controls that would stop the most likely path, using Cybersecurity Principles as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses control catalogues, incident write-ups, and a short technical standard. Seminar time is for the decision, not for reading the materials aloud. Assessment is a defensive design with a test plan and a statement of residual risk. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS304 | Advanced Software Architecture Advanced Software Architecture (CS304) is a 20-credit course on BSc (Hons) Computer Science, with 200 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Advanced Software Architecture as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 20 · 200 h |
| CS305 | Honours Computing Project & Dissertation Honours Computing Project & Dissertation (CS305) is a 40-credit course on BSc (Hons) Computer Science, with 400 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, using Honours Computing Project & Dissertation as the working context rather than a generic management example. The course is taught in three movements. First, students establish the terms and the decision the course is about. Second, they apply the method to a case, dataset, text, or design and compare it with a weaker alternative. Third, they revise the work after feedback and state what the conclusion cannot support. Preparation uses a specification, a test note, and an incident or post-mortem. Seminar time is for the decision, not for reading the materials aloud. Assessment is a specification or reviewed component with tests and a trade-off note. A pass requires a clear method, evidence a marker can check, and an explicit limit. Credit is not awarded for summary alone.
| 40 · 400 h |
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.
The published duration is 3 years full-time. Teaching language: English. Actual time-to-complete depends on mode and any recognised prior learning.
You may study this award fully online from your country, or — where published — on campus at Brigant. Online study does not require a student visa. Campus study may.
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.
Requirements are grouped on this page (academic, English, documents). Equivalent qualifications are considered. English may be waived after prior English-medium study.
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.
Recognition of the award for local employment, professional licence, or ministry attestation is decided by your employer or regulator. University of Brigant publishes verification pages for certificates. We do not claim automatic equivalence in every country.
Start an application on this website. Progress is saved from the first step. Admissions: admissions@brigant.uk.
Recognised & Accredited
