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.
? Tutorial for this page

Bart Vanhaute

dblp:17/1713 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2001
—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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software architecture › component-based software engineering
component-based systems
0.012001
Dynamic and Selective Combination of Extensions in Component-Based Applications · ICSE 2001
Requirements engineering and software design
software architecture
0.012001
Dynamic and Selective Combination of Extensions in Component-Based Applications · ICSE 2001
Requirements engineering and software design
separation of concerns
0.012001
Dynamic and Selective Combination of Extensions in Component-Based Applications · ICSE 2001

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

mixin-like wrappers · 0.0composition logic externalization · 0.0
YearPublicationVenuePosition
2001 Dynamic and Selective Combination of Extensions in Component-Based Applications
abstract
Support for dynamic and client-specific customization is required in many application areas. We present a (distributed) application as consisting of a minimal functional core, implemented as a component based system, and an unbound set of potential extensions that can be selectively integrated within this core functionality. An extension to this core may be a new service due to new requirements of end users. Another important category of extensions we consider are non-functional services such as authentication, which typically introduce interaction refinements at the application level. In accordance with the separation of concerns principle, each extension is implemented as a layer of mixin-like wrappers. Each wrapper incrementally adds behavior and state to a core component instance from the outside, without modifying the component's implementation. The novelty of this work is that the composition logic, responsible for integrating extensions into the core system, is externalized from the code of clients, core system and extensions. Clients (end users, system integrators) can customize this composition logic on a per collaboration basis by 'attaching' high-level interpretable extension identifiers to their interactions with the core system.
Eddy Truyen, Bart Vanhaute, Wouter Joosen, Pierre Verbaeten, Bo Nørregaard Jørgensen
ICSE2