Loading…
Loading…
Dual UK Honours Bachelor's Degree — Conferred jointly with University of Brigant (UK) & Coventry University TNE Network (UK)
Coventry University (United Kingdom)
Online or on campus
A career-accelerated undergraduate curriculum covering modern software engineering, Kubernetes & cloud infrastructure, cybersecurity protocols, and distributed databases. Students earn 2 independent accredited diplomas with a 65% / 35% international credit split. BSc (Hons) Computer Science & Cloud Systems (Dual Award) is taught as one award, not a list of unrelated modules. The published length is 36 months, and the credit total is 360. Students move from Systems and interfaces through Systems and interfaces; Building and testing; Running the system; Technical project; Systems and interfaces (BSC-105); Building and testing (BSC-106), and finish on Systems and interfaces (BSC-305). 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: Dual degree transcripts issued with comprehensive credit mobility (UK FHEQ Level 6) Hands-on production labs with AWS, GCP, and Azure cloud computing credits Direct fast-track admission to Master's dual-award degrees upon graduation with 2:1 or higher 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.
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 |
|---|---|---|
| BSC-101 | Systems and interfaces Systems and interfaces (BSC-101) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Systems and interfaces 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 |
| BSC-102 | Building and testing Building and testing (BSC-102) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Building and testing 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 |
| BSC-103 | Running the system Running the system (BSC-103) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Running the system 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 |
| BSC-104 | Technical project Technical project (BSC-104) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Technical project 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 |
| BSC-105 | Systems and interfaces (BSC-105) Systems and interfaces (BSC-105) (BSC-105) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Systems and interfaces (BSC-105) 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 |
| BSC-106 | Building and testing (BSC-106) Building and testing (BSC-106) (BSC-106) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Building and testing (BSC-106) 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 |
|---|---|---|
| BSC-201 | Running the system (BSC-201) Running the system (BSC-201) (BSC-201) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Running the system (BSC-201) 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 |
| BSC-202 | Technical project (BSC-202) Technical project (BSC-202) (BSC-202) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Technical project (BSC-202) 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 |
| BSC-203 | Systems and interfaces (BSC-203) Systems and interfaces (BSC-203) (BSC-203) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Systems and interfaces (BSC-203) 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 |
| BSC-204 | Building and testing (BSC-204) Building and testing (BSC-204) (BSC-204) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Building and testing (BSC-204) 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 |
| BSC-205 | Running the system (BSC-205) Running the system (BSC-205) (BSC-205) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Running the system (BSC-205) 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 |
| BSC-206 | Technical project (BSC-206) Technical project (BSC-206) (BSC-206) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Technical project (BSC-206) 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 |
|---|---|---|
| BSC-301 | Systems and interfaces (BSC-301) Systems and interfaces (BSC-301) (BSC-301) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Systems and interfaces (BSC-301) 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 |
| BSC-302 | Building and testing (BSC-302) Building and testing (BSC-302) (BSC-302) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Building and testing (BSC-302) 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 |
| BSC-303 | Running the system (BSC-303) Running the system (BSC-303) (BSC-303) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Running the system (BSC-303) 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 |
| BSC-304 | Technical project (BSC-304) Technical project (BSC-304) (BSC-304) is a 20-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Technical project (BSC-304) 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 |
| BSC-305 | Systems and interfaces (BSC-305) Systems and interfaces (BSC-305) (BSC-305) is a 40-credit course on BSc (Hons) Computer Science & Cloud Systems (Dual Award), 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 Systems and interfaces (BSC-305) 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 36 months. 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
