Demo Data from VLDB 2026 / reviewers in the wild / expert
Graham Jenson
dblp:81/3298
· DBLP profile ↗
2ranked-venue papers
2as 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 · 2 · 2 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 |
Software maintenance and evolution · 62% Requirements engineering and software design · 38% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution › software ecosystems
dependency management |
0.1 | 1 | 2009 | Improving Component Dependency Resolution with Soft Constraints, Validation and Verification · ASE 2009 |
Requirements engineering and software design › software architecture › component-based software engineering
component-based architecture |
0.0 | 1 | 2009 | Improving Component Dependency Resolution with Soft Constraints, Validation and Verification · ASE 2009 |
Requirements engineering and software design
software architecture |
0.0 | 1 | 2009 | Improving Component Dependency Resolution with Soft Constraints, Validation and Verification · ASE 2009 |
Methods — techniques the papers use, named apart from their topics
validation and verification · 0.1soft constraints · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2010 | A Formal Framework to Optimise Component Dependency ResolutionabstractDependency resolution (DR) uses a component's explicitly declared requirements to calculate systems where all dependencies are satisfied. There can be many configurations to choose from when resolving dependencies. DR should aim to identify and return an optimal component configuration. This becomes a significant challenge when diverse and sometimes conflicting criteria such as user preferences, contextual constraints and functional requirements must be considered. In this paper we present a framework in which to represent and compose such criteria. This is achieved by defining criteria as ranking systems over complete lattices and composing them in different ways. We present a depth first branch and bound algorithm for this framework, and an example problem that demonstrates the frameworks application. The presented framework will enable the formal definition and composition of criteria to optimise dependency resolution. Graham Jenson, Jens Dietrich 0001, Hans W. Guesgen |
APSEC | 1 |
| 2009 | Improving Component Dependency Resolution with Soft Constraints, Validation and VerificationabstractSoftware components are encapsulated units of execution which express dependencies through explicitly stated requirements and capabilities. These are used within component repositories to resolve sub-systems of deployable components. The main problem with this dependency resolution is not the lack of available solutions but the excess of them. Within current repositories the returned solution may not be optimal for the composers requirements and context. Improving dependency resolved solutions from repositories using soft constraints with validation and verification is the topic of our Ph.D. and discussed within this paper. Graham Jenson |
ASE | 1 |