Personal diary¶
Students need to keep a personal diary and return it at the end of the course. Each member of the team, need to return a text file or pdf file. Diary can be kept online, but it should move to a file before delivering. The diary is a personal task, not a team task.
The diary should contain at least
one weekly entry with the following information:
1. Tasks that you have performed during the week and time taken for each task. Be specific: e.g.
Implemented function [getActivity],
collected up and down movement data for sensor
2. Which has been the main challenges?
3. What have you learnt this week?
4. What are your tasks for next week.
The first entry should include your target grade and the tier you are aiming at.
|
|
points |
details |
| Personal diary |
1.5 |
|
 |
Diary entries per week
|
0.25
|
Diary contains at least one entry per week
|
 |
Main tasks and estimated time
|
0.75
|
Each entry in the diary contains information about the tasks performed during the week and the estimated time of each task.
If not all weeks are reported, can take maximum 0,5 points.
If the tasks are vaguely described or times are not correctly estimated, can get maximum of 0,25 points.
|
 |
Reflection
|
0.5
|
Each week answer to the three following questions:
* Which has been the main challenges?
* What have you learnt this week?
* What are your tasks for next week.
If not all questions are answered every week, can get maximum of 0.25
|
| Questions during final meeting |
2.0 |
|
 |
Justify code decisions and explain code structure
|
1.0
|
Students is able to answers questions about the code and justify decisions: how many estates have been used, which are the transitions, how many tasks, functionality of each task, number of sensors used, how data was collected ...
If student is not able to answer all questions, or justify all decisions, but he shows that understand general structure of the code maximum points is 0.5.
If student shows vague understanding of the code, but still can explain main parts of the code (0,25)
If student cannot answer basic questions related to the code structure CANNOT PASS THE MODULE.
|
 |
Theoretical questions related to implementation
|
1.0
|
Student should be able to answer theoretical questions related to implementation: what is a RTOS, what is a task, what is I2C, how data is collected from sensors, what is an interruption, what is a state machine.
If student can answer only some of the questions get 0.5.
If student cannot answer any of the questions, or answers are vague does not receive any points.
|
| Project contribution |
6.0 |
|
 |
Project contribution
|
6.0
|
The group can distribute 6 points among group members based on their contribution. Decision is agreed between students and evaluator during the meeting.
NOTE: If all have similar contribution, each student receive 2 points each
|
Diary and personal work 9.5 points maximum¶
This task is an individual task. Each member of the team should return a different file
In this section are also included the meeting/video grading (2 points) and the contribution of the project (6 points to share).