Final Project
Schedule
Week 7
|
5/8
|
Final project planning
|
Week 8
|
5/15
|
Final project work
|
Week 9
|
5/22
|
Final project presentations |
Week 10
|
5/29
|
Memorial Day - no class
|
Week 11
|
3/13
|
Final project write-up due |
Deliverables
- Group Project Proposal, due by midnight on Monday, May 8
- Individual Project Writeup, due by 4:45pm on Monday, June 5
Grading
- Group Project Proposal: 10pts
- Group Presentation: 15pts
- Individual Project Writeup: 15pts
Week 7: Final Project Planning
You will research various resources for cyber-physical computing
project ideas and work on developing a group project proposal. The
groups must consist of 2 or 3 students.
Where to look for project ideas?
In the Physical Computing lab (room 502) you will find dozens of
books as well as issues of Make magazine where you can find ideas
for projects. You can also look for ideas online at
http://makezine.com/category/electronics/raspberry-pi/?post_type=projects&path=FromNav
There are also many videos describing Raspberry Pi projects on
YouTube:
https://www.youtube.com/results?search_query=raspberry+pi+projects
Once you have decided on a group (of 2 or 3 students) and a project,
please send me by email a one page description of the group members,
a summary of what you plan to do, and a list of equipment you expect
to use. The deadline for sending me the one page description is
midnight on Monday, May 8. You can get started on the project once I
approve the project.
Weeks 7, 8, and 9: Final Project Work
You will work on your project during class hours.
Week 9: Final Project Group Presentations
You will complete and present the physical computing system you
have developed.
Finals Week: Individual Final Project Writeup, due by 4:45pm on
Monday, June 5
You will submit through D2L a 3-4 page writeup on the project. Each
student will write his/her own writeup! In your writeup, you should
include:
- The project name and group members
- A short description of the cyberphysical computing system you
have built
- A list of equipment and Python code you used
- A detailed description of the workings of the system you have
built
- A self-reflection addressing the various difficulties you
encountered (whether hardware-related, software-related, and
group interactions)