<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Softwaretechnik-Trends 36(4) - 2016</title>
<link>http://dl.gi.de/handle/20.500.12116/40614</link>
<description/>
<pubDate>Tue, 21 Jul 2026 14:24:31 GMT</pubDate>
<dc:date>2026-07-21T14:24:31Z</dc:date>
<item>
<title>Combining Application-Level and Database-Level Monitoring to Analyze the Performance Impact of Database Lock Contention</title>
<link>http://dl.gi.de/handle/20.500.12116/40638</link>
<description>Combining Application-Level and Database-Level Monitoring to Analyze the Performance Impact of Database Lock Contention
Knoche, Holger
Database lock contention can severely impact application performance and limit scalability. This can be of particular importance when major modifications are made to transactional software, such as large refactorings or modernization projects. In order to assess the criticality of such modifications, it is necessary to measure the current degree of database lock contention, and attribute the effects to the appropriate sections of the application. However, current monitoring tools do not provide both application-level and database-level monitoring data with sufficient detail at the same time. In this paper, we present an approach to combine application-level and database-level monitoring to measure lock contention on a per-section basis, and present first experimental results from a prototypical implementation for PostgreSQL.
</description>
<pubDate>Fri, 01 Jan 2016 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/40638</guid>
<dc:date>2016-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Leveraging Palladio for Performance Awareness in the IETS 3 Integrated Specification Environment</title>
<link>http://dl.gi.de/handle/20.500.12116/40637</link>
<description>Leveraging Palladio for Performance Awareness in the IETS 3 Integrated Specification Environment
Keller, Fabian; Völter, Markus; van Hoorn, André; Birken, Klaus
Performance is an important concern when designing and implementing software-intensive systems. Various techniques are available for specifying and evaluating performance concerns throughout the system Performance is an important concern when designing and implementing software-intensive systems. Various techniques are available for specifying and evaluating performance concerns throughout the system life-cycle. However, there is a gap in terms of tooling when moving between requirements, design, and implementation artifacts. We address this gap by integrating simulation-based and analytical performance prediction tools into IETS3 — an integrated specification environment for technical software systems based on the JetBrains MPS language workbench. In this paper, we provide an overview of our work in progress on integrating performance awareness support into the IETS3 editor and user interface. We leverage Palladio’s prediction infrastructure by transforming to Palladio’s modeling language to obtain performance predictions, which are then fed back into the IETS3 user interface. The approach yields a tight integration of the requirements and the design of a system strengthened by a real-time feedback loop.b life-cycle. However, there is a gap in terms of tooling when moving between requirements, design, and implementation artifacts. We address this gap by integrating simulation-based and analytical performance prediction tools into IETS3 — an integrated specification environment for technical software systems based on the JetBrains MPS language workbench. In this paper, we provide an overview of our work in progress on integrating performance awareness support into the IETS3 editor and user interface. We leverage Palladio’s prediction infrastructure by transforming to Palladio’s modeling language to obtain performance predictions, which are then fed back into the IETS3 user interface. The approach yields a tight integration of the requirements and the design of a system strengthened by a real-time feedback loop.
</description>
<pubDate>Fri, 01 Jan 2016 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/40637</guid>
<dc:date>2016-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Advanced Typing for the Kieker Instrumentation Languages</title>
<link>http://dl.gi.de/handle/20.500.12116/40636</link>
<description>Advanced Typing for the Kieker Instrumentation Languages
Jung, Reiner; Wulf, Christian
The observation of software systems is a complicated task due to the heterogeneity of technologies and programming languages involved. In Kieker , we address this heterogeneity with two domain-specific languages (DSLs) which allow to define event types and monitoring probes independent from specific languages. The DSLs allow to extend event types individually and to adapt probes accordingly. In monitoring, different event types are used together to observe a specific property, like call traces. In case additional attributes, like message size, must be observed, multiple types must be extended simultaneously. This is cumbersome for large sets of types and an error prone task. In case of missed types or wrongly initialized attributes, the errors may harm analysis results. We address these challenges with a new type extension mechanism and semantic constraints for attributes.
</description>
<pubDate>Fri, 01 Jan 2016 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/40636</guid>
<dc:date>2016-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Security Modeling with Palladio—Different Approaches</title>
<link>http://dl.gi.de/handle/20.500.12116/40635</link>
<description>Security Modeling with Palladio—Different Approaches
Hilbrich, Marcus; Frank, Markus; Lehrig, Sebastian
Security is never perfect, security deals with a lot of uncertainty, and security is complex. Nevertheless, security is one of the non-functional properties, that we, as software architects, have to consider. It is needed to include security in many trade-off decisions (usability, performance, costs, etc. versus security), to compare the security of different architectures, and to check whether legal constraints are meet. Thus it is demanded to include security modeling to approaches like Palladio. In this paper, we describe two approaches to model and analyze security using Palladio. The first approach is an external one and requires to adapt Palladio. The second approach is proposed by us and does not need to modify Palladio. Furthermore, we explain why we needed to develop a new approach based on a use case and its demanded pragmatism for the model.
</description>
<pubDate>Fri, 01 Jan 2016 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/40635</guid>
<dc:date>2016-01-01T00:00:00Z</dc:date>
</item>
</channel>
</rss>
