• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Home mess systems- Prototype 2 & Evaluation
 

Home mess systems- Prototype 2 & Evaluation

on

  • 2,064 views

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

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

Statistics

Views

Total Views
2,064
Views on SlideShare
1,777
Embed Views
287

Actions

Likes
0
Downloads
18
Comments
0

3 Embeds 287

http://kashesi.wordpress.com 284
http://www.slideshare.net 2
http://www.onlydoo.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • -2 Aunts on both moms and dads side.-Sister goes to River ridge
  • Had a large collection of blocks when I was young.
  • Kindergarten: learning basic math and reading skills1st:don’t remember reading changing.4th: Science was pretty simple when it started
  • Kindergarten: learning basic math and reading skills1st:don’t remember reading changing.4th: Science was pretty simple when it started
  • Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.
  • Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.
  • Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.
  • Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.
  • Game designing (don’t know a lot of programming)Never been hunting but have shot a shotgun.

Home mess systems- Prototype 2 & Evaluation Home mess systems- Prototype 2 & Evaluation Presentation Transcript

  • Home-Mess System
    *Final Presentation*
    Prototype II & Evaluation II
    Arundhati, Ihab, Ibrahim, Fareed,Zain
  • Introduction
    • Retracing the last 10 weeks
    • Purpose of the project
    • Steps taken to complete it
    Completing the design process
  • The end to another beginning…
    OBJECTIVES
    • Recap of all our previous phases.
    • Re-design of our first prototype
    • Evaluating users with newly designed prototype
    • Consolidating all results
    • Formulating new design alternatives for future prototypes
    • Conclusion of project & groupwork
  • Communication is defined as a process by which we assign and convey meaning in an attempt to create shared understanding
    P
    RECAP
  • 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
    • Questionnaires
    • Focus Group Interviews
    Focus on the user…
  • Data yielded results, who knew?
    • Asking the right types of questions guarantees informative answers.
    • Constructive and innovative solutions can be formed by simply observing the needs, wants and habits of the target group.
    • Using triangulation, we were able to transcend the limits of simply postulating theories, observing users and trying new methods.
    • 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
    • Questionnaires
    • Focus Group Interviews
    User Requirements
  • 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.
  • This is what they want…
    Users wanted a system that could do the following:
    • Enable smooth communication between members.
    • Leave personal messages.
    • Is easy to use.
    • Can expedite menial tasks.
  • Creation of personas…
  • 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.
  • 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.
  • 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
  • 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…
  • RESULTS OF EVALUATION
    One 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.
    • Adding new accessibility options.
    • Adding help functions and tutorials.
    • Improvement to privacy and system response.
  • PROTOTYPE
  • EVALUATION II
  • 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
  • RESULTS OF USABILITY TESTING
    Task: Create a new private message
  • RESULTS OF ANALYTICAL EVALUATION
    Summary of expert evaluation
  • USABILITY ISSUES RANKED
  • 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’
  • “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.”
  • RECOMMENDATION
    FOR
    VERSION 3.0
  • CONSOLIDATION OF RESULTS
    Summary
  • DesignRecommendations
    • Creating customizable options – such as choice of colours, the size of font etc.
    • Provide a directory of contacts for direct messaging
    • Redesigning the ‘notification’ bar
    • Separate accessibility control from the volume bar
  • CONCLUSION
  • Develop the design brief
    Investigate
    Evaluate
    Plan
    Create
  • Introduce the elephant in the room
  • Know your user requirements
  • Why usedifferent evaluation methods
  • Testing it outin the ‘real’world
  • User testing brings outflaws in design
  • More Thoughts…
  • ANY QUESTIONS