Commit 8ea67d45 authored by Ellie's avatar Ellie

update d3, d3p

parent cd57c405
......@@ -474,34 +474,39 @@ You may also use specialized tools like [InVision](https://invisionapp.com) or [
### D3: Document Specification
Turn in A SINGLE well-organized file containing:
1. **Breif recap of problem and proposed solution**:
1. **Intro Memo**:
- Team names
- Summary of individual contributions
- Requests for feedback
2. **Breif recap of problem and proposed solution**:
- Summarize your problem & proposed solution clearly, but concisely.
- Include images of prototype and/or storyboards as useful to convey your design.
2. **Evaluation Summary**:
3. **Evaluation Summary**:
- Identify the features or use cases you tested.
- Synthesize across your various evaluations to create a list and brief description of the key results of your evaluation: What areas of your design worked well? What problems did you identify?
3. **Next Steps:** Propose a set of _next steps_ as if you had more time on this project.
4. **Next Steps:** Propose a set of _next steps_ as if you had more time on this project.
- What would you change in response do feedback?
- What would you not change?
- Would you want to conduct more evaluations before iterating the design or are you ready to make a revision first?
4. **Reflection** (3-6 paragraphs): Focus on what you learned, what challenges you faced, and how the design process worked for you in this milestone. You should answer questions like:
5. **Reflection** (3-6 paragraphs): Focus on what you learned, what challenges you faced, and how the design process worked for you in this milestone. You should answer questions like:
- What went well in this milestone? What challenges did you face? What would have made you more successful?
- What prototyping methods/tools did you choose, and _why_ you made that decision. In retrospect, was it a good decision? Why?
- How did the different 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? This should be a reflection on the experience of conducting the evaluation, not a reflection on the contents of what you found in your evaluation.
- 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?
- **For full credit, this reflection _must_ include references to course readings/materials on relevant topics such as brainstorming, storyboarding, values & design, critical design, human factors, etc.**
5. **Appendix**:
6. **Appendix**:
- One evaluation report for each evaluation in the templates you developed.
- Prototype Description with Pictures/Images/Scans to fully document your prototype.
### D3: Grading
- 2 -- **Format and Presentation:** Well-organized document with a high quality of presentation style.
The grade for each listed criteria will have a _completeness_ component and a _quality_ component.
- 2 -- **Format and Presentation:** Well-organized document with a high quality of presentation style, good grammar, clear writing. Document includes required memo up front. All materials are compiled into a single document.
- 1 -- **Problem + Solution Recap** Clear and concise recap of problem space that motivates your proposed solution.
- 2 -- **Evaluation Summary:** Clear and concise summary of evaluation results highlighting key takeaways for the reader.
- 1 -- **Next Steps:** Degree to which the report is compelling in motivating the proposed next steps.
- 1 -- **Next Steps:** Degree to which the report is compelling in motivating a set of proposed next steps.
- 2 -- **Reflection:** Includes references to course materials, compelling explanation of _why_ prototyping decisions were made, is thoughtful and shows evidence of _reflection on personal learning_.
- 2 -- **Appendix:**
- Complete templates that capture the results of each evaluation.
......@@ -513,7 +518,7 @@ Turn in A SINGLE well-organized file containing:
<p class = "warning">
This milestone is still under revision, and directions are subject to change.
Rubric still needs to be updated, otherwise this is complete.
</p>
......@@ -541,7 +546,7 @@ Everyone will present off of the computer in the room. It does not support dual
You should prepare your presentation as a human-centered design case study.
Do not feel compelled to focus on every single thing you did, instead tell us a story about your _process_, how you arrived at your final _result_, and what decisions you made along the way.
Do not feel compelled to focus on every single thing you did, instead tell us a story about your _process_ that helps us understand how you arrived at your final _result_, and has a clear takeaway for the audience (e.g., our design is good, our design needs work, we realized we solved the wrong problem, etc.). Your takeaway does not have to be "positive" about your work to be high quality or deserving of a good grade.
You should review [Designing Case Studies: Showcasing a Human-Centered Design Process](https://www.smashingmagazine.com/2015/02/designing-case-studies-human-centered-design-process/) for guidance.
......
......@@ -854,6 +854,13 @@ This milestone is still under revision, and directions are subject to change.
<h3 id="d3-document-specification">D3: Document Specification</h3>
<p>Turn in A SINGLE well-organized file containing:</p>
<ol>
<li><strong>Intro Memo</strong>:
<ul>
<li>Team names</li>
<li>Summary of individual contributions</li>
<li>Requests for feedback</li>
</ul>
</li>
<li><strong>Breif recap of problem and proposed solution</strong>:
<ul>
<li>Summarize your problem &amp; proposed solution clearly, but concisely.</li>
......@@ -891,11 +898,12 @@ This milestone is still under revision, and directions are subject to change.
</li>
</ol>
<h3 id="d3-grading">D3: Grading</h3>
<p>The grade for each listed criteria will have a <em>completeness</em> component and a <em>quality</em> component.</p>
<ul>
<li>2 &ndash; <strong>Format and Presentation:</strong> Well-organized document with a high quality of presentation style.</li>
<li>2 &ndash; <strong>Format and Presentation:</strong> Well-organized document with a high quality of presentation style, good grammar, clear writing. Document includes required memo up front. All materials are compiled into a single document.</li>
<li>1 &ndash; <strong>Problem + Solution Recap</strong> Clear and concise recap of problem space that motivates your proposed solution.</li>
<li>2 &ndash; <strong>Evaluation Summary:</strong> Clear and concise summary of evaluation results highlighting key takeaways for the reader.</li>
<li>1 &ndash; <strong>Next Steps:</strong> Degree to which the report is compelling in motivating the proposed next steps.</li>
<li>1 &ndash; <strong>Next Steps:</strong> Degree to which the report is compelling in motivating a set of proposed next steps.</li>
<li>2 &ndash; <strong>Reflection:</strong> Includes references to course materials, compelling explanation of <em>why</em> prototyping decisions were made, is thoughtful and shows evidence of <em>reflection on personal learning</em>.</li>
<li>2 &ndash; <strong>Appendix:</strong>
<ul>
......@@ -906,7 +914,7 @@ This milestone is still under revision, and directions are subject to change.
</ul>
<h2 id="d3p-final-presentation">D3P: Final Presentation</h2>
<p class = "warning">
This milestone is still under revision, and directions are subject to change.
Rubric still needs to be updated, otherwise this is complete.
</p>
<p>During the Finals time slot, each team will give a short (5-10 minute) presentation on their design project.</p>
<p>This assignment is worth 5 points.</p>
......@@ -923,7 +931,7 @@ This milestone is still under revision, and directions are subject to change.
<p>Everyone will present off of the computer in the room. It does not support dual displays.</p>
<h3 id="d3p-specification--requirements">D3P: Specification / Requirements</h3>
<p>You should prepare your presentation as a human-centered design case study.</p>
<p>Do not feel compelled to focus on every single thing you did, instead tell us a story about your <em>process</em>, how you arrived at your final <em>result</em>, and what decisions you made along the way.</p>
<p>Do not feel compelled to focus on every single thing you did, instead tell us a story about your <em>process</em> that helps us understand how you arrived at your final <em>result</em>, and has a clear takeaway for the audience (e.g., our design is good, our design needs work, we realized we solved the wrong problem, etc.). Your takeaway does not have to be &ldquo;positive&rdquo; about your work to be high quality or deserving of a good grade.</p>
<p>You should review <a href="https://www.smashingmagazine.com/2015/02/designing-case-studies-human-centered-design-process/">Designing Case Studies: Showcasing a Human-Centered Design Process</a> for guidance.</p>
<p><strong>All team members should participate in the presentation.</strong></p>
<h3 id="d3p-grading">D3P: Grading</h3>
......
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