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.

Mohammad Hadi Zibaeenejad

dblp:149/0333 · DBLP profile ↗
← Back
1ranked-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 · 1 · 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 · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software product lines
feature interaction
0.312017
Continuous variable-specific resolutions of feature interactions · ESEC/SIGSOFT FSE 2017
Requirements engineering and software design › software product lines
feature interaction resolution
0.312017
Continuous variable-specific resolutions of feature interactions · ESEC/SIGSOFT FSE 2017
Requirements engineering and software design › software product lines
feature-oriented software development
0.112017
Continuous variable-specific resolutions of feature interactions · ESEC/SIGSOFT FSE 2017
Requirements engineering and software design
software architecture
0.112017
Continuous variable-specific resolutions of feature interactions · ESEC/SIGSOFT FSE 2017

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

resolution strategies · 0.3
YearPublicationVenuePosition
2017 Continuous variable-specific resolutions of feature interactions
abstract
Systems that are assembled from independently developed features suffer from feature interactions, in which features affect one another's behaviour in surprising ways. The Feature Interaction Problem results from trying to implement an appropriate resolution for each interaction within each possible context, because the number of possible contexts to consider increases exponentially with the number of features in the system. Resolution strategies aim to combat the Feature Interaction Problem by offering default strategies that resolve entire classes of interactions, thereby reducing the work needed to resolve lots of interactions. However most such approaches employ coarse-grained resolution strategies (e.g., feature priority) or a centralized arbitrator.
Mohammad Hadi Zibaeenejad, Joanne M. Atlee
ESEC/SIGSOFT FSE1