Md Afif Al Mamun

dblp:400/6504 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
1since 2021 · last 2026
0000-0002-9319-3483ORCID · reported

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

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

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
Empirical software engineering · 56% Software maintenance and evolution · 44%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
bug triage
1.012026
TriagerX: Dual Transformers for Bug Triaging Tasks With Content and Interaction Based Rankings · IEEE Trans. Software Eng. 2026
Empirical software engineering › AI for software engineering › machine learning for software engineering
developer recommendation
1.012026
TriagerX: Dual Transformers for Bug Triaging Tasks With Content and Interaction Based Rankings · IEEE Trans. Software Eng. 2026
Empirical software engineering
mining software repositories
0.312026
TriagerX: Dual Transformers for Bug Triaging Tasks With Content and Interaction Based Rankings · IEEE Trans. Software Eng. 2026

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

transformer · 1.0pre-trained language model · 1.0dual-transformer architecture · 1.0
YearPublicationVenuePosition
2026 TriagerX: Dual Transformers for Bug Triaging Tasks With Content and Interaction Based Rankings
abstract
Pretrained Language Models or PLMs are transformer-based architectures that can be used in bug triaging tasks. PLMs can better capture token semantics than traditional Machine Learning (ML) models that rely on statistical features (e.g., TF-IDF, bag of words). However, PLMs may still attend to less relevant tokens in a bug report, which can impact their effectiveness. In addition, the model can be suboptimal with its recommendations when the interaction history of developers around similar bugs is not taken into account. We designed TriagerX to address these limitations. First, to assess token semantics more reliably, we leverage a dual-transformer architecture. Unlike current state-of-the-art (SOTA) baselines that employ a single transformer architecture, TriagerX collects recommendations from two transformers with each offering recommendations via its last three layers. This setup generates a robust content-based ranking of candidate developers. TriagerX then refines this ranking by employing a novel interactionbased ranking methodology, which considers developers’ historical interactions with similar fixed bugs. Across five datasets, TriagerX surpasses all nine transformer-based methods, including SOTA baselines, often improving Top-1 and Top-3 developer recommendation accuracy by over 10%. We worked with our large industry partner to successfully deploy TriagerX in their development environment. The partner required both developer and component recommendations, with components acting as proxies for team assignments—particularly useful in cases of developer turnover or team changes. We trained TriagerX on the partner’s dataset for both tasks, and it outperformed SOTA baselines by up to 10% for component recommendations and 54% for developer recommendations. Replication package.https://github.com/afifaniks/triagerX
Md Afif Al Mamun, Gias Uddin 0001, Lan Xia, Longyu Zhang
IEEE Trans. Software Eng.1