ASSIGNMENT – “THEN” (INDIVIDUAL or TEAMS-OF-TWO)
PROPOSAL DUE: FRIDAY NOVEMBER 2ND @ 13H30
PROTOTYPE DUE: FRIDAY NOVEMBER 16TH @ 13H30
FINAL DUE: FRIDAY NOVEMBER 30TH @ 13H30
FINAL DOCUMENTATION DUE:FRIDAY DEC 7TH @ 13H30
This is an open project. Most of you seem interested in different topics related to physical computing, and we don’t want to enforce any specific topic on you. Take some time to think about what you would really want to work on. Think about something fun where you feel you will learn something exciting instead of banging your head on a wall trying to debug a project that bores you.
4 RESEARCH QUESTIONS
- Think of a context and an environment where you would like to intervene. Where will you present your project? Who is it made for?
- Think about the kind of relationship you wish to foster between your users and the artifact or installation. How can you use your project to destabilize the users and make them reflect on themselves, their environment and society?
- Think about the notion of empowerment. Is your artifact really helping or challenging its users in any way or is it just another psychological prosthesis?
- Think about something meaningful. What are you trying to tell us with your project?
TOPICS YOU MAY WANT TO EXPLORE
- Tangible User Interfaces – connecting people to the digital world through new physical objects.
- Responsive Environments – large-scale installations that react to user intervention.
- Wearable Electronics – reactive fabrics that challenge our relationship with the things we normally wear.
- Expressive Interfaces – new media for expression, physical instruments for performance.
- Distributed Sensor/Actuator Networks – swarms of simple networked modules that exhibit emergent
- Your project must have more than one level of interaction and must afford the intended modes of interaction.
- It must be meaningful to users beyond the element of surprise.
- It must be functional for the presentation.
Each team will provide one in class presentation of the prototype and final project on the respective due dates.
Each team will provide one HARD COPY of their proposal on the 2nd November.
Each team will provide one submission of the proposal and final project documentation, which MUST be posted on Github by the respective due dates.
Choose only one team member’s ONLINE CART 360 Github repo to post to.
Highlight the chosen Github url in the printed proposal.
Make a directory at the top level of this repository labelled FINAL_ASSIGNMENT_THEN and place all items in there.
Please Note: We will not look for your documentation in any other location other than the github url that you provided in the proposal.
DELIVERABLES: PROPOSAL – NOVEMBER 2nd (5%)
- Design and Prepare a printed document that outlines your project proposal and contains the following:
- A name for your project + team member names
- Github url for documentation
- A non-technical description of the themes and major elements of the project that answers the four questions at the top of the page (minimum 250 words per question)
- Describe your project’s levels of interaction through a storyboard
- Research and give a brief summary (minimum 250 words each) of at least three similar projects.
- Write a paragraph on how/why your project will be different and more interesting in comparison to the projects you researched.
- If working in a team, list each team member’s role and responsibilities.
- Put a digital copy of your printed document (as a pdf) into the appropriate directory of the github repository by the due date.
DELIVERABLES: NOVEMBER 16th (10%)
Bring a working prototype to class. Each team will have to present their progress to us individually.
This deadline will allow you to receive feedback and have the time to resolve any issues before the final due date.
DELIVERABLES: NOVEMBER 30th & DECEMBER 7th (20%)
- Present and demonstrate your functioning project in class. (November 30th)
- Post the following to the appropriate github repository (December 7th)
- Documentation of ALL your research process
- The schematic of the electronics involved in your project
- All source code
- Photos of the progress and minimum five photos of the finished project
- Videos of the progress and a video documentation of the finished project