What To Pay Attention To In 5EID0 Project Course
Question
What are the main things to pay attention to in this TU/e project course?
Most Important Points
1. This is not just a coding course
The project absolutely includes coding, but the manual is very explicit that:
- technical results matter
- design process matters
- testing matters
- task allocation matters
- milestones and planning matter
- system engineering matters
So if you only think in terms of “I will just code my part”, you may undershoot what the course is actually grading.
2. The V-model and process must be visible
The manual explicitly says teams are expected to follow and report a systematic system engineering process based on the V-model.
That means you need to be able to contribute not only to implementation, but also to:
- requirements
- architecture
- detailed design
- tests
- integration plan
- reflection on the process
3. Deliverables are heavy on reporting
The grade split is:
- design report
15% - demo video
15% - final report
70%
So documentation and explanation are not side tasks; they are a major part of the grade.
4. You still need broad system understanding
Even if you specialize, the final report expects a system-level view and the individual report asks:
- what your technical contribution was
- what specialization you took
- what you learned about design and system engineering
- how you handled planning and teamwork
So your role can be focused, but your understanding cannot be narrow.
5. Teamwork is part of the course
The team is random and cannot be changed.
Also:
- attendance is expected in person
- task division is up to the team
- you are supposed to discuss preferences and split the work intentionally
So role negotiation early on matters a lot.
6. TAs will not solve the project for you
They mainly help with:
- checking whether hardware is functioning properly
- monitoring team dynamics
They are not there to resolve the actual technical design challenge.
7. Final demo constraints matter
During the final video/demo:
- robots need to act autonomously
- they must avoid cliffs, boundaries, and mountains
- they must recognize rocks and report via MQTT
- no cable should be connected during operation
So last-minute partial solutions that depend on manual intervention or tethering are risky.
Best Practical Summary
Treat this course as:
- a robotics/software project
- a system-engineering project
- a teamwork and planning project
- a documentation-heavy course
not just a coding assignment.
Counterpoints and Gaps
- a strong specialist role is still valuable, but only if it is integrated into the broader team process
- the course leaves teams freedom in design choices, which is powerful but also increases coordination risk