Demo Data from VLDB 2026 / reviewers in the wild / expert
Holger Hofmann
dblp:72/4298
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2002
—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 |
Requirements engineering and software design · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › software architecture › reusable architecture
product line architecture |
0.0 | 1 | 2002 | Integrating hundred's of product through one architecture: the industrial IT architecture · ICSE 2002 |
Requirements engineering and software design
software architecture |
0.0 | 1 | 2002 | Integrating hundred's of product through one architecture: the industrial IT architecture · ICSE 2002 |
Requirements engineering and software design
software product lines |
0.0 | 1 | 2002 | Integrating hundred's of product through one architecture: the industrial IT architecture · ICSE 2002 |
Methods — techniques the papers use, named apart from their topics
case study · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2002 | Integrating hundred's of product through one architecture: the industrial IT architectureabstractDuring the last few years, software product line engineering has gained significant interest as a way for creating software products faster and cheaper. But what architecture is needed to integrate huge amounts of products, from different product lines? This paper describes such an architecture and its support processes and tools. Through cases, it is illustrated how the architecture is used to integrate new --- and old --- products in such diverse integration projects as vessel motion control, airport baggage handling systems, pulp&paper and oil&gas, in a very large organization. However, in a large organization it is a challenge to make everyone follow an architecture. Steps taken to ensure global architectural consistency are presented. It is concluded that a single architecture can be used to unify development in a huge organization, where the distributed development practices otherwise may prohibit integration of various products. Lars Bratthall, Robert van der Geest, Holger Hofmann, Edgar Jellum, Zbigniew Korendo, Robert Martinez, Michal Orkisz, Christian Zeidler, Johan S. Andersson |
ICSE | 3 |