As part of the course work, you and your group will invent, design and implement a non-trivial embedded system. Within some constraints described below, you will be able to present your own project idea, which you will then bring to life during the semester. Your group project work will be advised by a tutor, which we will assign to your group after your successful project pitch. The lab space and hardware needed to realize the system will be provided by us. To ensure good progress on the project during the semester, you will have to reserve significant time for the project. Part of our learning goals is for you to experience a real engineering process, so there will be milestones and artifacts, which you hand in.
All projects will be group projects, where groups consist of 3 to 4 students. Finding and forming groups until the project pitch is your own responsibility.
A pitch of your project idea has to be presented within the project session in week 3 on May 6th.
Milestones / Artifacts
Your work progress during the weekly project work sessions should be documented by a protocol, which you will upload after the sessions and complete until the end of the week. Furthermore, we expect certain documents and models at specific milestones.
- Project Pitch (May 6th)
- Preliminary Design / Specifications ("Pflichtenheft") (May 19th)
Artifact: Specification document
- Virtual Prototype / Simulations (June 2nd)
Artifacts: Simulink Models, accompanying documentation
- Test cases / Risk analysis (June 16th)
Artifacts: Test cases for Simulink/FPGA-Design, HW testbench, scripts, description of test setup, Risks document
- Prototype (June 30th)
Artifacts: Updated specification document, first real prototype
- Verification (July 14th)
Artifacts: Model, properties, accompanying documentation, scripts
- Final project (July 24th)
Artifacts: Updated specification document, finished project
The best project will be determined by a student vote in the final project session before the end of the semester.
Guidelines & Requirements
- Must communicate
- "Not implementable on a single smartphone"
- Must interact with the physical world
- At least two real-time platforms
Use the time for brainstorming, sketching, designing, distributing work, and actual project work
- Have an agenda for every meeting
- The project session is the opportunity to interact with your tutor.
- Document your progress in your engineering notebook.
Record your work on the project, including brainstorming, sketches, calculations, designs and action items
Record project meetings, including agendas, major discussion items, and action items that result from the meeting
Record recommendations from your tutor
Record related work that influenced you
If documents/software is too big to include, give the location where it can be found
Obtain a timestamp: Upload notebook to rcms at the end of every day