Demo Data from SIGIR 2026 / reviewers in the wild / expert
Thomas Neumayer
dblp:27/559
· DBLP profile ↗
4ranked-venue papers
0as first author
0since 2021 · last 2010
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 4Artificial intelligence and machine learning · 1Applied, interdisciplinary, general and emerging computing · 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 |
Requirements engineering and software design · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design
software product lines |
0.1 | 1 | 2007 | Integrated tool support for software product line engineering · ASE 2007 |
Requirements engineering and software design › software product lines
variability management |
0.0 | 1 | 2007 | Integrated tool support for software product line engineering · ASE 2007 |
Methods — techniques the papers use, named apart from their topics
domain-specific modeling · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2010 | Structuring the modeling space and supporting evolution in software product line engineering
Deepak Dhungana, Paul Grünbacher, Rick Rabiser, Thomas Neumayer |
J. Syst. Softw. | 4 |
| 2008 | Supporting Evolution in Model-Based Product Line EngineeringabstractSoftware maintenance and evolution are among the most challenging and cost-intensive activities in software engineering. This is not different for software product lines due to their complexity and long life-span. New customer requirements, technology changes and internal enhancements lead to the continuous evolution of a product line's reusable assets. Due to the size of product lines, single stakeholders or teams can only maintain a small part of a system which poses additional challenges for evolution. This paper presents an approach supporting product line evolution by organizing variability models of large-scale product lines as a set of interrelated model fragments defining the variability of particular parts of the system. The approach allows semi-automatic merging of fragments into complete variability models. We also provide tool support to automatically detect changes that would make models and the architecture inconsistent. Furthermore, our approach supports the co-evolution of variability models and their respective meta-models. We illustrate the approach with examples from an ongoing industry collaboration. Deepak Dhungana, Thomas Neumayer, Paul Grünbacher, Rick Rabiser |
SPLC | 2 |
| 2008 | Supporting the Evolution of Product Line Architectures with Variability Model FragmentsabstractEvolution is a permanent challenge in product line engineering. Reusable assets such as software components or documents evolve continuously due to new customer requirements or technology changes. This leads to modifications or extensions of the product line's variability models describing the reference architecture. Due to the large size of product lines, single stakeholders or teams can only maintain a small part of a system which poses additional challenges for evolution. This paper presents a tool-supported approach for building and maintaining variability models of large-scale product lines. We structure variability models into multiple model fragments of manageable size that can be created and maintained by individual teams. Model fragments can be merged semi- automatically into a variability model. We illustrate the approach with examples from ongoing industry collaboration. Deepak Dhungana, Thomas Neumayer, Paul Grünbacher, Rick Rabiser |
WICSA | 2 |
| 2007 | Integrated tool support for software product line engineeringabstractProduct line engineering comprises many heterogeneous activities such as capturing the variability of reusable assets, supporting the derivation of products from the product line, evolving the product line, or tailoring the approach to the specifics of a domain. The inherent complexity of product lines implicates that tool support is inevitable to facilitate smooth performance and to avoid costly errors. Product line engineering tools have to support heterogeneous stakeholders involved in diverse activities. Tool integration therefore is of particular importance to foster their seamless cooperation. However, the integration is difficult to achieve due to the diversity of models and work products. This paper describes the DOPLER tool suite which has been developed to provide such integrated support. The tool suite is flexible and extensible to support domain-specific needs Deepak Dhungana, Rick Rabiser, Paul Grünbacher, Thomas Neumayer |
ASE | 4 |