260 likes | 283 Views
This paper explores the formalism in Human-Computer Interaction (HCI), specifically focusing on the challenges and potential solutions in adopting formal methods. It discusses the factors that contribute to the uptake of formalism in HCI, such as expertise, utility, tools, cost, and fear. The paper also examines the importance of notations in HCI and proposes strategies for moving towards a ubiquitous semantics of interaction. The advantages of shared semantics, Galois connections, and mapping between different notations are highlighted, along with the significance of addressing real-time issues in HCI. The paper concludes by discussing the hierarchy of time in task analysis and the challenges in achieving clear and shared semantics in HCI.
E N D
towards a ubiquitous semantics of interaction Alan Dix Lancaster University
formalism in HCI adolescence or … rigormortis
formalism in HCI • blocks to uptake? • expertise • utility • tools • cost • fear • use only where value exceeds cost • safety critical, ?generic widgets?
ubiquity • lots of simple devices • but complex context: • lots of users • mobile • context dependent behaviour • good for FM
simple devices complex context ubiquity good for formal methods!
discrete most common good for GUI familiar notations continuous very few VR, ubicomp simpler semantics models what do they mean?
notationfever! pattern
notations • lots of them • why? • cult of notation in computer science • differing paradigms and problems • tractability • familiarity
myriad notations • problems • communication • education • tools • meaning and satisfaction ?? moving to ubiquity ??
routes myriadnotations interoperability UML-ishness single notation one size fits alltranslation shared semanitics
transformation model 1 model 2 (notation A) (notation B) Galois connection
model 1 model 2 model 1 model 2 common semantics? complete meta-semantics
model 1 model 2 common semantics? shared sub-semantics
external phenomena trace / scenario
advantages obvious physical/real common relates to real time problems not obvious e.g. CCS/CSP internal structure binding to real granularity/instants real time issues
Z * x Y instances x a b c a x happenings b a x a Y b c meta-model model time
instances a – b – a – b – a – c – a – b … happenings < < < < < < < event stream model P a b P | a c P time
somestate otherstate turntaking & states action response s0 – a1 – r1 – s1 – a2 – r2 – s2 – … one happening or two?
Z * x Y interstices a b c ? NO mapping model 1 P a b P | a c P < < < < < < < < < < < < < model 2
status and events A S1 S2 A S1 – A – S2 – A – S1 – A – S2 ….
0. DSV-IS talk 1. prepare 2. talk 3. discussion 2.2 sld 1 2.2 sld 1 2.3 conc 3.1 Q 3.2 A 3.1 Q 3.2 A 2.1 intro time hierarchies – task analysis
application level change selection format dialogue level underline is ‘word’ subscript size is 10 finished! click radio btn mouse activity on menu font size menu click OK lexical level layers – UI events None Word Single Double Dotted
continuous • status–event analysis • CS hybrid system literature • TACIT – hybrid Petri Nets & continuous interactors • Wuther???? – systems theory
common features • actions • at events, discrete changes in state • interstitial behaviour • between events, continuous change
other continuous issues • granularity issues – do it today • two timing – infinitely fast times • temporal gestalt – words, gestures
summary • harder than it looks! … but easier than pairwise matching • consequences: less sloppy semantics clear semantics shared toolsfoundation …