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
Demo Data from EDBT 2026 / reviewers in the wild / expert

Kashif Manzoor

dblp:33/6149 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 2008
—ORCID · none

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

Software engineering, systems software and programming languages · 2

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
2 papers
Software maintenance and evolution · 100%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
refactoring		 0.222008
Effective Software Merging in the Presence of Object-Oriented Refactorings · IEEE Trans. Software Eng. 2008
Refactoring-Aware Configuration Management for Object-Oriented Programs · ICSE 2007
Software maintenance and evolution › software merging
merge conflict resolution		 0.122008
Effective Software Merging in the Presence of Object-Oriented Refactorings · IEEE Trans. Software Eng. 2008
Refactoring-Aware Configuration Management for Object-Oriented Programs · ICSE 2007
Software maintenance and evolution
software configuration management		 0.122008
Effective Software Merging in the Presence of Object-Oriented Refactorings · IEEE Trans. Software Eng. 2008
Refactoring-Aware Configuration Management for Object-Oriented Programs · ICSE 2007
Software maintenance and evolution › software merging
refactoring-aware merging		 0.112008
Effective Software Merging in the Presence of Object-Oriented Refactorings · IEEE Trans. Software Eng. 2008
Software maintenance and evolution
software merging		 0.012008
Effective Software Merging in the Presence of Object-Oriented Refactorings · IEEE Trans. Software Eng. 2008

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

change operation replay · 0.2controlled experiment · 0.1
YearPublicationVenuePosition
2008 Effective Software Merging in the Presence of Object-Oriented Refactorings
abstract
Current text based Software Configuration Management (SCM) systems have trouble with refactorings. Refactorings result in global changes which lead to merge conflicts. A refactoring-aware SCM system reduces merge conflicts. This paper describes MolhadoRef, a refactoring-aware SCM system and the merge algorithm at its core. MolhadoRef records change operations (refactorings and edits) used to produce one version, and replays them when merging versions. Since refactorings are change operations with well defined semantics, MolhadoRef treats them intelligently. A case study and a controlled experiment show that MolhadoRef automatically solves more merge conflicts than CVS while resulting in fewer merge errors.
Danny Dig, Kashif Manzoor, Ralph E. Johnson, Tien N. Nguyen
 IEEE Trans. Software Eng.2
2007 Refactoring-Aware Configuration Management for Object-Oriented Programs
abstract
Current text based software configuration management (SCM) systems have trouble with refactorings. Refactorings result in global changes and lead to merge conflicts. A refactoring-aware SCM system reduces merge conflicts, preserves program history better and makes it easier to understand program evolution. This paper describes MolhadoRef a refactoring-aware SCM system and the merge algorithm at its core. MolhadoRef records change operations (refactorings and edits) used to produce one version, and replays them when merging versions. Since refactorings are change operations with well defined semantics, MolhadoRef treats them intelligently. A case-study shows that MolhadoRef solves automatically more merge conflicts than CVS while resulting in fewer merge errors.
Danny Dig, Kashif Manzoor, Ralph E. Johnson, Tien N. Nguyen
 ICSE2