The project will be graded based on an interim design report, a final presentation, and a final report.

  • Design report (week 2) - 15% of the final result
  • Presentation (week 8) - 15% of the final result
  • Final report (week 8) - 70% of the final result

Design report

The design report must be submitted through Canvas before 11:59 pm on May 6th, 2018. The report consists of two parts. Part 1 (max 10 pages A4 including title page and table of content) should contain the following elements:

  • Problem statement that highlights the key challenges that need to be addressed in this design project.
  • Discussion on the system-level design of the system including a discussion on the trade-offs that have been made for each component in the system? I.e., the system level description of the system should consider multiple different scenarios including possible fault situations.
  • Concise description on the working of each component in the system including a clear definition of the interfaces of each component. I.e., after reading the discussion on the components the reader should be able to assess whether all components can successfully be interconnected.
  • A test plan that defines tests (and expected outcomes) for testing the components as well as a series of tests that define how the component integration is tested. Note that the test plan does not have to define the time at which the tests are executed (planning).
  • A detailed project planning. I.e., a reasonable amount of time should be assigned for the development and testing of each individual component, sufficient time should also be available for the integration. Furthermore, realistic milestones should be defined along the project timeline to monitor progress and to define actions in case deadlines are missed.
Part 2 (2 pages A4 per team member) should reflect the following aspects/questions:
  • Technical contribution. What is your technical contribution to the design?
  • Design process. What did I learn about the design process? (Do not only mention technical aspects, but also discuss your experience with working in a team on the design.)
  • Planning and project management. How well did you manage to keep your planning? How did you keep others informed on your progress?
  • Learning outcomes. What did you learn from the project so far? About yourself? About working in the field?
  • Reflection towards the future. What are your lessons for the future? What was successful? Why? What would you do differently in the next part of the project? Why?

Presentation

At the end of the project, a video presentation (max 10 minutes) must be submitted through Canvas before 11:59 pm on June 21st, 2018. The video should demonstrate your design in action and explain the design concept and motivate your teams main design decisions.

Final report

At the end of the project, a The final report must be submitted through Canvas before 11:59 pm on June 24th, 2018. Similar to the design report, the final report should consists of two parts. Part 1 (max 15 pages A4 including title page and table of content) should contain the following elements:

  • Problem statement that highlights the key challenges that need to be addressed in this design project.
  • Discussion on the system-level design of the system including a discussion on the trade-offs that have been made for each component in the system. I.e., the system level description of the system should consider multiple different scenarios including possible fault situations.
  • Concise description on the working of each component in the system including a clear definition of the interfaces of each component. I.e., after reading the discussion on the components the reader should be able to build the components him/herself and understand the main points of the design of the components.
  • Discussion on the tests performed to verify the correct operation of the individual components. I.e., the set of performed tests should cover all possible conditions including possible fault situations. For each test the discussion shoudl include the following: (1) description of the test setup, (2) expected outcomes, (3) obtained results, (4) reflection on obtained results.
  • A conclusion that summarizes the main results achieved in the project. I.e., the conclusion should explain under which conditions the system is working. If the system is not working properly, it should be explained what needs to be done in order to arrive at a working system.
Part 2 (2 pages A4 per team member) should reflect the following aspects/questions:
  • Technical contribution. What is your technical contribution to the system?
  • Design process. What did I learn about the design process? (Do not only mention technical aspects, but also discuss your experience with working in a team on the design.)
  • Planning and project management. How well did you manage to keep your planning? How did you keep others informed on your progress?
  • Learning outcomes. What did you learn from the project? About yourself? About working in the field?
  • Reflection towards the future. What are your lessons for the future? What was successful? Why? What would you do differently in a future project? Why?

Demonstration

In addition to the above mentioned reports, we will also organize a demonstration on June 22th during which each team has to show the performance of its system on the actual planet. The schedule for this demo will be announced later.