http://dl.gi.de/handle/20.500.12116/40854 Tue, 21 Jul 2026 14:24:29 GMT 2026-07-21T14:24:29Z http://dl.gi.de/handle/20.500.12116/40894 Why Models and Code Should be Treated as Friends Derakhshanmanesh, Mahdi; Ebert, Jürgen; Engels, Gregor Various approaches have been proposed to face the difficulties related to constructing and maintaining modern software systems. Often, they incorporate models in some part of the development or evolution process. Even the use of models at runtime seems to receive more and more attention as a way to enable the quick, systematic and automated application of change operations on software as it executes. Assuming that existing systems have been largely developed in code and that novel target architectures depend on – or even embed – models to some extent, the possible roles of models and code as well as their interaction and interchangeability need to be thoroughly examined. In this position paper, we attempt to initiate a discussion on why models and code should become closer friends. Wed, 01 Jan 2014 00:00:00 GMT http://dl.gi.de/handle/20.500.12116/40894 2014-01-01T00:00:00Z http://dl.gi.de/handle/20.500.12116/40895 Reverse-Modellierung von Traceability zwischen Code, Test und Anforderungen Sneed, Harry M. In diesem Beitrag zur Modellierung der architektonischen Abhängigkeiten zwischen Code, Test und Anforderungen wird ein Reverse Engineering Prozess zur Wiederherstellung von Traceability zwischen Code-Bausteinen, Testfällen und Anforderungen über die Anwendungsfälle geschildert. Im Mittelpunkt des Prozesses steht ein SoftwareRepository, das dazu dient die aus dem Code und dem Test gewonnenen Abhängigkeiten zusammenzuführen. Das Ziel ist festzustellen, welche Testfälle welche Anforderungen testen und welche Code-Bausteine welche Anforderungen implementieren. Wed, 01 Jan 2014 00:00:00 GMT http://dl.gi.de/handle/20.500.12116/40895 2014-01-01T00:00:00Z http://dl.gi.de/handle/20.500.12116/40892 User-Driven Adaptation of Model Differencing Results Müller, Klaus; Rumpe, Bernhard In model-based software development, models are core development artifacts which are typically created and modified by multiple developers over a period of time. In order to be able to reason about the evolution of models, the computation of the differences between different versions of a model, called model differencing, is a crucial activity. However, in general a completely automatic approach to model differencing cannot infer the differences correctly in all cases. Errors in the reported model differences are particularly problematic, when the model differences are used in an automated process as a basis to perform other activities. In this paper, we propose an approach to model differencing in which users can integrate knowledge of how specific model elements changed from one model (version) to the other. By means of this, users can influence the reported model differences to avoid that wrong model differences are reported. Wed, 01 Jan 2014 00:00:00 GMT http://dl.gi.de/handle/20.500.12116/40892 2014-01-01T00:00:00Z http://dl.gi.de/handle/20.500.12116/40893 Modellbasierte und Modellgetriebene Softwaremodernisierung Becker, Steffen; Riebisch, Matthias; Sauer, Stefan; Klatt, Benjamin; Ruhroth, Thomas P. Wed, 01 Jan 2014 00:00:00 GMT http://dl.gi.de/handle/20.500.12116/40893 2014-01-01T00:00:00Z