Commit 9b62a73e authored by Ellie's avatar Ellie

minor hci project fixes, 305 finish major updates, remove tentative flag

parent 9c79b399
......@@ -16,7 +16,6 @@ menu:
parent: "Teaching"
cascade:
tentative: true
quarter: 202001
type: "class"
date: 2019-11-01
......
This diff is collapsed.
......@@ -21,8 +21,7 @@ menu:
| **Meetings**| Thursdays, 4:40 - 6:30, FAB 47 |
| **Final Exam**| [Thursday, 5:30 - 7:20](https://www.pdx.edu/registration/final-exams)\* |
| **Instructor** |Dr. Ellie Harmon <br/> <ellie.harmon@pdx.edu> <br/> she / her / hers |
| **Office Hours** | M+T 4:00 - 5:00<br/>[FAB 120-15](/~harmon8/faq#how-to-find-my-office)<br/>
Or [by appointment](/~harmon8/faq#meetings-with-me)|
| **Office Hours** | M+T 4:00 - 5:00<br/>[FAB 120-15](/~harmon8/faq#how-to-find-my-office)<br/>Or [by appointment](/~harmon8/faq#meetings-with-me)|
| **Prerequisites** | College level reading and writing. Upper division standing. |
| **Website** | <https://web.cecs.pdx.edu/~harmon8/classes/cs305/> |
| **D2L** | Will be used _only_ for assignment turnin and grade return. |
......@@ -258,7 +257,9 @@ projects, including Atom, Eclipse, Mono, Rails, Swift, and many more.
In this course, we will also have a code of conduct.
<p class=".warning">
As a starting point, we will use this [code of conduct](https://docs.google.com/document/d/1ZP-mYO0ss-zSnY0h24V7X4FzbZFDYd2_TbidJqE6qKI/edit?usp=sharing) based on the Mozilla participation guidelines and on feedback from students in prior classes. Please add any comments or suggestions to this document during weeks 1 & 2. We will finalize it at the start of our third course meeting.
</p>
#### What to Do About Harassment
......
......@@ -78,6 +78,7 @@ This is worth 5 points towards your final grade. All group members will receive
## D1P: Research Presentation
This is an informal 4-6 minute presentation in which you will share your research-in-progress with the class and get feedback on your problem statement.
### D1P: Logistics
......@@ -181,7 +182,7 @@ You should create three diagrams for this project. At least one diagram must be
- 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)
- Personas [LUMA INSTITUTE](https://drive.google.com/file/d/1IgjGxy3iFfysnCKJMfpTj2h0aVcpXB6V/view?usp=sharing) + [bolt|peters](https://speakerdeck.com/boltpeters/avoiding-bullshit-personas)
- Personas [LUMA INSTITUTE](https://drive.google.com/file/d/1IgjGxy3iFfysnCKJMfpTj2h0aVcpXB6V/view?usp=sharing) + [bolt|peters](https://speakerdeck.com/boltpeters/avoiding-bullshit-personas)
#### Part 4: Problem Statement
......@@ -439,51 +440,41 @@ _Note: this section will change_
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. Evaluate your prototype ...
- Choose and conduct 2 evaluations from this list: <!-- TODO: create new forms -->
- Choose and conduct 2 evaluations from this list:
- TODO: create new forms for each.
- **Heuristics Evaluation**: Choose one of the heuristics lists discussed in class and evaluate your design based on that list. How well does your design uphold each principle?
- **Human Factors Check**: Use the human factors checklist you developed in class at the end of Week 8 to evaluate your prototype. How well does your design meet each item in the checklist?
- **Cognitive Walkthrough**: Follow the method described in either [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) to conduct a cognitive walkthrough.
- **And** conduct at least two **Think-Aloud** evaluations with a prospective user of your design:
- Review the relevant sections in [this chapter](https://drive.google.com/open?id=1e23Pt4SyuuE2tNzrUa1iHg01P7-xuDzi) from Bill Buxton's sketching book for a detailed explanation. You will give them a task or two to do and then you will observe how they carry it out.
3. Write a brief retrospective case study
- <!-- TODO: case study directions -->
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.**
- <!-- TODO: new form -->
- **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!).
- <!-- TODO: new form -->
3. You should also recruit at least 1 people to participate in a short think-aloud exercise. R You should use the [Usability Aspect Report](https://drive.google.com/open?id=1sv3dMNvk3_e9wv8-qJz-GlaRor2gXzm3) to record your observations.
- TODO: case study directions
### D3: Document Specification
Turn in A SINGLE well-organized file containing:
1. **Pictures & Description of your prototype**: include an explanation of what features or use cases your prototype allows you to text, a description of what prototyping methods/tools you chose, and why you made both of those decisions.
2. **Evaluation Summary & Next Steps** Based on all of your evaluations, write a brief report:
1. **Prototype Description with Pictures/Images/Scans**: Description should include:
- what features or use cases your prototype allows you to test
- what prototyping methods/tools you chose
- why you made both of those decisions
2. **Evaluation Summary & Next Steps**:
- What evaluations did you conduct?
- What were the key problems that you identified?
- If you had more time to work on this project:
- What would you change in response do feedback?
- What would you not change about your design?
- Would you want to conduct more evaluations before iterating the design or are you ready to change things now?
- Would you want to conduct more evaluations before iterating the design or are you ready to make a revision first?
3. **Reflection** (3-6 paragraphs)
- A reflection on the experience of prototyping
- What worked well?
- What did not work well?
- Reflection on the evaluation process
- At a high level, what kind of problems did each evaluation surface? Were they similar or different? Why do you think that is?
- Which evaluation was most helpful (or were they all equally helpful)? Why?
- What went well in this milestone?
- What challenges did you run into on this milestone?
- How did the various evaluation methods compare to eachother in terms of what you learned from them / what kind of problems they surfaced?
- Which evaluation was the most useful for you (or were they all equally helpful)? Why?
- What would you do differently next time regarding **both** prototyping and evaluation?
- Did you learn anything from this exercise? If so, what? If not, why not?
4. **Appendix**: One evaluation report for each of your **four** evaluations (2x self-reflective evaluation + 2x think aloud):
- [UAR Word Template](https://drive.google.com/open?id=1sv3dMNvk3_e9wv8-qJz-GlaRor2gXzm3) -- used for think aloud and heuristic evaluations
- [CW Word Template](https://drive.google.com/open?id=1UWjvjp8xFHU0mYyRdzYNEzTBoJYwH6vk) -- used only for cognitive walkthrough
- TODO: New Templates
### D3: Grading
......
......@@ -72,7 +72,7 @@ Reading responses & sketchbook entries are due promptly at the start of class. M
#### Survey: Sun, Jan 12
- Due:
- Due:
- [Intro Survey](https://portlandstate.qualtrics.com/jfe/form/SV_3kH2FR8nxeay7WJ)
### Week 2
......@@ -88,8 +88,8 @@ What are we doing in this class anyway? What is UX Design & Research?
- Minhas, Saadia. 2018. “User Experience Design Process.” _UX Planet (Medium)_ (blog). April 3, 2018. <https://uxplanet.org/user-experience-design-process-d91df1a45916>
- Capital One Design. "Service Design Tools." _ONE Design (Medium)_. January 25, 2018. <https://medium.com/capitalonedesign/service-design-tools-methods-6e7f62fcf881>
- In Class:
- [What is UX](https://www.youtube.com/watch?v=Um3BhY0oS2c)
- Topic pitches
- Video: [What is UX](https://www.youtube.com/watch?v=Um3BhY0oS2c)
- Intros / Topic pitches
- The UX / IXD Process
- Group breakout
- Form project teams
......
......@@ -67,9 +67,6 @@
<p class="warning">This page is still under construction.
<strong>All information is subject to change without notice.</strong></p>
<div class="is-row">
<div class="is-col is-34 sidebar">
......
......@@ -17,7 +17,7 @@
<pubDate>Fri, 01 Nov 2019 00:00:00 +0000</pubDate>
<guid>https://web.cecs.pdx.edu/~harmon8/classes/cs305/syllabus/</guid>
<description>Course CS 305 - Social, Ethical, and Legal Implications of Computing Meetings Thursdays, 4:40 - 6:30, FAB 47 Final Exam Thursday, 5:30 - 7:20* Instructor Dr. Ellie Harmon ellie.harmon@pdx.edu she / her / hers Office Hours M+T 4:00 - 5:00FAB 120-15 Or by appointment Prerequisites College level reading and writing.</description>
<description>Course CS 305 - Social, Ethical, and Legal Implications of Computing Meetings Thursdays, 4:40 - 6:30, FAB 47 Final Exam Thursday, 5:30 - 7:20* Instructor Dr. Ellie Harmon ellie.harmon@pdx.edu she / her / hers Office Hours M+T 4:00 - 5:00FAB 120-15Or by appointment Prerequisites College level reading and writing. Upper division standing.</description>
</item>
<item>
......
This diff is collapsed.
......@@ -67,9 +67,6 @@
<p class="warning">This page is still under construction.
<strong>All information is subject to change without notice.</strong></p>
<div class="is-row">
<div class="is-col is-34 sidebar">
......
......@@ -67,9 +67,6 @@
<p class="warning">This page is still under construction.
<strong>All information is subject to change without notice.</strong></p>
<div class="is-row">
<div class="is-col is-34 sidebar">
......
......@@ -67,9 +67,6 @@
<p class="warning">This page is still under construction.
<strong>All information is subject to change without notice.</strong></p>
<div class="is-row">
<div class="is-col is-34 sidebar">
......@@ -241,11 +238,7 @@ Or <a href="/~harmon8/faq#meetings-with-me">by appointment</a></p>
</tr>
<tr>
<td align="right"><strong>Office Hours</strong></td>
<td align="left">M+T 4:00 - 5:00<br/><a href="/~harmon8/faq#how-to-find-my-office">FAB 120-15</a><br/></td>
</tr>
<tr>
<td align="right">Or <a href="/~harmon8/faq#meetings-with-me">by appointment</a></td>
<td></td>
<td align="left">M+T 4:00 - 5:00<br/><a href="/~harmon8/faq#how-to-find-my-office">FAB 120-15</a><br/>Or <a href="/~harmon8/faq#meetings-with-me">by appointment</a></td>
</tr>
<tr>
<td align="right"><strong>Prerequisites</strong></td>
......@@ -492,7 +485,9 @@ projects, including Atom, Eclipse, Mono, Rails, Swift, and many more.
<li><strong>Ubuntu Code of Conduct:</strong> <a href="http://ubuntu.com/about/about-ubuntu/conduct">ubuntu.com/about/about-ubuntu/conduct</a></li>
</ul>
<p>In this course, we will also have a code of conduct.</p>
<p>As a starting point, we will use this <a href="https://docs.google.com/document/d/1ZP-mYO0ss-zSnY0h24V7X4FzbZFDYd2_TbidJqE6qKI/edit?usp=sharing">code of conduct</a> based on the Mozilla participation guidelines and on feedback from students in prior classes. Please add any comments or suggestions to this document during weeks 1 &amp; 2. We will finalize it at the start of our third course meeting.</p>
<p class=".warning">
As a starting point, we will use this [code of conduct](https://docs.google.com/document/d/1ZP-mYO0ss-zSnY0h24V7X4FzbZFDYd2_TbidJqE6qKI/edit?usp=sharing) based on the Mozilla participation guidelines and on feedback from students in prior classes. Please add any comments or suggestions to this document during weeks 1 & 2. We will finalize it at the start of our third course meeting.
</p>
<h4 id="what-to-do-about-harassment">What to Do About Harassment</h4>
<p>If you are a victim of harassment of any kind in this class, there are
several resources available to you:</p>
......
......@@ -777,8 +777,9 @@ This milestone is still under revision, and directions are subject to change.
</li>
<li>Evaluate your prototype &hellip;
<ul>
<li>Choose and conduct 2 evaluations from this list: <!-- TODO: create new forms -->
<li>Choose and conduct 2 evaluations from this list:
<ul>
<li>TODO: create new forms for each.</li>
<li><strong>Heuristics Evaluation</strong>: Choose one of the heuristics lists discussed in class and evaluate your design based on that list. How well does your design uphold each principle?</li>
<li><strong>Human Factors Check</strong>: Use the human factors checklist you developed in class at the end of Week 8 to evaluate your prototype. How well does your design meet each item in the checklist?</li>
<li><strong>Cognitive Walkthrough</strong>: Follow the method described in either <a href="https://drive.google.com/open?id=1Mk9txWxZB92AEghQNqZjX0v4JHFbyCba">Wharton et al 1994</a> OR <a href="https://drive.google.com/open?id=1L8Aio1Ijve1tAccVVbWK_A8bPqM_x95L">Spencer et al 2000</a> to conduct a cognitive walkthrough.</li>
......@@ -793,25 +794,21 @@ This milestone is still under revision, and directions are subject to change.
</li>
<li>Write a brief retrospective case study
<ul>
<li>
<!-- TODO: case study directions -->
</li>
<li>TODO: case study directions</li>
</ul>
</li>
</ol>
<p>At least <strong>two</strong> of your team-members should <strong>separately</strong> conduct <strong>one</strong> 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.
- <strong>Heuristics Details</strong>: Consider <a href="http://www.nngroup.com/articles/ten-usability-heuristics/">Jakob Neilsen's famous list</a> or others that we discussed in class, or another of your choosing. If you choose your own, you <strong>must explain where you found it, why you chose it, and why I should believe it's a legit list.</strong>
- <!-- TODO: new form -->
- <strong>Cognitive Walkthrough Details</strong>: These two write-ups give detailed examples of using the method: <a href="https://drive.google.com/open?id=1Mk9txWxZB92AEghQNqZjX0v4JHFbyCba">Wharton et al 1994</a> OR <a href="https://drive.google.com/open?id=1L8Aio1Ijve1tAccVVbWK_A8bPqM_x95L">Spencer et al 2000</a>. You may follow the style of either one (they are different!).
- <!-- TODO: new form --></p>
<ol start="3">
<li>You should also recruit at least 1 people to participate in a short think-aloud exercise. R You should use the <a href="https://drive.google.com/open?id=1sv3dMNvk3_e9wv8-qJz-GlaRor2gXzm3">Usability Aspect Report</a> to record your observations.</li>
</ol>
<h3 id="d3-document-specification">D3: Document Specification</h3>
<p>Turn in A SINGLE well-organized file containing:</p>
<ol>
<li><strong>Pictures &amp; Description of your prototype</strong>: include an explanation of what features or use cases your prototype allows you to text, a description of what prototyping methods/tools you chose, and why you made both of those decisions.</li>
<li><strong>Evaluation Summary &amp; Next Steps</strong> Based on all of your evaluations, write a brief report:
<li><strong>Prototype Description with Pictures/Images/Scans</strong>: Description should include:
<ul>
<li>what features or use cases your prototype allows you to test</li>
<li>what prototyping methods/tools you chose</li>
<li>why you made both of those decisions</li>
</ul>
</li>
<li><strong>Evaluation Summary &amp; Next Steps</strong>:
<ul>
<li>What evaluations did you conduct?</li>
<li>What were the key problems that you identified?</li>
......@@ -819,33 +816,24 @@ This milestone is still under revision, and directions are subject to change.
<ul>
<li>What would you change in response do feedback?</li>
<li>What would you not change about your design?</li>
<li>Would you want to conduct more evaluations before iterating the design or are you ready to change things now?</li>
<li>Would you want to conduct more evaluations before iterating the design or are you ready to make a revision first?</li>
</ul>
</li>
</ul>
</li>
<li><strong>Reflection</strong> (3-6 paragraphs)
<ul>
<li>A reflection on the experience of prototyping
<ul>
<li>What worked well?</li>
<li>What did not work well?</li>
</ul>
</li>
<li>Reflection on the evaluation process
<ul>
<li>At a high level, what kind of problems did each evaluation surface? Were they similar or different? Why do you think that is?</li>
<li>Which evaluation was most helpful (or were they all equally helpful)? Why?</li>
</ul>
</li>
<li>What went well in this milestone?</li>
<li>What challenges did you run into on this milestone?</li>
<li>How did the various evaluation methods compare to eachother in terms of what you learned from them / what kind of problems they surfaced?</li>
<li>Which evaluation was the most useful for you (or were they all equally helpful)? Why?</li>
<li>What would you do differently next time regarding <strong>both</strong> prototyping and evaluation?</li>
<li>Did you learn anything from this exercise? If so, what? If not, why not?</li>
</ul>
</li>
<li><strong>Appendix</strong>: One evaluation report for each of your <strong>four</strong> evaluations (2x self-reflective evaluation + 2x think aloud):
<ul>
<li><a href="https://drive.google.com/open?id=1sv3dMNvk3_e9wv8-qJz-GlaRor2gXzm3">UAR Word Template</a> &ndash; used for think aloud and heuristic evaluations</li>
<li><a href="https://drive.google.com/open?id=1UWjvjp8xFHU0mYyRdzYNEzTBoJYwH6vk">CW Word Template</a> &ndash; used only for cognitive walkthrough</li>
<li>TODO: New Templates</li>
</ul>
</li>
</ol>
......
......@@ -418,8 +418,8 @@ Or <a href="/~harmon8/faq#meetings-with-me">by appointment</a></p>
</li>
<li>In Class:
<ul>
<li><a href="https://www.youtube.com/watch?v=Um3BhY0oS2c">What is UX</a></li>
<li>Topic pitches</li>
<li>Video: <a href="https://www.youtube.com/watch?v=Um3BhY0oS2c">What is UX</a></li>
<li>Intros / Topic pitches</li>
<li>The UX / IXD Process
<ul>
<li>Group breakout</li>
......
......@@ -122,7 +122,7 @@ Assignment Overview Each week, for weeks 2-9, you will need to make at least thr
<pubDate>Fri, 01 Nov 2019 00:00:00 +0000</pubDate>
<guid>https://web.cecs.pdx.edu/~harmon8/classes/cs305/syllabus/</guid>
<description>Course CS 305 - Social, Ethical, and Legal Implications of Computing Meetings Thursdays, 4:40 - 6:30, FAB 47 Final Exam Thursday, 5:30 - 7:20* Instructor Dr. Ellie Harmon ellie.harmon@pdx.edu she / her / hers Office Hours M+T 4:00 - 5:00FAB 120-15 Or by appointment Prerequisites College level reading and writing.</description>
<description>Course CS 305 - Social, Ethical, and Legal Implications of Computing Meetings Thursdays, 4:40 - 6:30, FAB 47 Final Exam Thursday, 5:30 - 7:20* Instructor Dr. Ellie Harmon ellie.harmon@pdx.edu she / her / hers Office Hours M+T 4:00 - 5:00FAB 120-15Or by appointment Prerequisites College level reading and writing. Upper division standing.</description>
</item>
<item>
......
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