You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: how-tos/schedule.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,12 @@ Follow these steps:
38
38
-**PDR**: Validate preliminary designs, ensuring alignment with mission requirements.
39
39
-**CDR**: Finalize detailed designs for all subsystems.
40
40
41
+
If you know your expected launch date or when you want the project to be completed, you can identfy the dates of the above milestones to fit to your completion date. You should try not to spend too much time in the ideation phase, as the aim is to devlop a hands-on project, once you start building things will still change.
42
+
43
+
Once you have your mission in mind, set out to start developing the subsystem requirements to make that mission successful. This will be inthe form of a requirements sheet (if you don't know how to do that, [you can find the tutorial here.]({{site.url}}/how-tos/req-sheet))
44
+
45
+
Your MDR ideally shouldn't be more than 2 months after identifying your mission.
46
+
41
47
**Result**: A high-level structure for the schedule is established.
42
48
43
49
2.**List major project tasks.**
@@ -106,13 +112,20 @@ Here is an example timeline for a CubeSat project:
0 commit comments