Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Raghuram Gopalakrishnan

dblp:200/1099 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
0since 2021 · last 2017
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 67% Empirical software engineering · 33%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software architecture › architectural design
architectural tactics
0.312017
Can latent topics in source code predict missing architectural tactics? · ICSE 2017
Empirical software engineering
mining software repositories
0.312017
Can latent topics in source code predict missing architectural tactics? · ICSE 2017
Requirements engineering and software design
software architecture
0.312017
Can latent topics in source code predict missing architectural tactics? · ICSE 2017

Methods — techniques the papers use, named apart from their topics

predictor models · 0.3latent topic modeling · 0.3
YearPublicationVenuePosition
2017 Can latent topics in source code predict missing architectural tactics?
abstract
Architectural tactics such as heartbeat, resource pooling, and scheduling provide solutions to satisfy reliability, security, performance, and other critical characteristics of a software system. Current design practices advocate rigorous up-front analysis of the system's quality concerns to identify tactics and where in the code they should be used. In this paper, we explore a bottom-up approach to recommend architectural tactics based on latent topics discovered in the source code of projects. We present a recommender system developed by building predictor models which capture relationships between topical concepts in source code and the use of specific architectural tactics in that code. Based on an extensive analysis of over 116,000 open source systems, we identify significant correlations between latent topics in source code and the usage of architectural tactics. We use this information to construct a predictor for generating tactic recommendations. Our approach is validated through a series of experiments which demonstrate the ability to generate package-level tactic recommendations. We provide further validation via two large-scale studies of Apache Hive and Hadoop to illustrate that our recommender system predicts tactics that are actually implemented by developers in later releases.
Raghuram Gopalakrishnan, Palak Sharma, Mehdi Mirakhorli, Matthias Galster
ICSE1
2017 A search engine for finding and reusing architecturally significant code
Ibrahim Mujhid, Joanna C. S. Santos, Raghuram Gopalakrishnan, Mehdi Mirakhorli
J. Syst. Softw.3