Warning: Undefined array key "DOKU_PREFS" in /home/clients/0de9ff9beee4541cf1f61437ce7bce2b/web/hec/inc/common.php on line 2082
Chapter 5 Validating The Prototype [HEC 4 ALL]

Warning: Undefined array key 3 in /home/clients/0de9ff9beee4541cf1f61437ce7bce2b/web/hec/inc/html.php on line 1453

Warning: Undefined array key -1 in /home/clients/0de9ff9beee4541cf1f61437ce7bce2b/web/hec/inc/html.php on line 1458

Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Prochaine révision
Révision précédente
tm:chapter5 [d-m-Y H:i]
boris créée
tm:chapter5 [d-m-Y H:i]
boris
Ligne 1: Ligne 1:
 +[[tm:chapter4]]
 +
 ====== Chapter 5  Validating The Prototype ====== ====== Chapter 5  Validating The Prototype ======
  
Ligne 85: Ligne 87:
 ===== 5.4  Feedbacks ===== ===== 5.4  Feedbacks =====
  
-The three scenarios and other small interactions have been tested with multiple users on the final prototype during the month of September 2008. They all had knowledge of BMO ranging from novice to intermediate. Computer knowledge for the majority was intermediate, except for one who was an expert (see table [[#tab:UserSummary|5.144User summarytable.5.1]] for a summary).+The three scenarios and other small interactions have been tested with multiple users on the final prototype during the month of September 2008. They all had knowledge of BMO ranging from novice to intermediate. Computer knowledge for the majority was intermediate, except for one who was an expert (see table 5.1 for a summary).
  
-**User** **BMO knowledge** **Computer knowledge** **Tested Scenario** Assistant Intermediate Expert 1,2 and 3 Assistant Intermediate Intermediate 3 Assistant Intermediate Intermediate 1 and 2 Assistant Intermediate Intermediate 3 Consultant and a developer Intermediate Expert Defining a new Business Model and exploring future alternatives Professor Expert Expert Miscellaneous Observations Student group Novice Intermediate On TouchWall develop a new model Consultant Expert Intermediate On TouchWall wizard, annotations and some editing Table 5.1: User summary +|  Table 5.1: User summary  |||| 
 +^**User** ^**BMO knowledge** ^**Computer knowledge** ^**Tested Scenario** 
 +|Assistant |Intermediate |Expert |1,2 and 3 
 +|Assistant |Intermediate |Intermediate |
 +|Assistant |Intermediate |Intermediate |1 and 2 
 +|Assistant |Intermediate |Intermediate |
 +|Consultant and a developer |Intermediate |Expert |Defining a new Business Model and exploring future alternatives 
 +|Professor |Expert |Expert |Miscellaneous Observations 
 +|Student group |Novice |Intermediate |On TouchWall develop a new model 
 +|Consultant |Expert |Intermediate |On TouchWall wizard, annotations and some editing 
  
 Globally feedback was positive. The testers managed to use the prototype without having too much trouble identifying the right action for their intensions. On the usefulness side of things, there were no real test, but the general opinion is that the reporting features as well as the versioning and layers features may certainly help in providing value over the paper based static solution. Globally feedback was positive. The testers managed to use the prototype without having too much trouble identifying the right action for their intensions. On the usefulness side of things, there were no real test, but the general opinion is that the reporting features as well as the versioning and layers features may certainly help in providing value over the paper based static solution.
Ligne 130: Ligne 141:
 Since the trash can permanently delete’s the object that is released onto it, it could be wise to ask for confirmation when the action has serious repercussions like when deleting a layer. Additionally, the dialog box could propose to take a snapshot before deletion. Since the trash can permanently delete’s the object that is released onto it, it could be wise to ask for confirmation when the action has serious repercussions like when deleting a layer. Additionally, the dialog box could propose to take a snapshot before deletion.
  
-It should also be taken into consideration to change the artifact’s image. A document shredder would perhaps be a better metaphor than the trash can based on the knowledge that ’Visual metaphors leverage real-world knowledge of objects, but metaphors that are very literal may introduce information that is irrelevant or misleading to a task’ [[[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 4.7 p. 129]+It should also be taken into consideration to change the artifact’s image. A document shredder would perhaps be a better metaphor than the trash can based on the knowledge that //’Visual metaphors leverage real-world knowledge of objects, but metaphors that are very literal may introduce information that is irrelevant or misleading to a task’// [ [[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 4.7 p. 129]
  
 ==== 5.4.4  Click Interaction and Menu ==== ==== 5.4.4  Click Interaction and Menu ====
Ligne 198: Ligne 209:
 Add a button to close the dialog. Perhaps to resolve problem with the link selection from previous case add possibility to edit links from this dialog as well as directly dragging the displayed links. Add a button to close the dialog. Perhaps to resolve problem with the link selection from previous case add possibility to edit links from this dialog as well as directly dragging the displayed links.
  
-In the current version of the prototype the general purpose detail dialog does suffice and adds consistency, but in future iterations with more specialized need for each block, a different approach will have to be chosen to provide desired functionalities. [[[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 3.3 p. 84]+In the current version of the prototype the general purpose detail dialog does suffice and adds consistency, but in future iterations with more specialized need for each block, a different approach will have to be chosen to provide desired functionalities. [ [[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 3.3 p. 84]
  
 ==== 5.4.7  Layers ==== ==== 5.4.7  Layers ====
Ligne 222: Ligne 233:
 Add a button, menu or increase the zone that enables the creation of a new layer. Add a button, menu or increase the zone that enables the creation of a new layer.
  
-Make visibility, and layer dependence for new elements two separate options. Either by adding a second selection column or by selecting the layers in the new element dialog. Still it is a good idea to keep in mind that ’Displaying all active task entities enhances understanding and feelings of control, but each display elements adds to the complexity of the user design’ [[[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 4.1 p. 115]+Make visibility, and layer dependence for new elements two separate options. Either by adding a second selection column or by selecting the layers in the new element dialog. Still it is a good idea to keep in mind that //’Displaying all active task entities enhances understanding and feelings of control, but each display elements adds to the complexity of the user design’// [ [[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 4.1 p. 115]
  
 ==== 5.4.8  Annotations ==== ==== 5.4.8  Annotations ====
Ligne 236: Ligne 247:
 === Observations === === Observations ===
  
-When looking at the annotations, many users did not find the answer annotations, because they are by default filtered. This can be related to ’Dynamic hiding of controls that are not in use conserves space and simplifies the display, but also conceals the controls’ affordances from the user’ [[[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 4.5 p. 125]+When looking at the annotations, many users did not find the answer annotations, because they are by default filtered. This can be related to //’Dynamic hiding of controls that are not in use conserves space and simplifies the display, but also conceals the controls’ affordances from the user//’ [ [[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 4.5 p. 125]
  
 Most of the users expected to be able to click on an annotation to edit it, instead of having to double click it. Most of the users expected to be able to click on an annotation to edit it, instead of having to double click it.
Ligne 268: Ligne 279:
 Give the possibility to create a new element from a selected portion of the answer. Or perhaps change the placement of the block and the questions. Give the possibility to create a new element from a selected portion of the answer. Or perhaps change the placement of the block and the questions.
  
-Although the wizard can guide novice user to identify missing elements and provide assessments question for more advanced users, a more open view should always be provided. This because ’Decomposing complex plans into chunks aids learning and application of action plans, but the sequence may create arbitrary or unnatural step boundaries.’ [[[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 5.5 p. 166]+Although the wizard can guide novice user to identify missing elements and provide assessments question for more advanced users, a more open view should always be provided. This because //’Decomposing complex plans into chunks aids learning and application of action plans, but the sequence may create arbitrary or unnatural step boundaries.’// [[[#rosson_usability_2002|Rosson and Carroll, 2002]], Tradeoff 5.5 p. 166]
  
 ===== 5.5  Touch Interactions ===== ===== 5.5  Touch Interactions =====
Ligne 274: Ligne 285:
 To see if the prototype is useable and could be useful on a projected wall, this mainly in the intent to be as near as possible to the original sticky note experience, it was first tested on Tablet PC. Tablet PC gives the user the same display size as the normal screen experience, but instead of using a mouse the user can directly manipulate the objects on screen with a pen. This first experience revealed that most of the action are working as well as with the mouse, or even easier for some drag and drop operations. Naturally since the keyboard is still available it is the preferred input method for text, even if handwriting recognition is available. As explained in the technical chapter, early on such a test revealed that click interactions are somewhat imprecise and have to be taken into consideration for detecting the double click actions. To see if the prototype is useable and could be useful on a projected wall, this mainly in the intent to be as near as possible to the original sticky note experience, it was first tested on Tablet PC. Tablet PC gives the user the same display size as the normal screen experience, but instead of using a mouse the user can directly manipulate the objects on screen with a pen. This first experience revealed that most of the action are working as well as with the mouse, or even easier for some drag and drop operations. Naturally since the keyboard is still available it is the preferred input method for text, even if handwriting recognition is available. As explained in the technical chapter, early on such a test revealed that click interactions are somewhat imprecise and have to be taken into consideration for detecting the double click actions.
  
-The next step was to test the prototype on a real big screen solution. It was choosen to augment a normal projector with the e-Beam<sup>[[#note32|1]]</sup> interact solution to test the application. The setup can be seen in figure [[#fig:prot2wall|5.152Prototype 2 projected onto a wall and eBeam interact as pointerfigure.5.1]]. This solution acts as a single touch cursor that can be calibrated over any flat surface onto which can be projected with a beamer. The idea was to test not only usability, but also to see how working with a projected solution would compare to the paper based system concerning group interactions, brainstorming possibilities and other design aspects. Unfortunately, during testing mostly usability problems were observed and there was not enough time to see the real impact on the usage side. Further testing with expert users and a greater time allocation is needed.+The next step was to test the prototype on a real big screen solution. It was choosen to augment a normal projector with the [[http://e-beam.com/|e-Beam]] interact solution to test the application. The setup can be seen in figure 5.1. This solution acts as a single touch cursor that can be calibrated over any flat surface onto which can be projected with a beamer. The idea was to test not only usability, but also to see how working with a projected solution would compare to the paper based system concerning group interactions, brainstorming possibilities and other design aspects. Unfortunately, during testing mostly usability problems were observed and there was not enough time to see the real impact on the usage side. Further testing with expert users and a greater time allocation is needed. 
 + 
 +Prototype 2 projected onto a wall and eBeam interact as pointer  
 + 
 +{{ tm:touchwall.jpg }}
  
-> {{main028.gif}} Figure 5.1: Prototype 2 projected onto a wall and eBeam interact as pointer  
  
 As for the usability, it has become clear that touch solution are even more approximate for registering clicks and pointer location. For example, involuntary perspective collapse occurred frequently due to unintentional clicking on empty space of a perspective. Link selection was nearly impossible since the highlighting of a link is required and occurs only if the cursor is exactly over it. As for the usability, it has become clear that touch solution are even more approximate for registering clicks and pointer location. For example, involuntary perspective collapse occurred frequently due to unintentional clicking on empty space of a perspective. Link selection was nearly impossible since the highlighting of a link is required and occurs only if the cursor is exactly over it.
Ligne 306: Ligne 320:
 Lastly it is unclear how useful the wizard view mode actually is. It would be interesting to test its usage from beginning to end against a more sporadic usage. Naturally this can also be done on the paper based version. Lastly it is unclear how useful the wizard view mode actually is. It would be interesting to test its usage from beginning to end against a more sporadic usage. Naturally this can also be done on the paper based version.
  
----- +[[tm:chapter6]]
- +
-  * **1** [[http://e-beam.com/|http://e-beam.com/]]+
  
tm/chapter5.txt · Dernière modification: d-m-Y H:i de boris
chimeric.de = chi`s home Creative Commons License Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0 Fristcher.ch