1. Context as an antidote to information overload Gail C. Murphy University of British Columbia Tasktop Technologies Unless otherwise indicated on a particular slide, this work is licensed under a Creative Commons Attribution-Share Alike 2.5 Canada LicenseCreative Commons Attribution-Share Alike 2.5 Canada License Presented at MSA 2010 on March 18, 2010

2. warnings… emerging thoughts mixture of fact and fiction definitions may be fuzzy

3. Slide not available under Creative Commons license

4. information is everywhere and is needed Slide not available under Creative Commons license

5. especially in programming from 10,000 metres 10,000Java files 26,000Bugzilla bugs 45,000newsgroup entries eclipse 3.0 www.eclipse.org/eclipse/development/eclipse_3_0_stats.html Java files

6. especially in programming from 1 metre massive amounts of data available changes every 54 seconds (IBM group) Fritz, Ou, Murphy and Murphy-Hill, ICSE 2010.

7. fact 1: programmers face an avalanche of information daily

8. historical information can be helpful recommendations - previous change tasks [Ĉubranić et. al, 2003] - methods that frequently change together [Zimmermann et. al, 2004] - methods navigated together [DeLine et. al, 2005]

9. emerging information can be critical changing web services team awareness [Sarma et al, 03]

10. fact 2: historical and emerging information increase the avalanche NowHistoricalEmerging

11. programmers work with fragments of information change sets are partial Soloway et. al., 1988 Ko et. al., 2005

12. fact 3: programmers work with small parts of the avalanche Now HistoricalEmerging

13. fact 1 programmers face an avalanche of information daily fact 2 historical and emerging information increase the avalanche fact 3programmers work with small parts of the avalanche information overload Slide not available under Creative Commons license

14. the nature of work tasks yesterday knowledge ownership

15. context subset of (optionally decorated) structured information elements tasks yesterday knowledge ownership

16. context Mylyn - gathering and representation degree-of-knowledge (DOK) - broader representation information fragments - composition and presentation

17. Mylyn – task context built automatically as a programmer works interest each element in context decorated with degree-of-interest (DOI) Kersten and Murphy, FSE 2006.

18. Mylyn in action…

19. Mylyn – task context tasks

20. fact 1 programmers face an avalanche of information daily fact 2 historical and emerging information increase the avalanche fact 3programmers work with small parts of the avalanche Mylyn – task context

21. DOK – developer context programmer 1 built automatically as a programmer works from interaction & authorship each element decorated with degree- of-knowledge (DOK) Fritz, Ou, Murphy and Murphy-Hill, ICSE 2010. programmer 2

22. DOK – developer context authorship changes

23. DOK – developer context element interaction

24. DOK – developer context DOK(e, p): a*FA(e, p) + b*DL(e, p) - c*AC(e,p) + d *DOI(e,p) e = element of interest FA = first authorship by programmer p DL = deliveries by programmer p AC = accepts by programmer p DOI = degree-of-interest a, b, c, d are weightings

25. DOK – developer context expertise recommendation study with 7 IBM developers 55% accuracy compared to developer assessments of experts for packages 11% better accuracy than existing approaches on same data

26. DOK – developer context bug recommendation - can pick out pertinent ones programmer 1 knowledge model bug 2234 bug 5588 bug 9221 changing bugs with change sets

27. DOK – developer context programmer1 DOK programmer2 DOK

28. fact 1 programmers face an avalanche of information daily fact 2 historical and emerging information increase the avalanche fact 3programmers work with small parts of the avalanche DOK – developer context

29. information fragments - composition and presentation bugs fragment team fragment composed fragment presentation 1 presentation 2 x y z

30. information fragments - composition and presentation bug s composer

31. information fragments - composition and presentation change sets composer

32. information fragments - composition and presentation source code compos er

33. information fragments - composition and presentation compos er what is my team working on? what has changed in my code?

34. information fragments - composition and presentation 18 industrial participants working on unfamiliar data set from industrial project

35. information fragments - composition and presentation interviewed 11 industrial developers 78 questions of interest - Who is working on what? - What is the evolution of the code? - Who is using the API I am about to change? …

36. information fragments - composition and presentation RSS feed for web service API bug changes

37. information fragments - composition and presentation

38. fact 1 programmers face an avalanche of information daily fact 2 historical and emerging information increase the avalanche fact 3programmers work with small parts of the avalanche information fragments - composition and presentation

39. pervasive use of contexts (getting there) tasks developer model information fragments

40. pervasive use of contexts (future)

41. Task s Context Selection Concern Summary

42. three top challenges automatic determination of context or pre-configured contexts for 98+% of cases intuitive, low-effort user interfaces for applying and manipulating contexts work with, share, trade, filter with contexts

43. meghan allen john anvik elisa baniassad wesley coelho davor cubranic brian de alwis rob elves thomas fritz jan hannemann lyndon hiew reid holmes mik kersten shawn minto e murphy-hill jingwen ou martin robillard izzet safer david shepherd ducky sherwood p. viriyakattiyaporn annie ying robert walker and others!

44. information is everywhere and is needed

45. Slide not available under Creative Commons license

46. context as an antidote to information overload Gail Murphy www.cs.ubc.ca/~murphy