P3: Functional Prototype, Project Presentation and documentation
The goal of this project milestone is to implement, present, and document a functional prototype of your project. By 12/6, your prototype should be complete in the sense that you are ready to demonstrate the tasks you discussed in your conceptual design. When possible, user interactions should be live, not canned responses.
On 11/22 in class, your team will briefly present a progress report to the class. Describing what you have accomplished since the proof-of-concept presentation.
Part A: Presentation and demonstration
On 12/6, your team will present your project to the class and to guests. You will have a 20-minute time slot, 12 minutes for team presentation and 8 minutes for peer critique, questions and answers.
Your task then is to prepare a 12 minutes presentation (feel free to use Power Point or Prezi) that covers the following:
- Problem statement: what is the goal of the system? what problems it addresses? who are the intended users of this system? and what are the main tasks they can accomplish by using it?
- Conceptual design: show sketches of your envisioned system that illustrate the context in which it operates , the components of the system, and its envisioned look .
- Design process and artifacts: present your early stage design artifacts (storyboard, and low fidelity prototypes). Discuss what you learned from these prototypes and how your design has evolved based on their critique.
- Functional prototype: show a video clip that shows how your functional prototype operates. You video clip should demonstrate how the system can be used to complete the tasks you discussed as part of your problem statement. Discuss the implementation details of your prototype (in terms of development environment, information architecture, communication etc).
- Critique: discuss the strengths and weaknesses of the design and implementation of your system. What future work on this project may include?
All team members should actively participate in the presentation. Be ready to demonstrate your prototype in the lab, following the presentation. A copy of the presentation should be uploaded to Google Docs and shared with the course Google group by 12/6 at 12:30 pm. Document the development process (and especially your part) in your blog.
Part B: Documentation
By 12/13 you should email to the course Google group a link of a website that document your project. In addition you should submit a documented version of your source code. You should also complete and update your personal blog.
The project website should include the name of your project, the names of all team memeber as well as cover all the materials that were discussed in your final presentation:
- Problem statement
- Conceptual design
- Design process and artifacts
- Functional prototype: show a video clip that demonstrates your functional prototype.
Your source code folder should be uploaded to Google Docs and shared with the course Google group.
Your personal blog should be updated with details about the design and implementation of your project. You should elaborate on your part in the design and implementation of your project. You are also encourage to reflect back on the ideas and concepts we discussed in this course.