SERG. Combining Micro-Blogging and IDE Interactions to Support Developers in their Quests

Transcription

1 Delf Universiy of Technology Sofware Engineering Research Group Technical Repor Series Combining Micro-Blogging and IDE Ineracions o Suppor Developers in heir Quess Anja Guzzi, Marin Pinzger and Arie van Deursen Repor TUD-SERG SERG

2 TUD-SERG Published, produced and disribued by: Sofware Engineering Research Group Deparmen of Sofware Technology Faculy of Elecrical Engineering, Mahemaics and Compuer Science Delf Universiy of Technology Mekelweg CD Delf The Neherlands ISSN Sofware Engineering Research Group Technical Repors: hp:// For more informaion abou he Sofware Engineering Research Group: hp:// Noe: In Proceedings of he 26h Inernaional Conference on Sofware Mainenance (ICSM2010) ERA Track, IEEE Compuer Sociey c copyrigh 2010, by he auhors of his repor. Sofware Engineering Research Group, Deparmen of Sofware Technology, Faculy of Elecrical Engineering, Mahemaics and Compuer Science, Delf Universiy of Technology. All righs reserved. No par of his series may be reproduced in any form or by any means wihou prior wrien permission of he auhors.

3 SERG Guzzi, Pinzger & van Deursen Combining Micro-Blogging and IDE Ineracions o Suppor Developers in heir Quess James Core Combining Micro-Blogging and IDE Ineracions knowledge messages messages o Suppor Developers in heir Quess collecor builder navigaion daa ineracion races builder Anja Guzzi Marin Pinzger Arie van Deursen Visualizaions Delf Universiy of Technology The Neherlands {a.guzzi, m.pinzger, arie.vandeursen}@udelf.nl Saisics DB Recommenders... Absrac Sofware engineers spend a considerable amoun of ime on program comprehension. Alhough vendors of Inegraed Developmen Environmens (IDEs) and analysis ools address his challenge, curren suppor for reusing and sharing program comprehension knowledge is limied. As a consequence, developers have o go hrough he ime-consuming program undersanding phase muliple imes, insead of recalling knowledge from heir pas or oher s program comprehension aciviies. In his paper, we presen an approach o making he knowledge gained during he program comprehension process accessible, by combining micro-blog messages wih ineracion daa auomaically colleced from he IDE. We implemened he approach in an Eclipse plugin called James and performed a firs evaluaion of he underlying approach effeciveness, assessing he naure and usefulness of he colleced messages, as well as he added benefi of combining hem wih ineracion daa. I. INTRODUCTION In order o be able o conduc a sofware mainenance ask, sofware developers need o build up a subsanial amoun of knowledge abou he sofware being changed [1]. For example, developers need o undersand dependencies beween classes, he impac of changes o paricular mehods, or he ways in which wo services inerac. Once he mainenance ask is compleed, mos of his knowledge buil up during he process of conducing he ask will disappear : he only permanen resul is he modified sofware, and, opionally, some updaes made o he requiremens or (UML) design documenaion. This is an unforunae siuaion, since his knowledge may be valuable for fuure mainenance asks, possibly being conduced by differen developers. In our research, we seek ways o avoid his loss of precious knowledge. In his paper, we presen a novel ligh-weigh approach ha inegraes (Twier-like [2]) micro-blogging ino he Inegraed Developmen Environmen (IDE). Inspired by he remendous success of Twier, we firs of all encourage developers o micro-blog abou heir aciviies. Furhermore, we propose o combine hese shor messages wih ineracion daa auomaically colleced from he IDE. One could say ha we add locaion awareness o he messages by recording which, e.g., classes, mehods, and work producs are inspeced or modified by he developer. The approach is implemened ino a prooype ool called James, which includes an Eclipse plugin allowing developers o wrie and view new messages, and which collecs IDE evens riggered by he developer. Using James, we conduced a se of exploraive user sudies, in which we evaluae: messages ineracion daa Fig. 1. messages collecor ineracion races builder Visualizaions James Core knowledge builder Saisics DB Overview of he James approach Recommenders (1) o wha exen developers are willing o communicae heir aciviies hrough micro-blog messages; (2) he sor of informaion hey ypically provide in he messages; and (3) he qualiy of he connecions beween messages and ineracions as esablished by our algorihms. The resuls of our exploraive sudies provide srong indicaion of he grea poenial in he combinaion of micro-blogging and auomaed collecion of IDE ineracion daa. Naural nex seps for our work are o share he colleced knowledge among all he eam members, o inegrae oher elemens of social neworks ino he IDE, such as he abiliy o (un)follow eam maes, specific projecs, packages, or classes, and he adopion of recommender sysems based on ineracion and micro-blogging hisories [3]. The focus of he presen paper is on he messages hemselves and heir connecion o IDE ineracions, providing a necessary firs sep owards such a collaboraive developmen environmen. II. APPROACH: QUEST = MESSAGE + INTERACTIONS In his paper, we aim a combining messages and IDE ineracions o record knowledge buil up during sofware mainenance asks. We discuss how we collec and group ineracion daa, and how we expec developers o repor on heir aciviies. The overall approach is illusraed in Figure 1. Developers inerac wih heir IDE as hey normally do, resuling in navigaion daa colleced as ineracion races by an IDE plugin. Furhermore, developers can acively wrie (shor) messages, which are also colleced by he IDE. Boh daa sources are linked o each oher and sored in a reposiory. We refer o his combinaion as ques. The sored daa can hen be used in visualizaions, recommendaions, or oher presenaion forms helpful o developers.... TUD-SERG

4 ... Visualizaions Saisics Recommenders Guzzi, Pinzger & van Deursen Combining Micro-Blogging and IDE Ineracions o Suppor Developers in heir Quess A. Capuring IDE Ineracions We wan o capure a fine granulariy model of how developers inerac wih he IDE. Our minimal independen uni capuring user ineracion wihin he environmen (he IDE) is called Acion. Acions refer o IDE feaures ha can be execued by he user, such as opening a file, changing ab, selecing ex, performing an ediing operaion, closing a file, running a es case, ec. For every acion deeced, we record he developer who performed i, he IDE eniy involved (i.e., Java file X, Package Explorer view, ec.), he ype of acion (i.e., opening/closing of a view, ediing, ec.) and he dae and ime a which he acion has been performed. Fig. 2. Example of user acions wihin he IDE on a imeline Figure 2 shows a imeline of acions a developer performs wihin an IDE while working on an ordinary ask. On he ime line we draw a verical mark for every acion deeced, wih more recen acions on he righ. Acions are auomaically colleced and hen processed. We group acions ino ineracions according o heir ime proximiy. Acions a a shor ime disance apar from each oher will be par of a single ineracion, modeling he fac ha people ake a few insans o decide on wha o focus on. As an example: when a user closes a number of files one afer he oher (which is recorded as hree disinc acions), we consider his a single ineracion wih he IDE (which would be described as closing files X, Y, Z ). Our heurisic is based on he ime elapsed beween one acion and he nex one. Afer he iniial acion, every oher acion in he same ineracion has been performed wihin x from he previous one. From observaions during our iniial experimens, we se = 3 seconds. Fig. 3. Example of grouping acions ino five ineracions As an example, Figure 3 visually depics he grouping of he acions previously presened ino five ineracions. We can also noice ha single ineracions can differ from each oher by various facors and degrees. Some ineracions group few acions, while some ohers are longer, grouping more acions. B. Micro-blogging wihin he IDE Users are requesed o explicily ell wha hey are doing in he form of a shor, Twier-like, message. Developers are encouraged o conribue in firs person, discussing he hings hey care abou in heir code. For every message, we also record he developer who wroe i and he dae and ime a which he message has been wrien. To encourage developers o keep heir messages shor, we propose a (Twier-like) message lengh indicaor, suggesing a maximum message lengh of 140 characers.!! Fig. 4.? messages?!! James Core Developers sending micro-blog messages Figure 4 depics he micro-blogging scenario. Developers wrie and send a series of shor messages, in which hey can provide informaion abou heir aciviies and express quesions, remarks or any oher informaion relaed o he sofware projec. Messages are colleced and sored ino a cenral daabase. C. Quess: Building a Knowledge Base In our approach, we combine a micro-blog message and a series of ineracions ino a ques. We refer o he message as ques goal and o he ineracions as ques race. The ques race conains all he colleced ineracions unil a new ques goal is enered by he developer. Figure 5 depics how quess ac as conainers for a series of ineracions. Micro-blog messages are shown as aller lines wih respec o acions, while quess are represened as recangles. Fig. 5. Quess are formed by one message and a series of ineracions The chronological hisory of user ineracions wih he IDE can be suiable for he idenificaion of developmen sessions. According o Robbes e al., developmen sessions, defined as phases during which a developer acively modifies a sofware sysem, represen a valuable resource for program comprehension as hey hold useful informaion o comprehend he developmen plans of developers [4]. In our approach, no only informaion abou he developer aciviies are available, bu also explici messages wrien by he developer himself. Such messages poenially conain relevan informaion o beer undersand he session s course. D. Implemenaion SERG We implemened he proposed approach in an Eclipse plugin named James. James follows a clien-server archiecure. The clien plug-in collecs navigaion informaion and allows users (i.e., developers) o ener ques messages. Messages and acions are sen o he James server in order o be sored and analyzed. Noe ha our approach is language-independen, hus can be applied o any IDE (e.g., IBM Jazz, Microsof Visual Sudio). We also anicipae he implemenaion of a fully web-based clien. More informaion on James can be found a hp:// guzzi/james/. 2 TUD-SERG

5 SERG III. INITIAL EVALUATION We conduced an iniial evaluaion wih 7 developers in 5 differen seings. The goal of his exploraive sudy was o provide firs insighs ino he following research quesions: (1) How ofen do developers change ques? (2) Wha do developers wrie in messages? and (3) How can quess suppor programming aciviies in muli-developer projecs? A. Sudy Seup In all 5 seings, he developers used Eclipse wih he James plug-in insalled, ha colleced heir ques messages and IDE ineracions. We clarified he use of James o he developers. Seing I was a pilo sudy ha involved hree developers who were asked o micro-blog while performing he following mainenance ask on he James plug-in iself (4,5k lines of code): Implemen a new feaure ha rerieves he laes messages from he daabase and properly displays hem in he James view. Each paricipan performed he ask (which ook approximaely 4 hours) on her own. The goal of his pilo sudy was mainly o find ou abou he conen of messages. One of he paricipans was an exper of he code, while he oher wo only knew he basics of he approach. Only wo of he developers were familiar wih micro-blogging. Seings II o V were wih developers working on academic and indusrial sofware projecs. We invied one developer per projec o use James while performing her ypical developmen and mainenance aciviies for wo weeks. Boh developers in Seing II and Seing III were focusing on bug fixing: one in an indusrial projec (200k lines of code) and he oher one in an academic projec (19k lines of code). In Seing IV, he developer was esing a 4k lines of Java code academic projec. All he developers were exper of he code hey were mainaining. The main aciviy in Seing V was rying o undersand he srucure and dependencies beween Eclipse plug-ins. Only he developer in Seing II was no familiar wih micro-blogging. B. The Daa Se We colleced a oal of 300 messages in he 5 seings. For each of he hree developers in Seing I, here was a large number of messages (35-40) in a single developmen session, whereas in Seing II o V we idenified a oal of 29 sessions, mos of which couned beween 3 and 9 messages. Analyzing he ques races, we noiced ha he races of more han half of he quess conain beween 1 and 10 ineracions. Looking a he ineracions, we found ha he majoriy of ineracions (66%) comprise only a single acion. C. Daa Analysis Guzzi, Pinzger & van Deursen Combining Micro-Blogging and IDE Ineracions o Suppor Developers in heir Quess 1) How ofen do developers change ques? More han half of he messages have been wrien wihin 5 minues from he previous one. Of he remaining messages, many were wrien eiher wihin a shor (10 minues) or afer a longer (1 hour or more) delay. Almos no message was wrien afer minues from he previous one. Such a rend is common o all our 5 seings, indicaing ha he frequency a which developers updae heir ques message is probably independen from he seing in which hey work. The number and frequency of colleced messages are a firs indicaion ha users are willing o share wha hey are doing. 2) Wha do developers wrie in messages? To answer his quesion, we had a deailed look a he conen of all he 300 colleced messages. The conen of messages in a developmen session seems o be sufficien o ge an idea of wha he developer has been working on during he session. As an example, Figure 6 shows a word cloud 1 creaed from messages enered by one of he paricipans in Seing I, who worked on implemening he rerieval of messages from a daabase. The size of a word corresponds o is frequency in he messages. Fig. 6. Mos used words in messages by one of he users in Seing I We also observed ha a fair share (28%) of he messages reference a code elemen (package, class, mehod or aribue). Ineresingly, he porion of messages menioning a leas one code elemen is similar in every seing. To give a beer feeling abou heir conen, we presen a subse of messages colleced during our sudy: 1) firs figuring ou how o connec o he server 2) esing o see he imporance of he synchronized saecomparor 3) Trying o figure ou how o creae a proper UUID from an in in he daabase. 4) Finding ou ha blue acually means green here 5) No real significan differences found beween CrawlQueue / SpeedQueue, We noiced ha we can disinguish ques messages expressing pas, curren or fuure aciviies and messages commening on (pars of) he code. Some users also wroe o-do s. For his reason, we manually caegorized messages according o wha hey expressed. We observe ha 33% of he messages are abou fuure inenions ( Now I am going o.. ), 21% on a pas aciviy ( I jus did... ), while 23% covers an ongoing aciviy ( I am.. ). The remaining messages are divided beween commens ( This is like so, 16%) and odo s ( Laer, I will need o.., 6%). Figure 7 visually describes he resul of his caegorizaion. We can see ha only a minor par of messages does no fall ino one of he proposed caegories. Inspecing ques messages very close o each oher (wihin 30 seconds), we noiced ha hey are eiher direcly correlaed, wih he second message acing as annoaion for he previous ques message, or i is he case ha he firs message saes he end of he previous aciviy. 1 Image creaed by Wordle.ne (hp:// colors are chosen a random and do no represen any meaningful aribue. TUD-SERG

6 Guzzi, Pinzger & van Deursen Combining Micro-Blogging and IDE Ineracions o Suppor Developers in heir Quess oal commen 16% repor (pas) 21% Fig. 7. odo 6% remaining 1% inenion (fuure) 33% ongoing aciviy 23% Caegories of wha developers wrie in messages inenion (fuure) ongoing aciviy repor (pas) commen SERG We furher analyzed how messages connec o ineracions and we invesigaed wheher hese connecions are in principle meaningful. By manually comparing ques goals expressed in similar messages, we observed ha quess provide informaion valuable o oher developers working on similar asks, boh in he associaed races and in he goals hemselves. From he exploraory evaluaion, we can conclude ha knowledge abou he sofware being changed, consanly buil up by developers, can be capured in he form of quess. Accessibiliy o his knowledge base has a grea poenial for supporing developers in heir mainenance asks. Regarding he lengh of messages, more han half of he messages (58%) are beween 20 and 80 characers long, wih an average of 54.5 characers per message. This indicaes ha he limi suggesed by James of 140 characer per message is sufficien o express wha hey are doing. 3) How can quess suppor programming aciviies in muli developer projecs? Concerning his quesion, we analyzed quess from Seing I ha referred o Java classes and mehods. As resul, we found ha a porion of hese messages refers o common problems faced by he developers, as demonsraed by he following example: User A: I hink sarplugin() and sopplugin() are good places o sar/sop he job. (Q5) User B: firs figure ou where he job is invoked ;-) (Q6) User B: posponed saring - have o figure ou firs where o sar he job (Q7, 16 minues afer Q6) We can see ha he answer o Q6 is direcly embedded in Q5. However, no having access o his informaion, user B spen quie some ime browsing class files in he projec before evenually reaching he same conclusion as user A (2 minues afer seing Q7). User B could have saved almos 20 minues by having easy access o he ques message previously expressed in Q5 by user A. We hypohesize ha easy and ligh-weigh accessibiliy o he knowledge base abou he sysem could have helped (laer) developers in heir programming aciviy. D. Summary of Findings The number, frequency and conen of colleced messages indicae ha developers are willing and inclined o share wha hey are doing by means of a shor micro-blog message, regardless from he seing in which hey work. Developers paricipaing in our pilo sudy (Seing I) wroe a new ques message, in mos cases, every five minues. We found 5 caegories of messages and observed ha one hird of he messages express fuure inenions. Saus updaes referring o concluded and ongoing aciviies each accoun for one fifh of all he messages. Remaining messages included commens and o-do s. More han one fourh of all he colleced messages conained an explici reference o a code elemen (e.g., a class name). E. Fuure Research Direcions Through he sharing of he knowledge capured by James, developers could ake advanage of he knowledge of ohers. This paves he way for a range of applicaions, such as increasing knowledge awareness among developers or recommending comprehension pahs. For example, developers could acively follow (in a Twier-like manner) each oher, a projec, a class, ec.. Furhermore, given a ques goal, James could sugges where o look in he source code or which developer(s) o conac for assisance, esablishing in his way a foundaion for collaboraive program comprehension. We idenified a number of challenges o be ackled in order o srenghen our approach. Firs of all, we wonder and plan o sudy o wha exen he sharing of messages beween developers impacs he frequency of messages. We hypohesize ha he frequency of messages would slighly decrease when a developer filers ou hose messages in which she mainly alks o herself. Second, our Eclipse James plugin capures acions modeling navigaion informaion in he IDE, such as browsing hrough projecs files. However, oher programming aciviies, such as wriing code, are currenly no moniored. Furher invesigaion on which daa o collec and also on how o cluser acions in ineracions is needed. Third, developers referring o code elemens in ques messages suggess ha James should suppor developers, for example in he form of auo-compleion, o easily esablish a direc link beween heir messages and he source code. Addiionally, furher research on how o beer link ineracions o corresponding ques goals is needed. In his direcion, we propose o invesigae wheher and o which exen (auomaic) caegorizaions of messages can help deermining an appropriae associaion of ques messages wih ineracion races. Anoher imporan research quesion o be addressed is how o idenify informaion relevan o he user s goal and how o mainain he consisency and value of he colleced daa, when he sysem evolves. Furhermore, we envision ha users will have he possibiliy o ell he IDE wheher heir journey hrough he code (capured in he race) has been any useful o accomplish he ques goal. Wih direc feedback from developers, addiional value is added o he ques race. This informaion can be paricularly imporan when sharing his knowledge wih oher developers. 4 TUD-SERG

7 SERG Guzzi, Pinzger & van Deursen Combining Micro-Blogging and IDE Ineracions o Suppor Developers in heir Quess IV. RELATED WORK Our research builds upon several (sofware engineering) disciplines. Firs, here is relaed work concerning sudies of wha developers do, and wha informaion hey need from he IDE. As an example, Sillio e al. provide a sudy of quesions asked during programming change asks [5] and Ko e al. repor on an ehnographic sudy of how developers work a Microsof and wha heir informaion needs are [6]. Sofware developmen and mainenance are inherenly collaboraive aciviies: a survey of research in he area of collaboraive sofware engineering is provided by [7]. Web 2.0 provides new ways of collaboraion and informal communicaion [8], and he incorporaion of Web 2.0 echniques in sofware developmen is aracing more and more aenion boh in indusry and academia [9], [3]. As an example, IBM s Jazz 2 incorporaes he possibiliy of adding ags o work iems, and is use by IBM developers has been sudied exensively by Treude and Sorey [10]. Micro-blogging is an imporan elemen of Web 2.0, and hanks o he massive success of, e.g., Twier, an acive area of research iself 3 [11]. We are no aware of oher papers sudying he poenial of micro-blogging during sofware developmen. Similar o some exen o micro-blogging, however, are Inerne Relay Cha (IRC) discussions, and heir use during he developmen of he Linux Gnome code has recenly been analyzed by Shihab [12]. A number of exising sudies repor on he meaningfulness of navigaion races and heir poenial. Friz e al. conduced an empirical sudy assessing he relaionship beween programmers aciviy and wha a programmer knows abou a code base [13] and DeLine e al. repor resuls of wo sudies which demonsrae ha sharing navigaion daa can improve program comprehension and is subjecively preferred by users [14]. Boh Mylyn [15] and NavTracks [16] are navigaion aids based on wha he programmer is currenly looking a in he IDE, o recommend oher eniies o look a. Addiionally, a sudy by Robbes on recommender sysems based on recorded ineracions [17], recognizes he lack of suppor for ineracion annoaions. V. CONCLUDING REMARKS During he process of rying o undersand a piece of code, developers build up a subsanial body of knowledge on he code hey are inspecing knowledge ha ofen evaporaes afer he corresponding mainenance ask is finished. In his paper, we propose a mehod o sop his loss of valuable knowledge, by recording how developers inerac wih he source code, and by encouraging developers o ell heir eam members wha hey are doing. Based on our firs sudies, we consider he combinaion of micro-blogging messages and auomaically colleced ineracion daa a highly promising roue for recording and sharing knowledge buil up in he program comprehension process. 2 hp://jazz.ne/projecs/conen/projec/plans/jia-overview/ 3 See he bibliography a hp:// Fuure research direcions include enriching he James ool suie wih addiional mechanisms such as providing he abiliy o follow specific developers or work producs, enhance ques visualizaions, and carrying ou larger scale case sudies in which eams will be using James for a longer period of ime. REFERENCES [1] T. A. Corbi, Program undersanding: Challenge for he 1990s, IBM Sysems Journal, vol. 28, no. 2, pp , [2] T. O Reilly and S. Milsein, The Twier Book. O Reilly Media, Inc., [3] A. van Deursen, A. Mesbah, B. Cornelissen, A. Zaidman, M. Pinzger, and A. Guzzi, Adinda: A knowledgeable, browser-based IDE, in 23d Inernaional Conference on Sofware Engineering; New Ideas and Emerging Resuls Track (ICSE NIER). ACM, [4] R. Robbes and M. Lanza, Characerizing and undersanding developmen sessions, in ICPC 07: Proceedings of he 15h IEEE Inernaional Conference on Program Comprehension. Washingon, DC, USA: IEEE Compuer Sociey, 2007, pp [5] J. Sillio, G. C. Murphy, and K. De Volder, Asking and answering quesions during a programming change ask, IEEE Transacions on Sofware Engineering, vol. 34, no. 4, pp , [6] A. J. Ko, R. DeLine, and G. Venolia, Informaion needs in collocaed sofware developmen eams, in ICSE 07: Proceedings of he 29h inernaional conference on Sofware Engineering. Washingon, DC, USA: IEEE Compuer Sociey, 2007, pp [7] J. Whiehead, Collaboraion in sofware engineering: A roadmap, in FOSE 07: 2007 Fuure of Sofware Engineering. Washingon, DC, USA: IEEE Compuer Sociey, 2007, pp [8] T. O Reilly, Wha is Web 2.0: Design paerns and business models for he nex generaion of sofware, Oreillyne, 2005, hp:// com/pub/a/oreilly/im/news/2005/09/30/wha-is-web-20.hml. [9] C. Treude, M.-A. Sorey, K. Ehrlich, and A. van Deursen, Web2se: Firs workshop on web 2.0 for sofware engineering, in Companion o he Proceedings of he Inernaional Conference on Sofware Engineering. ACM, [10] C. Treude and M.-A. Sorey, How agging helps bridge he gap beween social and echnical aspecs in sofware developmen, in Proceedings of he 31s Inernaional Conference on Sofware Engineering (ICSE 09). IEEE Compuer Sociey, [11] J. H. Grace, D. Zhao, and d. boyd, Eds., Proceedings of he CHI Workshop on Microblogging: Wha and How can We Learn from I? ACM, 2010, hp:// julia/chi2010.hml. [12] E. Shihab, Z. M. Jiang, and A. E. Hassan, On he use of Inerne Relay Cha (IRC) meeings by developers of he GNOME GTK+ projec, in Proceedings of he 6h IEEE Working conference on Mining Sofware Reposiories (MSR). IEEE, [13] T. Friz, G. C. Murphy, and E. Hill, Does a programmer s aciviy indicae knowledge of code? in ESEC-FSE 07: Proceedings of he he 6h join meeing of he European sofware engineering conference and he ACM SIGSOFT symposium on The foundaions of sofware engineering. New York, NY, USA: ACM, 2007, pp [14] R. DeLine, M. Czerwinski, and G. Roberson, Easing program comprehension by sharing navigaion daa, in VLHCC 05: Proceedings of he 2005 IEEE Symposium on Visual Languages and Human-Cenric Compuing. Washingon, DC, USA: IEEE Compuer Sociey, 2005, pp [15] M. Kersen and G. C. Murphy, Using ask conex o improve programmer produciviy, in SIGSOFT 06/FSE-14: Proceedings of he 14h ACM SIGSOFT inernaional symposium on Foundaions of sofware engineering. New York, NY, USA: ACM, 2006, pp [16] J. Singer, R. Elves, and M.-A. Sorey, Navracks: Supporing navigaion in sofware, in IWPC 05: Proceedings of he 13h Inernaional Workshop on Program Comprehension. Washingon, DC, USA: IEEE Compuer Sociey, 2005, pp [17] R. Robbes, On he evaluaion of recommender sysems wih recorded ineracions, in SUITE 09: Proceedings of he 2009 ICSE Workshop on Search-Driven Developmen-Users, Infrasrucure, Tools and Evaluaion. Washingon, DC, USA: IEEE Compuer Sociey, 2009, pp TUD-SERG

8 Guzzi, Pinzger & van Deursen Combining Micro-Blogging and IDE Ineracions o Suppor Developers in heir Quess SERG 6 TUD-SERG

9

10 TUD-SERG ISSN SERG