MS Software Delivery

Users, requirements, and a refusal (S2OLA01) is a 30-credit course on MS Software Delivery, with 300 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, 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 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.

• Users, components, and the interface between parts — Users, requirements, and a refusal
• Build, test, failure, and fix — Users, requirements, and a refusal
• Deployment, logs, and recovery — Users, requirements, and a refusal
• Trade-offs the designer must defend — Users, requirements, and a refusal
• Security and failure in ordinary operation — Users, requirements, and a refusal
• A supervised build or design with a defence — Users, requirements, and a refusal

Build and review (S24M303) is a 30-credit course on MS Software Delivery, with 300 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, 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 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.

• Users, components, and the interface between parts — Build and review
• Build, test, failure, and fix — Build and review
• Deployment, logs, and recovery — Build and review
• Trade-offs the designer must defend — Build and review
• Security and failure in ordinary operation — Build and review
• A supervised build or design with a defence — Build and review

Operations (S1UMH04) is a 30-credit course on MS Software Delivery, with 300 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, 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 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.

• Users, components, and the interface between parts — Operations
• Build, test, failure, and fix — Operations
• Deployment, logs, and recovery — Operations
• Trade-offs the designer must defend — Operations
• Security and failure in ordinary operation — Operations
• A supervised build or design with a defence — Operations

Capstone: technical file (S1ANA06) is a 30-credit course on MS Software Delivery, with 300 notional learning hours. By the end, students can specify a small system, show how it was tested, and state how it fails, 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 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.

• Users, components, and the interface between parts — Capstone: technical file
• Build, test, failure, and fix — Capstone: technical file
• Deployment, logs, and recovery — Capstone: technical file
• Trade-offs the designer must defend — Capstone: technical file
• Security and failure in ordinary operation — Capstone: technical file
• A supervised build or design with a defence — Capstone: technical file