Project Abstract & Introduction (Polished)
Submit a second, polished version of your project abstract. If you are building an interactive system as part of your project, include a Scenario, Storyboard, or other form of sketch or prototype that demonstrates concretely what the interaction with your system will look like. Other students will review and critique this work in class on Monday.
Combine your writeup with you related work review in one document. Bring 2 hardcopies to class on Monday 11/8.
The project abstract should cover the following topics:
Research Question: What are you trying to answer? State this as clearly as possible in one sentence.
Hypothesis: what do you think the answer to your question is, and why?
Systems and Interfaces: What hardware or software artifacts will you create? How will user interaction with these systems work?
Method: how will you explore your hypothesis, and why is that the right approach? (This should include the design of your study.) Grounding this in methodologies that other researchers have used (e.g. by drawing from the class readings) is a good idea. There are three major points you should hit here.
- Study design: What are you going to do?
- Evaluation: How will you know you succeeded? What will you measure? How will you measure it?
- Ecological Validity: Why does your study answer your research question? Why does your evaluation address your hypothesis?
Study Recruitment Plan: how will you get participants for your study? For pilot studies, we suggest you recruit from within the class -- "trading" participation with other groups is a great way to learn about what others are doing. For larger studies (e.g. for those not building a system), you need a clear recruitment plan.
Biggest Risk: what's the riskiest component of your project? (may not be able to get the hardware you need, robustly implementing the ___ algorithm may take too long, the difference between conditions may not be measurable, ...)
For the draft, we expect you to cover all topics in 2-3 paragraphs--be concise but concrete in your descriptions. For the final version, you'll want to go into greater depth (approximately 2 paragraphs for each issue, with the exception of the research question, which should still be be one precise sentence).
We encourage you to iterate multiple times on this abstract. While there is only one formally defined point for receiving feedback from course staff, you should seek out more informal feedback as you work on this. E-mail us at any point if you'd like us to take a look at your current submission, or come to office hours if you'd like to discuss in person. You are free to change directions after submitting your draft, but the sooner you nail down a direction, the better your project is likely to be.
You will submit your assignment on this wiki.
Create a Wiki Page for this assignment
Create a wiki page called PolishedAbstract-FirstName1LastName1FirstName2LastName2 and link to it from each group member's personal account page. Replace FirstNames and LastNames with the names of your group members. Then click on the link and enter the information about your assignment.
Describe your project plan on the wiki
On the page you just created, write up your abstract, covering all topics described above in 2-3 paragraph total.
Also add the related work section from last week, so you have one document that covers abstract AND related work.
Add Link to Your Finished Assignment
One you are finished editing the page, add a link to it at the bottom of the page with your full name as the link text. The wiki syntax will look like this: *[[PolishedAbstract-FirstName1LastName1FirstName2LastName2|Firstname1 Lastname1 and Firstname2 Lastname2]]. Hit the edit button for the last section to see how we created the link for our group.
Bring two printouts to class
Bring two hardcopies of your final document to class on Monday 11/8. You will exchange abstracts with other groups and critique each others' work.
Links to Finished Assignments
Add your submission below this line.
- Bjoern Hartmann and Lora Oehlberg
- Kenzan Boo and Linsey Hansen
- Siamak Faridani and David Wong
- Kurtis Heimerl and Bryan Trinh
- Aaron Hong, Brandon Liu, and Richard Shin
- Thejo Kote and Shaon Barman
- Dan Lynch
- Anand Kulkarni and Matthew Can
- Thomas Schluchter and Charlie Hsu
- Matthew Chan and Pablo Paredes
- Arpad Kovacs
- Krishna Janakiraman
- Aditi Muralidharan
- Luke Segars
- Drew Fisher