CS295J/Boards from class 7.11: Difference between revisions
< CS295J
Wenjun Wang (talk | contribs) |
Wenjun Wang (talk | contribs) |
||
| Line 10: | Line 10: | ||
The factors we can consider to compare : | The factors we can consider to compare : | ||
The type of users: are they multi-tasking people ? Or do they like better to spend long time on one software and then turn to another ? What is the percentage of each group of people? How does this habit difference influence the design of software combo ? | * The type of users: are they multi-tasking people ? Or do they like better to spend long time on one software and then turn to another ? What is the percentage of each group of people? How does this habit difference influence the design of software combo ? | ||
The use of time : What is the time expense in the switching tasks ? Which is the better , AAABBB OR ABABAB ? (A and B stands for different softwares, and each character stands for an hour's shift) | * The use of time : What is the time expense in the switching tasks ? Which is the better , AAABBB OR ABABAB ? (A and B stands for different softwares, and each character stands for an hour's shift) | ||
For different features, what kind of softwares assist each other ? what kind of softwares conflict each other ? Can we apply some cognitive principles ? | * For different features, what kind of softwares assist each other ? what kind of softwares conflict each other ? Can we apply some cognitive principles ? | ||
Given a task and a software in use , how to develop a strategy to select the best software match for this given software in a software pool? | * Given a task and a software in use , how to develop a strategy to select the best software match for this given software in a software pool? | ||
Could you design a graph or an experiment to measure how usable , how annoying and how ... among different combos . | * Could you design a graph or an experiment to measure how usable , how annoying and how ... among different combos . | ||
* Hypothesis | * Hypothesis | ||
:1 We assume that consistency should be an important factor in platform combos. The universal identifier, function of shortcuts, transferred data forms, software operations should keep the same. | :1 We assume that consistency should be an important factor in platform combos. The universal identifier, function of shortcuts, transferred data forms, software operations should keep the same. | ||
:2 If impossible to keep the same , we should make them totally different. Because being similar is even worse. It will make a lot of confusions . We may design an experiment to testify that for the same function or future , " the exactly same design" is better than " totally different design " , which are both better than " similar design ". | :2 If impossible to keep the same , we should make them totally different. Because being similar is even worse. It will make a lot of confusions . We may design an experiment to testify that for the same function or future , " the exactly same design" is better than " totally different design " , which are both better than " similar design ". | ||
Revision as of 20:29, 13 October 2011
Identifying and Addressing Common Workflow Gaps in Brain Data Analysis (Caroline)
Notes: Combine with some kind of cognitive load measurement, insight evaluation, to discover patterns that help explain evaluation results?
Comparison of user experience across different platform combos(Wenjun)
Notes: Compare work efficiency, user experience and other factors in different platform combos for users who need to transfer data between softwares
The factors we can consider to compare :
- The type of users: are they multi-tasking people ? Or do they like better to spend long time on one software and then turn to another ? What is the percentage of each group of people? How does this habit difference influence the design of software combo ?
- The use of time : What is the time expense in the switching tasks ? Which is the better , AAABBB OR ABABAB ? (A and B stands for different softwares, and each character stands for an hour's shift)
- For different features, what kind of softwares assist each other ? what kind of softwares conflict each other ? Can we apply some cognitive principles ?
- Given a task and a software in use , how to develop a strategy to select the best software match for this given software in a software pool?
* Could you design a graph or an experiment to measure how usable , how annoying and how ... among different combos .
- Hypothesis
- 1 We assume that consistency should be an important factor in platform combos. The universal identifier, function of shortcuts, transferred data forms, software operations should keep the same.
- 2 If impossible to keep the same , we should make them totally different. Because being similar is even worse. It will make a lot of confusions . We may design an experiment to testify that for the same function or future , " the exactly same design" is better than " totally different design " , which are both better than " similar design ".