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

Stefan Baerisch

dblp:60/4787 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2007
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 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 testing · 56% Requirements engineering and software design · 44%

Topics — the 2 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
model-driven engineering
0.112007
Model-driven test-case construction · ESEC/SIGSOFT FSE 2007
Software testing
system testing
0.012007
Model-driven test-case construction · ESEC/SIGSOFT FSE 2007

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

model-driven engineering · 0.1
YearPublicationVenuePosition
2007 Model-driven test-case construction
abstract
Automatic system tests are frequently coupled to implementation details of the system under test. Such a tight coupling is problematic for a number of reasons: It prevents reuse of existing tests for multiple versions or variants of a system or for a number of systems in a system family and it makes the ability to construct executable tests for a system dependent on programming skills. In this paper we present an approach that decouples test specification and test execution by using system models and test models for the representation of systems under test and tests. We motivate the use of abstract test models and system models, introduce the relevant concepts of our approach and discuss the relationship to relevant fields.
Stefan Baerisch
ESEC/SIGSOFT FSE1