Group Project
A team-built Space Science production line, taken from a shared starting save through to a self-sufficient rocket launch.
Due: 23 October 2026 · Weight: 30%
The brief#
As a group, take a shared base from where Week 7 leaves it to a self-sufficient Space Science operation.
Groups form in Week 7 and inherit one save between them. Everything from that point — role allocation, which sub-system each member owns, how conflicting blueprint choices get resolved — is part of the assessment, not incidental to it. A base that works because one person did everything is not a passing group project, however good the base is.
What you submit#
The shared save file at hand-in, a design report covering the production chain’s key ratios and the layout decisions that made them hold, and a short note from each member on what they built and what they relied on a teammate for.
The spec
The brief poses the problem and leaves room for a response. The spec is the fixed part: what a marker checks. Some lines can be checked mechanically; the rest call for judgement.
- a shared save file that reaches a sustained Space Science output, or launches a rocket, without manual intervention
- a design report explaining the base's key structural decisions and how they were reached
- evidence that the work was actually shared across the group, not produced by one member alone
How it is marked
| Criterion | Weight |
|---|---|
| Base output and reliability | 50% |
| Design report | 30% |
| Collaboration evidence | 20% |