HCI 3e - Ch 16: Dialogue notations and design

chapter 16 dialogue notations and design

Dialogue Notations and Design Dialogue Notations Diagrammatic state transition networks, JSD diagrams, flow charts Textual formal grammars, production rules, CS P Dialogue linked to the semantics of the system – what it does the presentation of the system – how it looks Formal descriptions can be analysed for inconsistent actions for difficult to reverse actions for missing actions for potential miskeying errors

what is dialogue? conversation between two or more parties usually cooperative in user interfaces refers to the structure of the interaction syntactic level of human–computer ‘conversation’ levels lexical – shape of icons, actual keys pressed syntactic – order of inputs and outputs semantic – effect on internal application/data

structured human dialogue human-computer dialogue very constrained some human-human dialogue formal too … Minister: do you man’s name take this woman … Man: I do Minister: do you woman’s name take this man … Woman: I do Man: With this ring I thee wed (places ring on womans finger) Woman: With this ring I thee wed (places ring ..) Minister: I now pronounce you man and wife

lessons about dialogue wedding service sort of script for three parties specifies order some contributions fixed – “I do” others variable – “do you man’s name …” instructions for ring concurrent with saying words “with this ring …” if you say these words are you married? only if in the right place, with marriage licence syntax not semantics

… and more what if woman says “I don’t”? real dialogues often have alternatives: the process of the trial depends on the defendants response focus on normative responses doesn’t cope with judge saying “off with her head” or in computer dialogue user standing on keyboard! Judge: How do you plead guilty or not guilty? Defendant: either Guilty or Not guilty

dialogue design notations dialogue gets buried in the program in a big system can we: analyse the dialogue: can the user always get to see current shopping basket change platforms (e.g. Windows/Mac) dialogue notations helps us to analyse systems separate lexical from semantoc … and before the system is built notations help us understand proposed designs

graphical notations state-transition nets (STN) Petri nets, state charts flow charts, JSD diagrams

State transition networks (STN) circles - states arcs - actions/events

State transition networks - events arc labels a bit cramped because: notation is `state heavy‘ the events require most detail

State transition networks - states labels in circles a bit uninformative: states are hard to name but easier to visualise

Hierarchical STNs managing complex dialogues named sub-dialogues Graphics Submenu Text Submenu Paint Submenu Main Menu select ‘graphics’ select ‘paint’ select ‘text’

Concurrent dialogues - I simple dialogue box Text Style bold italic underline example

Concurrent dialogues - II three toggles - individual STNs bold italic underline NO bold bold click on ‘bold’ NO italic italic click on ‘italic’ NO u’line u’line click on ‘underline’

Concurrent dialogues - III bold and italic combined NO style bold only click on ‘bold’ click on ‘ italic’ click on ‘ italic’ Text Style bold italic underline example italic only bold italic click on ‘bold’

Concurrent dialogues - IV all together - combinatorial explosion ‘ italic’ NO style bold only ‘ bold’ italic only bold italic ‘ bold’ ‘ italic’ u’line only bold u’line ‘ bold’ italic u’line bold italic u’line ‘ bold’ ‘ italic’ ‘ italic’ ‘ underline’ ‘ underline’ ‘ underline’ ‘ underline’ Text Style bold italic underline example

escapes ‘ back’ in web, escape/cancel keys similar behaviour everywhere end up with spaghetti of identical behaviours try to avoid this e.g. on high level diagram ‘ normal’ exit for each submenu plus separate escape arc active ‘everywhere’ in submenu Graphics Submenu Text Submenu Paint Submenu Main Menu select ‘graphics’ select ‘paint’ select ‘text’ normal finish ESC normal finish ESC normal finish ESC

help menus similar problems nearly the same everywhere but return to same point in dialogue could specify on STN … but very messy usually best added at a ‘meta’ level Finish Help Subsystem Circle 1 click on circumference Circle 2 from Menu press HELP button draw circle rubber band click on centre Help Subsystem press HELP button

Petri nets one of the oldest notations in computing! flow graph: places – a bit like STN states transitions – a bit like STN arcs counters – sit on places (current state) several counters allowed concurrent dialogue states used for UI specification (ICO at Toulouse) tool support – Petshop

Petri net example Bold On Italic On Bold Off Italic Off user presses ‘Italic’ user presses ‘Bold’ T1 T2 T3 T4 user actions represented as a new counter transition ‘fires’ when all input places have counters

State charts used in UML extension to STN hierarchy concurrent sub-nets escapes OFF always active history link marked H goes back to last state on re-entering subdialogue On Off 1 2 3 4 Sound Channel H SEL SEL SEL SEL MUTE Standby OFF ON RESET

Flowcharts familiar to programmers boxes - process/event - not state use for dialogue (not internal algorithm) Delete D1 Please enter employee no.: ____ Delete D3 Name: Alan Dix Dept: Computing delete? (Y/N): _ Please enter Y or N Delete D2 Name: Alan Dix Dept: Computing delete? (Y/N): _ answer? C2 Finish Finish read record C1 delete record C3 other N Y

it works! formal notations – too much work? COBOL transaction processing event-driven – like web interfaces programs structure ≠ dialogue structure used dialogue flow charts discuss with clients transform to code systematic testing 1000% productivity gain formalism saves time!! Delete D1 Please enter employee no.: ____ Delete D3 delete? (Y/N): _ Please enter Y or N Delete D2 Name: Alan Dix Dept: Computing delete? (Y/N): _ answer? C2 Finish Finish read record C1 other N Y delete record C3

JSD diagrams for tree structured dialogues less expressive greater clarity transaction login add employee record change employee record display employee record logout Personnel Record System delete employee record *

textual notations grammars production rules CSP and event algebras

Textual - Grammars Regular expressions sel-line click click* dble-click compare with JSD same computational model different notation BNF expr ::= empty | atom expr | '(' expr ')' expr more powerful than regular exp. or STNs Still NO concurrent dialogue

Production rules Unordered list of rules: if condition then action condition based on state or pending events every rule always potentially active Good for concurrency Bad for sequence

Event based production rules Sel-line  first C-point first  rest C-point rest  rest D-point rest  < draw line > Note: events added to list of pending events ‘ first ’ and ‘ rest ’ are internally generated events Bad at state!

Prepositional Production System State based Attributes: Mouse: { mouse-off, select-line, click-point, double-click } Line-state: { menu, first, rest } Rules (feedback not shown): select-line  mouse-off first click-point first  mouse-off rest click-point rest  mouse-off double-click rest  mouse-off menu Bad at events!

CSP and process algebras used in Alexander's SPI, and Agent notation good for sequential dialogues Bold-tog = select-bold?  bold-on  select-bold?  bold-off  Bold-tog Italic-tog = . . . Under-tog = . . . and concurrent dialogue Dialogue-box = Bold-tog || Italic-tog || Under-tog but causality unclear

Dialogue Notations - Summary Diagrammatic STN, JSD, Flow charts Textual grammars, production rules, CSP Issues event base vs. state based power vs. clarity model vs. notation sequential vs. concurrent

Semantics Alexander SPI (i) Two part specication: EventCSP - pure dialogue order EventISL - target dependent semantics dialogue description - centralised syntactic/semantic trade-off - tollerable

Semantics Alexander SPI (ii) EventCSP Login = login-mess -> get-name -> Passwd Passwd = passwd-mess -> (invalid -> Login [] valid -> Session) EventISL event: login-mess prompt: true out: “Login:” event: get-name uses: input set: user-id = input event: valid uses: input, user-id, passwd-db wgen: passwd-id = passwd-db(user-id)

Semantics - raw code event loop for word processor dialogue description - very distributed syntactic/semantic trade-off - terrible! switch ( ev.type ) { case button_down: if ( in_text ( ev.pos ) ) { mode = selecting; mark_selection_start(ev.pos); } ... case button_up: if ( in_text ( ev.pos ) && mode == selecting ) { mode = normal; mark_selection_end(ev.pos); } ... case mouse_move: if (mode == selecting ) { extend_selection(ev.pos); } ... } /* end of switch */

Action properties completeness missed arcs unforeseen circumstances determinism several arcs for one action deliberate: application decision accident: production rules nested escapes consistency same action, same effect? modes and visibility

Checking properties (i) completeness double-click in circle states? double click ?

Checking properties (ii) Reversibility: to reverse select `line'

Checking properties (ii) Reversibility: to reverse select `line' click

Checking properties (ii) Reversibility: to reverse select `line' click - double click

Checking properties (ii) Reversibility: to reverse select `line' click - double click - select `graphics' (3 actions) N.B. not undo

State properties reachability can you get anywhere from anywhere? and how easily reversibility can you get to the previous state? but NOT undo dangerous states some states you don't want to get to

Dangerous States word processor: two modes and exit F1 - changes mode F2 - exit (and save) Esc - no mode change but ... Esc resets autosave edit exit menu F1 F2 Esc

Dangerous States (ii) exit with/without save  dangerous states duplicate states - semantic distinction F1-F2 - exit with save F1-Esc-F2 - exit with no save edit exit menu F1 F2 Esc edit exit menu F1 F2 Esc any update

Lexical Issues visibility differentiate modes and states annotations to dialogue style command - verb noun mouse based - noun verb layout not just appearance ...

layout matters word processor - dangerous states old keyboard - OK Esc F1 F2 F3 ... F4 ... 1 tab ... ... edit exit menu F1 F2 Esc edit exit menu F1 F2 Esc any update

layout matters new keyboard layout intend F1-F2 (save) finger catches Esc Esc F1 F2 F3 ... edit exit menu F1 F2 Esc edit exit menu F1 F2 Esc any update

layout matters new keyboard layout intend F1-F2 (save) finger catches Esc F1-Esc-F2 - disaster! Esc F1 F2 F3 ... edit exit menu F1 F2 Esc edit exit menu F1 F2 Esc any update

Dialogue Analysis - Summary Semantics and dialogue attaching semantics distributed/centralised dialogue description maximising syntactic description Properties of dialogue action properties: completeness, determinism, consistency state properties: reachability, reversibility, dangerous states Presentation and lexical issues visibility , style , layout N.B. not independent of dialogue

Digital watch – User Instructions two main modes limited interface - 3 buttons button A changes mode

Digital watch – User Instructions dangerous states guarded … by two second hold completeness distinguish depress A and release A what do they do in all modes?

Digital watch – Designers instructions and ... that’s just one button

HCI 3e - Ch 16: Dialogue notations and design

More Related Content

What's hot (20)

Viewers also liked (14)

Similar to HCI 3e - Ch 16: Dialogue notations and design (20)

More from Alan Dix (20)

Recently uploaded (20)

HCI 3e - Ch 16: Dialogue notations and design