Jannik Dahlke

dblp:204/3607 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2017
—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 · 67% Programming languages and type systems · 33%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Embedded and real-time systems · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
reactive systems
0.312017
From scenario modeling to scenario programming for reactive systems with dynamic topology · ESEC/SIGSOFT FSE 2017
Programming languages and type systems › programming paradigms
scenario-based programming
0.312017
From scenario modeling to scenario programming for reactive systems with dynamic topology · ESEC/SIGSOFT FSE 2017
Requirements engineering and software design › specification
scenario-based specification
0.312017
From scenario modeling to scenario programming for reactive systems with dynamic topology · ESEC/SIGSOFT FSE 2017
Embedded and real-time systems
reactive systems
0.112017
From scenario modeling to scenario programming for reactive systems with dynamic topology · ESEC/SIGSOFT FSE 2017

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

scenario modeling language · 0.6code generation · 0.6
YearPublicationVenuePosition
2017 From scenario modeling to scenario programming for reactive systems with dynamic topology
abstract
Software-intensive systems often consist of cooperating reactive components. In mobile and reconfigurable systems, their topology changes at run-time, which influences how the components must cooperate. The Scenario Modeling Language (SML) offers a formal approach for specifying the reactive behavior such systems that aligns with how humans conceive and communicate behavioral requirements. Simulation and formal checks can find specification flaws early. We present a framework for the Scenario-based Programming (SBP) that reflects the concepts of SML in Java and makes the scenario modeling approach available for programming. SBP code can also be generated from SML and extended with platform-specific code, thus streamlining the transition from design to implementation. As an example serves a car-to-x communication system. Demo video and artifact: http://scenariotools.org/esecfse-2017-tool-demo/
Joel Greenyer, Daniel Gritzner, Florian König, Jannik Dahlke, Jianwei Shi 0001, Eric Wete
ESEC/SIGSOFT FSE4