Work fragmentation in developer interaction data
Open accessAbstract
ABSTRACT Information workers and software developers are exposed to work fragmentation, an interleaving of activities and interruptions during their normal work day. Small‐scale observational studies have shown that this can be detrimental to their work. In this paper, we perform a large‐scale study of this phenomenon for the particular case of software developers performing software evolution tasks. Our study is based on several thousands interaction traces collected by Mylyn and the Eclipse Usage Data Collector. We observe that work fragmentation is correlated to lower observed productivity at both the macro level (for entire sessions) and at the micro level (around markers of work fragmentation); further, longer activity switches seem to strengthen the effect, and different activities seem to be affected differently. These observations give ground for subsequent studies investigating the phenomenon of work fragmentation.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
1 of 28 cited sources checked · 1 supported · 0 flagged
- Findingown data
26% of traces had at least an interruption over 8 hours.
“Finally, we found that 26% of traces had at least an interruption over 8 hours, which is hence large enough to represent the difference between two working days.”
Quote in the paperSubstantial claim - Findingown data
A long interruption of activity implicitly splits a trace into two sub-traces.
“After exploring a sample of traces, we noticed that a long interruption of activity implicitly splits a trace into two sub-traces.”
Quote in the paperSubstantial claim - Findingown data
The Mylyn dataset contains 6182 bug reports with 8102 Mylyn task contexts.
“In total, there were 6182 bug reports which contained 8102 Mylyn task contexts.”
Quote in the paperNot a substantial claim - Findingown data
Short interruptions predominate over prolonged interruptions.
“Moreover, we observe that the short interruptions predominate over the prolonged interruptions (Table IV).”
Quote in the paperNot a substantial claim - Findingown data
The effect size of interruptions over number of edits per minute is (very) large.
“As shown in Table VII, we note that the effect size of the interruptions over the number of edits by minute is (very) large.”
Quote in the paperSubstantial claim
- Findingown data
We find an inverse relationship between number of interruptions and our three productivity indicators.
“In Section 5, we answer our first research question: we find an inverse relationship between number of interruptions and our three productivity indicators.”
Quote in the paperSubstantial claim- The authors state this as an assumption: A productive programmer will perform more coding activities than selections or navigations.
- Findingown data
There is a large difference between sessions without interruptions and those with interruptions in distribution of events per minute and edit ratio.
“We observe a large difference between the sessions without interruptions and the ones who do.”
Quote in the paperSubstantial claim - Findingown data
After applying clustering techniques to all subsequences, three recurrent patterns of interruptions were found: neutral, positive, and negative.
“After applying clustering techniques over all the subsequences, we always found the formation of three recurrent patterns that show different effects of the interruption: neutral, positive and negative.”
Quote in the paperSubstantial claim - Findingown data
The edit ratio is smaller in sessions with prolonged interruptions compared to sessions with only short interruptions.
“Similar results occurs when we look at the edit ratio (Figure 6): the edit ratio is smaller in sessions that have prolonged interruptions, compared to the ones that only have short interruptions.”
Quote in the paperSubstantial claim - Findingown data
The effect size of interruption duration on the number of edits per minute is very large.
“We note that the effect size of the interruption duration over the number of edits per minute is very large.”
Quote in the paperSubstantial claim - Findingown data
Based on the type of events executed, there are differences in the activities performed after a positive or negative interruption.
“Finally Section 11 answers our fifth research question; based on the type of events executed, we find differences in the activities performed after a positive or negative interruption.”
Quote in the paperSubstantial claim - Findingown data
There are three patterns of interruptions with different characteristics.
“we further find three patterns of interruptions with different characteristics.”
Quote in the paperSubstantial claim - Findingown data
The rate of events per minute decreases slightly when the session has more interruptions.
“Further, we observe that the rate of events per minute decreases slightly when the session has more interruptions.”
Quote in the paperSubstantial claim - Findingown data
In UDC data, there is a significant decrease of edit events, being below selection events approximately 10 minutes before the interruption.
“The latest can be better visualized in 14 H. SANCHEZ, R. ROBBES, L. CRUZ, V. GONZALEZ Figure 15 with the UDC data as a significant decrease of edit events, being below the selection events approximately 10 minutes before the interruption.”
Quote in the paperNot a substantial claim - Findingown data
98% of sessions had at least one gap of activity.
“We identified that 98% of sessions had at least one gap of activity.”
Quote in the paperSubstantial claim - Findingown data
In the average case, the activity reaches the median activity 12 to 18 minutes after the interruption.
“We see that in the average case, it reaches the median activity 12 to 18 minutes after the interruption.”
Quote in the paperNot a substantial claim - Findingown data
This relationship is more pronounced for development sessions with at least one longer interruption.
“In Section 6, we answer our second research question, finding that this relationship is more pronounced for development sessions with at least one longer interruption.”
Quote in the paperSubstantial claim - Findingown data
There is a gradual increase of productivity during the recovery time after an interruption.
“In Section 10, we answer the fourth research question, finding a gradual increase of productivity during the recovery time after an interruption”
Quote in the paperSubstantial claim - Findingown data
User activity, measured as edits and selections per minute, follows an inverse relationship with the number of interruptions.
“Adding this to our previous result, we observe that both the user activity (in terms of raw quantity of edits and selections per minute) and the user productivity (in terms of edit ratio), both follow an inverse relationship with the number of interruptions.”
Quote in the paperSubstantial claim - Findingcitation
In sessions without interruptions, the edit lag is clearly visible at the start of the session, similar to Parnin's study.
“This is similar to the edit lag in Parnin's study [9]: in sessions without interruptions, the edit lag is clearly visible at the start of the session.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [9] 9. C. Parnin and S. Rugaber, "Resumption strategies for interrupted programming tasks," Software Quality Journal, vol. 19, no. 1, pp. 5-34, 2011.
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Findingown data
In sessions without interruptions, edit frequency exceeds selection frequency.
“Moreover, the edit frequency exceeds the selection frequency in sessions without interruptions.”
Quote in the paperSubstantial claim - Findingreasoning
Time series without interruptions have much more edits in the middle of the session than the others.
“We also notice that the time series without interruptions have much more edits in the middle of the session than the others.”
Quote in the paperSubstantial claim - Findingown data
There is a relation between recovery time productivity and the nature of the interruption, whether positive or negative.
“and a relation with the nature of the interruption, whether is positive or negative.”
Quote in the paperSubstantial claim - Findingown data
Our productivity indicators are lower in the vicinity of interruptions.
“In Section 7 we answer our third research question and find that our productivity indicators are indeed lower in the vicinity of interruptions”
Quote in the paperSubstantial claim - Findingown data
The three metrics show a tendency to increase and reach a maximum between the last phase of the recovery time and the peak of the session.
“The three metrics show a tendency to increase and reach a maximum between the last phase of the recovery time and the peak of the session.”
Quote in the paperNot a substantial claim - Findingown data
After a negative interruption, navigation around classes, find and replace, searches, debug, clean and build are more common.
“On the other hand the navigation around classes, find and replace, searches, debug, clean and build are actions more common after a negative.”
Quote in the paperSubstantial claim - Findingown data
The quartiles of the distribution of the duration of the peak phase are 3.38, 8.05, and 16.31 minutes.
“25% 50% 75% quartile 3.38 8.05 16.31”
Quote in the paperNot a substantial claim - Findingnone given
There is no clear pattern during a neutral interruption.
“There is not a clear pattern during a neutral interruption.”
Quote in the paperNot a substantial claim - Findingown data
Despite differences in effect sizes, the differences on UDC are still significant.
“Note despite the differences in effect sizes, the differences are still significant.”
Quote in the paperSubstantial claim - Findingown data
After a positive interruption, the more common activities are text edition, refactoring, file management and, to a lesser extent, navigation through the text.
“After a positive interruption we can see that the more common activities are text edition, refactoring, file management and, to a lesser extent, navigation through the text.”
Quote in the paperSubstantial claim - Findingown data
On UDC data, the edit ratio decreases as the number of interruptions increases, reaching maximum when there are none.
“The edit ratio behaves similarly in comparison with the data on Mylyn, where the median changes accordingly with the number of interruptions, decreasing when there are more and reaching the maximum when there are none.”
Quote in the paperSubstantial claim - Findingnone given
On UDC data, before a negative interruption, editions per minute is above average for the 30 minutes before the interruption.
“Also, the editions per minute metric is above the average for the 30 minutes before the interruption.”
Quote in the paperNot a substantial claim - Findingown data
On UDC data, before a positive interruption, editions per minute is below average for approximately 16 minutes prior to the interruption.
“It is important to notice that before the interruption happens the editions per minute metric is below the average for approximately 16 minutes prior to the interruption.”
Quote in the paperSubstantial claim - Findingown data
On UDC data, with short interruptions the metrics are greater than when facing at least a prolonged one.
“We can see in the Figure 13 that with short interruptions the metrics are greater than when facing at least a prolonged one, for more time is needed to recover after a long interruption.”
Quote in the paperSubstantial claim - Findingown data
On UDC data, after a negative interruption, the metrics take longer to reach the median.
“In contrast, when facing the effects of a negative interruption the metrics take longer to reach the median.”
Quote in the paperSubstantial claim - Findingown data
On UDC data, edits pass below selections near the interruption.
“Similarly than for Mylyn, we can see that the edits pass below the selections events near the interruption.”
Quote in the paperNot a substantial claim - Findingnone given
Navigation in the code and control version activities are more common after the Recovery Time.
“The navigation in the code and control version activities are more common after the Recovery Time.”
Quote in the paperNot a substantial claim - Findingown data
The overall effects observed were larger for the Mylyn dataset than for the UDC dataset.
“the overall effects observed were larger for the Mylyn dataset than for the UDC dataset.”
Quote in the paperNot a substantial claim - Findingown data
The before interruption phase represents the time where productivity drops just before the next interruption.
“the before interruption phase represents the time where the productivity drops just before the next interruption, as seen in the results of the last research question.”
Quote in the paperNot a substantial claim - Findingown data
Our global analysis found an inverse relationship between number and duration of interruptions and all three of our productivity indicators.
“Our global analysis found an inverse relationship between number and duration of interruptions and all three of our productivity indicators.”
Quote in the paperSubstantial claim - Findingown data
After a positive interruption the most common events during the first minutes of the Recovery Time are those with an assertive intention such as edition, refactoring and saving files.
“In addition, we found that after a positive interruption the most common events during the first minutes of the Recovery Time are those with an assertive intention such as edition, refactoring and saving files.”
Quote in the paperSubstantial claim - Findingown data
We analyzed several thousands software evolution tasks, originating from several dozens of developers.
“We analyzed several thousands software evolution tasks, originating from several dozens of developers.”
Quote in the paperSubstantial claim - Findingown data
The workbench activation and deactivation events were reliable markers of when the user leaves and returns to Eclipse.
“For instance, we found that they were reliable markers of when the user leaves and returns to Eclipse-and we used this fact to accurately detect interruptions-but we had more uncertainty on other scenarios.”
Quote in the paperSubstantial claim - Study design and conductown data
Massive events overstate developer activity because each event does not correspond to an individual developer action.
“These events overstate the activity of developers as each of these does not correspond to an individual developer action; rather, the entire sequence is.”
Quote in the paperSubstantial claim - Premisecitation
The operational data used (Mylyn and UDC) is of lower quality than data from a full-fledged observational study.
“The downside is that the data exploited, being operational data [1], is of lower quality than data extracted from a full-fledged observational study.”
Quote in the paperSubstantial claim0 of 1 sources checked- cites [1] 1. A. Mockus, "Is mining software repositories data science? (keynote)," in Proceedings of MSR 2014, 2014, p. 1. source
- Interpretationreasoning
Too much aggregation in a trace severely compromises detection of work fragmentation.
“Clearly, too much aggregation in a given trace severely compromises the detection of work fragmentation as this relies on accurate timestamps.”
Quote in the paperSubstantial claim - Study design and conductreasoning
Compressing the MTS by pulling apart interruptions as a new variable allows computing activity indicators independently of the amount of inactivity in a session.
“Consequently, the temporal component represents the real working time of a programming task, excluding inactivity.This allows us to compute our activity indicators (number of edits, selections, edit ratio) independently of the amount of inactivity in a session.”
Quote in the paperSubstantial claim - Interpretationown data
The relationship between user activity and interruptions could be adversely affected by interruptions of longer duration.
“We conclude that the relationship between user activity and interruptions could be adversely affected by interruptions of longer duration.”
Quote in the paperSubstantial claim - Interpretationown data
The inverse relationship between productivity and interruption duration is more pronounced in sessions with at least one longer interruption.
“These findings seem to indicate that the inverse relationship between productivity and time of duration is more pronounced in session with at least one longer interruption.”
Quote in the paperSubstantial claim - Interpretationown data
The relationship between number of interruptions and productivity indicators (edits and selections) tends to be inversely proportional.
“Therefore, we can intuit that the relationship between number of interruptions and the productivity indicators that are edits and selections, tends to be inversely proportional.”
Quote in the paperSubstantial claim - Interpretationreasoning
The higher edit ratio after positive interruptions is in accordance with the hypothesis of more efficient activity after having looked for missing information.
“positive interruptions have a higher edit ratio after the interruption (in accordance with the hypothesis of a more efficient activity after having looked for missing information)”
Quote in the paperSubstantial claim - Interpretationown data
Work fragmentation is extremely prevalent in our dataset.
“This first result tells us that work fragmentation is extremely prevalent in our dataset.”
Quote in the paperSubstantial claim- The authors state this as an assumption: Activity gaps observed in IDE activity are indicators of work fragmentation in general.
- Interpretationcitation
The drop in activity before an interruption may be because the interruption was imminent and the programmer used suspension strategies, which reduce activity.
“Also, when the interruption is imminent or expected, the programmer make use of different suspension strategies like writing physical notes, making a mental note or leaving a reminder cue on the code or window, as mentioned by Parnin and DeLine [10].These activities reduce the activity before the gap and they are seen in the interaction data mostly as selection events.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [10] 10. C. Parnin and R. DeLine, "Evaluating cues for resuming interrupted programming tasks," in Proceedings of CHI 2010, 2010, pp. 93-102.
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Premisereasoning
The UDC data size is several orders of magnitude larger than the Mylyn dataset.
“As the UDC was installed by default on all the Eclipse distributions from 2008 to 2010, the size of the information collected is several orders of magnitude larger than the Mylyn dataset, which was collected since then on a few dozen of developers who installed it voluntarily and contributed to the Mylyn and Eclipse projects.”
Quote in the paperSubstantial claim- Rests on an assumption: The Mylyn and UDC datasets represent the same kind of information.
- Rests on an assumption: The interaction data recorded by Mylyn is the basis for a recommendation tool, and is focused on Java projects.
- Interpretationreasoning
After a negative interruption there are more uncertainty and doubt judging by the activities performed like debugging, searching for text or navigating around classes; activities related to program comprehension.
“After a negative interruption there are more uncertainty and doubt judging by the activities performed like debugging, searching for text or navigating around classes; activities related to program comprehension.”
Quote in the paperSubstantial claim - Interpretationreasoning
After a positive interruption there are more assertive actions with a clear intention like refactoring a class or saving all changes; activities related to program edition.
“We can conclude that after a positive interruption there are more assertive actions with a clear intention like refactoring a class or saving all changes; activities related to program edition.”
Quote in the paperSubstantial claim - Premisecitation
Multitasking can allow the worker to use dead periods of the project where there is a decrease of the required activities and do tasks related to other projects, increasing efficiency and productivity.
“Multitasking can allow the worker to use dead periods of the project where there is a decrease of the required activities and do tasks related to other projects, increasing the efficiency and productivity [41].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [41] 41. R. Van Solingen, E. Berghout, and F. Van Latum, "Interrupts: just a minute never is," IEEE software, no. 5, pp. 97-103, 1998. source
- Interpretationreasoning
Work fragmentation is not a synonym of lower productivity rates.
“Certainly, work fragmentation is not a synonym of lower productivity rates.”
Quote in the paperSubstantial claim - Premisecitation
Our results and theoretical foundations are based on observational studies performed on information workers' development environments.
“Our results and theoretical foundations are based on observational studies performed on information workers' development environments [5,6,35,10].”
Quote in the paperSubstantial claim0 of 4 sources checked- cites [5] 5. G. Mark, V. M. González, and J. Harris, "No task left behind?: examining the nature of fragmented work," in Proceedings of CHI 2005, 2005, pp. 321-330. source
- cites [6] 6. S. T. Iqbal and E. Horvitz, "Disruption and recovery of computing tasks: field study, analysis, and directions," in Proceedings of CHI 2007, 2007, pp. 677-686. source
- cites [35] 35. J. Cohen, "The earth is round (p < 0.5)," American Psychologist, vol. 49, no. 12, pp. 997-1003, 1994. source
- cites [10] 10. C. Parnin and R. DeLine, "Evaluating cues for resuming interrupted programming tasks," in Proceedings of CHI 2010, 2010, pp. 93-102.
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationreasoning
The UDC data is a better source of information to analyze phenomena on a wide scale.
“This makes of the UDC data a better source of information to analyze phenomenons on a wide scale.”
Quote in the paperSubstantial claim- Rests on an assumption: The Mylyn and UDC datasets represent the same kind of information.
- Rests on an assumption: The interaction data recorded by Mylyn is the basis for a recommendation tool, and is focused on Java projects.
- Interpretationown data
In general, the effect of positive and negative interruptions is the inverse.
“In general, the effect of positive and negative interruptions is the inverse.”
Quote in the paperSubstantial claim - Interpretationown data
More time is needed to recover after a long interruption.
“We can see in the Figure 13 that with short interruptions the metrics are greater than when facing at least a prolonged one, for more time is needed to recover after a long interruption.”
Quote in the paperSubstantial claim - Study design and conductreasoning
For the Mylyn dataset, the main threat to validity is due to the exclusion of development sessions with aggregated information.
“For the Mylyn dataset, the main threat to validity is due to the exclusion of development session with aggregated information.”
Quote in the paperSubstantial claim - Study design and conductcitation
Our three indicators (edits per minute, selections per minute, and edit ratio) provide a reasonable measure of productivity.
“We believe our three indicator (edits per minute, selections per minute, and edit ratio) provide a reasonable measure of productivity (especially with the addition of edit ratio, used in other work [13]).”
Quote in the paperSubstantial claim0 of 1 sources checked- cites [13] 13. M. Kersten and G. C. Murphy, "Using task context to improve programmer productivity," in Proceedings of FSE 2006, 2006, pp. 1-11. source
- Study design and conductcitation
The main threats to the validity of our study are construct validity threats due to the operational nature of the data recorded by Mylyn and the UDC.
“The main threats to the validity of our study are construct validity threats due to the operational nature of the data recorded by Mylyn and the UDC [1].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [1] 1. A. Mockus, "Is mining software repositories data science? (keynote)," in Proceedings of MSR 2014, 2014, p. 1. source
- Classified as probably not a substantial claim. 55
- May combine two claims. 70
- The quote only partly states this claim. 2
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
PremisecitationZou and Godfrey found omnipresence of inactivity in interaction data, interpreted as interruptions, corroborated by programmers.
“One of their findings was the omnipresence of inactivity in the interaction data, that they interpreted as interruptions.They corroborated this with the programmers which agreed that many such periods of inactivity were indeed interruptions.”
Quote in the paperNot a substantial claim1 of 1 sources checked- cites [2] 2. L. Zou and M. W. Godfrey, "An industrial case study of program artifacts viewed during maintenance tasks," in Proceedings of WCRE 2006, 2006, pp. 71-82. source
May combine two claims.
Findingown data12% of normal events had a duration >0 seconds and 3% ≥1 hour.
“However, 12% of normal events had a duration > 0 seconds and 3% ≥ 1 hour, these events are outliers.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim. May combine two claims.
FindingreasoningAfter keeping traces without aggregate information and a little group with aggregate info (max 5 min or two actions), we were left with 6260 traces.
“In order to keep as many traces as possible, we have also kept a little group of traces with aggregate information where the aggregate events have a maximum duration time of five minutes (to minimize uncertainty) or have only two aggregate actions (since the actual event timestamps are known in this case).Thus, we were left with 6260 traces.”
Quote in the paperSubstantial claimClassified as probably not a substantial claim.
Findingown dataAfter considering minimum duration 30 minutes, we obtained 4284 useful sessions.
“After this, we considered a minimum duration time of 30 minutes in order to ensure a minimum of activity during a session.In this way, we obtained a final total of 4284 useful sessions to be processed in the next phase.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingown data156 traces (3%) had more than one timezone.
“We found 156 traces (3%) with more than one timezone.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataAfter preprocessing, edit events increased by 5%, selection events decreased by 20%, total events decreased by 10%.
“edit 452236 475554 +5% selection 658768 527652 -20% total 1111004 1003206 -10%”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingown dataThe total number of selection events was reduced by 45% after joining massive events.
“The total number of selection events was reduced by 45%.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataFor selections, the effect is moderate for sessions having up to three interruptions, and large to very large for sessions with over four interruptions.
“In selections, the effect is moderate for sessions having up three interruptions, and large to very large for sessions with over four interruptions.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataAll differences observed between interruption groups are statistically significant with very low p-values according to Mann-Whitney U-test.
“First, all the differences observed are statistically significant with very low p-values (see Table VII) according to the Mann-Whitney U-test.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataPrevalence of interruptions by duration: 69% 3-12 min, 18% 12-30 min, 9% 30min-2hr, 4% 2hr-8hr.
“duration ratio examples [3 -12min 69% short pause, answer a question, thinking, looking for interruption [12 -30min 18% coffee break, short meeting, extended interruption [30min -2hr 9% lunch break, a meeting [2hr -8hr 4% extended meeting”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataIn sessions with at least one interruption, code navigation (selections) tends to exceed the frequency of edits, and this is more pronounced when there is at least one prolonged interruption.
“The opposite occurs in sessions with at least one interruption-and is more pronounced when there is at least one prolonged interruption-, where the code navigation tends to exceed the frequency of edits.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataSession statistics: total 4284, min 2, 1st Qu 18, median 35, mean 48.91, 3rd Qu 62, max 535.
“total 4,284 min.2 min 1st Qu. 18 min median 35 min mean 48.91 min 3rd Qu. 62 min max.535 min”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataThe relationship between edit ratio and number of interruptions is statistically significant, with effect sizes large to very large.
“A look at the practical and statistical significance of these results (Table VII, bottom) show that the results are (unsurprisingly) statistically significant, and that the observed effect sizes are large to very large.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataThe effect size of interruption duration on selections per minute is moderate for short interruptions and large for prolonged interruptions.
“In selections, the effect is moderate for short interruptions, and large for prolonged interruptions.”
Quote in the paperSubstantial claimThe quote only partly states this claim.
Findingown dataIn sessions with at least one prolonged interruption (≥12 minutes), the number of events per minute is lower than in sessions with only short interruptions (<12 minutes).
“We observe that the number of events per minute is lower in sessions with at least one prolonged interruption.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataThe edit ratio drops slightly the closer one is to an interruption, and this effect is small but significant.
“The boxplots in Figure 9 show that the edit ratio drops slightly the closer we are to an interruption.The effect is small, but significant (see Table IX).”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataThe local analysis shows three well-defined groups of interruptions, with the two largest having clear effects on activity in the session.
“This local analysis shows that there are indeed three well-defined groups of interruptions, with the two largest of them having clear effects on the activity in the session.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataAll previous conclusions agree with the UDC data, although the size of the observed effects differ.
“In Section 9, we replicate our first three research questions with the UDC data; we find that all of the previous conclusions agree with this new data, although the size of the observed effects differ.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataIn sessions with interruptions, the median activity is less than in sessions without interruptions, mainly in edit frequency.
“We observe that the median activity in sessions with interruptions is less than in sessions without interruptions, mainly in the edit frequency.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataThe mean edit ratio for sessions with short interruptions is 0.4, so the edit ratio close to interruptions is clearly lower in the 5 to 10 minutes around an interruption.
“As a reference, the mean edit ratio for sessions with short interruptions is 0.4, so the edit ratio close to the interruptions are clearly lower in the 5 to 10 minutes around an interruption.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataOn UDC data, sessions with only short interruptions show a level of edit activity similar to selection activity overall, but with a tendency to rise over time (except a drop in the last segment).
“Sessions with only short interruptions show a level of edit activity similar to selection activity overall, but with a tendency to rise overtime (except a drop in the last segment).”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataOn UDC data, the effect of interruptions on productivity appears less pronounced than in Mylyn; most observed effects are medium, while in Mylyn they were large.
“An important difference is that the effect overall appears to be less pronounced in UDC and we can see it on the effect size tests shown in the Table XVI.Most of the observed effects are medium, while in the Mylyn datasets the effects were large.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataOn UDC data, the effect sizes for interruption duration are medium to large, less pronounced than in Mylyn.
“The effect size test results in the Table XVII matches the previous observations on a less pronounced effect compared to the Mylyn dataset.The Cohen's d test results tell us that we can label the effect from medium to large and the median values act accordingly to our hypothesis and conclusions with Mylyn.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataOn UDC data, after a negative interruption, editions per minute is below selections per minute and takes longer to reach average.
“On the contrary to facing a positive interruption, the editions per minute metric is below the selections per minute, and the former takes longer than the latter to reach the average value.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataOn UDC data, the median editions and selections per minute are greater in sessions without interruptions, and editions are more common than selections.
“The median of editions and selections per minute are greater in sessions without interruptions, and the editions are more common than selections.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataFrom the query, 4,321,349 unique events were extracted, around 0.18% of the whole dataset.
“From this query we extracted 4,321,349 unique events, which are around 0.18% of the whole dataset.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataAfter splitting into sessions and filtering for at least 30 minutes of productive time, 15,825 useful sessions were obtained from UDC, compared to 4,284 from Mylyn.
“After this, we obtained a total of 28,989 different sessions; but after a filter to keep only those with at least 30 minutes of productive time (as we did with the Mylyn dataset), we ended up with 15,825 useful sessions, in contrast with the 4,284 we had from Mylyn.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataOn UDC data, close to the interruption the frequency of editions and selections drastically drop, and in a radius of around 10 minutes both metrics are below the overall median.
“We observed that close to the interruption the frequency of editions and selections drastically drop, and in a radius of around 10 minutes both metrics are below the overall median.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataOn average, the peak lasts for 12 minutes, while the maximum registered is of 145 minutes.
“On average, the peak lasts for 12 minutes, while the maximum registered is of 145 minutes.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataOn UDC data, when facing zero interruptions, editions and selections per minute are greater than with one or more interruptions, and as more interruptions occur these metrics gradually decrease.
“When facing zero interruptions the editions and selections per minute are greater than with one or more interruptions, and as more interruptions occur this metrics gradually decrease.”
Quote in the paperSubstantial claimMay combine two claims. The quote only partly states this claim.
Findingown dataThe proportion of events after classification is: edition 34.6%, selection 31.1%, system 31.5%, control 0.8%.
“The proportion of events after the classification is shown in the Table XIII.We used an iterative process involving two of the authors of the paper to arrive to this result; the process was iterative, until we reached consensus.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataOn UDC data, both positive and negative interruptions have a proportion of 44% each, and neutrals 12%.
“Both positive and negative interruptions have a proportion of 44% each of all the interruptions, and the neutrals stand with the 12%, and they are similar to the proportions on Mylyn.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataOn UDC data, editions per minute recover quickly, approximately 5 minutes after the interruption, but selections per minute take longer to reach the global average and tend to be below average for an extended period.
“The editions per minute recover quickly, approximately 5 minutes after the interruption, but the selections per minute take a little longer to reach the global average and this metric tend to be below the average for an extended period.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataOn UDC data, when facing at least one prolonged interruption, the metrics drop compared to short interruptions and selections are more frequent than edit events.
“When facing at least one prolonged interruption we can see the metrics drop in comparison with short interruptions and the selections are now more frequent than the edit events.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataThe results indicate a clear diminish of productivity when facing interruptions, but with a high number of interruptions the change of productivity stops decreasing.
“Furthermore, the results indicate a clear diminish of productivity when facing interruptions, but with a high number of interruptions the change of productivity stops decreasing.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataThe latter actually occurs in the results but the effect is too subtle.
“The latter actually occurs in the results but the effect is too subtle.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataThis analysis also found two well-defined patterns around interruptions: interruptions yielding negative effects (consistent with a real-life interruption involving an expensive context switch), and interruptions with positive effects (consistent with information-seeking behavior).
“This analysis also found two well-defined patterns around interruptions: interruptions yielding a negative effects (consistent with a real-life interruption involving an expensive context switch), and interruptions with positive effects (consistent with information-seeking behavior).”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataThe additional evidence uncovered in the UDC supports this hypothesis, since different activities appear to take place in both types of interruptions.
“the additional evidence uncovered in the UDC does support this hypothesis, since different activities appear to take place in both types of interruptions.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim. May combine two claims.
Findingown dataOur local analysis uncovered two well-defined patterns around gaps of inactivity: ones hypothesized as actual interruptions (negative effect post-interruptions), and ones hypothesized as more likely information-seeking activities (positive effect post-interruption).
“We note that our local analysis uncovered two well-defined patterns around gaps of inactivity: ones that we hypothesize are actual interruptions (negative effect post-interruptions), and the ones that we hypothesize are more likely information-seeking activities (positive effect postinterruption).”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataOur additional dataset (the UDC) comes from a much larger and more varied sample of users, and does show similar behavior, which raises confidence in our results.
“Our additional dataset (the UDC) comes from a much larger and more varied sample of users, and does show similar behavior, which raises confidence in our results.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataA subsequent local analysis around interruptions confirmed these results as the activity around interruptions was found to be lower than average.
“A subsequent local analysis around interruptions confirmed these results as the activity around interruptions was found to be lower than average.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataWe found a higher productivity when the interruption is positive and identified a positive evolution of the metrics as the programmer advances through the Recovery Time, reaching a peak of productivity between the last minutes of the Recovery Time and 10 minutes before the next interruption happens.
“We first analyzed the Recovery Time in detail, finding a higher productivity when the interruption is positive and we identified a positive evolution of the metrics as the programmer advances through this stage, reaching a peak of productivity between the last minutes of the Recovery Time and 10 minutes before the next interruption happens.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataAfter a negative interruption the most common events are debugging, searching and navigation around classes, which tell us about a doubtful and uncertain behavior from the programmer.
“In contrast, after a negative interruption the most common events are debugging, searching and navigation around classes, which tell us about a doubtful and uncertain behavior from the programmer.”
Quote in the paperSubstantial claimClassified as probably not a substantial claim. May combine two claims.
Study design and conductreasoningThe partition of data into sessions does not alter the results because we are interested in values by minute.
“Additionally, the partition of the data into sessions do not alter the results since we are interested in the values by minute, so having longer sessions do not necessarily increase the number of events per minute.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S2 (checkable). May combine two claims.
InterpretationreasoningTrading quality for quantity allows exploring different aspects and generating hypotheses for subsequent studies.
“Trading quality for quantity allows us to explore different aspects of the problem, and to generate hypotheses for subsequent studies of work fragmentation and interruptions in software development.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationInformation workers average 3 minutes on a task before switching to another task.
“An observational study by Gonzalez and Mark found that information workers experience high level of multitasking, averaging 3 minutes on a task before switching to another task [3].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [3] 3. V. M. González and G. Mark, ""constant, constant, multi-tasking craziness": managing multiple working spheres," in Proceedings of CHI 2004, 2004, pp. 113-120. source
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
PremisereasoningThe study of Parnin and Rugaber is closest in amount of data, but its large-dataset analysis focused principally on edit lag, while this paper investigates productivity indicators along entire session.
“The study of Parnin and Rugaber is the closest to ours in terms of amount of data considered.However, the analysis performed on large datasets in their study focused principally on the edit lag metric, while we investigate metrics which are indicators of productivity along the entire session.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationA worker needs on average 25 minutes to get back on an interrupted task.
“a study of 24 information workers found that a worker needs on average 25 minutes to get back on an interrupted task [5].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [5] 5. G. Mark, V. M. González, and J. Harris, "No task left behind?: examining the nature of fragmented work," in Proceedings of CHI 2005, 2005, pp. 321-330. source
Classified as probably not a substantial claim.
Study design and conductreasoningMylyn task contexts are a rather reliable account of IDE usage over time.
“The task context contains the entire interaction history since a developer activated the task he or she was working on, and as such is a rather reliable account of IDE usage over time (barring a few issues explained below).”
Quote in the paperSubstantial claimMay combine two claims.
Study design and conductreasoningAggregate events in Mylyn data lose specific time besides range, because Mylyn does not register all user events for scalability.
“Whenever an aggregation occurs, the event is expanded to include two timestamps defining a range of time, instead of a single timestamp, and a number of events.Accordingly, these aggregate events lose their specific time besides the range of time.The reason of this is that for scalability-in terms of storage-Mylyn does not register all the user events.”
Quote in the paperSubstantial claimClassified as probably not a substantial claim.
PremisecitationShort interruptions typically last around 3 minutes.
“This is based on previous work where we observed that short interruptions lasted usually this long [3].”
Quote in the paperSubstantial claim0 of 1 sources checked- cites [3] 3. V. M. González and G. Mark, ""constant, constant, multi-tasking craziness": managing multiple working spheres," in Proceedings of CHI 2004, 2004, pp. 113-120. source
May combine two claims.
Study design and conductreasoningVery long events have duration much larger than mean, mainly in aggregate events, due to Mylyn registering end time when task resumed after long downtime.
“These events have a duration time (|EndT ime -StartT ime|) much larger than the mean.This mainly occurs in aggregate events.We believe that this issue is due to factors related to Mylyn, since it can register the end time of an event when the task is resumed after a long downtime.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
Premisenone givenMost prior studies operate on small datasets.
“As above, most of these studies operate on small datasets.”
Quote in the paperNot a substantial claimMay combine two claims.
Study design and conductreasoningThe duration of very long events is overstated; finding their actual duration is not trivial.
“Consequently, the duration of these events is overstated; however, finding their actual duration is not trivial.”
Quote in the paperNot a substantial claimMay combine two claims.
PremisereasoningThe literature lacks studies targeting software developers and large-scale data.
“If the literature contains extensive studies of interaction workers, it lacks in two aspects: (1) most studies target information workers (fewer target the specific population of software developers), and (2) the studies are usually field studies, which are limited in the amount of data they contain.”
Quote in the paperSubstantial claimMay combine two claims.
PremisecitationParnin and Rugaber evidenced edit lag in majority of large sample of development sessions, showing developers need time to resume work after interruption.
“Parning and Rugaber evidenced the presence of an edit lag in the majority of a large sample of development session spanning several datasets, hence showing that developers need time to resume work after an interruption [9].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [9] 9. C. Parnin and S. Rugaber, "Resumption strategies for interrupted programming tasks," Software Quality Journal, vol. 19, no. 1, pp. 5-34, 2011.
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S4 (based).
InterpretationreasoningWork fragmentation impact may be worse for software developers because they build complex mental models that are more sensitive to interruptions and costly to rebuild.
“Work fragmentation is indeed an important phenomenon within the context of modern software development, and the impact there may be even worse since developers build and maintain complex mental models of the software they are working on-these models may be more sensible to interruptions, and costly to rebuild.”
Quote in the paperNot a substantial claimMay combine two claims.
Interpretationown dataThe observation that time series without interruptions have more edits in the middle matches the hypothesis that developers need time to build their mental model and are less productive early in a session.
“This observation matches the hypothesis that developers need time to build their mental model for their task, and are less productive early in a session.”
Quote in the paperSubstantial claimMay combine two claims.
PremisecitationActivity Theory models consider interruptions after ~3 minutes of sustained attention at action level and after ~12 minutes at activity level.
“This study presented work fragmentation at two different levels: actions and activities.Interruptions originated after a period of around three minutes of sustained attention to the previous action were considered when people were switching at the level of interactions with artifacts of people.Interruptions originated after a period of twelve minutes of sustained attention to a previous activity w”
Quote in the paperSubstantial claim0 of 1 sources checked- cites [33] 33. R. Robbes and M. Lanza, "Characterizing and understanding development sessions," in Proceedings of ICPC 2007, 2007, pp. 155-166. source
Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenThe finding that the inverse relationship between productivity and interruption duration is more pronounced with longer interruptions agrees with the literature for information workers.
“This agrees with the literature for information workers.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationcitationThe drop in activity before an interruption may be because the programmer found a problem and engaged in debugging or asking teammates, which reduces IDE activity.
“This is might be because of two reasons: the programmer could have found a problem while coding, who at first will try to solve it by reading the code, switching out from the IDE, navigating the call stack and debugging, before going to ask another teammate, according to LaToza et al. [35]; this set of actions end up with an interruption and reduce the observed activity within the IDE.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [35] 35. J. Cohen, "The earth is round (p < 0.5)," American Psychologist, vol. 49, no. 12, pp. 997-1003, 1994. source
Probably not a substantial claim: may not pass S1 (asserted), S3 (load-bearing).
Interpretationown dataThe increasing trend of activity after an interruption reflects the programmer immersing again into the programming task.
“We hypothesize that the programmer is immersing again into the programming task, increasing progressively the activity as represented by the number of edits and selections.”
Quote in the paperNot a substantial claimMay combine two claims.
InterpretationreasoningThese results support previous observations at a finer level and corroborate the literature saying that time is needed to start or get back on task.
“These results support our previous observations at a finer level, and corroborate the literature saying that time is needed to start or get back on task.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationown dataThe finding that interruptions inversely relate to activity and productivity agrees with previous literature on the harmfulness of multitasking, work fragmentation, and interruptions.
“This finding agrees with the previous literature on the harmfulness of multitasking, work fragmentation, and interruptions.”
Quote in the paperNot a substantial claimMay combine two claims.
Study design and conductown data53% of the interruptions had 30 minutes before and after the interruption and were selected for the analysis; the remaining 47% could not be used due to lack of time around them.
“In total, 53% of the interruptions had 30 minutes before and after the interruption and were selected for the analysis.The rest 47% of the interruptions can not be used on this analysis due to the lack of time around them.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationcitationThe drop in edit ratio near interruptions matches Parnin's observations with the edit lag.
“This matches the observations Parnin made with the edit lag [9].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [9] 9. C. Parnin and S. Rugaber, "Resumption strategies for interrupted programming tasks," Software Quality Journal, vol. 19, no. 1, pp. 5-34, 2011.
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
May combine two claims.
InterpretationreasoningIn sessions with interruptions, the edit lag behavior is not visible; each session may have several edit lags after each interruption, equally distributed, resulting in flat lines.
“This behavior is not visible in sessions with interruptions; indeed, each session may have several edit lags (after each interruptions), and those would be equally distributed over the entire duration of the session, resulting in the”
Quote in the paperSubstantial claimMay combine two claims.
Interpretationown dataInterruptions and user activity follow inverse relationships, and they are quite pronounced.
“This reinforces our impressions that interruptions and user activity follow inverse relationships, and that they are quite pronounced.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S4 (based). May combine two claims.
InterpretationreasoningTo have the same amount of information we have with UDC it would require to monitor the user activity for a year or two and have a record of all the activities performed, like the number and duration of the interruptions.
“For example, to have the same amount of information we have with UDC it would require to monitor the user activity for a year or two and have a record of all the activities performed, like the number and duration of the interruptions.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing), S4 (based).
Interpretationnone givenAnalyzing interaction data is a convenient way to understand almost the same kind of events on the environment.
“On the other hand, analyzing interaction data is a convenient way to understand almost the same kind of events on the environment.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningThe small size of the Mylyn dataset may have favored outliers, affecting the results.
“The (comparatively) small size of the Mylyn dataset may have favored outliers: since there is data from dozens of developers only in the Mylyn dataset, a few outliers may have affected the results.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing). May combine two claims.
InterpretationreasoningThese findings helped us understand the response to work fragmentation according to the recorded user activity, and it was possible to make a relation between the user's data and the phenomena that occur on the working places described in the studies.
“These findings helped us understand the response to work fragmentation according to the recorded user activity, and it was possible to made a relation between the user's data and the phenomena that occur on the working places describe on the studies.”
Quote in the paperNot a substantial claimMay combine two claims.
InterpretationreasoningEditions per minute describes the effect better and selections do not show a major change.
“The editions per minute describes better the effect and the selections do not show a major change.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationAs the number of switches between tasks increases, the effectiveness degrades in a linear fashion.
“Moreover, as the number of switches between tasks increases, the effectiveness degrades in a linear fashion [42].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [42] 42. S. Aral, E. Brynjolfsson, and M. Van Alstyne, "Information, technology, and information worker productivity," Information Systems Research, vol. 23, no. 3-part-2, pp. 849-867, 2012. source
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
PremisecitationThe pre-processed UDC data by Murphy-Hill is cleaned and preprocessed, making transformation simple.
“We used the pre-processed data by Murphy-Hill, that is published on Google BigQuery [39].This is an alternative version of the original UDC dataset, that is cleaned and preprocessed, so that the transformation phase is simple and focused on our needs.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [39] 39. E. J. Keogh, "Exact indexing of dynamic time warping," Knowledge and Information Systems, vol. 7, pp. 358-386, 2005. source
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
InterpretationreasoningThis could be reflecting what observational studies tell us about multitasking, which is that with higher number of interruptions (increased multitasking) the productivity stops being affected and might increase.
“This could be reflecting what observational studies tell us about multitasking, which is that with higher number of interruptions (increased multitasking) the productivity stops being affected and might increase.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable). May combine two claims.
Interpretationown dataUsage data describes the history of activities of the programmer and it is possible to analyze the effect of events, as shown in this work.
“Usage data describes the history of activities of the programmer and it is possible to analyze the effect of events, as shown in this work.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim. May combine two claims.
Study design and conductreasoningThe problem with analyzing interaction data is the lack of context of the events and, in our case, the lack of information of the programmers to enrich the results.
“The problem with this is the lack of context of the events and, in our case, the lack of information of the programmers to enrich the results.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductnone givenThe classification of events into edition and selection was done through an iterative process involving two authors until consensus.
“We used an iterative process involving two of the authors of the paper to arrive to this result; the process was iterative, until we reached consensus.”
Quote in the paperNot a substantial claimMay combine two claims.
Study design and conductreasoningThe models are not directly comparable: Mylyn records edition and selection events directly, while the UDC records a broader array of user activity; classification of UDC events does not exactly replicate the Mylyn model.
“The models are not directly comparable: Mylyn records edition and selection events directly, while the UDC records a broader array of user activity.”
Quote in the paperSubstantial claimMay combine two claims.
PremisecitationAt some level, switching between tasks can provide the needed arousal and alertness to improve productivity, but higher levels of multitasking can be detrimental and cause a negative effect.
“At some level, switching between tasks can provide the needed arousal and alertness to improve the productivity, but higher levels of multitasking can be detrimental and cause a negative effect.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [42] 42. S. Aral, E. Brynjolfsson, and M. Van Alstyne, "Information, technology, and information worker productivity," Information Systems Research, vol. 23, no. 3-part-2, pp. 849-867, 2012. source
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
InterpretationreasoningAll the observations go in the same direction, which lends more confidence in the conclusions.
“The fact that all the observations go in the same direction lends us more confidence in our conclusions.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim. May combine two claims.
Study design and conductreasoningWe cannot guarantee that an interruption was an actual interruption of work; it could also be a change to a Web design tool, server configuration tool or the browser, which are common activities in Web developers and not necessarily detrimental to productivity.
“Hence, we can not guarantee that an interruption was an actual interruption of work; due to the definition of an interruption, it could also be a change to a Web design tool, server configuration tool or the browser, which are common activities in Web developers and not necessarily detrimental to productivity.”
Quote in the paperSubstantial claimClassified as probably not a substantial claim.
Interpretationown dataThe lower edit ratio after negative interruptions is in accordance with the hypothesis that the programmer may be rebuilding context after an unwanted task switch.
“negative interruptions have a lower edit ratio after the interruption (in accordance with the hypothesis that the programmer may be rebuilding his context after an unwanted task switch)”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing).
PremisereasoningImplementing an observational study of this kind can be very expensive, for the time and material need.
“However, implementing a study of this kind can be very expensive, for the time and material need.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
Study design and conductown dataAfter selecting interruptions with at least 15 minutes before another interruption, 5,684 valid interruptions were obtained from a total of 110,077.
“It was required to make a selection of those interruptions which had a period afterwards of at least 15 minutes before another interruption.After this query we obtained 5,684 valid interruptions from a total of 110,077.”
Quote in the paperSubstantial claimMay combine two claims.
InterpretationreasoningThe first five minutes after an interruption and the moment before the next one are the phases where productivity is more affected, while the phases around the peak are where productivity is more favorable.
“From this we can conclude that the first five minutes after an interruption and the moment before the next one are the are the phases where productivity is more affected, while the phases around the peak are where the productivity is more favorable.”
Quote in the paperSubstantial claimMay combine two claims.
InterpretationreasoningThese categories of events agree with the previous hypothesis that positive interruptions are related to information seeking, while negative interruptions are related to actual task switches where context needs to be rebuilt afterwards.
“These categories of events agree with our previous hypothesis that positive interruptions are related to information seeking [9,35], while negative interruptions are related to actual task switches where context needs to be rebuilt afterwards.”
Quote in the paperSubstantial claim0 of 2 sources checked- cites [9] 9. C. Parnin and S. Rugaber, "Resumption strategies for interrupted programming tasks," Software Quality Journal, vol. 19, no. 1, pp. 5-34, 2011.
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- cites [35] 35. J. Cohen, "The earth is round (p < 0.5)," American Psychologist, vol. 49, no. 12, pp. 997-1003, 1994. source
Probably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationThe duration of the peak varies among working spheres.
“The duration of the peak varies among the also called working spheres, as mentioned by Gonzalez and Mark [5].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Gonzalez and Mark [5]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenThe peak phase is where productivity should be reaching its maximum, as programmers are not taking actions to retake the lost mental model or preparing for an interruption.
“The peak phase is where the productivity should be reaching its maximum, as the programmers are not taking actions to retake the lost mental model or preparing for an interruption.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
PremisecitationThe recovery time is established as the 15-minute period after an interruption, without considering the time consumed by the interruption itself.
“We established the recovery time as the 15 minute period after an interruption, without considering the time consumed by the interruption itself.The length of the period was chosen according to the observations by Solingen et al. [40].”
Quote in the paperSubstantial claim0 of 1 sources checked- cites [40] 40. W. Snipes, E. Murphy-Hill, T. Fritz, M. Vakilian, K. Damevski, A. R. Nair, and D. Shepherd, Analyzing Software Data. Morgan Kaufmann, 2015, ch. A Practical Guide to Analyzing IDE Usage Data. source
Probably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductnone givenOther effect size measures such as the common language effect size or A12 may slightly alter the discussion.
“Other effect size measures such as the common language effect size [44] or A 12 [45] may slightly alter the discussion.”
Quote in the paperNot a substantial claim0 of 2 sources checkedProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing).
Interpretationown dataThese findings agree with the literature on information workers and software developers.
“These findings agree with the literature on information workers and software developers.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing).
Study design and conductnone givenWe were careful not to conclude that every gap of activity is an actual interruption.
“As stated in the introduction, we were careful not to conclude that every gap of activity is an actual interruption.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductreasoningOur separation of sessions in short and long interruptions is not perfect, as it is based on the presence of at least one long interruption, and nothing more.
“We acknowledge that our separation of sessions in short and long interruptions is not perfect, as it is based on the presence of at least one long interruption, and nothing more.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductreasoningWe used Cohen's d, a parametric effect size measure, as it has defined thresholds allowing easier interpretation of the results.
“We used Cohen's d, a parametric effect size measure, as it has defined thresholds allowing easier interpretation of the results.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductcitationOther indicators of productivity (such as actual changes) may yield different results.
“However we can not exclude that other indicators of productivity (such as actual changes [43]) may yield different results.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [43] 43. R. F. Adler and R. Benbunan-Fich, "Juggling on a high wire: Multitasking effects on performance," International Journal of Human-Computer Studies, vol. 70, no. 2, pp. 156-168, 2012. source
May combine two claims.
Study design and conductnone givenThe gathered data corresponds to a limited group of programmers, which use both Mylyn and Eclipse regularly.
“The gathered data corresponds to a limited group of programmers, which use both Mylyn and Eclipse regularly.”
Quote in the paperSubstantial claimClassified as probably not a substantial claim. May combine two claims.
Study design and conductown dataWe decided not to count workbench activation and deactivation events as 'system' events, and thus only use them to define an interruption or the end of a session.
“Therefore, we decided not count them as”
Quote in the paperSubstantial claimMay combine two claims.
Interpretationown dataThese findings support our hypotheses that positive interruptions are due to information-seeking, while negative interruptions are due to context rebuilding after an actual interruption.
“These findings support out hypotheses that positive interruptions are due to information-seeking, while negative interruptions are due to context rebuilding after an actual interruption.”
Quote in the paperSubstantial claimMay combine two claims.
Study design and conductown dataWe have not found evidence of bias due to the exclusion of sessions with aggregated information, but it may still be present.
“We have not found evidence of bias due to this but it may still be present.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductreasoningOther factors present in the group of sessions with at least one long interruption may contribute to the observed effect.
“Other factors present in the group of sessions with at least one long interruption may contribute to the observed effect (for instance, these sessions may also have more interruptions overall).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductnone givenA large variation of the thresholds (8 hours of inactivity, 30 minutes minimum session, 3 minutes minimum interruption, ≥12 minutes prolonged interruptions) might significantly alter the results.
“However, a large variation of these thresholds might significantly alter the results.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
Study design and conductreasoningOur classification of events is a possible threat, as it was based on our own criteria of what should be an Edition and Selection event.
“Additionally, our classification of events is a possible threat, as it was based on our own criteria of what should be an Edition and Selection event.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing), S4 (based).
Study design and conductnone givenThe same threats about the metrics, implications and statistical conclusions apply on the results observed with the UDC.
“The same threats about the metrics, implications and statistical conclusions apply on the results observed with the UDC.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductnone givenWe took special care when establishing the classification, using an iterative process involving two authors of this paper.
“We took special care when establishing the classification, using an iterative process involving two authors of this paper.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductnone givenWe ran tests of what kind of data was recorded for specific usage scenarios of the IDE in order to better understand the nature of the dataset when particular events were unclear.
“We also ran tests of what kind of data was recorded for specific usage scenarios of the IDE in order to better understand the nature of the dataset when particular events were unclear.”
Quote in the paperNot a substantial claim
The authors state this as an assumption.
Activity gaps observed in IDE activity are indicators of work fragmentation in general.
“we assume they are indicators of work fragmentation in general (that is, a programmer switching contexts to perform other activities while developing, such as answering email, looking for the solution of a problem on the Internet, etc).”
The authors state this as an assumption.
A productive programmer will perform more coding activities than selections or navigations.
“The edit ratio might be also a good indicator, under the assumption that a productive programmer will perform more coding activities than selections or navigations.”
The paper relies on this without support.
The Mylyn and UDC datasets represent the same kind of information.
“Although they represent the same kind of information both Mylyn and UDC datasets have some peculiarities that make them unique that we discuss here.”
The paper relies on this without support.
The interaction data recorded by Mylyn is the basis for a recommendation tool, and is focused on Java projects.
“The interaction data recorded by Mylyn is the basis for a recommendation tool, and is focused on Java projects.”
The paper relies on this without support.
Mylyn has been shown to facilitate task switching and to increase the edit ratio of its users compared to non-users.
“Mylyn has been shown to facilitate task switching and to increase the edit ratio of its users compared to non-users.”
The paper relies on this without support.
The workbench activation and deactivation events can be executed under many circumstances.
“The workbench activation and deactivation events were a particular issue, for they can be executed under many circumstances.”
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
Each contradiction between two passages listed here was confirmed by an independent check.
UDC session durations fall below the stated cutoff
MajorThe UDC sessions were reportedly filtered to have at least 30 minutes of productive time. Table XII nevertheless gives a 2-minute minimum and a 22-minute median for those sessions.
“Table XII.Statistics about the sessions in UDC.stat value total 15,825 min.2 min 1st Qu. 11 min median 22 min mean 31.09min 3rd Qu. 45 min max.131 min”
“but after a filter to keep only those with at least 30 minutes of productive time (as we did with the Mylyn dataset), we ended up with 15,825 useful sessions”
UDC interruption-count groups overlap at seven
MinorTable XVI labels the highest interruption group as at least seven, which overlaps the preceding five-to-seven group. The accompanying figure instead labels the highest group as greater than seven.
“none ≤ 2 [3 -4] [5 -7] ≥ 7 Edits mean 3.97 2.18 1.82 1.70 1.59”
“none [1-2] [3-4] [5-7] >7 0 2 4 6 8 12 Interruptions Edits / minute”
UDC attribute count disagrees with its schema
MinorThe dataset is described as having five attributes per row, but Table XI lists seven: userId, what, kind, bundleId, bundleVersion, description, and datetime.
“The UDC is a large dataset that contains information of around 1,800,000 users, and has a total of 2,323,233,101 unique rows with 5 attributes each.Table XI shows a description of the attributes.”
“Table XI.Attributes in UDC data.attribute description userId Unique number that identifies a user what The action of the event (deactivated, activated, opened, executed, etc.) kind What kind of event was executed (workbench, view, command, etc.) bundleId Description of the event's package bundleVersion Version of the bundle's event description Description of the event datetime Date and time in UNIX format”
Cites
Silhouettes: A graphical aid to the interpretation and validation of cluster analysis
Rousseeuw, P. J. (1987) · Journal of Computational and Applied Mathematics · doi:10.1016/0377-0427(87)90125-7 · Cited by 21,392 · see citing works
(1996) · Cited by 4,738 · see citing works
The earth is round (p < .05).
Cohen, J. (1994) · American Psychologist · doi:10.1037/0003-066x.49.12.997 · Cited by 4,003 · see citing works
Exact indexing of dynamic time warping
Keogh, E., & Ratanamahatana, C. A. (2004) · Knowledge and Information Systems · doi:10.1007/s10115-004-0154-9 · Cited by 1,962 · see citing works
Acting with technology: Activity theory and interaction design
Kaptelinin, V., & Nardi, B. (2007) · First Monday · doi:10.5210/fm.v12i4.1772 · Cited by 1,647 · cited 1× · see citing works
“As we described previously we consider that a prolonged interruption has a duration of ⩾ 12 minutes—a decision based on the literature.[3,41] For every session, we calculated the proportion of prolonged interruptions as the sum of interruptions with duration equal or greater than”
MethodA common language effect size statistic
McGraw, K. O., & Wong, S. P. (1992) · Psychological Bulletin · doi:10.1037/0033-2909.111.2.361 · Cited by 934 · cited 1× · see citing works
“Other effect size measures such as the common language effect size [44] or A 12 [45] may slightly alter the discussion.”
BackgroundA diary study of task switching and interruptions
Czerwinski, M., Horvitz, E., & Wilhite, S. (2004) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/985692.985715 · Cited by 830 · see citing works
The cost of interrupted work: more speed and stress
Mark, G., Gudith, D., & Klocke, U. (2008) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1357054.1357072 · Cited by 728 · cited 1× · see citing works
“This often results in work fragmentation and interruptions which some studies found has detrimental effects to knowledge workers, such as stress and frustration [4].”
Background"Constant, constant, multi-tasking craziness": managing multiple working spheres
González, V. M., & Mark, G. (2004) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/985692.985707 · Cited by 715 · see citing works
Self-citationMaintaining mental models: a study of developer work habits
LaToza, T. D., Venolia, G., & DeLine, R. (2006) · Proceedings of the 28th international conference on Software engineering · doi:10.1145/1134285.1134355 · Cited by 628 · see citing works
Data mining and knowledge discovery in databases
Fayyad, U., & Uthurusamy, R. (1996) · Communications of the ACM · doi:10.1145/240455.240463 · Cited by 590 · see citing works
How We Refactor, and How We Know It
Murphy-Hill, E., Parnin, C., & Black, A. P. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.41 · Cited by 547 · see citing works
No task left behind?: examining the nature of fragmented work
Mark, G., Gonzalez, V. M., & Harris, J. (2005) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1054972.1055017 · Cited by 503 · see citing works
Self-citationInformation Needs in Collocated Software Development Teams
Ko, A. J., DeLine, R., & Venolia, G. (2007) · 29th International Conference on Software Engineering (ICSE'07) · doi:10.1109/icse.2007.45 · Cited by 499 · see citing works
Clustering in an object-oriented environment
Struyf, A., Hubert, M., & Rousseeuw, P. (1997) · Journal of Statistical Software · doi:10.18637/jss.v001.i04 · Cited by 457 · see citing works
Using task context to improve programmer productivity
Kersten, M., & Murphy, G. C. (2006) · Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1181775.1181777 · Cited by 452 · see citing works
How are Java software developers using the Eclipse IDE?
Murphy, G. C., Kersten, M., & Findlater, L. (2006) · IEEE Software · doi:10.1109/ms.2006.105 · Cited by 413 · see citing works
Peopleware: Productive Projects and Teams
Jones, L. A. (1990) · R and D Management · doi:10.1111/j.1467-9310.1990.tb00681.x · Cited by 350 · see citing works
Disruption and recovery of computing tasks: field study, analysis, and directions
Iqbal, S. T., & Horvitz, E. (2007) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1240624.1240730 · Cited by 300 · see citing works
Information, Technology, and Information Worker Productivity
Aral, S., Brynjolfsson, E., & Van Alstyne, M. (2012) · Information Systems Research · doi:10.1287/isre.1110.0408 · Cited by 256 · see citing works
Software developers' perceptions of productivity
Meyer, A. N., Fritz, T., Murphy, G. C., & Zimmermann, T. (2014) · Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering · doi:10.1145/2635868.2635892 · Cited by 224 · see citing works
Juggling on a high wire: Multitasking effects on performance
Adler, R. F., & Benbunan-Fich, R. (2012) · International Journal of Human-Computer Studies · doi:10.1016/j.ijhcs.2011.10.003 · Cited by 203 · see citing works
On the Comprehension of Program Comprehension
Maalej, W., Tiarks, R., Roehm, T., & Koschke, R. (2014) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2622669 · Cited by 180 · see citing works
Micro interaction metrics for defect prediction
Lee, T., Nam, J., Han, D., Kim, S., & In, H. P. (2011) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/2025113.2025156 · Cited by 151 · see citing works
Programmers Are Users Too: Human-Centered Methods for Improving Programming Tools
Myers, B. A., Ko, A. J., LaToza, T. D., & Yoon, Y. (2016) · Computer · doi:10.1109/mc.2016.200 · Cited by 144 · see citing works
A degree-of-knowledge model to capture source code familiarity
Fritz, T., Ou, J., Murphy, G. C., & Murphy-Hill, E. R. (2010) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/1806799.1806856 · Cited by 123 · see citing works
How do code refactorings affect energy usage?
Sahin, C., Pollock, L., & Clause, J. (2014) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/2652524.2652538 · Cited by 113 · see citing works
Interrupts: just a minute never is
van Solingen, R., Berghout, E., & van Latum, F. (1998) · IEEE Software · doi:10.1109/52.714843 · Cited by 104 · see citing works
Resumption strategies for interrupted programming tasks
Parnin, C., & Rugaber, S. (2011) · Software Quality Journal · doi:10.1007/s11219-010-9104-9 · Cited by 103 · see citing works
Does a programmer's activity indicate knowledge of code?
Fritz, T., Murphy, G. C., & Hill, E. (2007) · doi:10.1145/1287624.1287673 · Cited by 96 · see citing works
Improving code completion with program history
Robbes, R., & Lanza, M. (2010) · Automated Software Engineering · doi:10.1007/s10515-010-0064-x · Cited by 95 · see citing works
Self-citationThe sky is not the limit: multitasking across GitHub projects
Vasilescu, B., Blincoe, K., Xuan, Q., Casalnuovo, C., Damian, D., Devanbu, P., & Filkov, V. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884875 · Cited by 77 · see citing works
Capturing and analyzing low-level events from the code editor
Yoon, Y., & Myers, B. A. (2011) · doi:10.1145/2089155.2089163 · Cited by 74 · see citing works
Improving software developers' fluency by recommending development environment commands
Murphy-Hill, E., Jiresal, R., & Murphy, G. C. (2012) · Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering · doi:10.1145/2393596.2393645 · Cited by 67 · see citing works
Evaluating Cues for Resuming Interrupted Programming Tasks
Parnin, C., & DeLine, R. (2010) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1753326.1753342 · Cited by 60 · cited 2× · see citing works
“Our theoretical foundations are based on observational studies performed on information workers’ development environments.[5,6,16,45] These findings helped us understand the response to work fragmentation according to the recorded user activity, and it was possible to make a relation between the user’s data and the ph…”
BackgroundThe Effect of Frequent versus Infrequent Interruptions on Primary Task Resumption
Monk, C. A. (2004) · Proceedings of the Human Factors and Ergonomics Society Annual Meeting · doi:10.1177/154193120404800304 · Cited by 52 · see citing works
Characterizing and Understanding Development Sessions
Robbes, R., & Lanza, M. (2007) · 15th IEEE International Conference on Program Comprehension (ICPC '07) · doi:10.1109/icpc.2007.12 · Cited by 51 · see citing works
Self-citationImpact analysis of change requests on source code based on interaction and commit histories
Zanjani, M. B., Swartzendruber, G., & Kagdi, H. (2014) · Proceedings of the 11th Working Conference on Mining Software Repositories · doi:10.1145/2597073.2597096 · Cited by 47 · see citing works
Feature-Based Visual Sentiment Analysis of Text Document Streams
Rohrdantz, C., Hao, M. C., Dayal, U., Haug, L.-E., & Keim, D. A. (2012) · ACM Transactions on Intelligent Systems and Technology · doi:10.1145/2089094.2089102 · Cited by 43 · see citing works
The Influence of the Task on Programmer Behaviour
Ying, A. T. T., & Robillard, M. P. (2011) · 2011 IEEE 19th International Conference on Program Comprehension · doi:10.1109/icpc.2011.35 · Cited by 41 · see citing works
Collecting and Processing Interaction Data for Recommendation Systems
Maalej, W., Fritz, T., & Robbes, R. (2013) · Springer eBooks · doi:10.1007/978-3-642-45135-5_7 · Cited by 37 · see citing works
Self-citationProgrammer information needs after memory failure
Parnin, C., & Rugaber, S. (2012) · IEEE International Conference on Program Comprehension (ICPC) · doi:10.1109/icpc.2012.6240479 · Cited by 37 · see citing works
Using developer interaction data to compare expertise metrics
Robbes, R., & Rothlisberger, D. (2013) · 2013 10th Working Conference on Mining Software Repositories (MSR) · doi:10.1109/msr.2013.6624041 · Cited by 36 · see citing works
Self-citationAVISPA: a tool for analyzing software process models
Hurtado Alegría, J., Bastarrica Piñeyro, M. C., & Bergel, A. (2014) · Universidad de Chile · doi:10.1002/smr · Cited by 26 · see citing works
Comparing and combining evolutionary couplings from interactions and commits
Bantelay, F. T., Zanjani, M. B., & Kagdi, H. (2013) · Proceedings - Working Conference on Reverse Engineering · doi:10.1109/wcre.2013.6671306 · Cited by 23 · see citing works
Quantifying Program Comprehension with Interaction Data
Minelli, R., Mocci, A., Lanza, M., & Kobayashi, T. (2014) · Asia-Pacific Conference on Quality Software (APAQS) · doi:10.1109/qsic.2014.11 · Cited by 23 · see citing works
An Industrial Case Study of Program Artifacts Viewed During Maintenance Tasks
Zou, L., & Godfrey, M. W. (2006) · 2006 13th Working Conference on Reverse Engineering · doi:10.1109/wcre.2006.12 · Cited by 20 · see citing works
Towards understanding how developers spend their effort during maintenance activities
Soh, Z., Khomh, F., Guéhéneuc, Y., et al. (2013) · Proceedings - Working Conference on Reverse Engineering · doi:10.1109/wcre.2013.6671290 · Cited by 19 · see citing works
On the effect of program exploration on maintenance tasks
Soh, Z., Khomh, F., Guéhéneuc, Y., Antoniol, G., & Adams, B. (2013) · Working Conference on Reverse Engineering (WCRE) · doi:10.1109/wcre.2013.6671314 · Cited by 17 · see citing works
An empirical study of spreadsheet authors' mental models in explaining and debugging tasks
Kankuzi, B., & Sajaniemi, J. (2013) · 2013 IEEE Symposium on Visual Languages and Human Centric Computing · doi:10.1109/vlhcc.2013.6645237 · Cited by 14 · see citing works
An Initial Study on Refactoring Tactics
Liu, H., Gao, Y., & Niu, Z. (2012) · IEEE Annual Computer Software and Applications Conference (COMPSAC) · doi:10.1109/compsac.2012.31 · Cited by 10 · see citing works
Web usage patterns of developers
Corley, C. S., Lois, F., & Quezada, S. (2015) · 2015 IEEE International Conference on Software Maintenance and Evolution (ICSME) · doi:10.1109/icsm.2015.7332489 · Cited by 10 · see citing works
On understanding how developers use the Spotter search tool
Kubelka, J., Bergel, A., Chiș, A., Gîrba, T., Reichhart, S., Robbes, R., & Syrel, A. (2015) · IEEE Working Conference on Software Visualization (VISSOFT) · doi:10.1109/vissoft.2015.7332426 · Cited by 8 · see citing works
Self-citationObject-oriented software extensions in practice
Robbes, R., Röthlisberger, D., & Tanter, É. (2014) · Empirical Software Engineering · doi:10.1007/s10664-013-9298-0 · Cited by 5 · see citing works
Self-citationIs mining software repositories data science? (keynote)
Mockus, A. (2014) · Proceedings of the 11th Working Conference on Mining Software Repositories · doi:10.1145/2597073.2600728 · Cited by 3 · see citing works
Mining Intentional Process Models
Khodabandelou, G. (n.d.) · doi:10.70675/d8116e96ze4adz48ccz8aadz7e5d87263c05
Extensions during Software Evolution: Do Objects Meet Their Promise?
Robbes, R., Röthlisberger, D., & Tanter, É. (2012) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-31057-7_3
Self-citation
Flagged first, then by citations
Research works printed but not linked: 1
- Snipes W, 2015, Analyzing Software Data
Cited by
Sorted by citations
Razzaq, A., Buckley, J., Lai, Q., Yu, T., & Botterweck, G. (2025) · ACM Computing Surveys · doi:10.1145/3687299 · Cited by 36 · see citing works
“(1) Dealing with Interruptions to Avoid Disruptions — Interruptions are inevitable in teams and multitasking [S159].”
Abad, Z. S. H., Karras, O., Schneider, K., Barker, K., & Bauer, M. (2018) · Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018 · doi:10.1145/3210459.3210471 · Cited by 32 · see citing works
Robbes, R., Lungu, M. F., & Janes, A. (2019) · IEEE/ACM International Conference on Software Engineering: New Ideas and Emerging Results (ICSE-NIER) · doi:10.1109/icse-nier.2019.00033 · Cited by 5 · see citing works
“show that information workers [2] and developers [3], [4] see their productivity affected beyond the context switch, and may need time to rebuild the context they lost during the interruption.”
BackgroundSelf-citationWeb Augmentation as a Technique to Diminish User Interactions in Repetitive Tasks
Aldalur, I., Perez, A., & Larrinaga, F. (2021) · IEEE Access · doi:10.1109/access.2021.3104187 · Cited by 3 · see citing works
“[50] observes that work fragmentation is correlated with lower productivity observed both at the macro level (for entire sessions) and at the micro level (around work fragmentation markers).”
BackgroundAbad, Z. S. H., Karras, O., Schneider, K. A., Barker, K. E., & Bauer, M. (2018) · EasyChair preprint · doi:10.29007/464w · Cited by 4 · see citing works
- Authors
- Cruz, L. C., Sanchez, H., González, V. M., & Robbes, R.
- Affiliations
- Instituto Tecnológico Autónomo de México (MX)
- University of Chile (CL)
- Corresponding author
- Robbes, Romain
- Venue
- Journal of Software: Evolution and Process
- Publisher
- Wiley
- Published
- 2017-01-30
- Volume
- 29
- Issue
- 3
- ISSN
- 2047-7473 (ISSN-L)
- 2047-7481
- OpenAlex
- W2580754782
- Cited by
- 6
- References
- 55
- Citations by year
- 2025: 1 · 2024: 1 · 2021: 1 · 2019: 1 · 2018: 2
- FWCI
- 1.32
- Type
- journal article
- Language
- en
- Open access
- bronze
- doi.org
- Locations
- Journal of Software Evolution and Process (publishedVersion)
- Open Research (University of Surrey) (submittedVersion)
- Funders
- LACCIR (RFP2012LAC004)
- Topics
- Social Sciences › Decision Sciences › Information Systems and Management › Personal Information Management and User Behavior
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Keywords
- work fragmentation, software developers, developer productivity, interruptions, interaction traces
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Claims read by deepseek-v4.1-flash under definition version 3 (extract-v3) on 2026-10-11.
Classified by jev-1.13-20260917 (gold-guideline-v0.2) on 2026-10-11.
Cited sources are checked by gpt-6-sol.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review