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

Seyed Hooman Mostafavi

dblp:358/9114 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
1since 2021 · last 2024
0009-0001-7360-4951ORCID · reported

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

Software engineering, systems software and programming languages · 1 · 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
Debugging and program repair · 100%
Databases, data mining, and information retrieval
1 paper
Information retrieval · 100%

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

TopicWeightPapersLastEvidence papers
Debugging and program repair › fault localization
bug localization
0.812024
On Using GUI Interaction Data to Improve Text Retrieval-based Bug Localization · ICSE 2024
Debugging and program repair
fault localization
0.812024
On Using GUI Interaction Data to Improve Text Retrieval-based Bug Localization · ICSE 2024
Information retrieval
document retrieval
0.212024
On Using GUI Interaction Data to Improve Text Retrieval-based Bug Localization · ICSE 2024
Information retrieval
retrieval models
0.212024
On Using GUI Interaction Data to Improve Text Retrieval-based Bug Localization · ICSE 2024

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

GUI interaction data · 1.5
YearPublicationVenuePosition
2024 On Using GUI Interaction Data to Improve Text Retrieval-based Bug Localization
abstract
One of the most important tasks related to managing bug reports is localizing the fault so that a fix can be applied. As such, prior work has aimed to automate this task of bug localization by formulating it as an information retrieval problem, where potentially buggy files are retrieved and ranked according to their textual similarity with a given bug report. However, there is often a notable semantic gap between the information contained in bug reports and identifiers or natural language contained within source code files. For user-facing software, there is currently a key source of information that could aid in bug localization, but has not been thoroughly investigated - information from the graphical user interface (GUI).
Junayed Mahmud, Nadeeshan De Silva, Safwat Ali Khan, Seyed Hooman Mostafavi, S. M. Hasan Mansur 0001, Oscar Chaparro, Andrian Marcus, Kevin Moran
ICSE4