MSc

MSc Cloud and Infrastructure

Cloud computing degree UK. 6 assessed courses, 1,800 notional hours, tuition-free.

Online or on campus

18 months180 creditsEnglish

Overview

Cloud computing degree UK. MSc Cloud and Infrastructure at University of Brigant: 6 assessed courses, 180 credits and 1,800 notional learning hours, at 10 hours per credit. The hours on each course add up to that total. Seminars run online. An Edinburgh campus route is published separately from this online award. This award is the university's own. It is not a vendor certificate. MSc Cloud and Infrastructure is taught as one award, not a list of unrelated modules. The published length is 18 months, and the credit total is 180. Students move from Users, requirements, and a refusal through Users, requirements, and a refusal; Design and the interface; Build and review; Operations; Security and responsibility; Capstone: technical file, and finish on Capstone: technical file. Each course has a question, a method, and a submission. In this field, students draw the system, name the constraint that binds it, and compare two responses. Reading is a system description, an indicator note, and a project option paper. The artefact a marker expects is a recommendation for one decision, with the evidence and the downside. The award is built so that a graduate can do the following in practice: Produce a professional file in Cloud and Infrastructure Choose a method and write what the evidence cannot support Keep a record a third party can review 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. This course does not confer a professional engineering licence. 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.

Each credit is 10 notional learning hours. The courses add up to 180 credits and 1,800 hours. This award is the university's own. It is not a vendor certificate.

Who This Programme Is For

People already working around Cloud and Infrastructure
Career-changers who can study without leaving their city
Teams who need a file they can review, not a slogan

Faculty spotlight

University of Brigant supervises the courses and the final assessed file. Supervision is assigned from the school that owns the award.

How you can study

Recommended

Study online

100% tuition-free online

Online tuition is free. Online examinations are free. There is no exam fee for online study.

✦ Tuition: £0 / $0
✦ Examinations are free. There is no exam fee.
✦ Learn from anywhere · Live online seminars

Apply online →

On-campus study

Study at our campus

Prefer to learn at our Edinburgh campus? Campus tuition and campus examinations are charged. The published campus price is on each programme page.

✦ Tuition: £9,500 / US$12,000/year
✦ Location: 3 Lady Lawson St, Edinburgh EH3 9DS, United Kingdom
✦ Campus examinations are charged
✦ In-person seminars, library & student services

Apply for campus →

What You Will Learn

Produce a professional file in Cloud and Infrastructure
Choose a method and write what the evidence cannot support
Keep a record a third party can review
State the limit of the award
Submit the final project inside the published hours

Curriculum

Stage 1 — 900 hours

Code	Course	Credits · hours
SOB0W01	Users, requirements, and a refusal Users, requirements, and a refusal (SOB0W01) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Users, requirements, and a refusal 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. SOB0W01-M1 · System boundary, constraint, and actors — Users, requirements, and a refusal SOB0W01-M2 · Indicators, sources of error, and a better measure — Users, requirements, and a refusal SOB0W01-M3 · Two options on cost, time, and downside — Users, requirements, and a refusal SOB0W01-M4 · Safety, environmental limit, and who bears the risk — Users, requirements, and a refusal SOB0W01-M5 · A site, grid, or product decision — Users, requirements, and a refusal SOB0W01-M6 · A recommendation with evidence and residual risk — Users, requirements, and a refusal	30 · 300 h
SP4ZQ02	Design and the interface Design and the interface (SP4ZQ02) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Design and the interface 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. SP4ZQ02-M1 · System boundary, constraint, and actors — Design and the interface SP4ZQ02-M2 · Indicators, sources of error, and a better measure — Design and the interface SP4ZQ02-M3 · Two options on cost, time, and downside — Design and the interface SP4ZQ02-M4 · Safety, environmental limit, and who bears the risk — Design and the interface SP4ZQ02-M5 · A site, grid, or product decision — Design and the interface SP4ZQ02-M6 · A recommendation with evidence and residual risk — Design and the interface	30 · 300 h
SOV0403	Build and review Build and review (SOV0403) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Build and review 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. SOV0403-M1 · System boundary, constraint, and actors — Build and review SOV0403-M2 · Indicators, sources of error, and a better measure — Build and review SOV0403-M3 · Two options on cost, time, and downside — Build and review SOV0403-M4 · Safety, environmental limit, and who bears the risk — Build and review SOV0403-M5 · A site, grid, or product decision — Build and review SOV0403-M6 · A recommendation with evidence and residual risk — Build and review	30 · 300 h

Code

Course

Credits · hours

SOB0W01

Users, requirements, and a refusal

Users, requirements, and a refusal (SOB0W01) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Users, requirements, and a refusal 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.

SOB0W01-M1 · System boundary, constraint, and actors — Users, requirements, and a refusal
SOB0W01-M2 · Indicators, sources of error, and a better measure — Users, requirements, and a refusal
SOB0W01-M3 · Two options on cost, time, and downside — Users, requirements, and a refusal
SOB0W01-M4 · Safety, environmental limit, and who bears the risk — Users, requirements, and a refusal
SOB0W01-M5 · A site, grid, or product decision — Users, requirements, and a refusal
SOB0W01-M6 · A recommendation with evidence and residual risk — Users, requirements, and a refusal

30 · 300 h

SP4ZQ02

Design and the interface

Design and the interface (SP4ZQ02) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Design and the interface 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.

SP4ZQ02-M1 · System boundary, constraint, and actors — Design and the interface
SP4ZQ02-M2 · Indicators, sources of error, and a better measure — Design and the interface
SP4ZQ02-M3 · Two options on cost, time, and downside — Design and the interface
SP4ZQ02-M4 · Safety, environmental limit, and who bears the risk — Design and the interface
SP4ZQ02-M5 · A site, grid, or product decision — Design and the interface
SP4ZQ02-M6 · A recommendation with evidence and residual risk — Design and the interface

30 · 300 h

SOV0403

Build and review

Build and review (SOV0403) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Build and review 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.

SOV0403-M1 · System boundary, constraint, and actors — Build and review
SOV0403-M2 · Indicators, sources of error, and a better measure — Build and review
SOV0403-M3 · Two options on cost, time, and downside — Build and review
SOV0403-M4 · Safety, environmental limit, and who bears the risk — Build and review
SOV0403-M5 · A site, grid, or product decision — Build and review
SOV0403-M6 · A recommendation with evidence and residual risk — Build and review

30 · 300 h

Stage 2 — 900 hours

Code	Course	Credits · hours
SPOYX04	Operations Operations (SPOYX04) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Operations 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. SPOYX04-M1 · System boundary, constraint, and actors — Operations SPOYX04-M2 · Indicators, sources of error, and a better measure — Operations SPOYX04-M3 · Two options on cost, time, and downside — Operations SPOYX04-M4 · Safety, environmental limit, and who bears the risk — Operations SPOYX04-M5 · A site, grid, or product decision — Operations SPOYX04-M6 · A recommendation with evidence and residual risk — Operations	30 · 300 h
SPEZB05	Security and responsibility Security and responsibility (SPEZB05) is a 30-credit course on MSc Cloud and Infrastructure, with 300 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 Security and responsibility 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. SPEZB05-M1 · Assets, trust boundaries, and the adversary model — Security and responsibility SPEZB05-M2 · Threat modelling and attack paths — Security and responsibility SPEZB05-M3 · Identity, logging, and segmentation — Security and responsibility SPEZB05-M4 · Detection, containment, and evidence — Security and responsibility SPEZB05-M5 · Residual risk and what a control does not stop — Security and responsibility SPEZB05-M6 · Defensive design, test plan, and after-action review — Security and responsibility	30 · 300 h
SQ8Y406	Capstone: technical file Capstone: technical file (SQ8Y406) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Capstone: technical file 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. SQ8Y406-M1 · System boundary, constraint, and actors — Capstone: technical file SQ8Y406-M2 · Indicators, sources of error, and a better measure — Capstone: technical file SQ8Y406-M3 · Two options on cost, time, and downside — Capstone: technical file SQ8Y406-M4 · Safety, environmental limit, and who bears the risk — Capstone: technical file SQ8Y406-M5 · A site, grid, or product decision — Capstone: technical file SQ8Y406-M6 · A recommendation with evidence and residual risk — Capstone: technical file	30 · 300 h

Code

Course

Credits · hours

SPOYX04

Operations

Operations (SPOYX04) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Operations 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.

SPOYX04-M1 · System boundary, constraint, and actors — Operations
SPOYX04-M2 · Indicators, sources of error, and a better measure — Operations
SPOYX04-M3 · Two options on cost, time, and downside — Operations
SPOYX04-M4 · Safety, environmental limit, and who bears the risk — Operations
SPOYX04-M5 · A site, grid, or product decision — Operations
SPOYX04-M6 · A recommendation with evidence and residual risk — Operations

30 · 300 h

SPEZB05

Security and responsibility

Security and responsibility (SPEZB05) is a 30-credit course on MSc Cloud and Infrastructure, with 300 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 Security and responsibility 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.

SPEZB05-M1 · Assets, trust boundaries, and the adversary model — Security and responsibility
SPEZB05-M2 · Threat modelling and attack paths — Security and responsibility
SPEZB05-M3 · Identity, logging, and segmentation — Security and responsibility
SPEZB05-M4 · Detection, containment, and evidence — Security and responsibility
SPEZB05-M5 · Residual risk and what a control does not stop — Security and responsibility
SPEZB05-M6 · Defensive design, test plan, and after-action review — Security and responsibility

30 · 300 h

SQ8Y406

Capstone: technical file

Capstone: technical file (SQ8Y406) is a 30-credit course on MSc Cloud and Infrastructure, with 300 notional learning hours. By the end, students can draw the system, name the constraint that binds it, and compare two responses, using Capstone: technical file 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.

SQ8Y406-M1 · System boundary, constraint, and actors — Capstone: technical file
SQ8Y406-M2 · Indicators, sources of error, and a better measure — Capstone: technical file
SQ8Y406-M3 · Two options on cost, time, and downside — Capstone: technical file
SQ8Y406-M4 · Safety, environmental limit, and who bears the risk — Capstone: technical file
SQ8Y406-M5 · A site, grid, or product decision — Capstone: technical file
SQ8Y406-M6 · A recommendation with evidence and residual risk — Capstone: technical file

30 · 300 h

Career Paths

Software developer
IT analyst
Cloud operations officer
Product analyst
Technical programme coordinator

Programme Highlights

180 credits · 1,800 notional hours · 6 courses
Course hours add up to the programme total
cloud computing degree UK
Seminars run online. An Edinburgh campus route is published separately from this online award.

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.

Admission requirements

Academic entry

A bachelor's degree from a recognised institution, or equivalent professional standing considered by admissions

Documents

A statement of about 500 words on why this award fits your work
Two references, academic or professional
A CV

Programme questions

How long is the MSc Cloud and Infrastructure?

The published duration is 18 months. Teaching language: English. Actual time-to-complete depends on mode and any recognised prior learning.

Can I study this from my country?

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.

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. University of Brigant 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@brigant.uk.

Recognised & Accredited

Ready to begin?MSc Cloud and Infrastructure

Start an application

Loading…