Concurrent engineering of space missions

ENG-411

ReportFinalise report on the shared gdoc file (usi...

This page is part of the content downloaded from ReportFinalise report on the shared gdoc file (usi... on Monday, 30 June 2025, 15:39. Note that some content and any files larger than 50 MB are not downloaded.

Description

Report

Finalise report on the shared gdoc file (using markdown language already), it will be added on the wiki page later.

If needed, we can plan 1-2 writing sessions, booking the CDF, so you can work all together on the report.

Deadline: April 30th (week 11, just after the Easter holidays).

Structure:

  • Introduction (all, coordinated by SEs)
  • Executive Summary (all)
  • Results (for each subsystem):
  1. Requirements:
    E.g.: Shall provide a trajectory to correctly enter the lunar orbit and its duration.
  2. Tradeoffs
  3. Justifications
  4. Results
  • Budgets (SEs)
  • Technical Lessons Learned (for each subsystem)
  • Glossary (all, if needed to complement the global wiki glossary)
  • Appendix (all, if needed)
For grading the final report we will focus on these three criteria:
Report (criteria)WeightsMinimum to get a 4Expected to get a 6
Quality of the explanations of the results50%Results are:
- Complete
- Relevant
- Justified
- Coordinated with the other subsystems		- The text isn't too long
- The text is easy to read and understandable
Quality of the figures and tables25%- Correctly cite the sources of statements and quotes, ensuring the figures are readable and all the axes are labeled, etc- Figures are super clean and useful
Quality of the lessons learnt25%Lessons learnt are:
- Relevant
- Clear / understandable
- Extracted form a real experience in the CDF		- lessons are especially interesting and provide insight about how to improve the EPFL implementation of concurrent engineering (on at least 1 of the 5 pillars: team, facility, software, central repo, process)

Grades between 4 and 6 are at the discretion of the reviewers.