Showing posts with label design. Show all posts
Showing posts with label design. Show all posts

Thursday, April 5, 2012

Design a questionnaire

D H Stone

Another not-super-exciting blog, but since we're in the middle of coming up with evaluation material it's probably more useful to me than another hand tracking algorithm.  This paper is on: how to write a useful questionnaire.  It also came out of a medical journal, although I don't think that changes much because the concepts behind making a solid questionnaire are still the same.  Anyway, back on topic:

According to the author, a good questionnaire is "one that works".  Basically, that the respondent's answers can be analyzed without bias, error, or misrepresentation.  While there is not a strict set of rules to follow to achieve this, the author does give a set of guidelines he feels will help you toward this goal.

Questions should be:
* Appropriate - The questions give relevant information.
* Intelligible - The language in the questionnaire is understandable by the respondent.
* Unambiguous - The questions mean the same thing to both the respondent and inquirer.
* Unbiased - Equal chance for all answers, also avoid "Recall Bias" (memory based).
* Omnicompetent - Be able to handle as many responses as possible. (Use 'other' and 'don't know' categories)
* Appropriately coded - Make sure your categories are mutually exclusive.
* Piloted - Questionnaires should always be piloted to check for any errors or other faults.
* Ethical - Get consent, etc. (IRB)

The author also has a step-by-step guide on the actual design of the questionnaire, rather than just theory behind the questions, which should be useful when actually constructing the survey:

(1) Decide what data you need
(2) Select items for inclusion
(3) Design individual questions
(4) Compose wording
(5) Design layout
(6) Think about coding
(7) Prepare first draft and pretest
(8) Pilot and evaluate
(9) Perform survey



Thursday, March 22, 2012

Guidelines for Multimodal User Interface Design

                                         Leah M. Reeves
Jennifer Lai
James A. Larson
Sharon Oviatt
T. S. Balaji
Stéphanie Buisine
Penny Collings
Phil Cohen
Ben Kraal
Jean-Claude Martin
Michael McTear
TV Raman
Kay M. Stanney
Hui Su
Qian Ying Wang


Communications of the ACM

Since I'm doing a large amount of the UI programming for our project, I thought I'd make a bit of  a topic switch and read up on some UI research.  The paper I read focused on multimodal UI design.



According to the paper, there are six major categories for guidelines.  These are:

  • Requirements Specification
    • Design for a broad range of users
    • Privacy/Security Issues
  • Designing Multimodal Input and Output
    • Maximize human cognitive/physical abilities
    • Integrate input methods in a way compatible with user preference/system functionality/context
  • Adaptivity
    • Adapt to the needs of your users (Ex: Gesture input!)
  • Consistency
    • Make it look consistent, use common features
  • Feedback
    • Users should be aware of which inputs are available
    • Users should notified of alternative interaction options
  • Error Prevention/Handling
    • Provide clearly marked exits from tasks
    • Allow undoing of commands
    •  If an error occurs, permit users to switch to a different modality
The authors do note that more research needs to be done in order to get a better grasp of what the most intuitive/effective combination of different input and output methods are, since the population that these decisions affect is so broad.  They also say that new techniques for error handling and adaptivity should be explored.

These guidelines will be useful to keep in mind as we create the interface for our project, especially since the Kinect is multimodal.




Source: http://delivery.acm.org/10.1145/970000/962106/p57-reeves.pdf?ip=128.194.247.31&acc=ACTIVE%20SERVICE&CFID=91378723&CFTOKEN=92548257&__acm__=1332440500_e7a95379e3a0a0cd7ffc5c29f7d7138f