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

Vibhu Mohindra

dblp:10/1689 · DBLP profile ↗
← Back
1ranked-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 · 1

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

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution › software evolution
library API evolution		 0.112008
ReBA: refactoring-aware binary adaptation of evolving libraries · ICSE 2008
Software maintenance and evolution
software evolution		 0.112008
ReBA: refactoring-aware binary adaptation of evolving libraries · ICSE 2008
Software maintenance and evolution
refactoring		 0.012008
ReBA: refactoring-aware binary adaptation of evolving libraries · ICSE 2008

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

binary rewriting · 0.1
YearPublicationVenuePosition
2008 ReBA: refactoring-aware binary adaptation of evolving libraries
abstract
Although in theory the APIs of software libraries and frameworks should be stable, they change in practice. This forces clients of the library API to change as well, making software maintenance expensive. Changing a client might not even be an option if its source code is missing or certain policies forbid its change. By giving a library both the old and the new API, clients can be shielded from API changes and can run with the new version of the library.
Danny Dig, Stas Negara, Vibhu Mohindra, Ralph E. Johnson
 ICSE3