2015 IEEE/ACM 37th IEEE International Conference on Software Engineering 2015
DOI: 10.1109/icse.2015.255
|View full text |Cite
|
Sign up to set email alerts
|

Poster: Discovering Code Dependencies by Harnessing Developer's Activity

Abstract: Abstract-Monitoring software developer's interactions in an integrated development environment is sought for revealing new information about developers and developed software. In this paper we present an approach for identifying potential source code dependencies solely from interaction data. We identify three kinds of potential dependencies and additionally assign them to developer's activity as well, to reveal detailed task-related connections in the source code. Interaction data as a source allow us to iden… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2015
2015
2019
2019

Publication Types

Select...
3
1

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(5 citation statements)
references
References 7 publications
0
5
0
Order By: Relevance
“…Then we aggregate fixations (coordinates on the screen transformed into line and column positions in source code documents) into area(s)-of-interest, i.e., source code elements (possibly blocks of code) as the source and target places of performed navigation. With this approach we identify potential dependencies between not just documents, but more fine-grained source code entities within and between documents [11,12]. In the example shown in Figure 1, the areas underneath fixations 7 and 13 may be potentially dependent.…”
Section: Identification Of Dependenciesmentioning
confidence: 99%
See 4 more Smart Citations
“…Then we aggregate fixations (coordinates on the screen transformed into line and column positions in source code documents) into area(s)-of-interest, i.e., source code elements (possibly blocks of code) as the source and target places of performed navigation. With this approach we identify potential dependencies between not just documents, but more fine-grained source code entities within and between documents [11,12]. In the example shown in Figure 1, the areas underneath fixations 7 and 13 may be potentially dependent.…”
Section: Identification Of Dependenciesmentioning
confidence: 99%
“…All these works differ in details of used interactions and their processing. In addition to other use cases for interaction data, e.g., assisting comprehension [3,17,18], or maintaining mental models and task contexts [7,10,14]; identifying and providing source code dependencies when syntactic analysis is not possible [11,12,16] is different approach to answer this problem than using dynamic analysis of source code [16,19].…”
Section: Related Workmentioning
confidence: 99%
See 3 more Smart Citations