Ritgard is presented, a tool that mines GitHub repositories for their STAs, namely Issues, Pull Requests, and Discussions, and visualizes them as 3D islands covered with trees, depicting the evolution of features and concerns throughout the project's lifetime.
Abstract
A software project is more than just code. Non-code artifacts often document the human processes and decisions behind source code. The rationale behind a library change, an architectural decision, a problem encountered by a user are all examples of information typically present in socio-technical artifacts (STAs), created and persisted in channels separate from the repository itself (yet sometimes very close---e.g., GitHub Issues with GitHub repositories). These STAs are a trove of information about the project's architecture and its evolution, containing details and insights that code alone cannot provide. Unfortunately, this information is not easily extracted and explored as STAs are frequently fragmented over different communication channels, and are written in natural language. We present Ritgard, a tool that mines GitHub repositories for their STAs, namely Issues, Pull Requests, and Discussions, and visualizes them as 3D islands covered with trees. Each tree represents a single artifact and each island is a topic extracted from the artifacts through a combination of text embedding and text summarization. The terrain of the islands rises out of the ocean as the topic becomes active and sinks back in when it becomes stale, thus depicting the evolution of features and concerns throughout the project's lifetime. We describe the tool's usage and implementation, showing the numerous technical challenges behind Ritgard's visualization.
A 3D visualization approach mapping topics found across a project's socio-technical artifacts onto vegetation-covered islands, where the individual artifacts are depicted as trees of various types.
Adam J. Stepánek, Marco Raglianti, V. Rusňák et al.· 1 citation
User Stories are key artifacts in Requirement and Software Engineering. Despite their wide adoption, their writing in industrial contexts tends to diverge from the principles initially stated in Agile methodologies. In this context, sets of metrics such as INVEST or QUS emerged to qualify these items. In this paper, we...
M. Ortega, Hassan Imhah, N. Mellouli et al.· Proceedings of the ACM on So...· 0 citations
The results show that short-term collective innovation leaves detectable behavioral and structural traces in software repositories and provide a reproducible basis for isolating innovation-contest software and studying how its outputs relate to the sustained open-source ecosystem around them.
Eisha Tir Raazia, Carlos Vivar-Rios, Robin Franken et al.· Proceedings of the 14th ACM...· 0 citations
Recovered artefacts convey design that tests do not capture, offering a scalable source of design-level data for agents that design before they implement, and the round trip measures this without human references.
Cezar Sas, Sandra Mitrović, Fabio Barth et al.· 0 citations
As software projects grow, both their structure and their team dynamics become opaque. ExplorViz visualizes the structure and runtime behavior of software systems as interactive 3D software cities, but provides no view of contributor activity. Such a view could highlight development bottlenecks or reveal risks, such as...
Johannes Klindt· Kiel Software Engineering Re...· 0 citations
A theoretical framework is constructed that expands assumptions about individual motivation to include the idea of a long-term, value-informed quest beyond short-term rewards, and contains three theoretical conjectures that seek to explain how collectively elaborated standards of excellence prompt developers to produce...
G. von Krogh, Stefan Haefliger, S. Spaeth et al.· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.