Notes for user (DELETE WHEN DONE)

Anything enclosed in angle brackets <> means you should replace it with the appropriate name:

• <PROJECT> becomes e.g. "SAC '24 OMEN"

• <SUBSYSTEM> becomes e.g. "Avionics"

Italicized text is a comment/instructions from the template creator(s).

During the project's lifetime, this page should be a useful reference for information. After a project is done, you should be able to send this to someone, and they should not have to ask questions about what the project and each subsystem intended to accomplish and actually accomplished.

Project overview

Briefly describe the project's goals and its context (for Launch, this will be a competition, onboarding, or R&D)

Table of Contents

Pages

Goals

Post-mortem

When the project is done, go over, according to your judgement, what went right and wrong.

Design overview

<SUBSYSTEM: COPY ALL CONTENTS PER SUBSYSTEM>

<SUBSYSTEM> requirements

Mission requirements

Derived from the goals.

<EXTERNAL> requirements

Describe what an external organization (probably ESRA, URRG, or EH&S) requires of this one.

Interface requirements

Describe what other subsystems require of this one.

Design

This should describe high-level distinguishing features of this subsystem. If this project is recurring (Space Race or IREC), focus on the items you judge would be important to tell the next year's team, especially specific improvements over previous years.

Post-mortem

When the project is done, go over, according to your judgement, what went right and wrong.

<SUBSYSTEM: COPY ALL CONTENTS PER SUBSYSTEM>

<SUBSYSTEM> requirements

Mission requirements

Derived from the goals.

<EXTERNAL> requirements

Describe what an external organization (probably ESRA, URRG, or EH&S) requires of this one.

Interface requirements

Describe what other subsystems require of this one.

Design

This should describe high-level distinguishing features of this subsystem. If this project is recurring (Space Race or IREC), focus on the items you judge would be important to tell the next year's team, especially specific improvements over previous years.

Post-mortem

When the project is done, go over, according to your judgement, what went right and wrong.

<SUBSYSTEM: COPY ALL CONTENTS PER SUBSYSTEM>

<SUBSYSTEM> requirements

Mission requirements

Derived from the goals.

<EXTERNAL> requirements

Describe what an external organization (probably ESRA, URRG, or EH&S) requires of this one.

Interface requirements

Describe what other subsystems require of this one.

Design

This should describe high-level distinguishing features of this subsystem. If this project is recurring (Space Race or IREC), focus on the items you judge would be important to tell the next year's team, especially specific improvements over previous years.

Post-mortem

When the project is done, go over, according to your judgement, what went right and wrong.

<SUBSYSTEM: COPY ALL CONTENTS PER SUBSYSTEM>

<SUBSYSTEM> requirements

Mission requirements

Derived from the goals.

<EXTERNAL> requirements

Describe what an external organization (probably ESRA, URRG, or EH&S) requires of this one.

Interface requirements

Describe what other subsystems require of this one.

Design

This should describe high-level distinguishing features of this subsystem. If this project is recurring (Space Race or IREC), focus on the items you judge would be important to tell the next year's team, especially specific improvements over previous years.

Post-mortem

When the project is done, go over, according to your judgement, what went right and wrong.