<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>P332 - Software Engineering 2023</title>
<link>http://dl.gi.de/handle/20.500.12116/40068</link>
<description/>
<pubDate>Tue, 21 Jul 2026 13:25:42 GMT</pubDate>
<dc:date>2026-07-21T13:25:42Z</dc:date>
<image>
<title>P332 - Software Engineering 2023</title>
<url>http://dl.gi.de:80/bitstream/id/ccf98021-554b-4db3-8614-f0ded30d08c9/</url>
<link>http://dl.gi.de/handle/20.500.12116/40068</link>
</image>
<item>
<title>Editing Support for Software Languages: Implementation Practices in Language Server Protocols (Summary)</title>
<link>http://dl.gi.de/handle/20.500.12116/40127</link>
<description>Editing Support for Software Languages: Implementation Practices in Language Server Protocols (Summary)
Barros, Djonathan; Peldszus, Sven; Assunção, Wesley K. G.; Berger, Thorsten
Engels, Gregor; Hebig, Regina; Tichy, Matthias
We present our paper published at the 25th International Conference on Model Driven Engineering Languages and Systems (MODELS) [Ba22a]. Effectively using software languages requires effective editing support. Modern IDEs, modeling tools, and code editors typically provide sophisticated support to create, comprehend, or modify instances of particular languages. Unfortunately, building such editing support is challenging. While the engineering of languages is well understood and supported by modern model-driven techniques, there is a lack of engineering principles and best practices for realizing their editing support. We study practices for implementing editing support in so-called language servers—implementations of the language server protocol (LSP). LSP is a recent de facto standard to realize editing support for languages, separated from the editing tools, enhancing the reusability and quality of the editing support. Witnessing the LSP’s popularity, we take this opportunity to analyze the implementations of 30 language servers. We identify concerns that developers need to take into account when developing editing support, and we synthesize implementation practices to address them, based on a systematic analysis of the servers’ source code. We hope that our results shed light on an important technology for software language engineering, that facilitates language-oriented programming and systems development, including model-driven engineering.
</description>
<pubDate>Sun, 01 Jan 2023 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/40127</guid>
<dc:date>2023-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Component-based CEGAR - Building Software Verifiers from Off-the-Shelf Components</title>
<link>http://dl.gi.de/handle/20.500.12116/40128</link>
<description>Component-based CEGAR - Building Software Verifiers from Off-the-Shelf Components
Beyer, Dirk; Haltermann, Jan; Lemberger, Thomas; Wehrheim, Heike
Engels, Gregor; Hebig, Regina; Tichy, Matthias
Software verification tools typically consist of tighly coupled components, thereby precluding the easy integration of off-the-shelf components. We propose to decompose software verification into independent subtasks, each task being implemented by an own component communicating with other components via clearly defined interfaces. We apply this idea of decomposition to one of the most frequently used techniques in software verification: CEGAR. Our decomposition, called component-based CEGAR (C-CEGAR), comprises three components: An abstract model explorer, a feasibility checker and a precision refiner. It allows employing conceptually different components for each task within one instance. Our evaluation shows that C-CEGAR has, compared to a monolithic CEGAR-implementation, a similar efficiency and that the precision in solving verification tasks even increases.
</description>
<pubDate>Sun, 01 Jan 2023 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/40128</guid>
<dc:date>2023-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Software Engineering 2023 - kompletter Tagungsband</title>
<link>http://dl.gi.de/handle/20.500.12116/40125</link>
<description>Software Engineering 2023 - kompletter Tagungsband
Engels, Gregor; Hebig, Regina; Tichy, Matthias
</description>
<pubDate>Sun, 01 Jan 2023 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/40125</guid>
<dc:date>2023-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Synthesizing of Process-Aware Digital Twin Cockpits from Event Logs</title>
<link>http://dl.gi.de/handle/20.500.12116/40126</link>
<description>Synthesizing of Process-Aware Digital Twin Cockpits from Event Logs
Bano, Dorina; Michael, Judith; Rumpe, Bernhard; Varga, Simon; Weske, Mathias
Engels, Gregor; Hebig, Regina; Tichy, Matthias
In this work, we summarize our article “Process-Aware Digital Twin Cockpit Synthesis from Event Logs” published in the Journal of Computer Languages (COLA). The engineering of digital twins and their user interfaces with explicated processes, namely process-aware digital twin cockpits (PADTCs), is challenging due to the complexity of the systems and the need for information from different disciplines within the engineering process. Therefore, we have investigated how to facilitate their engineering by using already existing data, namely event logs. We present a low-code development approach that reduces the amount of hand-written code needed to derive PADTCs using process mining techniques. We describe what models could be derived from event log data, which generative steps are needed for the engineering of PADTCs, and how process mining could be incorporated into the resulting application. A PADTC prototype is created based on the MIMIC III dataset, which simulates an automated hospital transportation system. Initially, our approach requires no hand-written code and empowers the domain expert to iteratively create PADTC prototypes.
</description>
<pubDate>Sun, 01 Jan 2023 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/40126</guid>
<dc:date>2023-01-01T00:00:00Z</dc:date>
</item>
</channel>
</rss>
