The Elusive Nature of Context: Why We Need It and Were We Might Find It
•
1 gefällt mir•762 views
Keynote at CASCON 2016. Describes the need for software to support the work patterns of humans so that the software works for humans instead of humans working for the software.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie The Elusive Nature of Context: Why We Need It and Were We Might Find It
Ähnlich wie The Elusive Nature of Context: Why We Need It and Were We Might Find It (20)
Mehr von Gail Murphy
Mehr von Gail Murphy (10)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
The Elusive Nature of Context: Why We Need It and Were We Might Find It
- 1. 1 V E R Z U S W E L C O M E T O The Elusive Nature of Context Gail C. Murphy University of British Columbia Tasktop Technologies @gail_murphy A more restrictive license has been chosen given use of licensed images.
- 2. 2 “the situation in which something happens” M e r r i a m - We b s t e r D i c t i o n a r y Context
- 3. 3 Context-aware Computing where you are who you are with what is nearby
- 5. 5 Limited : where, who and what a ppr oach to co ntext En hanced: interaction traces can extend use of co ntext to work Futu re: intent + content makes appl ications work for h umans The Elusive Nature of Context Take-Aways
- 6. 6 I n t e r a c t i o n I n t e n t + C o n t e n t S u m m a r y The Plan: Context To d a y
- 9. 9 W h e r e Yo u A r e W h o Yo u A r e W i t h W h a t I s N e a r b y
- 10. 10 W h e r e Yo u A r e W h o Yo u A r e W i t h W h a t I s N e a r b y context on mobile is largely about the “where”
- 11. 11 W h e r e Yo u A r e W h o Yo u A r e W i t h W h a t I s N e a r b y mobile applications that provide “what” are often based on “where”
- 12. 12 W h e r e Yo u A r e W h o Yo u A r e W i t h W h a t I s N e a r b y when context is about “who” it is typically application- based
- 13. 13 Mobile only device based context between applications
- 14. 14 Mobile small steps to increased context between applications within vendor e.g., integration with Messages app in iOS 10
- 16. 16 Desktop context is about… location recent activity — files open — directories visited
- 17. 16 Desktop context is about… location recent activity — files open — directories visited
- 18. 17 Desktop manual configuration of work context via spaces
- 19. 17 Desktop manual configuration of work context via spaces
- 20. 18 Desktop prevalent metaphor is search working on this talk — search for files — open application — search email for details — find images using search — and so on…
- 21. 19 Desktop is it better when we can speak requests? different modality, same metaphor
- 23. 21 Limited : Wh ere, W ho and Wh at app roach to co ntext The Elusive Nature of Context Summary of Today humans responsible for bulk of context humans working for applications shouldn’t this be the other way around?
- 24. 22 I n t e n t + C o n t e n t S u m m a r y The Plan: Context To d a y I n t e r a c t i o n
- 26. 24 Humans work in episodes
- 27. 24 Humans work in episodes working on Elusive Context talk
- 28. 24 Humans work in episodes working on Elusive Context talk
- 29. 24 Humans work in episodes working on Elusive Context talk
- 30. 24 Humans work in episodes working on Elusive Context talk working on some other task
- 31. 24 Humans work in episodes working on Elusive Context talk working on some other task
- 32. 24 Humans work in episodes working on Elusive Context talk working on some other task
- 33. 24 Humans work in episodes working on Elusive Context talk working on some other task
- 34. 24 Humans work in episodes working on Elusive Context talk working on Elusive Context talk working on some other task
- 35. 24 Humans work in episodes working on Elusive Context talk working on Elusive Context talk working on some other task
- 36. 24 Humans work in episodes working on Elusive Context talk working on Elusive Context talk working on some other task
- 37. 24 Humans work in episodes working on Elusive Context talk working on Elusive Context talk working on some other task
- 38. 25 P R O J E C T D E S C R I P T I O N Time [minutes] Subject 0 30 60 90 120 150 180 T3 T2 T1 S4 S3 S2 S1 R4 R3 R2 R1 ● ● ● ● ● ● ●● ●●●● ● ● ● ● ● ● ●●●●● ● ● ●●● ●●● ●● ● 51 activity switches 10 task switches, 3 distinct tasks ● ● ●● ● ●●●● ● ●● ● ● ●● ●● ● ●● ●●● ●●●● ● ● ●● ● ● ● ●●● ● ● ● ●●● ● ●● ● ● ● ● ● ● ● ●● ● ● ● ● ● ●●●● ● ● ●● ● ●●●● ● ● ● ● ● ● ● ● ● ● ● ● ● ●● ●● ● ● ● ● ●● ● ● ● ● ● ●●● ● ● ● ● ● ● ● ●● ● ● ●● ● 166 activity switches 36 task switches, 3 distinct tasks ● ●●●● ● ● ● ●● ●●● ● ● ● ● ● ● ● ● ● ● ●● ● ●● ● ●●● ● ● ● ● ●●● ● ●● ● ● ● ● ● ● ● ● ●●●● ● ● ●●● ● ● ●● ● ● ●●● ●●● ●●● ●●●●● ● ● ●●●●●●●● ● ●●● ● ● ●● ●● ● ●● ● ●● ● ● ● ● ● ● ● ●● ● ●●●● ●●● ● ●● ● ●●●●●● ● ●● ● ●●● ● ● ● 230 activity switches 79 task switches, 4 distinct tasks ●● ●● ● ●● ● ● ●●● ● ●● ●●●●● ●● ●● ● ●●●●● ●● ● ●●●● ● ● ● ● ●● ●● ● ●● ● ● ● 85 activity switches 13 task switches, 4 distinct tasks ● ●● ●● ●● ● ● ● ●●● ●● ●●●● ● ● ● ●●● ● ● ● ● ● ● ● ● ●● ● ● ● ● ● ●● ● ● 59 activity switches 20 task switches, 5 distinct tasks ● ● ●●● ● ● ●●●● ●●● ● ● ● ● ● ● ● ●●● ●●● ● ● ● ● ● 88 activity switches 17 task switches, 5 distinct tasks ● ● ●●● ●●●●●●● ●● ●● ● ●●●● ● ● ● ● ●●●●● ● ● ● ●● ● ● ● ● ●● ●● ●●●●●●● ●● ● ●● ● ● ●●● ● ● ● ● ● ● ● ● ● ●● ● ● ● ● ●● ●● ●●● ●● ● ● ● ● ● ●●● ●● ● ● ● ●●● ● ● 148 activity switches 27 task switches, 4 distinct tasks ● ●●●●● ●● ● ● ● ● ●● ●●●●● ●●● ●● ● ●●●● ●●● ● ● ● ●●● ● ●● ●● ● 108 activity switches 16 task switches, 5 distinct tasks ● ● ● ● ● ● ●● ● ●● ● ● ●● ● ● ● ● ● ● ● ● ● ● ● ● ● 66 activity switches 25 task switches 4 distinct tasks ● ● ● ● ● ●●● ● ● ● ● ● ●●● ● ● ● ● ● ● ● ● ● ●● ● ● ● ● ● ●● ●● ● ● 102 activity switches 61 task switches 6 distinct tasks ● ● ● ●●● ● ●●●●●●●●●● ● ●● ● ● ● ● ● ● ● ● ●●●●●●● ● ● ●●●●● ●●●● ● ● ● ●●● ● ● ●● ●● ●● 96 activity switches 28 task switches, 4 distinct tasks ● ● ● ● ● ● Dev:VC Dev:Debug Dev:Code Dev:Review Dev:TestApp Dev:Other BrowsingRel BrowsingUnrel MeetInformal MeetPlanned Email Planning ReadWriteDoc Other Software development episodes [Meyer, Fritz, Murphy, Zimmermann, FSE 2014]
- 39. 26 P R O J E C T D E S C R I P T I O N What if we leverage episodic memory?
- 40. 26 P R O J E C T D E S C R I P T I O N What if we leverage episodic memory?
- 41. 27 Mylyn: leveraging episodic memory interest based on frecency [Kersten and Murphy, FSE 2006]
- 42. 27 Mylyn: leveraging episodic memory interest based on frecency [Kersten and Murphy, FSE 2006]
- 43. 27 Mylyn: leveraging episodic memory interest based on frecency [Kersten and Murphy, FSE 2006]
- 44. 27 Mylyn: leveraging episodic memory interest based on frecency [Kersten and Murphy, FSE 2006]
- 45. 27 Mylyn: leveraging episodic memory interest based on frecency [Kersten and Murphy, FSE 2006]
- 46. 27 Mylyn: leveraging episodic memory interest based on frecency result is a task context[Kersten and Murphy, FSE 2006]
- 47. 28 Mylyn: leveraging episodic memory interest based on frecency
- 48. 28 Mylyn: leveraging episodic memory interest based on frecency
- 49. 28 Mylyn: leveraging episodic memory interest based on frecency
- 50. 28 Mylyn: leveraging episodic memory interest based on frecency
- 51. 28 Mylyn: leveraging episodic memory interest based on frecency
- 52. 28 Mylyn: leveraging episodic memory interest based on frecency
- 53. 28 Mylyn: leveraging episodic memory interest based on frecency
- 54. 29 Mylyn: leveraging episodic memory interest based on frecency start with previous task context
- 55. 29 Mylyn: leveraging episodic memory interest based on frecency start with previous task context
- 56. 29 Mylyn: leveraging episodic memory interest based on frecency start with previous task context
- 57. 30 Mylyn: leveraging episodic memory interest based on frecency start with previous task context
- 58. 30 Mylyn: leveraging episodic memory interest based on frecency start with previous task context
- 59. 30 Mylyn: leveraging episodic memory interest based on frecency start with previous task context
- 60. 31 Mylyn: leveraging episodic memory
- 61. 31 Mylyn: leveraging episodic memory field study showed software developers more productive with Mylyn downloaded 2M times per month
- 62. 32 Task context is also useful for knowledge workers
- 63. 32 Task context is also useful for knowledge workers
- 64. 33 P R O J E C T D E S C R I P T I O N Task-focused UI (with task contexts) for knowledge workers [Kersten and Murphy, AI Magazine, 2015]
- 65. 34 field study longitudinal study 8 participants ~10 days use ~3 tasks per day tasks were revisited 75% of participants mixed documents and web pages high decay (20%) indicates relevance weighing matters Knowledge Workers 3 participants 300-600 days of use 16-24 tasks per day ~3-4 task revisits per day decay also shows relevance weighting matters
- 67. 36 En hanced: interaction traces can extend use of co ntext to work The Elusive Nature of Context Summary of Interaction tasks + interaction leverage episodic memory apps are starting to work for humans
- 68. 37 S u m m a r y The Plan: Context To d a y I n t e r a c t i o n I n t e n t + C o n t e n t
- 69. 38 Mylyn optimized for individuals can share task contexts must share same resource structure explicit shared statement of intent
- 70. 39 Mylyn optimized for individuals can share task contexts must share same resource structure explicit shared statement of intent what if we relax these two constraints?
- 71. 40 let’s focus back on software development
- 72. 41 “It is better to fail in originality than to succeed in imitation.” H e r m a n M e l v i l l e Developers Business Analysts Testers
- 73. 42 Each role… benefits from specific applications has a particular perspective P R O J E C T D E S C R I P T I O N
- 74. 43 Roles have to work together P R O J E C T D E S C R I P T I O N share project context
- 75. 44
- 80. 44 Business Analyst Business Analyst Tester Developers Our client has refined how data will be accessed
- 81. 44 Business Analyst Business Analyst Tester Developers Our client has refined how data will be accessed Communication through shared requirements application
- 82. 44 Business Analyst Business Analyst Tester Developers Our client has refined how data will be accessed Communication through shared requirements application
- 83. 44 Business Analyst Business Analyst Tester Developers Our client has refined how data will be accessed Communication through shared requirements application
- 84. 45 Business Analyst Business Analyst Tester Developers Our client has refined how data will be accessed Communication through shared requirements application
- 85. 45 Business Analyst Business Analyst Tester Developers Our client has refined how data will be accessed Communication through shared requirements application
- 86. 45 Business Analyst Business Analyst Tester Developers Our client has refined how data will be accessed Communication through shared requirements application
- 87. 45 Business Analyst Business Analyst Tester Developers Our client has refined how data will be accessed Communication through shared requirements application
- 88. 45 Business Analyst Business Analyst Tester Developers Our client has refined how data will be accessed Communication through shared requirements application Rich data synchronization Rich data synchronization Rich data synchronization
- 89. 46 Business Analyst Business Analyst Tester Developers Rich data synchronization Rich data synchronization Rich data synchronization
- 91. 46 Business Analyst Business Analyst Tester Developers Content (data) is transferred Intent (semantics) comes from application
- 92. 46 Business Analyst Business Analyst Tester Developers Content (data) is transferred Intent (semantics) comes from application
- 93. 47 intent is implicit in each application content is moved between applications each role has information in context no more searching emails, finding documents more time doing what humans are good at enable increased productivity
- 94. 48 Futu re: intent + content makes appl ications work for h umans The Elusive Nature of Context Summary of Intent + Content
- 95. 48 Futu re: intent + content makes appl ications work for h umans The Elusive Nature of Context Summary of Intent + Content Intent + Content
- 96. 48 Futu re: intent + content makes appl ications work for h umans The Elusive Nature of Context Summary of Intent + Content Intent + Content how does context change if intent + content can be recognized, represented and shared?
- 97. 49 The Plan: Context To d a y I n t e r a c t i o n I n t e n t + C o n t e n t S u m m a r y
- 98. 50 Daniel Almeida John Anvik Deepak Azad Elisa Baniassad Alex Bradley Roberto Bittencourt Wesley Coehlo Davor Cubranic Brian de Alwis Neil Ernst Michalis Famelis Sylvie Foss Thomas Fritz Jan Hannemann Lyndon Hiew Reid Holmes Rahul Jiresal Mik Kersten Albert Lai Gene Lee Arthur Marques Shawn Minto Emerson Murphy-Hill Owen Ou Marc Palyart Sarah Rastkar Martin Robillard Izzet Safer Nick Sawadsky David Shepherd Jonathan Stiansen Albert Thompson Apple Viriyakattiyaporn Giovanni Viviani Robert Walker Annie Ying Trevor Young Sedigheh Zolatkaf Thanks to Tasktoptians, NSERC, IBM, Microsoft, ABB and other funders for making much of the underlying work possible
- 99. 51 “the situation in which something happens” M e r r i a m - We b s t e r D i c t i o n a r y Context
- 100. 52 Apple Knowledge Navigator (1987) https://www.youtube.com/watch?v=QRH8eimU_20
- 101. A lack of context means 53 we (humans) are working for applications instead of applications working for us
- 102. 54 richer notions of context can enable applications to work for humans All is not lost
- 103. 55 Limited : Wh ere, W ho and Wh at app roach to co ntext En hanced: In teraction traces can extend use of co ntext to work Futu re: In tent + content makes appl ications work for h umans The Elusive Nature of Context Take-Aways @gail_mu rphy