THE ASSIGNMENT IS WORTH 100 POINTS
See PART 1 Description for IMPORTANT Details
Due 2/23 11:59pm on Canvas and Teams Page
The main goal of this report is to show that you can
apply the concepts from lecture notes and class activities
100 POINTS
5 points: Description of Design Context. Think of this as an updated Part 0. What is are the People/Places/Activities you are exploring
15 points: A brief description and justification of the methodology. This includes a discussion of the techniques used to gather information and their effectiveness. It should also summarize the results from class activities and from any studies you conducted (quantitative or qualitative). What are the limitations to the data you collected? What is an alternative methodological approach(5)?
10 points: A description of the important characteristics of the primary users (5), including other stakeholders (5). Must include a table that describes the participants in the interview study (5)
10 points: An affinity diagram and explanation of how each students data fit into the overall themes
10 points: An explanation of the data and themes. This should include a table with UTLITY goals that are gleaned from analyses. (This was the homework assignment for IMPLICIT utility goals.)
20 points: At least TWO detailed PERSONAS that highlight the important CURRENT USER characteristics (10each). Remember that this is based on the data you collected it is not "made up." in other words, some of the evidence should be in other parts of the report.
10 points: An initial list of usability criteria and utility criteria (evidence for measuring that a system is useful).
10 points: A discussion of the implications of what you learned above.
What are limitations of the methodology you used or the way you carried out the "study." What could you have done better? Is there adequate synthesis of data analyzed that leads toward advice for any solutions to build in Part 2 of this project. This will be evidence by making references to the studio logs or class assignments. This is the ONE place in this report where you can start to speculate about future designs.
10 points: Presentation, Cohesiveness, Grammar, Clarity
GENERAL NOTES
These are things that we have noticed while working with past teams and reviewing in-progress reports.
Continuity: Are themes, writing styles, etc, consistent throughout the entire report? For example, once you've defined who your primary, secondary, and tertiary stakeholders, are they referenced accurately throughout the rest of the report? Do sections written by different members read the same way?
Flow: Each individual section should flow clearly. Do you have introductory paragraphs introducing what you are talking about in each section and why? Does the larger narrative of your report clearly articulate how you went from a problem statement to your research to your design implications?
Systematic, iterative approach: Do you describe in detail the process by which you arrived at your final products for each section (i.e. class participation activities)? Was there clear evidence of iteration occurring? Do you demonstrate a clear understanding of the value of each exercise?
Evidence: When you make claims, are they backed up by external resources/data? When you write implications, are they supported by all the work you did in the report?
Course Material: do you site material from each of the chapters covered in class? Do you discuss how class activities show that you are conducting systematic evidence based design? Do you refer to material from the scholarship phase of class?
Team grade and membership: The team can present evidence that a member should not earn the same grade if a member does not meet the criteria established in the team contract. Further, if there is a teammate the continually falls short of their responsibilities to the team as established by the GTA/Prof/team members; they can be voted off the team.
Reflect on the Report: Have you demonstrated that you have internalized concepts from class and studio? Are using those concepts in a thoughtful way to investigate your problem space? We recommend discussing each of the concepts above as a team. It's very important that everyone is aligned on these items.