2014 Second IEEE Working Conference on Software Visualization 2014
DOI: 10.1109/vissoft.2014.29
|View full text |Cite
|
Sign up to set email alerts
|

Visualizing the Evolution of Systems and Their Library Dependencies

Abstract: Abstract-System maintainers face several challenges stemming from a system and its library dependencies evolving separately. Novice maintainers may lack the historical knowledge required to efficiently manage an inherited system. While some libraries are regularly updated, some systems keep a dependency on older versions. On the other hand, maintainers may be unaware that other systems have settled on a different version of a library. In this paper, we visualize how the dependency relation between a system and… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
31
0
1

Year Published

2016
2016
2020
2020

Publication Types

Select...
5
2

Relationship

3
4

Authors

Journals

citations
Cited by 44 publications
(32 citation statements)
references
References 20 publications
0
31
0
1
Order By: Relevance
“…Overall, it is our hope that our large database of API method invocations and annotation usages will trigger even more precise and reproducible work in relation to software APIs; for example to be used in conjunction with tools to visualize how systems and their library dependencies evolve (Kula et al 2014), allowing a finer grained analysis.…”
Section: Resultsmentioning
confidence: 99%
“…Overall, it is our hope that our large database of API method invocations and annotation usages will trigger even more precise and reproducible work in relation to software APIs; for example to be used in conjunction with tools to visualize how systems and their library dependencies evolve (Kula et al 2014), allowing a finer grained analysis.…”
Section: Resultsmentioning
confidence: 99%
“…Adopting a new version of a library may seem a simple task, but have many difficulties [5]. Knowledge about a system's past upgrade activity with respect to a library can help maintainers [6].…”
Section: Introductionmentioning
confidence: 99%
“…To analyze library update activity, Kula et al [6] proposed a visualization technique using configuration files for a dependency management system. On the other hand, there exists no appropriate tool to understand library update activity of a project using clone-and-own approach.…”
Section: Introductionmentioning
confidence: 99%
“…Another set of research use the API usage as a measure of stability or popularity [39,40]. Our previous work [41], among work leveraged popularity to recommend when libraries are deemed safe to use by the masses. Other related work that studied the impact of API evolution on their clients on online forums such as Stack Overflow [42] and the Android App [43], Pharo [44] and Smalltalk ecosystems [45].…”
Section: Related Workmentioning
confidence: 99%