460 likes | 624 Views
Context as an antidote to information overload. Gail C. Murphy University of British Columbia Tasktop Technologies. Presented at MSA 2010 on March 18, 2010.
E N D
Context as an antidote toinformation overload Gail C. MurphyUniversity of British ColumbiaTasktop Technologies Presented at MSA 2010 onMarch 18, 2010 Unless otherwise indicated on a particular slide, this work is licensed under a Creative Commons Attribution-Share Alike 2.5 Canada License
warnings… emerging thoughts mixture of fact and fiction definitions may be fuzzy
Slide not available under Creative Commons license
information is everywhere and is needed Slide not available under Creative Commons license
from 10,000 metres especially in programming eclipse 3.0 Java files www.eclipse.org/eclipse/development/eclipse_3_0_stats.html
from 1 metre especially in programming massive amountsof data availablechanges every54 seconds (IBM group) Fritz, Ou, Murphy and Murphy-Hill, ICSE 2010.
fact 1:programmers face an avalanche of information daily
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]
emerging informationcan be critical changing web services team awareness[Sarma et al, 03]
fact 2:historical and emerging information increase the avalanche Historical Now Emerging
programmers work with fragments of information change sets are partialSoloway et. al., 1988Ko et. al., 2005
fact 3:programmers work with small parts of the avalanche Historical Emerging Now
information overload Slide not available under Creative Commons license
the nature of work knowledge ownership yesterday tasks
context subset of (optionally decorated)structured information elements knowledge ownership yesterday tasks
context Mylyn - gathering and representationdegree-of-knowledge (DOK) - broader representationinformation fragments - composition and presentation
Mylyn – task context built automatically as a programmer works each element in context decorated with degree-of-interest (DOI) interest Kersten and Murphy, FSE 2006.
Mylyn – task context tasks
DOK – developer context programmer 1 programmer 2 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.
authorship changes DOK – developer context
element interaction DOK – developer context
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 pDL = deliveries by programmer pAC = accepts by programmer p DOI = degree-of-interest a, b, c, d are weightings
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
DOK – developer context bug recommendation- can pick out pertinent ones bug 2234 bug 5588 bug 9221 programmer1 knowledge model changing bugs with change sets
DOK – developer context programmer1DOK programmer2DOK
information fragments - composition and presentation bugs fragment composed fragment x team fragment y z presentation 1 presentation 2
information fragments - composition and presentation bugs composer
information fragments - composition and presentation change sets composer
information fragments - composition and presentation source code composer
information fragments - composition and presentation composer composer what is my team working on? what has changed in my code?
information fragments - composition and presentation 18 industrial participants working on unfamiliar data set from industrial project
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? …
information fragments - composition and presentation RSS feed for web service API bug changes
pervasive use of contexts(getting there) developer model tasks information fragments
pervasive use of contexts(future) CONTEXT Tasks ContextSelection ConcernSummary
three top challenges automatic determination of contextor pre-configured contexts for 98+% of cases intuitive, low-effort user interfaces for applying and manipulating contexts work with, share, trade, filter with contexts
meghan allenjohn anvikelisa baniassadwesley coelhodavor cubranicbrian de alwisrob elvesthomas fritzjan hannemannlyndon hiewreid holmesmik kerstenshawn mintoe murphy-hilljingwen oumartin robillardizzet saferdavid shepherdducky sherwoodp. viriyakattiyapornannie yingrobert walkerand others!
Slide not available under Creative Commons license
context as an antidote to information overload Gail Murphywww.cs.ubc.ca/~murphy