|
Counting Analysis for ACBC
|
|
| · | BYO: How often levels were included
|
| · | Unacceptables: How often levels were unacceptable
|
| · | Must-Haves: How often levels were must-haves
|
| · | Screeners: How many products were screened into the consideration set
|
| · | Choice Tournament: How often levels were included in the "winning" concept
|
| · | For the BYO and Tournament Winner, a column is written to the .csv file for every level in the study. A "1" indicates it was included in the concept; a "0" means it is not included.
|
|
|
| · | For the number of Screener questions marked "a possibility" a single value is written to the file.
|
|
|
| · | For the Must-Haves information, a column is written to the .csv file for every level in the study. A "1" indicates it is a "Must-Have" level; a "0" means it is not a "Must-Have" level.
|
|
|
| · | For the Unacceptables information, a column is written to the .csv file for every level in the study. A "1" indicates it is an "Unacceptable" level; a "0" means it is not an "Unacceptable" level.
|
| Partially Missing levels result when, say, only a subset of brands are brought forward to the ACBC questions for a respondent.
|
|
|
| An Entirely Missing Attribute results in all its levels not appearing in the ACBC questions for a respondent (for example, if that attribute was previously determined as entirely unimportant).
|
|
| · | When tallying the BYO product specifications, we assume you will want any partially-missing levels marked as 0 and any entirely missing attribute levels marked as missing.
|
|
|
| · | When tallying the Unacceptables and Must Haves, we assume you will want any partially-missing levels marked as unacceptable and any entirely missing attribute levels marked as missing (not known).
|
|
|
| · | When tallying the Tournament Winners, we assume you will want any partially-missing levels marked as 0 and any entirely missing attribute levels marked as missing.
|
| 1. VIA CONSTRUCTED LISTS: If the researcher has specified to treat missing attributes or levels as unacceptable, those are marked as unacceptable for the respondent.
|
|
|
| 2. INFERRED FROM MUST-HAVE QUESTION: For Attributes with Sequence Order set to "None", if the respondent indicates that one level is must-have, all other levels are marked unacceptable.
|
|
|
| 3. INFERRED FROM MUST-HAVE QUESTION: For Attributes with Sequence Order, the respondent indicates that a certain level is a "must-have" threshold (e.g. must have "at least" or "at most" this level). Any levels lower (if at least) or higher (if at most) than this level are marked unacceptable.
|
|
|
| For example, suppose MPG (miles per gallon) is the attribute in question with levels 20MPG, 25MPG, 30MPG, and 35MPG. If the respondent marks that "at least" 30MPG is a must-have, 20MPG and 25MPG are marked unacceptable.
|
|
|
| As a second example, if Seating Capacity is the attribute in question with levels 4-person, 5-person, 6-person, 7-person, and 8-person. If the respondent marks that "at most" 7-person seating is a must-have, 8-person is marked unacceptable.
|
|
|
| 4. DIRECTLY FROM UNACCEPTABLE QUESTION: For Attributes with Preference Order set to "None", if a respondent indicates a level is unacceptable, it is marked as unacceptable.
|
|
|
| 5. DIRECTLY FROM UNACCEPTABLE QUESTION: For Attributes with Preference Order, if the respondent indicates that a certain level is unacceptable, that level and
|
| any levels less preferred than it are marked unacceptable.
|
|
|
| Exception in the case of constructed lists: If an attribute is marked as having preference order, if an "unacceptable" level (omitted due to constructed list) is "more preferred" than the first "acceptable" level, it is changed to "acceptable".
|
| 1. If an attribute has only one level not marked as unacceptable, it is a "must-have."
|
|
|
| 2. If an attribute is marked as having preference order, the first "most preferred" acceptable level is marked as "must-have."
|
|
|
|
|