Home mess systems- Prototype 2 & Evaluation
Download as PPTX, PDF2 likes1,200 views
The document outlines the development and evaluation process of a communication system prototype over a ten-week project, emphasizing user-centered design and various evaluation methods. Key findings from user research included the need for easy communication, task management, and intuitive design, which were addressed through prototyping and testing. Recommendations for future iterations include customizable options and improved accessibility features based on user feedback.
Home mess systems- Prototype 2 & Evaluation
- 1. Home-Mess System*Final Presentation*Prototype II & Evaluation IIArundhati, Ihab, Ibrahim, Fareed,Zain
- 2. Introduction Retracing the last 10 weeks
- 3. Purpose of the project
- 4. Steps taken to complete itCompleting the design process
- 5. The end to another beginning…OBJECTIVES Recap of all our previous phases.
- 6. Re-design of our first prototype
- 7. Evaluating users with newly designed prototype
- 8. Consolidating all results
- 9. Formulating new design alternatives for future prototypes
- 10. Conclusion of project & groupworkCommunication is defined as a process by which we assign and convey meaning in an attempt to create shared understanding PRECAP
- 11. The first phase of design involves ascertaining the user requirements.Gathering User data helps in establishing these requirements.There were several methods used in gathering quality user generated data:Participant observation
- 12. Questionnaires
- 13. Focus Group Interviews Focus on the user…
- 14. Data yielded results, who knew?Asking the right types of questions guarantees informative answers.
- 15. Constructive and innovative solutions can be formed by simply observing the needs, wants and habits of the target group.
- 16. Using triangulation, we were able to transcend the limits of simply postulating theories, observing users and trying new methods.
- 17. Triangulation allowed us to accomplish more than the sum of its parts.The first phase of design involves ascertaining the user requirements.Gathering User data helps in establishing these requirements.There were several methods used in gathering quality user generated data:Participant observation
- 18. Questionnaires
- 19. Focus Group Interviews User Requirements
- 20. What have we learned…?Participant observation:Group members observed users overnight to pick up their habits, obstacles, needs and wants.Questionnaires:Questions were asked regarding lifestyle, occupation, number of people and activities. Focus Group Interviews:A relaxed group interview was conducted and a discussion commenced regarding communication gaps, technology handicaps and usability.
- 21. This is what they want…Users wanted a system that could do the following:Enable smooth communication between members.
- 23. Is easy to use.
- 24. Can expedite menial tasks.Creation of personas…
- 25. CREATING SCENARIOSThe next stage after acquiring the user requirements was to create scenarios from the personas.These scenarios offered various challenges that the HomeMess system needed to overcome, augment and facilitate for the benefit of the user.Scenarios included family members leaving messages for anything from picking up groceries to allocating user tasks.
- 26. APPROACH IN PROTOTYPINGJ. Nielsen distinguishestwolevels of prototypingaccording to the level of interaction.Horizontal PrototypeA surface interface of sorts that allows one to get the feel of a prototype. Physical layout of things such as screen and buttons help in outlining possible future hurdles.Vertical PrototypeImplementation of functionalities allows for a simulation of scenarios to occur, also allowing for the prototype to undergo user testing.
- 31. When all is said and done, test again…Creation and evaluation of a prototype reveals many factors overlooked before.The prototype performed admirably in some cases and poorly in others.Scenarios that should have been easy to implement proved confusing when used by a new user.E.g: Lack of help menus.Lack of a satisfying system response to tasks.PROTOTYPE EVALUATION
- 32. Heuristic EvaluationExpert users evaluate the system based on Jacob Nielson’s Heuristics. These allow for design improvements to be suggested.User TestingUser centric approach requiring that a user be observed in their own home, where the system is being employed.Cognitive WalkthroughsCollecting empirical data to measure a prototype’s usability by following a path a user could take.What sorts of tests, you may ask…
- 33. RESULTS OF EVALUATIONOne walkthrough, a test and an evaluation later…Through rigorous testing, improvements made held fast and the same problems tented not to occur.With newer tests came even newer problems and changes were thus implemented:Difference in buttons from text to icons.
- 34. Adding new accessibility options.
- 35. Adding help functions and tutorials.
- 36. Improvement to privacy and system response.PROTOTYPE
- 37. EVALUATION II
- 38. Evaluation MethodsAnalytical:Practical heuristics giving a quantitative measure of a list of problems from expert reviewsTask-based analysisField Study:Objective observation giving qualitative descriptions User quotes, opinionsUser Testing:Applied approach based in experimentation giving quantitative data.Questionnaires
- 39. RESULTS OF USABILITY TESTINGTask: Create a new private message
- 41. RESULTS OF ANALYTICAL EVALUATIONSummary of expert evaluation
- 43. RESULTS OF FIELD STUDYThe simplest measure is to count up the number of times a word was chosen by participants. In our studies, we find that we get a fair amount of consistency in the words chosen.Using‘word cloud’
- 44. “The buttons are so colourful! It looks more like a game device”.USER QUOTES & SUGGESTIONSThink-aloud protocolAdding a customizable setting “The text size is huge. Is there a way I can change that in the settings?”Allowing font changes from settings “How do I add the person I’m sending the message to?”Creating a button for directory of contacts“ Oh that was direct! I thought it would take more time to find the option.”
- 47. DesignRecommendationsCreating customizable options – such as choice of colours, the size of font etc.
- 51. Develop the design briefInvestigateEvaluatePlanCreate
- 52. Introduce the elephant in the room
- 53. Know your user requirements
- 54. Why usedifferent evaluation methods
- 55. Testing it outin the ‘real’world
- 56. User testing brings outflaws in design
- 57. More Thoughts…
- 58. ANY QUESTIONS
Editor's Notes
- #4: -2 Aunts on both moms and dads side.-Sister goes to River ridge
- #5: Had a large collection of blocks when I was young.
- #6: Kindergarten: learning basic math and reading skills1st:don’t remember reading changing.4th: Science was pretty simple when it started
- #8: Kindergarten: learning basic math and reading skills1st:don’t remember reading changing.4th: Science was pretty simple when it started
- #35: Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.
- #36: Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.
- #37: Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.
- #38: Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.
- #39: Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.