Independent Research Projects
Last modified by Hal Eden on 2010/08/20 11:06
Projects
deadline to submit final report: Monday, Dec 8, 2:00pm| Members | Title |
|---|---|
| Will Baird, Dara Cunningham, Matt Smith | Exploring User Centered Design Techniques in Architectural Models using 3D Simulations |
| Chris Baker, Jeff Hoehl, Jane Meyers | EDC Remixed |
| Dain Cilke, Matt Clark, Scott Keller, Ian York | Class Wiki v2? |
| Daniel Delany, Diana Tamabayeva | Freebase and the Collaborative Semantic Web |
| Mason Hauck, Amanda Orin, Stephanie Pitts | Rate Your Landlord |
| Kyle Madruga, Isaac Guererro, Tom Huber | Improving Google Maps Walking Directions Through Crowd Sourcing |
| Amanda Porter, Stephen Butler, Kate Starbird, Zac Taschdjian | Motivation and the Use of Tools in Online Environments |
| Pierce Edwards, Jacob Wisnesky, Joe Lilly, Colin Rieger, Janusz Strzepek | MMOs as a Source of DSS Study |
Format for Final Report
Maximum total length: 8 pages- Title
- Authors
- Abstract
- Keywords
- Statement of the Problem—including how your understanding of the problem has changed while you have worked on it over the period of the course
- Rationale—explain why the problem is interesting or important? Relate it to other systems and the literature! Why should someone else be interested in the problem chosen by you?
- Relationship to the Course—describe how your research is related to the topics which we discussed in the course
- Contribution of Individual Team Members—describe what element of the overall project of each member of your team focused on
- Description of Independent Research
- Non-Implementation Projects:
- Articulate clearly your contribution
- Describe how you advanced the knowledge (e.g., questionnaire, testing of developments, new conceptual framework, empirical data)
- Potential further developments of research - assuming you would have another year to work on: what would you do?
- Implementation Projects:
- Technical approach—discuss the impact of the tools (which you have selected) on the problem solution. Contrast your approach with other approaches to similar problems described in the literature.
- Description of the system—describe the structure of your system in sufficiently abstract terms (so that the reader does not get lost in technical details).
- Description of the system behavior—what does the program do? Illustrate it with a scenario!
- Evaluation of the program / system—it should address questions such as: how well does it work? What are the shortcomings and limitations? Which theoretical issues does it clarify?
- Potential further developments of your program /system—assuming you would have another year to work on: what would you do?
- Non-Implementation Projects:
- References—List the key references, other systems, previous projects on which your work is based.
