P3 - Sketching and Prototyping (Learning Pod)

pdf

School

University of California, Irvine *

*We aren’t endorsed by this school

Course

131

Subject

Computer Science

Date

Dec 6, 2023

Type

pdf

Pages

7

Uploaded by ChancellorRoseTurtle31

Report
P3 - Sketching and Prototyping (Learning Pod) Due Jun 9 by 5:30pm Points 200 Submitting a website url New Attempt Updated 06/7 - finalized rubric; see items highlighted in red below Overview Project 3 follows directly from Project 2. Now that you have done some basic user research and analysis, for Project 3, you will carry out basic design and prototyping. As with Project 2, Project 3 must be conducted in your Learning Pod and will culminate in a reflective report. Specifically, for Project 3 your Learning Pod will: 1. Choose a user story from P2 2. Critique your web app's support for the user story 3. Create wireframe redesign on paper and in Figma 4. Create a high-fidelity mockup of your redesign in Figma 5. Create an interactive prototype of your redesign in Figma 6. Write a reflective report (optionally add a "going the extra 7%") 7. Submit your report Step 0: Coordinate With Your Learning Pod This is a group project comprising the members of your Learning Pod . Please see your learning pod assignment ( https://docs.google.com/spreadsheets /d/1FoXUPiAdNcpA6D42kDHRuza0Ka01g_RL/edit?usp=share_link&ouid=111492439692688686211& rtpof=true&sd=true ) . In your Communication Agreement, you should have assigned high-level roles to each teammate. For this project, it can be useful to assign different roles to different teammates. To help you practice assigning roles and planning out interim deadlines and handoffs, this is something you should do as a team. Consider the following as you identify roles, deadlines, and handoffs: what skills, interests, and goals do each of you have? how might these align to P3 tasks? what availability do each of you have over the next three weeks? are there any subtasks that you can identify that will help you complete each step? what subtasks can be done in parallel, versus what subtasks need to be done in serial? Can any of these be done in advance, to improve your team's overall time efficiency? (example subtasks:
backwards engineer the color palette / font styles / etc. for the hi-fi prototype, learn how to make hi-fi and interactive prototypes in Figma, etc.) can you build in some "padding" in case there are unexpected delays? Step 1: Choose a User Story from P2 Craft a user story ( https://www.interaction-design.org/literature/topics/user- stories#:~:text=User%20stories%20are%20short%20statements,way%20to%20implement%20the%20featu that your team would collectively like to focus on for this final project. Your user story should be derived from the insights gleaned from your user research in P2 and it should be based on the persona you developed. The user story should follow the format and qualities described in the article linked above. The user story you choose should indicate a need of your subpopulation that is currently not adequately being met by the web app's current design. Think strategically about which user story you choose. Consider: how is the web app currently addressing this user story, if at all? will our group enjoy redesigning the web app to support this story? will the necessary redesign be substantial enough to practice/demonstrate your design capabilities? Will it be too substantial so as to be infeasible? how will your choice help you impress potential employers, instructors, and classmates? how will your choice play to your pod's strengths and help develop your weaknesses? Step 2: Critique the Web App's Design Now, drawing from all the design principles and lessons you have learned this quarter, conduct an expert review ( https://www.nngroup.com/articles/ux-expert-reviews/ ) of the interface with respect to the user story. That is, identify how your persona would accomplish the user story with the current web app design and what usability and accessibility issues they might encounter. Identify the strengths and weaknesses of the web app to support this user story. The result should be a roughly 2-3 page summary of the findings from the expert review, with screenshots, not unlike the analysis you conducted individually for Project 1. Step 3: Create Wireframes Start by sketching wireframes with pencil and paper for the updated web app design. Discuss alternatives amongst your team and iterate. It is imperative that your design "fits into" the design of the existing web app, to provide a consistent user experience. Then, take the most promising sketches and develop the finalized wireframes in Figma . Make sure that you have a wireframe drawing for each part of the interaction that is changed due to your redesign. We will have some time in class to practice Figma, but it is your responsibility to watch and
read tutorials and put in the hours to learn how to use this tool. Your wireframes should have an appropriate level of detail for a wireframe drawing--not too much, not too little--and should follow best practices for wireframing. Make sure that your Figma file is ordered cleanly and logically, so that it is obvious which screens represent the initial state of the system and which screens are the result of user interaction over time (usually, we arrange them from left to right in temporal order). Label your frames so that it is easy to understand. You are welcome to use design "kits" to make wireframing faster and cleaner. Step 4: Create Hi-Fi Mockups It's time to develop a high-fidelity prototype. Use Figma to re-present the wireframe drawings as a realistic visual design for the interface. Be sure not to overwrite the wireframes; they should be preserved, so you can document the design process from beginning to end. Your high-fidelity prototype should follow best practices for mockups. Remember that hi-fi prototypes are pixel-perfect renderings, with full color, accurate font style and size, etc. To the user's eye, this should be indistinguishable from the final interface in the web app. And, recall that your design changes should integrate seamlessly into the visual and interaction design of the web app's current interface. So, follow the brand guidelines and spatial layouts and general look and feel of the existing web app. Step 5: Create an Interactive Prototype Finally, Figma enables you to create animated interactive prototypes, to simulate a functional prototype. You only need to make the newly designed pages you designed functional. It is up to you and your team to decide how much interactivity is reasonable given the user story you developed. Create a video recording demoing your interactive functionality. Step 6: Write a Reflective Report Your submission will be in the form of a short executive summary with a long appendix. The executive summary should this template ( https://docs.google.com/document /d/1G53IxoTF7a4esRnBRc6qjNGB8L4mHaf2h62Sqyy2RkU/edit?usp=sharing ) . If you have questions about this assignment, please ask them in #ask-the-instructors on Slack so that everyone can benefit from the questions and answers. Step 7: Submit 1. Give the instructional team <inf-131-instructors@uci.edu> edit access to your Google Doc 2. Submit a URL to your accessible Google Doc (note, we will pay attention to whether changes are
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
P3 Rubric made after the deadline) Rubric Professional formatting - 20pts Conforms to word counts 1 - 1.25 line spacing Consistent look and feel; makes use of font size, lists, other forms of text emphasis, margins, images, etc. Clear communication (thesis statements, precise language, few grammatical issues and/or demonstration of effort) Accessibility - 20pts Overview - 10pts (did they answer the questions?) User Story - 10pts (did they answer the questions? Did they give evidence?) Expert Review - 10pts (did they answer the questions? Did they give evidence?) Wireframing - 10pts (did they answer the questions? Did they give evidence?) Mockups - 10pts (did they answer the questions? Did they give evidence?) Interactive Prototypes - 10pts (did they answer the questions? Did they give evidence?) Conclusion - 10pts (did they answer the questions?) Appendix - User Story - 6pts Expert Review - 20pts Wireframes (pencil + digital) - 10pts Mockups - 20pts Interactive prototype - 20pts Extra 7% - 14pts , optional
Criteria Ratings Pts 20 pts 20 pts 10 pts 10 pts 10 pts 10 pts Professional Formatting Conforms to word counts 1 - 1.25 line spacing Consistent look and feel; makes use of font size, lists, other forms of text emphasis, margins, images, etc. Clear communication (thesis statements, precise language, few grammatical issues and/or demonstration of effort) 20 pts Full Marks 15 pts Mostly Satisfying 10 pts Partially Satisfying 0 pts No Marks Accessibility Addresses headings, color contrast, lists, hyperlinks, images, and paragraphs/line spacing 20 pts Full Marks 15 pts Mostly Satisfying 10 pts Partially Satisfying 0 pts No Marks Report: Overview Briefly describe your entire project. What user story did you choose? How adequately was the web app you evaluated meeting the user needs for that story? What is / are the 1-2 key features of your final prototype that addresses the web app’s shortcomings to support your user story? What can we expect to find in the rest of the report? 10 pts Full Marks 8 pts Mostly Satisfying 5 pts Partially Satisfying 0 pts No Marks Report: User Story Role: <name of team member who did this> What did your team learn about crafting a user story? What would you do differently next time? 10 pts Full Marks 8 pts Mostly Satisfying 5 pts Partially Satisfying 0 pts No Marks Report: Expert Review Role: <name of team member who did this> What did you learn about expert review? What would you do differently next time? 10 pts Full Marks 8 pts Mostly Satisfying 5 pts Partially Satisfying 0 pts No Marks Report: Wireframes Role: <name of team member who did this> What did your team learn about wireframing? What would you do differently next time? 10 pts Full Marks 8 pts Mostly Satisfying 5 pts Partially Satisfying 0 pts No Marks
Criteria Ratings Pts 10 pts 10 pts 10 pts 6 pts 20 pts 10 pts 20 pts 20 pts Report: Mockups Role: <name of team member who did this> What did you learn about making high-fidelity mockups? What would you do differently next time? 10 pts Full Marks 8 pts Mostly Satisfying 5 pts Partially Satisfying 0 pts No Marks Report: Interactive Prototype Role: <name of team member who did this> What did you learn about making an interactive prototype? What would you do differently next time? 10 pts Full Marks 8 pts Mostly satisfying 5 pts Partially Satisfying 0 pts No Marks Report: Conclusion User stories, expert review, and prototyping are standard approaches to imagining new interaction designs. Based on your experience, what do you think their strengths and weaknesses are? Applying what you know about HCI design process, what are the next steps? If so, what? If not, why not? 10 pts Full Marks 8 pts Mostly satisfying 5 pts Partially Satisfying 0 pts No Marks Appendix: User Story 6 pts Full Marks 4 pts Mostly satisfying 3 pts Partially Satisfying 0 pts No Marks Appendix: Expert Analysis 20 pts Full Marks 15 pts Mostly satisfying 10 pts Partially Satisfying 0 pts No Marks Appendix: Wireframes pencil sketches + Figma wireframes 10 pts Full Marks 7.5 pts Mostly satisfying 5 pts Partially Satisfying 0 pts No Marks Appendix: Mockups 20 pts Full Marks 15 pts Mostly satisfying 10 pts Partially Satisfying 0 pts No Marks Appendix: Interactive Prototype 20 pts Full Marks 15 pts Mostly satisfying 10 pts Partially Satisfying 0 pts No Marks
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Total Points: 200 Criteria Ratings Pts 14 pts Appendix: Extra 7% (optional) 14 pts A Lot Extra 7 pts A Good Bit Extra 2 pts A Little Extra 0 pts No Marks