The final presentation of our coursework. Includes Prototype II, Evaluation of the same and the conclusion

1. Home-Mess System *Final Presentation* Prototype II & Evaluation II Arundhati, Ihab, Ibrahim, Fareed,Zain

3. Purpose of the project

4. Steps taken to complete itCompleting the design process

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

12. Questionnaires

13. Focus Group Interviews Focus on the user…

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.

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.

22. Leave personal messages.

23. Is easy to use.

25. CREATING SCENARIOS The 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 PROTOTYPING J. Nielsen distinguishestwolevels of prototypingaccording to the level of interaction. Horizontal Prototype A 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 Prototype Implementation 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 Evaluation Expert users evaluate the system based on Jacob Nielson’s Heuristics. These allow for design improvements to be suggested. User Testing User centric approach requiring that a user be observed in their own home, where the system is being employed. Cognitive Walkthroughs Collecting empirical data to measure a prototype’s usability by following a path a user could take. What sorts of tests, you may ask…

34. Adding new accessibility options.

35. Adding help functions and tutorials.

37. EVALUATION II

38. Evaluation Methods Analytical: Practical heuristics giving a quantitative measure of a list of problems from expert reviews Task-based analysis Field Study: Objective observation giving qualitative descriptions User quotes, opinions User Testing: Applied approach based in experimentation giving quantitative data. Questionnaires

39. RESULTS OF USABILITY TESTING Task: Create a new private message

41. RESULTS OF ANALYTICAL EVALUATION Summary of expert evaluation

42. USABILITY ISSUES RANKED

43. RESULTS OF FIELD STUDY The 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 & SUGGESTIONS Think-aloud protocol Adding 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.”

45. RECOMMENDATION FOR VERSION 3.0

46. CONSOLIDATION OF RESULTS Summary

48. Provide a directory of contacts for direct messaging

49. Redesigning the ‘notification’ bar

51. Develop the design brief Investigate Evaluate Plan Create

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