If you are looking for more types, another one that I don't think you
had (I could be wrong) was more of an open scale. I can't remember
what it is called but it essentially looks something like this.
|--------------------------|
good bad
The participant would just place a tick where they felt appropriate.
On a paper test you would quantify by measuring the distance, in an
electronic version this could be done with a slider.
- Justin
On 9-Dec-08, at 2:45 PM, Allison Bloodworth wrote:
Hi Blake,
We often use Likert Scale (http://en.wikipedia.org/wiki/
Likert_scale) questions in Fluid user testing. These can be sort of
like your rating question type, but we usually assign values to each
item instead of just the endpoints. Typical answers would be
something like this:
1. Strongly disagree
2. Disagree
3. Neither agree nor disagree
4. Agree
5. Strongly Agree
I've also used the "Array" or "Matrix" question type available in
Zoomerang before, and found it helpful. Here is a list of
Zoomerang's question types:http://zoomerangdemos.com/faq_images/qtypes.html
, and this list for LimeSurvey seems to have a lot more you may want
to check out: http://www.limesurvey.org/content/view/16/31/lang,en/.
Cheers,
Allison
On Dec 9, 2008, at 8:49 AM, Jess Mitchell wrote:
Blake,
From my experience with Viewsflash this looks like a pretty
straightforward list of question and answer types. I'm curious to
see if your consolidation at the bottom buys you much time, but it
also seems uncontroversial.
Do you have them listed in order-of-priority and therefore
development? 1-5? If so, that too looks good to me.
Best,
Jess
~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
[EMAIL PROTECTED]
/ w / 617.326.7753 / c / 919.599.5378
jabber: [EMAIL PROTECTED]
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~
On Dec 9, 2008, at 10:46 AM, electBlake wrote:
Hello All,
Blake here from Toronto/VULab WEB, and if you haven't herd - we
are making the switch to a proper php framework (EXCITING!). We
are looking at CodeIgniter.com and CakePHP.org, but that isn't why
I'm calling on you this morning.
Due to the dramatic (positive) change that a framework will bring
to VULab, we will be re-engineering the survey design tool/process
(nearly) from the ground up!
I want to start by isolating the types of questions we want to
offer as well as isolating the importance of each. Once we have a
list of question types we can agree on, we can develop them into
VULab working down the list from most important to optional
questions. You should consider what type of information you'd want
to gather if you were conducting a usability test.
VULab currently uses the phpESP survey design tool so I'll outline
what is included there and then I'll give me opinion on types/
priorities.
One thing that should be noted is that a question "type" can span
different "implementations". For example, a Boolean type of
question could be implemented as a True or False, or a Yes or No,
or even an Apples or Oranges. I'll distinguish between the types
of questions and the implementations below.
phpESP Current Question Types:
Boolean Question Type
This is a question type whose answers could resolve into a 1 or 0.
Implementations:
Yes/No
Text Input Question Type
This is a question type whose answers are stored as text.
Implementations:
Text Box
Essay Box
Numeric
Single Option Question Type
This is a question type whose answer is chosen from a list and is
specific to one option.
Implementations:
Radio Buttons
Dropdown Box
Multiple Select Question Type
This is a question type whose answer can be 1 or more options from
a given list.
Implementations:
Check Boxes
Date Question Type
This is a question type whose answer is a specific date.
Implementations:
Date
Rating Question Type
This is a question type whose answer is a number within a selected
scale.
Implementations:
Rank.
As I see it, we can consolidate a few of these and prioritize them
as follows for VULab
Note: Single/Multiple types have been combined.
Boolean Question Type
This is a question type whose answers could resolve into a 1 or 0.
Implementations:
Yes/No
Text Input Question Type
This is a question type whose answers are stored as text.
Implementations:
Text Line Box
Multi Line Box
Numeric
Multiple Option Question Type
This is a question type whose answer can be 1 or more options from
a given list.
Implementations:
Check Boxes
Radio Buttons
Dropdown Box
Rating Question Type
This is a question type whose answer is a number within a selected
scale.
Implementations:
Rank/Scale (Definable Start/Finish)
Date Question Type
This is a question type whose answer is a specific date.
Implementations:
Date
Are there any other question types that we should consider? Is
this an appropriate prioritizing? ANY input is much appreciated.
Thanks!
Blake
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
Allison Bloodworth
Senior User Interaction Designer
Educational Technology Services
University of California, Berkeley
(415) 377-8243
[EMAIL PROTECTED]
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
