Platform Independent Software Development Monitoring: Design of an Architecture

Poster: Discovering Code Dependencies by Harnessing Developer's Activity

“…Existing works use software developer's activity to identify relations between software artifacts or developers, ranging from recommending task assignees [6], through capturing task contexts [2], to recommending artifacts of developer's interest [1]. Many approaches attempt to reduce a space of task-related software artifacts, e.g., for bug fixing, but further research is required to uncover their direct dependencies and thus reduce the sparsity of an identified task context [7].…”

“…We use developer's interactions in an IDE, as an implicit feedback to source code [1], to identify potential source code dependencies [3] independently from source code contents. We define three kinds of such dependencies:…”

“…A developer performs interactions within activities to accomplish her task. Such interactions are open a source code document, navigate to a definition, or paste a code fragment [1]. Activities can be just studying her own but old code, someone else's code, or implementing a new feature.…”

“…3) Aggregating dependencies between pairs of source code components into oriented edges e imp ∈ E imp , in dependency graph, where e imp = (v 1 We then construct a graph of potential dependencies DG imp (V,E imp ) with vertices V of source code components and weighted oriented edges E imp . DG imp is an extension to traditional dependency graph identified from explicit statements in source code (type and member references, inheritance, and method calls), it can be similarly visualized or further analyzed.…”

“…In this work, we consider developer's interactions recorded in an integrated development environment (IDE) [1,2] as an alternative source for identification of potential source code dependencies -identified from implicit feedback to source code. Because of the low-level information of an interaction, we also identify developer's activities, e.g., to distinguish navigation in source code when studying (no changes in code) from debugging (between start and stop of debugging) or refactoring.…”