Home
Demonstration-based Modeling of Driver Performance with In
Contents
1. Recording toolbar buttons Behavior Recorder Header This button inserts a header which is ER required on each page of amock up The header will appear on the page as an icon of a coffee cup Ifthe header has already been inserted this button will ensure that it has not been modified or deleted Pseudo Tutor Header This button is not used for predictive performance modelling If you press this button by accident press the BR button again Button When you click on this tool it inserts a button at the insertion point or immediately following the current selection Use this tool to simu late a button in your interface Checkbox When you click on this tool it inserts a checkbox at the inser tion point or immediately following the current selection Use this tool to simulate a checkbox in your interface Link When you click on this tool it inserts a hyper link at the insertion point or immediately following the current selection This brings up a dia log box that asks the Link name Link location and Link Text Use this tool to designate text that will bring up another page of the mock up when clicked N a lo x List Menu When you click on this tool it inserts a List Menu at the inser tion point or immediately following the current selection Use this tool to simulate a drop down menu in your interface 10 11117 111 Locked List Menu When you click on this tool it inserts a Locked List Menu at the insertion
2. When you click on this tool it inserts a special hotspot over the image currently selected This brings up a dialog box that asks for a name Use this tool to simulate a menu item in your interface by creating a special hotspot on an image of a menu system The image or another hotspot within the image must be selected before the tool is clicked Submenu Name When you click on this tool it inserts a special hotspot over the image currently selected This brings up a dialog box that asks for a name Use this tool to simulate a submenu name in your interface by creating a special hotspot on an image of a menu system The image or another hotspot within the image must be selected before the tool is clicked Monitor Driving When you click on this tool it inserts a special button at the insertion point or immediately following the current selection The modeler can use this button to insert monitor driving time into the model Do not change the name of the inserted button Look At When you click on this tool it inserts a special button at the inser tion point or immediately following the current selection The modeler can use this button to specify when a user would simply look at an interface element without clicking on it or interacting with it Do not change the name of the inserted button Audio Input This is a special text field that represents the user talking to the device e g saying Call Mom to a cell phone During the tas
3. 1 1 3 Behavior Recorder Recording and Playback of Task The Behavior Recorder records the actions performed on the mock up in Netscape The mock up describes its contents to the Behavior Recorder which interprets the actions to build the task model A task model file con taining all of the recorded actions is exported from Behavior Recorder at the end of the demonstration For complete instructions on how to demonstrate a task using a mock up see the chapter Creating a Task Model by Demonstration ha 1 a Model Launcher Execute model To produce predictions the task model file must be executed by the Model Launcher program Model Launcher uses the ACT R cognitive architecture to simulate the demonstrated actions and calculate behavioral measures Predictions can be generated for two different contexts 1 Expert performance of the demonstrated task in isolation This method uses the Behavior Recorder and Netscape to simulate the task and pro duce a total time prediction 2 Performance of the task in a driving context This method uses a model of driver behavior and a driving simulation to produce more varied behavioral measures such as task time glance duration and magni tude of lane deviations For complete instructions on how to execute a task model see the chap ters Executing a Stand alone Task Model and Executing a Driving Plus Task Model 2 Creating a Mock up 2 1 Introduction An HTML mock up is a series o
4. 3 6 1 Exploring the effects of monitoring driving 00000 08 4 Executing a Stand alone Task Model 0 0oooooooooooo 4 1 Introduction 4 2 Preparing to Execute the Model 4 3 Execute the Task Model 2 0 0 0c ooo 5 Running a driving plus task model 2 0 0 0 es 5 1 Introduction 5 2 Preparing to Execute the Model 5 3 Execute the Task Model ONNHNMN BH 0 W Q 1 Introduction This manual describes the usage of the Performance Modeling by Demon stration System PMDS The components in this system allow user inter face UI designers to generate predictive cognitive models of user behavior simply by demonstrating tasks on HTML mock ups of interfaces These models can be executed by the theory backed ACT R cognitive architecture producing quantitative predictions of user behavior This User Guide will cover How to design and construct an HTML mock up using specially designed Dreamweaver tools How to demonstrate a task on a mock up to produce a task model How to execute the model to generate predictions 1 1 The tools and how they work together Four software applications are used by the PMDS Dreamweaver Netscape Behavior Recorder and Model Launcher First a special exten sion installed in Dreamweaver is used to create a storyboard like mock up of an interface Tasks are demonstrated by interacting with the mock u
5. X E See ocument Title Double Click on Example Text first to enter correct information Take pat tiie here Madeter pul mokle nae here Dai created put dee crid here Date of kisi update pet date ol daa ipda here Device horizontal distance fram comer of cook megas kit posllivo nee y Dro venical distance from center of console negative tip Posing dona y Double Click in the boxes first to bring up Properties box to Device height Tr enter in correct value NOTES put any notes ahnt the Biik bene Double click on the gold anchor to open Properties box to enter in page 2 link name m Tk E N ale AA ee ti ees ti ae ee A AA A AA Trex 005 SE 2 ee Figure 1 Modifications necessary on FirstPage html template 3 Modify the first five fields of the template by double clicking on the exam ple text next to the field s name and then entering in the correct informa tion Document Title The name that will appear in the Title state of the model file Title The mock up s name Modeler The name of who constructed the pages Date created Mock up creation date Date of last update Last modification to mock up 4 Modify the next four fields by double clicking in the value box next to the text field This will bring up its Properties window In the Properties win dow type the correct value in centimeters in the field marked init val Diver baal distance from comer of een legate RAL posin
6. distance fields are left at 0 Some notes are inserted in the NOTES section and the Link field in the Properties window of the link on the bottom of the page is modified to RadioMockup html which will be the filename of the second page of the mock up A new document is created in Dreamweaver The BR button is clicked inserting a coffee cup icon at the top of the page A file containing an image of the radio s interface is copied to the mock up folder and the image tool is used to insert it into the page Dreamweaver File Edit View Insert Modify Text Commands Site Window Help ote RABO rr TEA 606 _ Disc 2 Track 6 Task Radio Mockup v2 RadioMockup html XHTML O sa Code split gp Designa Title Disc 2 Track 6 Task rr Lt SD a E lt body gt lt p gt 783 x 620 38K 6 sec Figure 6 First image page of Radio Mock up storyboard Five hotspots are created with the hotspot tool one for the display and one fr each of the buttons used in the task Source Disc two and Next The hotspots are named appropriately 15 The Look At and Monitor Driving buttons are inserted at the bottom of the page to allow the modeler to indicate when the user looks at the dis play and when the user monitors driving conditions during the task This document is saved as RadioMockup html which completes the mock up 2 6 Guidelines When mocking up a physical device use hotspots instead of
7. in the Behavior Recorder window 5 When the task execution has completed a Results window will appear containing the total task time in seconds The time may be copied for reuse elsewhere by using the Copy to Clipboard button the Edit gt Copy menu item or the Command C keyboard shortcut 30 r Model Launcher File Edit Lisp Tools Windows u Model Startun Panel Results Total Task Time 11 66 KlmClick Mouse 6 Fired Module MOTOR running command CLICK NOUSE Module MOTOR running command PREPARAT OM COMPLETE Module MOTOR running command IHITIATION COMFLETE Device running command OUTPUT KEY Module MOTOR running command FIN SH MOVENENT Time 11 Checking for silent events _ Figure 16 Results dialog for a stand alone task in Model Launcher 6 Press the OK button to dismiss the window so that more models can be executed 7 When finished executing models quit the Model Launcher using the File gt Quit menu item or the Command Q keyboard shortcut 31 32 5 Running a driving plus task model 5 1 Introduction This chapter will describe the procedure for running a task model with a driving model This allows the modeler to examine the effects of performing a task while driving on driving performance and vice versa Unlike a stand alone model the driving plus task model is executed in a special driving environment created by the Model Launcher so the Behavior Recorder and Nets
8. model for the computer calculator would translate the demonstration into simulated mouse move ments and clicks and produce the appropriate motor timings for that method In addition to standard graphical interface widgets special mechanisms are provided for simulating speech input and output using text boxes for specifying shifts of attention to a driving task and for simulating a glance at a particular area of an interface These tools enable the mocking up of devices that have sound capabilities such as cell phones and talking navi gational systems and for exploring the implications of various interaction styles on driving performance 2 2 Current limitations of HTML mock ups Since the mock ups are HTML pages some interfaces may be difficult or impossible to simulate at the level of detail necessary In particular inter faces that have highly interactive direct manipulation behaviors interfaces which rely on animation or precise timing and interfaces which would require complex Javascript to simulate in an HTML page will not work well However it is possible to simulate a wide variety of software and physical devices using images buttons menus and speech 2 3 How to construct a Mock up A A 2 3 1 Mock ups consist of at least two pages including a required first page based on a template called FirstPage html and at least one page of sto ryboard for the task All mock ups must include a copy of FirstPage html
9. physical operations on pressing real buttons e g the HTML represents a cell phone flight management system or automobile navigation system The Export function creates appropriate ACT Simple code given the choice of this option e g it includes mouse clicks if the mock up is of a computer based system but does not include them for a mock up of a physical device 3 2 How to demonstrate a task on a mock up 1 Open the Behavior Recorder A Window titled Behavior Recorder for file untitled appears with the Demonstrate Mode radio button selected 2 Open Netscape 7 0 it must be able to connect to the Behavior Recorder through a network connection either active or inactive 3 Open the FirstPage html page of the desired mock up in Netscape by selecting File gt Open File A rectangle will appear in the Behavior Recorder window with the document title of the FirstPage html inside it 17 This is called the start state 60060 Behavior Recorder for file untitled File Edit Display Prod System Windows Help fe Demonstrate Mode Pseudo Tutor Mode Commutative Prod System Mode as Design A 1 databases ButtonPressed state Figure 7 State diagram after first action Each subsequent action on the mock up in Netscape will create new states in the Behavior Recorder connected by arrows with the action that brought about the change in state shown in a label on the arrow 4 Click on the Go to Step 1 in the task
10. point or immediately following the current selection This brings up a dialog box that asks Please enter a name for this menu Use this tool to simulate a drop down menu in your interface which is only enabled after the user clicks on another element of the interface The ele ment which unlocks the drop down menu must be selected when this but ton is clicked Radio Button When you click on this tool it inserts a radio button at the insertion point or immediately following the current selection Use this tool to simulate a radio button in your interface Radio Group When you click on this tool it inserts a group of radio but tons at the insertion point or immediately following the current selection This brings up a dialog box that asks for a group name the number of but tons desired and whether the buttons should be laid out using line breaks or a table Use this tool to simulate a group of radio buttons in your inter face Table When you click on this tool it inserts a table at the insertion point or immediately following the current selection This brings up a dialog box that asks for a name for the table and the number of rows and columns Each cell in the table will contain a text field Use this tool to create a table into which the user can enter text Text Field When you click on this tool it inserts a text field at the insertion point or immediately following the current selection Use this tool to simu late a text fi
11. task you are modeling 7 In the Link field in the Properties window enter the filename of the 2nd page of your storyboard the 1st image page of the device Double click on the gold anchor to open Properties box to enter I in page 2 link name BF aT ko Sep In ihe Ik vo arc modeling boda e EI Pi rer Foral Para Fa Stale me a au H J Tt E i LEN paN A A EF d S Foar Dein Peed Fae Saw Hara i I i EF EF Tarr ES Page Properties Enter name of 2nd page here Figure 3 Change link name 8 After all fields in the FirstPage html have been modified save the file in the folder you created in step 1 2 3 2 Creating subsequent pages of the mock up Mock up pages are created like regular Dreamweaver files except that cer tain Javascript code must be put in the page at the beginning This is accomplished by pressing the BR button the leftmost button on the tool bar An icon will appear on the page that looks like a cup of coffee This icon represents a Java applet which receives messages from the Behavior Recorder Do not alter the Javascript code or remove the N applet If you do so by accident press the BR button again The other buttons on the Recording Toolbar represent interface elements which talk to the Behavior Recorder during the task demonstration E A Dreamweaver File Edit View Insert Modify Text Commands Site Window Help Rain iM ER TT ORNSHRMBHABAU Bea FEB dd Figure 4 Recording toolbar
12. up its Prop erties window then insert the filename of the page to be linked to in the Link field If a hotspot does not link to another page the Link field should contain a character 4 Insert the Monitor Driving and Look At buttons if desired These but tons should be placed above or below the interface 5 Save the file in the same folder with your modified FirstPage html and copy of BehaviorRecorderApplet class 2 4 Possible trouble spots When an image is inserted Dreamweaver will sometimes indicate the posi tion of the image in your file system This may cause the image not to show up in Netscape when the task is demonstrated If the Src field in the image s Properties window contains a full pathname or anything other than just the image s filename modify it to contain just the filename Any images inserted in the page must also be copied to the folder containing the mock up pages Dreamweaver contains a number of bugs related to hotspot manipulation Hotspots will occasionally disappear when moved or resized If this hap pens press the F5 key on your keyboard to refresh the page For finer con trol of hotspot placement use the arrow keys to move the currently selected hotspot 13 2 5 Example mock up This section describes the creation of a mock up for a car radio device for the purpose of modelling a task in which the user selects track 5 of the sec ond CD in his car s CD changer First the FirstP
13. you are modeling hyperlink This will insert four new states as the sizing and position settings for the mock up are communicated to the Behavior Recorder 5 The second page of the mock up will appear Demonstrate the task as the user would perform it To designate a point in the task where the user would monitor driving conditions click the Monitor Driving button you inserted in the mock up To indicate that a user would simply look at 18 an interface element without clicking on it click the Look At button then the interface element 6 When the task has been correctly demonstrated after the last task action immediately export the demonstration file as described in the next section Do not perform any further actions in Netscape since all actions will be recorded by the Behavior Recorder N Demo CORRECTLY Start over if you make a mistake 3 3 Exporting demo file Creating a task model file Once you ve finished demonstrating the task select Export from the File menu in the Behavior Recorder 808 l Export Behavior Graph Radio Mockup v2 Device uses mouse Name Date Modified _ Hand starts on mouse Keyboard based task a i y a Name Radio asbl New Cancel vn ie Figure 8 Export Behavior Graph dialog box Modify the options if necessary and enter a name for the file This will save the task as an ACT Simp
14. Carnegie Mellon 4 Human Computer Interaction Institute Demonstration based Modeling of Driver Performance with In VehicleTelematics Tasks User Guide December 8 2003 Copyright 2003 Bonnie E John Konstantine Prevas Peter Centgraf and Sandra Esch All rights reserved 1 Table of Contents Io INTFOCUCHION acarreo AEREA AREA REA NOAA 1 1 The tools and how they work together o oooooooooooooooooooooo 1 1 1 Dreamweaver MX 2004 Mock up Creation ooooooooooooooo 1 1 2 Netscape 7 0 Task Demonstration 0 0 0 0 0 0 ccc cee eee 1 1 3 Behavior Recorder Recording and Playback of Task 1 1 4 Model Launcher Execute model 2 Creating a Mock up escrito raoba deere oe 2 1 Introduction 2 2 Current limitations of HTML MOCk UPS i oorosccnrran a 2 3 How to construct aMock up 2 22 o 2 3 1 Edit the FirstPage html Template acs oan na nora res 2 3 2 Creating subsequent pages of the mock Up ooooooooo 2 4 Possibl trouble SPOS car a ana en eae Oe hea ae 2 gt Example Mack UP ua u en ae en Ben ee od 2 6 Guidelines 3 Create a mode 3 1 Introduction I by demonstration 0 0 0 es 3 2 How to demonstrate a task on a mock up 0 ees 3 3 Exporting demo file Creating a task model file oo MI is SP e o oo Io 3 6 Editing The model les ae rs es e ar nn eee erden a
15. The Behavior Recorder window will display the title of the model 2 Press the Execute Model button The Choose a File dialog box will appear 29 r Model Launcher File Edit Lisp Tools Windows Model Startup Panel 1 Choose a Model Tyne Choose a File lt gt em Radio Mockup v2 E GM TSI Laptop _ Name Date Modified BehaviorRecorderApplet class Today E FirstPage html Today Radio Original psd Today O gq GS Netscape Radio jpg Today Loadig RadioMockup html Today 24 Macintosh HD Behavior Recorder _ Fe Compil Uni i ACT R Environ 4 A Applications A gmstaff 3 Documents ae Desktop New Folder Cancel a e Figure 15 Choose a File dialog in Model Launcher 3 Navigate to the task model file that was exported from the Behavior Recorder earlier The convention for this type of file is to use an asb file extension 4 Double click the task model file to select it The Model Launcher applica tion will execute the task model using the ACT R cognitive architecture The output displayed in the Listener 1 window describes the steps of execution carried out by the ACT R architecture You may safely ignore this unless detailed timeline data is required While the task is being executed the Behavior Recorder will simulate actions within Netscape The modeler can observe the actions by watch ing for page loading within Netscape and changes in the state diagram
16. age html file and the BehaviorRecorderApplet class file are copied into a new folder The FirstPage html file is opened in Dream weaver amp Dreamweaver File Edit View Insert Modify Text Commands Site Window Help FRecording Aero HB WB Hr Baa Fre e e 4g o zul gt o u Ta Lm we u 600 a Radio Radio Mockup v2 FirstPage html OF ka Code split 3 Design Title Radio ae It c El gt F Title Radio Modeler Peter Centeraf al Date created 10 23 03 Date of last update 12 2 03 Device horizontal distance from center of console negative let positive right a Re saes Device vertical distance from center of console negative up positive down 9 cm Device width p5 cm Device height 10 e Ste AA T A AA A A AA A AAA AN AAA AAA AAA TA AAA A AAA AAN AAA NOTES This model was created to demonstrate the use of the PMDS for a realistic automotive device lt body gt lt p gt lt a gt 783 x 609 IK 2 sec Format Paragraph H Style None H BBE Link RadioMockup html 8 Font Default Font 8 Size None Ha E Fre Target Es Page Properties Figure 5 FirstPage html for Radio Mock up The name of the mock up Radio is inserted in the Document Title field and the fields at the top of the page are filled out The device s width and height are measured and inserted in the appropriate fields Since the 14 device will be in the center of the console the
17. and device pop tells the model to move its hand from the steering wheel to the device think Is an action inserted automatically by the Behavior Recorder to account for mental processes taken by the user during the task look at actions are inserted before each button press The other actions correspond to steps in the demon stration The second through fifth presses of the Next button are indicated simply with press button Which tells the model to press the last button it pressed again This part of the model may be edited by hand Steps may be removed or inserted as long as any interface elements are specified in the previous section klm p klm klm goal klm think look at Source press button Source think look at Disc press button Disc think look at two press button two look at display think look at Next press button Next think press button think press button think press button think press button 22 This is the stand alone task model See Chapter 4 Executing a stand alone task model This section functions identically to the driving task model except that the names of interface elements must be enclosed in quotation marks and it may be edited by hand as described above pm start hand at mouse pm set params output speech t This section of the model sets some ACT R parameters and should not be edited by hand 3 6 Editing th
18. as the 1st page of the demonstration This page contains special code needed to accurately simulate the interface Edit this template only as described below The Mock up Template folder contains a template of FirstPage html along with other support code necessary for a mock up such as the BehaviorRe corderApplet class The file BehaviorRecorderApplet class must be in the same folder as the mock up The location of the Mock up Template folder in a standard installation is Macintosh HD gt Applications gt Behavior Recorder gt Mock up Template Edit the FirstPage html Template 1 Copy the contents of the Mock up Template folder into your mock up folder BE SURE TO HAVE COPIES OF BOTH FirstPage html and BehaviorRecorderApplet class IN THE FOLDER 2 Open the new copy of FirstPage html in Dreamweaver Double clicking FirstPage html will load it in a browser To open it in Dreamweaver drag it to the Dreamweaver icon on the Dock or use the File gt Open command within Dreamweaver FirstPage html will need to be modified for each storyboard The picture below shows what the page looks like and where modifications need to be made N Do not remove or alter the special code in the page represented in the Design view by the cof fee cup Icon Gf Dreamweaver File Edit View Insert Modify Text Commands Site Window Help Mein MRTG AED as TPR ee 4 4 isc Tithe Mew sp Firs baa hive ack up hemi life Marken ite
19. buttons checkboxes radio buttons etc These widgets can not be resized to match the physical layout of the device In addition using hotspots allows you to simulate the effect of a button press by linking the hotspot to a new page Lighter colored images work better because hotspots in Dreamweaver can be hard to see against a dark background Slider bars twist knobs and other controls requiring unusual interaction styles can not be mocked up 16 3 Create a model by demonstration 3 1 Introduction Once the instrumented web pages are created in Dreamweaver tasks can be demonstrated on these pages by opening the Behavior Recorder and the first HTML page in Netscape and demonstrating the task with mouse movement clicks and typing The web pages use HTML event handlers to send messages to the Behavior Recorder via the LiveConnect feature sup ported by Netscape As the user s actions are sent the Behavior Recorder creates a state tran sition diagram where the state of the webpage is a node and the demon strated actions are the transitions between nodes Once a correct procedure for a task is demonstrated the designer uses the Export item in the File menu to create a file containing ACT Simple code The designer has the option of declaring that the mock up is of a computer based sys tem where mouse pointing and clicking is a valid interaction technique or of a physical system where mouse operations are a stand in for actual
20. cape are not required to be open The output of a driving plus task model includes several measures of both task performance and driving performance In addition the model is required to react to the brake lights of a lead car and data on the model s reaction time before and during the task is collected 5 2 Preparing to Execute the Model 1 Open the Model Launcher by double clicking its icon in the dock 2 Press the Driving Task Model button to load the support for this type of model amp Model Launcher File Edit Lisp Tools Windows Model Startup Panel 1 Choose a Model Type Stand Alone Task Model Driving Task Model rer Execute Model CL USER Idle u Figure 17 Initial Model Launcher windows 33 The Model Launcher will load the necessary support files and display out put to a new Listener 1 window This output is related to the ACT R cogni tive architecture implementation and may be ignored When preparation has finished the Execute Model button will become active as shown below r A Model Launcher File Edit Lisp Tools Windows 1 Choose a Model Type Stand Alone Task Model Driving Task Model Execute Model Loading P Hacintosh HOSApplications ACT R Environment istand alonetactsimple Li Sp Compiler warnings H Unused lexical variable CURRENT MOUSE im KLM GOAL Unused lexical variable CURRENT YISUAL im KLM GORL Compiler warnings a Un
21. defined function Al im RUN SET ie Figure 18 Model Launcher after preparing to execute a Driving model The PMDS is now ready to execute a task model 5 3 Execute the Task Model To execute a driving plus task model and generate the analyses follow these steps 1 Press the Execute Model button The Choose a File dialog box will appear 34 r A Model Launcher File Ed Lisp Tools Windows Model Startup Panel 1 Choose a Model Tine Choose a File rr f Radio Mockup v2 Date Modified BehaviorRecorderApplet class Today E FirstPage html Today Radio Original psd Today d Dreamweaver M sS Radio_noPop asb Today a E GM TSI Laptop 2 Macintosh HD Radio jpg Today E Behavior Recorder RadioMockup html Today ACT R Environ c A Applications A gmstaff k Documents ae Desktop New Folder Cancel Figure 19 Choose a File dialog in Model Launcher 2 Navigate to the task model file that was exported from the Behavior Recorder earlier The convention for this type of file is to use an asb file extension 3 Double click the task model file to select it The Model Launcher application will open a new window to display the driving environment which will include the relevant interface elements from the task interface It will first execute the task model several times without driving to generate a baseline The driving environment will then be closed and
22. e model file 3 6 1 The placement of think Commands by the Behavior Recorder is opti mized for desktop software interfaces It may not be appropriate for other types of interfaces Fortunately ACT Simple s syntax allows for easy manipulation of these commands In the model above the five consecutive presses of the Next button are each preceded by a think command This is probably not appropriate so the think commands before the second through fifth button presses can simply be removed The think command by default takes the model 1200 milliseconds to execute which is an appropriate time for desktop software interfaces The length of a think can be changed by specifying a new length in seconds e g think 6 for a 600 millisecond command Exploring the effects of monitoring driving The driving task model includes pop commands where the modeler used the Monitor Driving button to indicate a point at which the user would monitor driving conditions Pops can also be inserted manually by typing pop after any command before the command s closing parenthe sis For example press button Source becomes press button Source pop Inserting pops by hand allows the modeler to quickly explore the effects of different strategies for monitoring driving For instance what if the user monitors driving after every action After each of the task s subtasks Only after the entire task is complete By editing the pops manually the
23. eld in your interface Image When you click on this tool it inserts an image at the insertion point or immediately following the current selection The image inserted does not communicate with the Behavior Recorder This tool is identical to the Image tool in Dreamweaver s Common toolbar and is included here for convenience Hotspot When you click on this tool it inserts a hotspot over the image currently selected This brings up a dialog box that asks for a name for the hotspot Use this tool to designate a section of an image in your interface which can be clicked on by the user The image or another hotspot within the image must be selected before the tool is clicked Rollover Hotspot When you click on this tool it inserts a rollover hotspot over the image currently selected This brings up a dialog box that asks for a name for the hotspot Use this tool to designate a section of an image in your interface which will respond when the user moves the mouse cursor over it The image or another hotspot within the image must be selected before the tool is clicked 11 Menu Name When you click on this tool it inserts a special hotspot over the image currently selected This brings up a dialog box that asks for a name Use this tool to simulate a menu in your interface by creating a special hotspot on an image of a menu system The image or another hotspot within the image must be selected before the tool is clicked Menu Item
24. ersion 35 4 El CL USER Idle u Figure 13 Initial Model Launcher windows The Model Launcher will load the necessary support files and display out put to a new Listener 1 window This output is related to the ACT R cogni tive architecture implementation and may be ignored When preparation has finished the Execute Model button will become active as shown below 28 r g Model Launcher File Edit Lisp Tools Windows 1 Choose a Model Type Stand Alone Task Mode Driving Task Model Execute Model Listener 1 Process Initial Loading P Mocintosh HDApplications ACTA Environment ts tand alone tactsimple Li Spas Compiler warnings 1 H Unused lexical variable CURRENT MOUSE im ELM GOAL Unused lexical variable CURRENT VISUAL in KLM GORL Compiler warnings Undefined function Al im RUN SET a IE Figure 14 Model Launcher after preparing to execute a Stand alone model The PMDS is now ready to execute a task model 4 3 Execute the Task Model To execute a task model and generate the total task time follow these steps 1 Make sure that the Behavior Recorder has a connection to the mock up and Netscape is displaying the first step of the task storyboard If you are not sure that the Behavior Recorder is ready resetto anew diagram by using the File gt New menu item and clicking No when prompted to save Finally reload the page containing the first step of the task story board
25. f web pages that simulates the user inter face of a device or piece of software The goal of a successful mock up Is to correctly simulate the series of actions performed by a user to complete a task These actions include such things as pressing buttons looking at display areas responding to audio stimuli and making a verbal response The primary user input to the PMDS is in the form of a simple mock up of a proposed interface A custom developed Dreamweaver extension is used to create an HTML based simulation of the graphical software interface or physical device Although interactions with these two types of interfaces have different physical and cognitive properties our system can produce valid models for both types by adjusting the instructions provided to the cognitive architecture For example a mock up could simulate a Calculator application on a desktop computer which uses keystrokes and mouse clicks to register input The same mock up could also be used to simulate a handheld calculator where input would require pressing buttons with a fin ger The demonstration of tasks for both devices would involve clicking simulated buttons in the mock up but by varying parameters of the output the performance model produced would be made appropriate to the desired context For the physical device the button clicks would be trans lated into simulated hand movements and given the appropriate motor tim ings for pressing buttons with fingers The
26. g righi p cm Device vertical detance from center of console negative up positive down g cm Device wiki cm a A 19 ___ Double Click in the boxes first ange si to bring up Properties box to Device height yg en enter in correct value NOTES pui w a a et k Bare deads demas op AA ere ET m Texifiecl Char width Tere i role line Ol ti ise Posse Cia Nora di pl ls Chart iret weil 10 Mira Enter correct value here Figure 2 Device dimension information fields Device horizontal distance from center of console nega tive left positive right Enter in the actual physical dis tance horizontally from the center of the console to the center of the physical device in centimeters Device vertical distance from center of console nega tive up positive down Enter in the actual physical dis tance vertically from the center of the console to the center of the physical device in centimeters Device width Enter in the actual physical width of the device in centimeters Device height Enter in the actual physical height of the device in centimeters N If multiple images are being used on a page to construct the image of the device use the dimensions of the extreme perimeter including buttons 5 Modify the last field NOTES if you want Modification of this field is optional The contents do not appear anywhere else 6 Double click on the gold anchor next to the text Go Step1 in the
27. k dem onstration the modeler types the words the user would say and this wid get translates the action into an operator in the resulting cognitive model that speaks these words rather than typing them Audio Output This is a special text field that represents the device talking to the user e g a navigation system saying In 400 feet turn right toa user During the task demonstration the modeler types the words the device would say and this widget translates the action into an operator in the resulting cognitive model that hears these words rather than typing them 1 Insert your images and widgets from the Recording toolbar on the page Create the page to look like the device interface in its initial state Do not put special characters or spaces in the name of any inter face elements or use a number as the name of an interface ele ment There must be at least one alphabetic character in the 12 name In addition each interface element must have a unique name 2 Apply your hotspots to sections of the images that will be used to record actions to Behavior Recorder besides those recorded from the buttons inserted in the step above When hotspots are applied they first appear as small blue rectangles in the upper left corner of the image You will need to move the hotspot and resize it 3 Add hyperlink addresses to any hotspots that will link to subsequent pages in the storyboard Double click on the hotspot to bring
28. le model which you can view in a text editor if you wish To help recognize files exported by the Behavior Recorder we ve adopted the asb extension but this extension is not required 19 3 4 Export file options Device uses mouse check this box if the interface you are mocking up is manipulated with a mouse or similar pointing and clicking device Standard desktop computer interfaces should use this setting devices using a touch screen or physical buttons should not Hand starts on mouse if the above setting is checked checking this set ting instructs the model to start with its right hand on the mouse If it is not checked the model will start with its right hand on the keyboard and the time it takes the model to move its hand to the mouse will be included in the task execution time Keyboard based task check this box if the interface you are mocking up is desktop computer based and the keyboard rather than the mouse is the primary means of controlling the interface e g Unix style text editors 3 5 The model file The task model exported by the Behavior Recorder is in the ACT Simple format which can be read into the ACT R cognitive architecture For a higher level of control over the task model ACT Simple can be edited by hand In the previous chapter a mock up of a radio interface was constructed Consider the task of selecting the fifth track of the second CD in the car s CD changer using this interface The steps i
29. mand C keyboard shortcut 36 Analyzing Task Time Figure 21 Sample output from a Driving Task Model 5 When finished executing models quit the Model Launcher using the File gt Quit menu item or the Command Q keyboard shortcut 3 38
30. modeler does not have to demonstrate the task again for each of these scenarios 23 24 4 Executing a Stand alone Task Model 4 1 Introduction A This chapter will describe the procedure for running a stand alone task model Stand alone task models simulate a task that is performed outside of any particular usage context The result measure produced by a stand alone model is the total task time Performance of the task is simulated using Behavior Recorder and Netscape allowing the modeler to observe the actions of the model in real time Netscape 7 0 opens the Mac OS 9 Classic Environment and must have an active network connection in order to operate The network connection may be vestigial merely connecting to a hub is suffi cient for communication between Netscape and Behavior Recorder to function 4 2 Preparing to Execute the Model In order for the PMDS to execute a task model several of the component applications need to be prepared 1 Open the Behavior Recorder by clicking the BehaviorRecorder jar icon in the dock You may also navigate to the Macintosh HD gt Applica tions gt Behavior Recorder folder and double click the BehaviorRe corder jar icon there When this step is complete a blank Behavior Recorder window will appear as shown below 25 f pact BehaviorRecorder BehaviorRecorder z e a e Behavior Recorder File Edit Display Prod System Windows Help Demonstrate Mode Pseud
31. n this task are 1 Press the source button 2 Press the disc button 3 Press the 2 button 4 Look at the display 5 Press the next button 5 times 6 Look at the display The ACT Simple code exported by the Behavior Recorder is shown below with comments after each section of the code set mouse clicks nil This first line contains the Device uses mouse setting in the Export dialog This line should not be changed by hand 20 if fboundp create task item setf task2 code progn This section indicates the start of the driving task model See Chapter 5 Executing a Driving Task Model This section must not be edited create task items Next item Next 534 392 20 9 Source item Source 637 392 20 9 display 1tem display 565 357 125 17 two tem two 557 371 14 4 Disc item Disc 527 371 14 4 This section lists the interface elements used in the task This section should not be edited by hand klm goal task2 drive move hand device pop think look at Source press button Source think look at Disc press button Disc think look at two press button two look at display think look at Next press button Next think press button think press button think press button think 21 press button This is the driving task model Each line after the first specifies an action for the model to take move h
32. o Tutor Mode Commutative Prod System Mode Figure 9 Blank Behavior Recorder window 2 Open the FirstPage html for your model in Netscape You may either drag the file s icon to the Netscape icon on the dock or use the File gt Open File menu option within Netscape a File Edit View Go Bookmarks Tools Window Help Radio Netscape B Q Q Q Q amp file 77Macintosh 20HD Users gmstaff Desktop l SS CN a O o Q a E Home G Radio My Netscape Cl Search Bookmarks Title Radio Modeler Peter Centgraf Date created 10 23 03 Date of last update 12 2 03 Device horizontal distance from center of console negative left positive right O cm Device vertical distance from center of console negative up positive down O cm Device width p5 cm Device height 10 cm NOTES This model was created to demonstrate the use of the PMDS for a realistic automotive device Go to Step in the task you are modeling 5 Of Applet Loaded Figure 10 FirstPage html for the CD player example loaded in Netscape After the FirstPage html has loaded the Behavior Recorder should dis play the title of your mock up in its main window as shown below 26 f pact BehaviorRecorder BehaviorRecorder eee Behavior Recorder File Edit Display Prod System Windows Help 9 Demonstrate Mode Pseudo Tutor Mode Commutative f Figure 11 Behavior Recorde
33. ps in Netscape Behavior Recorder records the actions performed on the mock up and exports a task model containing a description of these actions Finally the Model Launcher executes the model interacting either with Netscape or a driving simulation to produce human performance mea sures Dreamweaver MX 2004 Mock up Creation Dreamweaver was chosen as the tool to build mock ups because it pro vides a WYSIWYG environment familiar to designers and because its extension mechanism allowed quick adaptation for this purpose Special extensions are necessary in order for Dreamweaver to create HTML pages that can communicate actions to the Behavior Recorder These extensions allow HTML elements such as buttons text fields and image hotspots to represent interface elements such as a buttons menus and voice com mands in a proposed design For complete instructions on using Dreamweaver to create a mock up see the chapter Creating a Mock Up 1 1 2 Netscape 7 0 Task Demonstration The Netscape web browser allows interaction between Netscape and Behavior Recorder through LiveConnect This connection allows Behavior Recorder to record and replay actions performed within Netscape Netscape 7 0 opens the Mac OS 9 Classic Environment and must have an active network connection in order to operate The network connection may be vestigial merely connecting to a hub is sufficient communication between Netscape and Behavior Recorder to function
34. r with the model title displayed If the title does not appear there may be a problem establishing a connec tion between Netscape and the Behavior Recorder Make sure that the mock up contains the BehaviorRecorderApplet class file and that a net work connection of some kind is available on the computer Note The Behavior Recorder must be open before the mock up is loaded in order for the connection to be made If FirstPage html was opened before the Behavior Recorder simply refresh the browser window to estab lish the connection 3 Click on the link at the bottom of the page labeled with the text Go to Step1 in the task you are modeling The Behavior Recorder will register the size information from the model as states in the diagram 27 i pact BehaviorRecorder BehaviorRecorder 5 606 Behavior Recorder File Edit Display Prod System Windows Help 3 Demonstrate Mode Pseudo Tutor Mode Commutative Prod System Mode 7 state state2 state3 state4 Figure 12 Behavior Recorder window with sizing information 4 Open the Model Launcher by double clicking its icon in the dock 5 Press the Stand alone Task Model button to load the support for this type of model r amp Model Launcher File Edit Lisp Tools Windows Model Startup Panel 1 Choose a Model Type Stand Alone Task Model Driving Task Model Execute Model tener Helcome to Macintosh Common Lisp Y
35. re opened and the model will drive for approximately 40 seconds to generate baseline driving performance data After 40 seconds the model will execute the task several times while driving The output displayed in the Listener 1 window describes the steps of execution carried out by the ACT R architecture You may safely ignore this unless detailed timeline data is required The driving environment includes several indicators of the model s activity A green circle is displayed to represent the position of the model s right hand This circle starts on the box in the center of the window which repre sents the right side of the steering wheel Once the model begins to per form the task this circle will move accordingly Ared ring and a blue circle are used to show where the model is looking A white circle represents the position of the lead car 35 Driver View Figure 20 The driving simulation window 4 When the task execution has completed the Model Launcher compiles the data for the following measures Average task time in seconds for both driving and non driving conditions Average lateral deviation in meters both before and during task Average braking reaction time both before and during task Average number of glances to device per task Average glance duration These measures are displayed in the Listener 1 window and can be cop ied for reuse elsewhere by using the Edit gt Copy menu item or the Com
Download Pdf Manuals
Related Search
Related Contents
Sony NWZ-W252P Lincoln Electric PRO-CUT SVM146-A User's Manual Mode d`emploi Bulletin d`information - mai 2009 Le volet ferroviaire du plan de TV LED plano con luz de fondo MANUAL DE INSTRUCCIONES USER MANUAL - Hatteland Display AS サポートツール 取扱説明書 (インストール編) EEEA135A - Snap Manuel d`utilisation des ordinateurs de poche Palm™ de la série Copyright © All rights reserved.
Failed to retrieve file