Duke e-mail: rabih.younes
Instructor 1-on-1 office hours are available by appointment (link to make appointments on our Canvas homepage).
To provide anonymous feedback about anything related to the course, please follow the link provided on our Canvas homepage.
Teaching Assistant (TA): Qingning Zeng (qz150)
TA office hours: TuTh 11:30–12:30 — Hudson 101A
Course Description
In this course, students design, implement, and evaluate wearable and ubiquitous computing systems while learning about the fundamentals and pertinent research in the field. Topics covered include challenges and constraints in wearable and ubiquitous computing, input/output devices, human-computer interaction, embedded systems, prototyping, machine learning with focus on activity and affect recognition, applications with focus on healthcare, ethics, and societal impact. This course also covers project management and planning as students work on a semester-long team-based multidisciplinary project. Prerequisites: ECE 350L or ECE 550D. One course.Learning Objectives
Having successfully completed this course, the student should be able to:- design, develop, and evaluate wearable/ubiquitous computing systems;
- describe and discuss design constraints unique to wearable and ubiquitous computing;
- identify and utilize hardware and software development tools useful in wearable systems development;
- work efficiently in teams on resource-constrained open-ended projects with real-world impact;
- critically read, review, and present academic research papers; and
- create and deliver oral and written presentations documenting a design project to both technical and non-technical audiences.
Textbook and Other Course Material
No textbook is required for this course. All needed material will be posted on Canvas.Grading Policy
- Design project (70%): Students are required to work in teams of 3-4 on a semester-long project. The
project should relate to wearable computing, address a real-world problem, and it should add new information to
the existing
literature in the field (no exact duplication of other projects). Remember, the better the contribution of the
project the better would be the chances to publish it later in a paper.
Deliverables:- Project proposal (5%) — one per team
- Weekly deliverables (20%) — one per team, including individual progress reports (one per student)
- Mid-semester presentation (10%) — one per team
- Final presentation and demo (20%) — one per team
- Project report (15%) — one per team *Note that team members not contributing appropriately to their team project will be penalized accordingly (up to 100% of the project grade).
- Paper presentation (10%): Each student is required to present a research paper among the papers that are assigned throughout the semester. Each presentation should take about 15 minutes (not including questions).
- Paper reviews (10%): Students are required to submit a short review of one paper among many assigned per each topic (about 7 in total). Students presenting on that topic do not submit reviews.
- Class discussions (10%): Students are required to share their ideas in class about the papers that they read and engage in meaningful, insightful, and fruitful conversations. No person is allowed to dominate the conversation.
- Extra credit (+2): Each team member will receive two extra points on their final course grade if the team submits a one-minute video about their project's process and final deliverable (take pictures and videos along the way).
- NO EXAMS/QUIZZES!
- Late policy: Late submissions are not allowed unless you have a valid excuse. In that case, email your instructor about it as soon as possible and wait for a decision (might involve a penalty, depending on the excuse). Refer to this list of common but unacceptable excuses borrowed from Dr. Bletsch.
- Regrading policy: Regrading must be requested no later than one week after the assignment grade is released.
- Grading schema (minimum %):
- 97: A+
- 93: A
- 90: A-
- 87: B+
- 83: B
- 80: B-
- 77: C+
- 73: C
- 70: C-
- 67: D+
- 63: D
- 60: D-
- 0: F
Important Notes
We can only grade what we receive. Always check what you are submitting and make sure you submit the right files.
We will use the Scrum agile project management framework throughout the project. You are free to select the tool that would help you with that.
We will use Box to keep track of each team's progress (team meeting minutes, individual progress reports, etc.) in order to facilitate documentation and grading.
We have access to all ECE labs and Duke makerspaces for project-related work; Hudson 101A will be our main lab and has lockers we can use for storage.
There will be awards at the end of the semester for best project, best presenter, and best research analyst.
Misconduct
- Academic misconduct will not be tolerated and will be taken very seriously.
- You are expected to complete the assignments individually unless otherwise stated.
- Students are encouraged to share ideas, learn from each other, and learn from online sources, but cheating is not tolerated.
- Any borrowed design/code/etc. — if allowed to be borrowed — should be properly cited.
- Students suspected violating the Duke Community Standard will be reported.
- In addition to the measures taken by the administration, the affected assignment(s) will receive zero credit, or possibly -100% in extreme cases.
- If you are considering this course of action, please see me instead and we can work something out! I want every student in my course to be successful.
- Note that programming submissions will be compared to one another and to previous semesters using state-of-the-art tools to detect signs of plagiarism.
Tentative Schedule
| Week | Date | Topic | Due |
|---|---|---|---|
| 1 | Thu 1/9 | Syllabus | |
| 2 | Tue 1/14 | Intro to UbiComp + Prototyping | Presentation topic selection |
| 2 | Thu 1/16 | Agile Project Management with Scrum + NABC | |
| 3 | Tue 1/21 | Introduction to Embedded Systems and Making | |
| 3 | Thu 1/23 | Discussing Teams' Project Proposals | Team project proposal |
| 4 | Tue 1/28 | The Vision of UbiComp According to Mark Weiser | Paper review |
| 4 | Thu 1/30 | QFT & Decision Matrices + Project-Related Work | |
| 5 | Tue 2/4 | HCI/UCD | Paper review |
| 5 | Thu 2/6 | Project-Related Work | |
| 6 | Tue 2/11 | Challenges and Constraints in Wearables Design | Paper review |
| 6 | Thu 2/13 | Project-Related Work | Project weekly deliverables |
| 7 | Tue 2/18 | Wearable Input/Output Technologies | Paper review |
| 7 | Thu 2/20 | Project-Related Work | Project weekly deliverables |
| 8 | Tue 2/25 | UbiComp Sensing | Paper review + Team peer feedback 1 |
| 8 | Thu 2/27 | Project-Related Work | Project weekly deliverables |
| 9 | Tue 3/4 | Mid-Semester Project Presentations | Mid-semester project presentation |
| 9 | Thu 3/6 | Project-Related Work | Project weekly deliverables |
| 10 | Tue 3/11 | NO CLASS (Spring Recess) | |
| 10 | Thu 3/13 | NO CLASS (Spring Recess) | |
| 11 | Tue 3/18 | Context Awareness - Activity Recognition | Paper review + Team peer feedback 2 |
| 11 | Thu 3/20 | Project-Related Work | Project weekly deliverables |
| 12 | Tue 3/25 | Context Awareness - Affect Recognition | Paper review |
| 12 | Thu 3/27 | Project-Related Work | Project weekly deliverables |
| 13 | Tue 4/1 | *Tentative* Guest Lecture | |
| 13 | Thu 4/3 | Project-Related Work | Project weekly deliverables |
| 14 | Tue 4/8 | UbiComp & Healthcare | Paper review |
| 14 | Thu 4/10 | Project-Related Work | Project weekly deliverables |
| 15 | Tue 4/15 | UbiComp & Society | |
| 15 | Thu 4/17 | Project-Related Work | Project weekly deliverables |
| 16 | Tue 4/22 | Project Final Presentations & Demos | Final project presentation |
| 17 | Tue 4/29 | Project report |
This semester's award winners:
- Best project: TBD
- Best presenter: TBD
- Best research analyst: TBD