Commit 793b047e authored by Ellie's avatar Ellie

hci project, in progress

parent b32d5732
......@@ -12,115 +12,40 @@ menu:
---
The design project is meant to give you hands-on experience with a variety of techniques for HCI design. By the end of the quarter you will have engaged in substantive individual as well as group work, and should have material of appropriate quality for including in a portfolio to demonstrate your knowledge of HCI methods.
The design project is meant to give you hands-on experience with a variety of techniques for HCI design. By the end of the quarter you will have engaged in substantive individual as well as group work, and should have material of appropriate quality for including in a portfolio.
In week 1, you will conduct observations of people using technology individually as a basis for inspiring your project.
In **week 1**, you will conduct observations of people using technology individually as a basis for inspiring your project.
In weeks 2-5, you will work with a team to conduct further research on a shared topic, and identify a problem that you will address through a design project.
In **weeks 2-6**, you will work with a team to conduct further research on a shared topic, and identify a problem that you will address through a design project.
In weeks 6-10, you will develop a response to your problem through prototyping and initial user evaluation.
In **weeks 7-10**, you will develop a response to your problem through prototyping and preliminary user evaluation.
During the scheduled finals time slot, you will present your work to the rest of the class.
During the scheduled **finals** time slot, you will present your work to the rest of the class. Each of, you, individually, will close the term by writing a reflection on your experience in the course, including both the sketching activity & your engagement in this user-centered design project.
Each of, you, individually, will close the term by writing a brief reflection on your experience working through a user-centered design process for the first time.
_Note: Directions for each milestone are subject to change until the date that
the milestone is assigned and discussed in class._
_Note: Directions for each milestone are subject to change until the date that the milestone is assigned and discussed in class._
| Milestone | Individual/Group | Due Date | Points |
|:---|:---|:---|:--|
| [D0: Observation Report](#d0-observation-report) | Individual | Sun, Jan 13, 11:59p | 5 |
| [D1: Framing Your Design Challenge](#d1-framing-your-design-challenge) | Group | Sun, Jan 20, 11:59p | 5 |
| [D2: Research + Problem Statement](#d2-research-problem-statement) | Group | Sun, Feb 10, 11:59p| 10 |
| [D3: Design Proposal](#d3-design-proposal) | Group | Sun, Feb 24, 11:59p | 10 |
| [D4: Evaluation Plan](#d4-evaluation-plan) | Group | Sun, Mar 3, 11:59p | 2 |
| [D5: Final Design Report](#d5-final-design-report) | Group | Sun, Mar 17, 11:59p | 8 |
| [D6: Case Study Presentation](#d6-case-study-presentation) | Group | In Class, Final Exam Period | 5 |
| [FR: Final Reflection](#individual-reflection) | Individual | Fri, Mar 22, 5p | 10 |
### D0: Observation Report
**This milestone should be conducted individually**
For this milestone, you will conduct at least 40 minutes of observation in public, in order to learn about how people use technology in a context that you find interesting. The goal of this milestone is to get you thinking about how some technology is really used in the world, and to inspire ideas of topics for your final project.
#### Logistics
**Assigned & Discussed in Class:** Monday, January 7
**Due:** Sunday, January 13, 11:59p
**Turn In:** A _**single**_, _**well-organized**_ `.docx` file to the appropriate folder on D2L.
#### Directions
You should conduct two periods of observation in a public location. Each period should be at least 20 minutes long. You should vary either the time or location of your 2 observation periods meaningfully.
Because this is a very short class assignment, and you are a novice, you should
not conduct any observations in a location where people would have a
reasonable expectation of privacy. **Exception:** _**With permission**_, you may observe someone else in this class if you want to study something that does not occur in a public location -- e.g., if you want to observe how someone follows a recipe to cook something in their kitchen. You must get my okay in advance for what you plan to observe.
- For example, you might observe for 20 minutes at the food trucks at lunch time, and come back and conduct observations again at the same location for 20 minutes at 5pm.
- Or, you might observe people at the bus stop near city hall from 4:45-5:15 on one day, and observe people at Urban Plaza on PSU campus from 12:00-12:20 on another day.
You may take field notes in a medium of your choice (e.g., on your phone, laptop, or in a small notebook).
- Field notes should total **at least 4 pages** in length. It's okay if they are really messy. Field notes will not be graded for grammar, etc. We just want to see that you took notes in the field. I should see things like time stamps, written notes, small sketches or maps of the location. You can see examples of my own field notes in the lecture slides from January 7.
| [D0: Team Contract](#d0-team-contract) | Group | Sun, Jan 19, 11:59p | 5 |
| [D1: Research Report + Problem Statement](#d1-research-report-problem-statement) | Group | Sun, Feb 16, 11:59p| 10 |
| [D1P: Research Presentation](#d1p-research-presentation) | Group | In class, Week 7, Meeting 1 (Feb 17 or 18) | 5 |
| [D2: Design Proposal](#d2-design-proposal) | Group | Sun, Mar 1, 11:59p | 10 |
| [D3: Design Case Study](#d3-design-case-study) | Group | Sun, Mar 15, 11:59p | 10 |
| [D3P: Case Study Presentation](#d6-case-study-presentation) | Group | In Class, Final Exam Period | 5 |
| [FR: Final Reflection](#individual-reflection) | Individual | Fri, Mar 20, 5p | 15 |
- You should make **at least 4 sketches** while conducting observations, depicting scenes from your field site that are relevant to your understanding of how people are using (or not using) some technology.
#### Report Specification
### D0: Team Contract
Your report will contain two parts: a 1-2 page memo about your observations, and an appendix containing the raw materials documenting your work.
##### Memo
- **Summary (1-3 paragraphs):**
- Date, times, and location of observations. How and why did you choose these locations/days/times?
- List 3-5 interesting things you noticed. Explain why they are interesting.
- Did you notice any problems that people were having with technologies or notice situations or experiences that you think could be better? Do you have any new ideas for a design project?
- **Reflection (1-3 paragraphs)**: Reflect on the experience of conducting observations.
- Have you ever conducted observations before?
- What new things did you notice that you have not paid attention to before?
- What distracted you? Did you get bored?
- What parts of this assignment were easy? What was challenging?
- What would you do differently the next time you want to conduct observations?
##### Appendix
- **A copy of your field notes.**
- If you only have hand-written notes, please scan these or take high resolution photographs so that you can embed them in your report. Do not turn in multiple images.
- These should be at least 4 letter-size pages long (for example, if you took notes in a very small 3"x5" notebook, you should have ~16 pages).
- **The 4 sketches** you created while conducting observations.
- Each sketch should be captioned with a brief (1-4 sentence) description of what it is showing.
- Again, you must integrate these images into your report document. Do not upload separate images.
- If sketches are already integrated as part of your field notes that is fine, you do not need to include them twice. However, please do include brief descriptions of each sketch. You can include these on an additional page following the field notes.
#### Grading
This assignment is worth five points. It will be graded fairly simply.
- **0 points**: Not turned in
- **3 points**: Only partially fulfills the requirements. Some sections are significantly lacking.
- **~~3.75~~ 4 points**: Mostly meets requirements, but something silly is wrong, e.g., only included 3 sketches instead of 4.
- **~~4.25~~ 4.5 points**: All three sections (summary, reflection, appendix) are complete and fully meet the requirements.
- **5 points**: Assignment goes beyond the basic requirements, and demonstrates a thoughtful engagement with the process of conducting observations. Reflection includes references to course readings and/or discussions.
### D1: Framing Your Design Challenge
This is your first group milestone, and should be a very short turn in. It is mostly just about team logistics, and making sure you are all set up for a successful quarter. Should be 5 very easy points.
This is your first group milestone, and should be a very short turn in. It is mostly about team logistics, and making sure you are all set up for a successful quarter. Should be 5 very easy points.
#### Logistics
**Assigned & Discussed in Class:** Monday, January 14
**Assigned & Discussed in Class:** Week 2, Meeting 1
**Due:** Sunday, January 20, 11:59p
**Due:** End of Week 2 / Sunday, January 19, 11:59p
**Turn In:** A _**single**_, _**well-organized**_ `.docx` file to the appropriate folder on D2L.
**Turn In:** A _**single**_, _**well-organized**_ `.docx` or `.pdf` file to the appropriate folder on D2L.
The memo should include:
......@@ -137,7 +62,7 @@ The memo should include:
- Does anyone on your team have a major time commitment this quarter that may make it hard for them to contribute to the project during some period of time (e.g., a week long work trip, a best friend's wedding, a really important midterm in a really hard class)? How will you work around these commitments?
- When/how will you work outside of class? Will you have a regular meeting or schedule meetings as needed?
- What tools will you use to collaborate: e.g., will you use Google Docs to draft text, and provide feedback to each other there? If not, what is your alternative plan?
- An outline of individual responsibilities and project timeline: What are all the things that need to be done in each of the next 2 weeks so that you will be ready to turn in your D2 assignment on February 10? Who will take the lead on each of these tasks? Who will take the lead on motivating and coordinating the group, making sure everyone else has done their part?
- An outline of individual responsibilities and project timeline: There are a lot of moving parts between now and your first major milestone, due in week 6. Make a specific timeline with clear responsibilities and internal deadlines ahead of the class submission deadline. Who will take the lead on each of these tasks? Who will take the lead on motivating and coordinating the group, making sure everyone else has done their part?
- An outline of individual contributions so far. What has each person done to contribute to this first milestone? (_You will write a brief summary of individual contributions with each milestone. Please know that I read these, and will adjust grades accordingly._)
- Request for Feedback:
- What kind of feedback do you want from me right now? What questions do you have?
......@@ -152,34 +77,38 @@ This is worth 5 points towards your final grade. All group members will receive
- **5: Memo is not only complete but also thoughtful. It could be used as an example of excellent work in a future class.**
### D2: Research + Problem Statement
### D1: Research Report + Problem Statement
For this milestone, you will summarize your initial research findings, and revise your original design challenge into an actionable problem statement.
For this milestone, your team will conduct at least 4 interviews with stakeholders relevant to your design challenge. You will summarize your initial research findings, and revise your original design challenge into an actionable problem statement.
As part of this milestone, you should conduct at least 2 20-minute periods of observation and 4 15-minute interviews (total, split across the entire team).
This is a group project.
**Due:** Sun, Feb 10, 11:59p
**Due:** End of week 6 / Sun, Feb 16, 11:59p
**Turn in Directions:** You should upload to D2L:
- 4 audio files or other proof of completing the interviews
- a _**single**_, _**well-organized**_ `.docx` file containing all other required contents.
- A single zip file containing:
- 4 audio files or other proof of completing the interviews
- A _**single**_, _**well-organized**_ `.docx` or `.pdf` file containing all other required contents.
**Grading:** This project is worth up to 10 points. All team members will receive the same grade unless there is a major work discrepancy, in which case I may lower the grades of those who do not contribute to the assignment.
#### Directions
1. Conduct at least 1 additional 20-minute observation.
2. Conduct at least 4 interviews. You should complete these interviews no later than **the start of Week 4**
3. Create an affinity diagram in class in Week 4 to begin analyzing your data.
4. Create one additional diagram of your choice.
5. Refine your initial design challenge into a short 1-2 paragraph problem statement. (We will discuss in class in Week 4.)
6. Create two personas / persona stories / modular personas. (We will discuss in class at the start of Week 5.)
1. Conduct at least 2 20-minute observations.
2. Conduct at least 4 interviews. You must have completed all of these interviews no later than **the start of Week 6**
3. Create three diagrams or other data representations to summarize your major research findings. _We will discuss diagrams/maps/representations further in class in Week 6._
4. Refine your initial design challenge into a short 1-2 paragraph problem statement. _We will discuss problem statements in class in Week 5, but you should finalize this at the end of week 6._
##### Observation Requirements
<!-- TODO: copy in from old D0 milestone -->
##### Interview Requirements
- At least 3 of your interviews must be at least 10 minutes long. (You can have one failure! But after that, you need to redo them if they aren't lasting at least 10 minutes.)
- At least 3 of your interviews must be at least 15 minutes long. (You can have one failure! But after that, you need to redo them if they aren't lasting at least 15 minutes.)
- Prepare an interview guide with at least 10 questions on it before the first interviews.
- Revise the interview guide between interviews
- Record the interview. You MUST SECURE EXPLICIT PERMISSION from the interviewee before starting the recording!
......@@ -187,19 +116,21 @@ This is a group project.
- At least 1 interviewee must be someone who is NOT a computer science major.
##### A list of diagramming & mapping techniques:
##### Diagramming/Mapping/Representation Requirements:
You should create three diagrams for this project. At least one diagram must be focused on the _who_ of your project and one must focus on the _what_ of your project. We will discuss options in class in Week 6. Here is a list of resources:
- Experience Mapping from Adaptive Path [[Website]](http://mappingexperiences.com/) and [[Guide]](http://ellieharmon.com/wp-content/uploads/Adaptive_Paths_Guide_to_Experience_Mapping.pdf)
- IDEO HCD Toolkit: [Frameworks (Journey Maps, Relational Maps, 2x2s)](https://drive.google.com/open?id=11qd21HlISl2m57mkTW1YitRtT_NmIdEF)
- IDEO HCD Toolkit: [Journey Maps, Relational Maps, 2x2s](https://drive.google.com/open?id=11qd21HlISl2m57mkTW1YitRtT_NmIdEF)
- Universal Methods of Design: [Cognitive Mapping](http://ellieharmon.com/wp-content/uploads/UMD-Cognitive-Mapping.pdf)
- Universal Methods of Design: [Concept Mapping](http://ellieharmon.com/wp-content/uploads/UMD-Concept-Mapping.pdf)
- Universal Methods of Design: [Thematic Networks](http://ellieharmon.com/wp-content/uploads/UMD-Thematic-Networks.pdf)
- Universal Methods of Design: [Stakeholder Maps](http://ellieharmon.com/wp-content/uploads/UMD-Stakeholder-Maps.pdf)
- EMPATHY MAPS in the d.school [Understand Mixtape](https://drive.google.com/open?id=1lMoG9lVgkGAyJrSyu2N4cs3bHeWwrb98)
- Please ask on Twist if you have another idea of a map or diagram you want to use to make sense of your data.
- Personas <!-- TODO: links -->
#### Document Specification
#### Document Specification:
You should turn in a single document which includes, in an organized fashion:
......@@ -211,11 +142,11 @@ You should turn in a single document which includes, in an organized fashion:
2. **Research Summary:**
- **Observation Summary:**
- 1-3 paragraphs summarizing your new observation.
- Date, time, and location of observation.
- 1-3 paragraphs summarizing your 2 relevant observations.
- Date, time, and location of observations.
- How and why did you choose this location/day/time?
- 3-5 key findings -- what did you learn and why is it relevant?
- If there were any relevant findings from the observations that any team members completed for the D0 milestone, please briefly review those findings in a bulleted list.
- If there were any relevant findings from the observations that any team members completed for the first sketching assignment, please briefly summarize those findings in a bulleted list.
- **Interview Summaries:** For **each** interview, write a short (2-3 paragraph) summary of the interview. This should include:
- The setting of the interview
- The length of the interview
......@@ -223,57 +154,64 @@ You should turn in a single document which includes, in an organized fashion:
- Is the interviewee in this class?
- What is your relationship to this person (e.g., friend, family, roommate, classmate, stranger?)
- What is their major?
- Why did you choose to interview this person? What about them makes them a good candidate for an interview?
- Why did you choose to interview this person? What about them makes them a good candidate for an interview about your project?
- **Do NOT include any personally identifiable information (e.g. no names)**.
- 3-5 key findings -- what did you learn and why is it relevant?
- **Research Reflection:** 2-3 paragraphs reflecting on your experience conducting research for this milestone.
- This reflection should include answers to questions such as: What did you do differently in this round of observations? Do you feel your observation skills have improved? What would you do differently the next time you conduct user research -- observations and research both? What kinds of things did you learn from interviewing vs. observation? What parts of this research were easy/challenging, and why? How and why were each of your four interviews different?
3. **Data Analysis Diagrams**
1. A photo of the affinity diagram you made in class.
2. A photo of the second diagram your team chose to make.
3. A short reflection that answers each of these questions:
- What 2nd diagram did your team choose to make?
- Why did you chose this diagram?
- Who participated in the 2nd diagramming activity?
- How did this activity differ from affinity diagramming?
- Were these diagramming activities useful? Why or why not?
- For full credit, this reflection _must_ include references to course readings on relevant topics such as interviewing, observing, and research ethics.
3. **Data Analysis Diagrams/Maps/Representations**
1. A photo or digital version of the three diagrams/maps/representations you chose to make.
2. Relevant captions for each diagram that summarize it's contents and relevance to the design project.
3. A short reflection that answers, at minimum, each of these questions:
- What diagrams have you included?
- Why did you chose each diagram?
- Who participated in each diagramming activity?
- Were these activities useful? Why or why not?
- What would you do differently next time?
4. **Problem Statement**
- Refine your topic area into a clear problem statement that explains the problem that you will tackle in your project. This should be 1-2 paragraphs long, and meet the criteria discussed in class in Week 4.
5. **Personas / persona stories / modular personas**
- Explain the problem you want to solve from the perspective of 2 prospective users. Each persona story should include at least 1/2 page of text as well as one image or visual, and **follow the guidelines discussed in class on Monday February 5**.
- Refine your topic area into a clear problem statement that explains the problem that you will tackle in your project. This should be 1-2 paragraphs long, and meet the criteria discussed in weeks 4 & 6.
- Your problem statement should be clear as to whether you are embarking on a traditional user-centered design project or a critical design project.
6. **Appendix**
5. **Appendix**
- **Interview Questions**
- A photo or scan of the interview guide you used from each interview.
- The TA must be able to tell from this photo/scan that you took
notes as you went through the interview.
- The TA should also be able to tell from this document that you
revised your questions at least once.
- The TA must be able to tell from this photo/scan that you took notes as you went through the interview.
- The TA should also be able to tell from this document that you revised your questions at least once.
#### Grading
- **0/10: Not turned in or contains plagiarized content.**
- **5/10: Turned in something that is partially complete.**
- **+1 point: Cover page & Document Organization** - Cover page includes all listed elements, and document is well-organized.
- **+1 point: Research components** - Research sections are complete and show evidence of completing 4 interviews + 1 observation period.
- **+1 point: Research components** - Research sections are complete and show evidence of completing 4 interviews + 2 observation periods.
- Half of the grade for the research component is based on your reflection quality: Is it thoughtful? Does it show evidence of your engagement with the course readings and/or other materials and of your learning?
- **+1 point: Data Analysis** - Both required diagrams are present and show evidence of completing the task.
- **+1 point: Data Analysis** - Three required diagrams are present and show evidence of completing the task.
- Half of the grade for the data analysis component is based on your reflection quality: Is it thoughtful? Does it show evidence of your engagement with the course readings and/or other materials and of your learning?
- **+1 point: Problem Statement** - Problem statement is complete, and _meets criteria discussed in Week 4_: it is grounded in data and/or research, it is framed in a way that invites creative solutions (but does not specify a solution), it is specific about where/when/why/how a problem is occurring.
- **+1 point: Personas** - 2 personas are included, each includes some kind of image or diagram, each is grounded in data/research, each one tells a _story_.
- A quarter of your personas grade is a subjective measure of presentation quality: how well have you designed your persona presentation? How well are they communicating your ideas? Does it appear that you put some thought into their visual layout or did you just throw a stock image on a page and write a paragraph underneath?
- **+1 point: Problem Statement** - Problem statement is complete, and _meets criteria discussed in Week 4_: it is grounded in data and/or research, it is framed in a way that _invites creative solutions_ (but does not specify a solution), it is specific about where/when/why/how a problem is occurring, it includes criteria for judging the validity of a proposed response/solution (but **does not propose a solution**).
- **+1 point: Quality** - There are two parts to the quality grade:
- Taken as a whole, your report tells a compelling _story_ about your problem statement, that is clearly grounded in data & research.
- Taken as a whole, your report shows evidence of good design, presentation, and communication skills. Did you put some thought into the visual layout? Do your diagrams/maps/representations look professional and show evidence of creativity? Did you crop and rotate images appropriately? Did you caption things? Did you integrate images and text together in compelling ways? If I received this brief as a client, would I feel confident that I should continue to pay you money to do design work for me?
### D1P: Research Presentation
For this milestone, you will present the results of your research, and share your problem statement with the class.
Due: In class, Week 7, Meeting 1 (Feb 17 or 18)
Points: 5
### D3: Design Proposal
### D2: Design Proposal
For this milestone, you will come up with multiple solutions to your design problem, and propose one of them for moving forward with.
This is a group project.
**Due:** Sun, Feb 24, 11:59p
**Due:** Sun, March 1, 11:59p
**Turn In Directions:** You should upload a _**single**_, **_well-organized_** `.docx` or `.pdf` file to D2L, containing all required components. **Just one file per group**
......@@ -281,6 +219,7 @@ This is a group project.
#### Directions
**Part 1: Brainstorming**
We will have a brainstorming session in class in Week 6 to get you started on this milestone.
......@@ -368,66 +307,24 @@ Turn in a single, well-organized file, with all of the following sections:
- **+1.5 point: Reflection + Overall Quality** - The reflection is comprehensive and, at minimum, responds to all questions listed above. For full credit, your report should show evidence throughout of your engagement with course readings/materials, and of your _learning_ even if all elements are not perfectly executed.
- Because much of design work is about communication, half of this grade is devoted to overall presentation quality. For example, do your storyboards look neat and professional? Are they doing a good job of communicating your solution-in-context? Have you proof-read your text sections? Are they easy to read and understand? Do you use things like headers and page breaks to separate content?
### D4: Evaluation Plan
This is a group project. It is worth 2 points.
<!-- TODO: Wrap up old prototype/eval plan stuff into an in-class activity for Week 9 -->
This is a brief turn in to make sure you are on track with an evaluation and prototyping plan. This is adapted from the "Determine what to Prototype" activity in the IDEO UCD book.
#### Logistics
### D3: Design Case Study
**Assigned & Discussed in Class:** Week 8, Meeting 1
| [D3: Design Case Study](#d4-design-case-study) | Group | Sun, Mar 15, 11:59p | 10 |
**Due:** Sunday, March 3, 11:59p
As part of this milestone, you will create paper or other low-fidelity prototype of your chosen design solution, and conduct some simple evaluations of the system.
**Turn In:** A _**single**_, _**well-organized**_ `.docx` or `.pdf` file to the appropriate folder on D2L.
You will then write a retrospective case study that reviews your entire project to date.
#### Document Specification
The memo should include:
- Your team name.
- All team member names.
- Contribution summary for this milestone. Who did what?
- A _brief_ (2-5 sentence) summary of each of the following:
- Your problem statement.
- Your proposed solution.
- A list of the key elements of your idea. What are all the pieces you _could_ test? This list might include particular interface features or questions about use-in-context.
- Choose 2-3 questions you want to answer with your evaluation. _What part_ of your project do you want to test.
- What evaluations will you conduct to answer these questions?
- Think through what kind of prototype you need to build to answer these questions and conduct these types of evaluations. What will you build and how will you build it? _Hint: It may be easier to build multiple smaller prototypes, each targeted for a particular evaluation, rather than build one giant prototype that you try to use for everything._
- A list of responsibilities with a timeline:
- Lead person for prototype building.
- Date that prototype will be complete.
- For each evaluation you will conduct:
- What is it (think aloud, heuristic, cognitive walkthrough)?
- Who is going to do it?
- When will it be done?
- When will the report/form be completed for that evaluation?
- Request for Feedback:
- What kind of feedback do you want from me right now? What questions do you have?
#### Grading
This is worth 2 points towards your final grade. All group members will receive the same grade.
- **0: Not turned in or contains plagiarized content.**
- **1: Turned in something.**
- **2: Complete and high quality work.**
### D5: Final Design Report
For this milestone, you will create paper or other low-fi prototypes for your chosen design solution, and conduct some simple evaluations of the system.
This is a group project. It is worth 8 points.
This is a group project. It is worth 10 points.
#### Logistics
**Assigned & Discussed in Class:** Week 8, Meeting 1.
**Assigned & Discussed in Class:** Week 9, Meeting 1.
**Due:** Sun, Mar 17, 11:59p
**Due:** Sun, Mar 15, 11:59p
**Turn In Directions:** You should upload a _**single**_, **_well-organized_** `.docx` or `.pdf` to D2L, containing all required components.
......@@ -435,21 +332,26 @@ This is a group project. It is worth 8 points.
##### Prototyping Tools
I recommend paper. Here is an example of using [paper prototyping for website development](http://alistapart.com/article/paperprototyping)
I recommend paper. Here is an example of using [paper prototyping for website development](http://alistapart.com/article/paperprototyping). Here is the video we watched in class: <!-- TODO: add link to google video here -->.
For mobile apps, you might consider using a tool like [POP App](https://marvelapp.com/pop/) to make your paper prototypes come alive!
You can do something similar with presentation software like [PowerPoint](http://boxesandarrows.com/interactive-prototypes-with-powerpoint/), also see this article on [PowerPoint](http://keynotopia.com/guides-ppt/).
You may also use specialized tools like [Sketch](https://www.sketchapp.com/), [UX Pin](https://www.uxpin.com/), [Balsamiq](http://balsamiq.com/) or [Mockingbird](https://gomockingbird.com/mockingbird/#). It will take you longer. You have been warned.
You may also use specialized tools like [InVision](https://invisionapp.com) or [Sketch](https://www.sketchapp.com/). It will take you longer. You have been warned.
Some people like to use diagramming tools like Visio or OmniGraffle.
#### Directions
1. Create a prototype! See prototyping tools section above. Your prototype must be detailed enough to allow you to examine at least one of the use cases described in your storyboards turned in for the last milestone. If you have a major issue with this, you should meet with me about what is an appropriate scope for your prototype.
2. At least **two** of your team-members should **separately** conduct **one** self-reflective evaluation. You may choose to conduct either a cognitive walk-through or a heuristic evaluation. Each team mate can do the same one, or you can do different ones.
<!-- TODO: Clean all this up. Remove the terrible forms. -->
1. Create a prototype! See prototyping tools section above.
- Your prototype must be detailed enough to allow you to examine at least one of the use cases described in your storyboards turned in for the last milestone. If you have a concern about this, please meet with me about an appropriate scope for your prototype.
2. Conduct four evaluations of your proposed system: 1 reflective evaluation, and 1 evaluation that involves a prospective user.
At least **two** of your team-members should **separately** conduct **one** self-reflective evaluation. You may choose to conduct either a cognitive walk-through or a heuristic evaluation. Each team mate can do the same one, or you can do different ones.
- **Heuristics Details**: Consider [Jakob Neilsen's famous list](http://www.nngroup.com/articles/ten-usability-heuristics/) or others that we discussed in class, or another of your choosing. If you choose your own, you **must explain where you found it, why you chose it, and why I should believe it's a legit list.**
- You should use this form for recording your heuristic evaluations: Usability Aspect Report [UAR Word Template](https://drive.google.com/open?id=1sv3dMNvk3_e9wv8-qJz-GlaRor2gXzm3)
- **Cognitive Walkthrough Details**: These two write-ups give detailed examples of using the method: [Wharton et al 1994](https://drive.google.com/open?id=1Mk9txWxZB92AEghQNqZjX0v4JHFbyCba) OR [Spencer et al 2000](https://drive.google.com/open?id=1L8Aio1Ijve1tAccVVbWK_A8bPqM_x95L). You may follow the style of either one (they are different!). Regardless, you should use the form linked in the document specification below to record your findings.
......@@ -494,6 +396,8 @@ Turn in A SINGLE well-organized file containing:
### D6: Case Study Presentation
| [D3P: Case Study Presentation](#d6-case-study-presentation) | Group | In Class, Final Exam Period | 5 |
During the Finals time slot, each team will give a short (5-10 minute)
presentation on their design project.
......@@ -531,7 +435,9 @@ You may want to review [Designing Case Studies: Showcasing a Human-Centered Desi
### Individual Reflection
**This milestone should be completed individually. It is worth 10 points.**
| [FR: Final Reflection](#individual-reflection) | Individual | Fri, Mar 20, 5p | 15 |
**This milestone should be completed individually. It is worth 15 points.**
In this assignment, you will each reflect, individually, on your experience going through one cycle of an HCI design process, and what you’ve learned in this class.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment