Demo Data from EDBT 2026 / reviewers in the wild / expert
Joe Wheadon
dblp:05/8
· DBLP profile ↗
2ranked-venue papers
0as first author
0since 2021 · last 2000
—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
1 paper |
Requirements engineering and software design · 100% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › requirements engineering
requirements reuse |
0.0 | 1 | 1999 | Reusing Single System Requirements from Application Family Requirements · ICSE 1999 |
Requirements engineering and software design › conceptual modeling
domain modeling |
0.0 | 1 | 1999 | Reusing Single System Requirements from Application Family Requirements · ICSE 1999 |
Requirements engineering and software design
requirements modeling |
0.0 | 1 | 1999 | Reusing Single System Requirements from Application Family Requirements · ICSE 1999 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2000 | Representing Requirements on Generic Software in an Application Family Model
Mike Mannion, Oliver Lewis, Hermann Kaindl, Gianluca Montroni, Joe Wheadon |
ICSR | 5 |
| 1999 | Reusing Single System Requirements from Application Family RequirementsabstractReuse and requirements engineering are very important for efficient and successful systems development. However there are many open issues for performing them well in practice, especially raise of requirements. We present a new approach to reusing requirements based on application families i.e. several systems in a given problem domain. In contrast to precious approaches, an application family model in our approach consists of a pool of requirements (linked in a lattice structure), a domain model and a set of discriminants (a special kind of requirement that differentiate one system from another). We focus on how to make an efficient and clean selection of the requirements for a new system from an application family model. We have developed a method for solving this problem and a prototypical tool for supporting it. The method and the prototype were successfully developed under a study contract for ESA (European Space Agency). We present a case study, where we generated commanding requirements for an individual mission from an application family model of commanding requirements for spacecraft control operating systems. As a consequence, we propose this approach for reusing requirements based an application families. Mike Mannion, Hermann Kaindl, Joe Wheadon |
ICSE | 3 |