Final Project Deliverables

Due dates
Final presentations will take place during our final exam time slot of 2-4 pm on Thursday, December 17. All deliverables are due by 5 p.m. on Thursday, December 17.
Collaboration
Your final presentation, demo, and design documentation will be completed with your project team. Each student will submit an individual reflective essay.
Submitting your work
Your design documentation and slides should be shared with me (and your team) through Google Drive. I should receive an email (or text message?) inviting me to view your prototype. You will submit your reflective essay as a CLEo assignment.
Grading
140 points are distributed across the deliverables, as described below.

Overview

In the final assignments you will incorporate the feedback from  your hi-fi test to produce the final iteration of your iterface design. You will  then prepare:


Using hi-fi prototype test results

You should use the results and conclusions of your hi-fi prototype test along with any feedback we gave during your hi-fi prototype presentation. You should fix as many problems as you can, prioritized by severity. This is also your last change to design as much missing functionality as you can. The prototype should illustrate (or at least suggest) more functionality than just your three target tasks.

Please talk with me if you have questions about the overall scope of your project.

Presentation (25 points)

During during finals week, you will present your design to your peers and community partners.

Thursday, December 17:

Each presentation slot will be short: up to 20 minutes plus 5 minutes for questions. I will arrive early for extra time to set up, and I encourage you to do so as well.

Motivate your application, explain your target users and tasks, and demonstrate the final prototype. There may not be time for the complete story. Focus on the needs of your users and the benefits your solution provides. Assume the audience will not have seen your project before: make the presentation understandable and compelling for them.

You should convey a sense of your iterative process and how the design evolved from iteration to iteration. However, this presentation should focus less on the details of how the design changed in the most recent iteration and more on the big picture. Discuss at least one major insight from your interactions with users or other key stakeholders.

You may demonstrate your prototype live or include a video walkthrough in your presentation.

Here is one possible outline for your presentation:

These presentations will be public presentations. I will email you an invitation that you should forward to your community partners or other key stakeholders. You may also invite friends or others you would like to see your work.

In the future this should be more points and combined with the demo. Here's the point breakdown for Fall 2015:

Demo (15 points)

Design documentation (60 points)

Write a summative report containing the following information. Much of this can be gleaned from your previous investigation reports.

Put your report on Google Drive. Share it with me and with key stakeholders.

Mission statement (5 points)
What problem do you aim to solve? What is your overall approach? (1 paragraph)
Competitive analysis (5 points)
How is your approach distinct from existing approaches? (1 paragraph)
Target user group(s) (5 points)
Who will use your application? Are there other key stakeholders? (1 paragraph)
Task requirements (10 points)
What tasks do you aim to support? Include important tasks you discovered and would eventually aim to include in your app, whether they are supported in your prototype or not. I encourage you to present tasks in role-feature-reason format, which is often used by software developers:

As a kind of user,
I want to accomplish some task,
so that some larger purpose is achieved.

Non-functional requirements (5 points)
What are the non-task requirements for your app? For example, a ticket sales machine needs to be easy to for infrequent users to learn, and it is used in a place that is sometimes crowded and noisy. Non-functional requirements may come from your answers to the task analysis questions, or you may have learned them when getting feedback on your prototypes. (1 paragraph or a bullet list)
Prototype walkthrough (15 points)
Walk through your target tasks. Explain other features of your prototype not included in the target task walkthrough. Your goal is to convey a clear system image for key stakeholders and future software developers.
You may use text, storyboards, and annotated screenshots to explain your prototype, or you may link to a narrated screen recording video.
Design process (10 points)
Give a brief overview of your design process for someone who is not familiar with the assignments you were given. Identify a few key insights from different stages of your process. (2-3 paragraphs or a bullet list)
Next steps (5 points)
If you were going to continue development of your app, what would your next step(s) be? What questions are most urgent to answer next, and how would you answer them? Before writing your response, step back and consider the entire human-centered design cycle.(1 paragraph)

Individual reflection (40 points)

Write a 400-800 word essay addressing one of the following prompts:

Although you may have many ideas, choose one big idea (or a few closely related ideas) to discuss in depth.

Your essay should have a clear thesis statement supported by concrete evidence from your experiences. To place what you learned in context, you should quote or paraphrase course texts, using any citation style you choose. In my assessment, I will also consider the  organization and readability of your essay.

You may discuss the content of your individual reflection with anyone you choose. You may obtain feedback on your writing from anyone you choose. However, the words and ideas in your individual reflection should be your own.

Submit your individual reflection as an assignment on CLEo.


Janet Davis (davisj@whitman.edu)

Created December 3, 2015
Last revised December 18, 2015

Acknowledgments: Presentation and demo from assignments previously adapted by Björn Hartmann and Maneesh Agrawala at UC Berkeley and by Jim Boerkel at Harvey Mudd College. The remaining parts are my own.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License.