@inproceedings{21931, author = {{Koch, Thorsten and Meyer, Matthias and Fazal-Baqaie, Masud and Runschke, Hubert}}, booktitle = {{Software Engineering 2020 (SE 2020)}}, editor = {{Felderer, Michael and Hasselbring, Wilhelm and Rabiser, Rick and Jung, Reiner}}, publisher = {{Gesellschaft für Informatik e.V.}}, title = {{{Softwareentwicklung wie am Fliessband}}}, doi = {{10.18420/SE2020\_58}}, year = {{2020}}, } @inproceedings{27428, abstract = {{The development of software-intensive technical systems (e.g., within the automotive industry) involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model-based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of a discipline-spanning system model. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline-specific development to start, for example, into specific requirements for the embedded software. Since existing MBSE approaches lack support for this refinement step, we conceived a systematic and iterative transition from MBSE to model-based software requirements engineering, which we present in this talk. We automated the steps of the transition where possible, in order to avoid error-prone and time-consuming manual tasks. We illustrate the approach and perform a case study with an example of an automotive embedded system.}}, author = {{Holtmann, Jörg and Bernijazov, Ruslan and Meyer, Matthias and Schmelter, David and Tschirner, Christian}}, booktitle = {{Proceedings of the Software Engineering 2017, Lecture Notes in Informatics (LNI), Band P-267}}, editor = {{Jürjens, Jan and Schneider, Kurt}}, pages = {{109--110}}, publisher = {{Gesellschaft für Informatik}}, title = {{{Integrated and Iterative Systems Engineering and Software Requirements Engineering for Technical Systems (Précis)}}}, volume = {{P-267}}, year = {{2017}}, } @unpublished{20798, abstract = {{Moderne und Automatisierungs- und Produktionssysteme speichern viele schützenswerte Daten wie zum Beispiel Produktionsmengen oder Verfahrenseinstellungen. Sie werden von speicherprogrammierbaren Steuerungen (SPS) gesteuert. Eine SPS bietet eine Vielzahl von Netzwerk-/Datenschnittstellen. Insbesondere Schnittstellen zum Internet ermöglichen neue Funktionalitäten, sind aber auch mögliche Angriffspunkte. Neben einer Netzwerktrennung durch Firewalls sollte zusätzlich programmatisch unterbunden werden, dass auf kritische/sensible Daten direkt oder indirekt über einen kritischen, unerwünschten Datenfluss zugegriffen werden kann. Bereits während der Entwicklung einer Anlage kann der Steuerungscode mittels statischer Programmanalyse untersucht werden. Die unabhängige Analyse von einzelnen Programmen reicht aber bei vernetzten Anlagen nicht aus, da sich der kritische Datenfluss erst aus der Kombination von Programm- und Netzwerkverhalten ergeben kann. Deshalb stellen wir in diesem Beitrag erste Ideen für eine verteilte statische Analyse der Steuerungssoftware einer vernetzten Industrieanlage vor, welche es ermöglicht den Datenfluss der gesamten vernetzten Anlage zu betrachten. Hierdurch wird es möglich zu beurteilen, ob kritische/sensible Daten die vernetzte Anlage verlassen oder ob diese manipuliert werden können. }}, author = {{Ghassemi, Faezeh and Meyer, Matthias and Pohlmann, Uwe and Priesterjahn, Claudia}}, title = {{{Verteilte statische Analyse zur Identifikation von kritischen Datenflüssen für vernetzte Automatisierungs- und Produktionssysteme}}}, year = {{2017}}, } @inproceedings{20802, abstract = {{The development of software-intensive technical systems (e.g., within the automotive industry) involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model-based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of a discipline-spanning system model. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline-specific development to start, for example, into specific requirements for the embedded software. Since existing MBSE approaches lack support for this refinement step, we conceived a systematic and iterative transition from MBSE to model-based software requirements engineering, which we present in this talk. We automated the steps of the transition where possible, in order to avoid error-prone and time-consuming manual tasks. We illustrate the approach and perform a case study with an example of an automotive embedded system.}}, author = {{Holtmann, Jörg and Bernijazov, Ruslan and Meyer, Matthias and Schmelter, David and Tschirner, Christian}}, booktitle = {{Proceedings of the Software Engineering 2017}}, editor = {{Jürjens, Jan and Schneider, Kurt}}, pages = {{109--110}}, publisher = {{Gesellschaft fuer Informatik}}, title = {{{Integrated and Iterative Systems Engineering and Software Requirements Engineering for Technical Systems (Précis)}}}, volume = {{P-267}}, year = {{2017}}, } @article{27468, abstract = {{The development of software-intensive technical systems involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model-based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline-spanning processes and a system model. Such a system model provides a common understanding of the system under development and serves as a starting point for the discipline-specific development. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline-specific development to start, e.g., into specific requirements for the embedded software. Since existing MBSE approaches lack support for this refinement step, we conceived in previous work a systematic transition from MBSE to model-based software requirements engineering. We automated the steps of the transition where possible, in order to avoid error-prone and time-consuming manual tasks. In this paper, we extend this approach with support for subsequent process iterations and provide an algorithm for the automated steps. We illustrate the approach and perform a case study with an example of an automotive embedded system.}}, author = {{Holtmann, Jörg and Bernijazov, Ruslan and Meyer, Matthias and Schmelter, David and Tschirner, Christian}}, journal = {{Journal of Software Evolution and Process}}, title = {{{Integrated and iterative systems engineering and software requirements engineering for technical systems}}}, doi = {{http://dx.doi.org/10.1002/smr.1780}}, year = {{2016}}, } @inproceedings{20824, abstract = {{Für die Ausführung der Software müssen die Softwarekomponenten auf ECUs verteilt werden. Dabei unterliegt die Verteilung sicherheitskritischen Constraints. Das Suchen der optimalen und gültigen Verteilung ist sehr komplex. Die Lösung kann effizient durch Verfahren des Operations Research ermittelt werden. Jedoch ist die manuelle Kodierung sehr aufwändig. Dieser Beitrag stellt eine modellgetriebene Methode und Werkzeugunterstützung vor, welche die Beschreibung von Constraints und Optimierungen vereinfacht sowie die formale Kodierung und Lösungssuche automatisiert. Dies erlaubt die effiziente Nutzung der Macht von formalen Modellen ohne Kenntnis der formalen mathematischen Verfahren. Die Vorteile der Methode werden anhand eines Beispiels aus der Automobilindustrie beschrieben. }}, author = {{Pohlmann, Uwe and Holtmann, Jörg and Meyer, Matthias}}, booktitle = {{Tagungsband Embedded Software Engineering Kongress 2016}}, pages = {{587--592}}, title = {{{Das Erwachen der Macht – Automatische Softwareverteilung}}}, year = {{2016}}, } @article{20829, abstract = {{The development of software-intensive technical systems involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model-based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline-spanning processes and a system model. Such a system model provides a common understanding of the system under development and serves as a starting point for the discipline-specific development. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline-specific development to start, e.g., into specific requirements for the embedded software. Since existing MBSE approaches lack support for this refinement step, we conceived in previous work a systematic transition from MBSE to model-based software requirements engineering. We automated the steps of the transition where possible, in order to avoid error-prone and time-consuming manual tasks. In this paper, we extend this approach with support for subsequent process iterations and provide an algorithm for the automated steps. We illustrate the approach and perform a case study with an example of an automotive embedded system.}}, author = {{Holtmann, Jörg and Bernijazov, Ruslan and Meyer, Matthias and Schmelter, David and Tschirner, Christian}}, journal = {{Journal of Software Evolution and Process}}, title = {{{Integrated and iterative systems engineering and software requirements engineering for technical systems}}}, doi = {{10.1002/smr.1780}}, year = {{2016}}, } @inproceedings{28303, abstract = {{The development of software-intensive technical systems (e.g., within the automotive industry) involves several engineering disciplines like mechanical, electrical, control, and software engineering. Model-based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline-spanning processes and system models. Such a system model provides a common understanding of the system under development and serves as a starting point for the discipline-specific development. An integral part of MBSE is the requirements engineering on the system level. However, for the discipline-specific development to start, these requirements need to be refined, e.g., into specific requirements for the embedded software. Since existing MBSE approaches lack support for this refinement step, we conceived a systematic transition from MBSE to model-based software requirements engineering, which we present in this paper. We automated the steps of the transition where possible, in order to avoid error-prone and time-consuming manual tasks. We illustrate the approach with an example of an automotive embedded system.}}, author = {{Holtmann, Jörg and Bernijazov, Ruslan and Meyer, Matthias and Schmelter, David and Tschirner, Christian}}, booktitle = {{Proceedings of the International Conference on Software and Systems Process (ICSSP)}}, pages = {{57--66}}, title = {{{Integrated Systems Engineering and Software Requirements Engineering for Technical Systems}}}, doi = {{http://dx.doi.org/10.1145/2785592.2785597}}, year = {{2015}}, } @inproceedings{20899, abstract = {{The development of software-intensive technical systems (e.g., within the automotive industry) involves several engineering disciplines like mechanical, electrical, control, and software engineering. Model-based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline-spanning processes and system models. Such a system model provides a common understanding of the system under development and serves as a starting point for the discipline-specific development. An integral part of MBSE is the requirements engineering on the system level. However, for the discipline-specific development to start, these requirements need to be refined, e.g., into specific requirements for the embedded software. Since existing MBSE approaches lack support for this refinement step, we conceived a systematic transition from MBSE to model-based software requirements engineering, which we present in this paper. We automated the steps of the transition where possible, in order to avoid error-prone and time-consuming manual tasks. We illustrate the approach with an example of an automotive embedded system. }}, author = {{Holtmann, Jörg and Bernijazov, Ruslan and Meyer, Matthias and Schmelter, David and Tschirner, Christian}}, booktitle = {{Proceedings of the 2015 International Conference on Software and System Process}}, isbn = {{9781450333467}}, title = {{{Integrated systems engineering and software requirements engineering for technical systems}}}, doi = {{10.1145/2785592.2785597}}, year = {{2015}}, } @inproceedings{20902, abstract = {{Die Komplexität moderner Fahrzeuge steigt aufgrund der zunehmenden Anzahl von Funktionen, die durch elektronische Systeme umgesetzt werden. Insbesondere nehmen die Abhängigkeiten zwischen den an der Entwicklung beteiligten Fachdisziplinen und der Softwareanteil massiv zu. Wir haben einen für die Automobilindustrie angepassten, zum Reifegradmodell Automotive SPICE konformen Prozess für die Entwicklung von Steuergeräten konzipiert, der ein fachdisziplinübergreifendes Systems Engineering und einen systematischen Übergang in die Softwareentwicklung unterstützt. Im Kontext dieses Entwicklungsprozess beschreiben wir in diesem Beitrag den Übergang vom UML-basierten Softwareentwurf zum in der Automobilindustrie etablierten AUTOSAR-Standard mit Hilfe einer automatischen Modelltransformation. So werden fehleranfällige und zeitaufwändige manuelle Tätigkeiten reduziert. Wir haben die Generierung von AUTOSAR-Modellen gemeinsam mit dem international tätigen Automobilzulieferer Hella KGaA Hueck & Co. in seriennahen Entwicklungsprojekten praktisch erprobt und Zeit- und Kostenersparnisse festgestellt.}}, author = {{Meyer, Jan and Holtmann, Jörg and Koch, Thorsten and Meyer, Matthias}}, booktitle = {{10. Paderborner Workshop Entwurf mechatronischer Systeme}}, editor = {{Gausemeier, Jürgen and Dumitrescu, Roman and Rammig, Franz-Josef and Schäfer, Wilhelm and Trächtler, Ansgar}}, pages = {{159–172}}, publisher = {{Heinz Nixdorf Institut}}, title = {{{Generierung von AUTOSAR-Modellen aus UML-Spezifikationen}}}, volume = {{343}}, year = {{2015}}, } @inproceedings{20903, author = {{Priesterjahn, Claudia and Holtmann, Jörg and Meyer, Matthias}}, booktitle = {{Tagungsband Embedded Software Engineering Kongress 2014}}, pages = {{619--627}}, title = {{{Smarte Entwicklung fuer smarte Systeme: Softwareentwicklung im Kontext des Gesamtsystems}}}, year = {{2014}}, } @article{20904, author = {{Diedrich, Christian and Meyer, Matthias and Evertz, Lars and Schäfer, Wilhelm}}, journal = {{atp edition - Automatisierungstechnische Praxis}}, pages = {{24--35}}, title = {{{Dienste in der Automatisierungstechnik}}}, year = {{2014}}, } @inproceedings{20905, author = {{Pohlmann, Uwe and Holtmann, Jörg and Meyer, Matthias and Gerking, Christopher}}, booktitle = {{Proceedings of the 40th Euromicro Conference on Software Engineering and Advanced Applications (SEAA)}}, publisher = {{IEEE Xplore}}, title = {{{Generating Modelica Models from Software Specifications for the Simulation of Cyber-physical Systems}}}, year = {{2014}}, } @article{20906, abstract = {{Von heutigen technischen Systemen wird immer mehr Funktionalität gefordert. Dies manifestiert sich in einer steigenden Anzahl von Anforderungen, die üblicherweise in freier natürlicher Sprache festgehalten werden. Das führt oft zu mehrdeutigen, widersprüchlichen oder unvollständigen Anforderungen. In diesem Beitrag wird eine Methode zur Spezifikation von Anforderungen auf Basis von Satzmustern inklusive ihrer Werkzeugunterstützung „ReqPat“ vorgestellt: Anforderungen werden weiterhin textuell aber in einer eingeschränkten natürlichen Sprache verfasst. Dadurch wird ein einheitliches Anforderungsverständnis erreicht und es werden Qualitätsanalysen sowie der Übergang zu Modellen automatisiert.}}, author = {{Fockel, Markus and Holtmann, Jörg and Meyer, Matthias}}, journal = {{OBJEKTspektrum}}, number = {{RE/2014}}, title = {{{Mit Satzmustern hochwertige Anforderungsdokumente effizient erstellen}}}, year = {{2014}}, } @inproceedings{20907, author = {{Becker, Steffen and Dziwok, Stefan and Gerking, Christopher and Heinzemann, Christian and Schäfer, Wilhelm and Meyer, Matthias and Pohlmann, Uwe}}, booktitle = {{Proceedings of the 36th International Conference on Software Engineering (Posters)}}, publisher = {{ACM, New York, NY, USA}}, title = {{{The MechatronicUML Method: Model-Driven Software Engineering of Self-Adaptive Mechatronic Systems}}}, year = {{2014}}, } @inproceedings{20908, author = {{Pohlmann, Uwe and Dziwok, Stefan and Meyer, Matthias and Tichy, Matthias and Thiele, Sebastian}}, booktitle = {{Proceedings of the 7th International ICST Conference on Simulation Tools and Techniques}}, title = {{{A Modelica Coordination Pattern Library for Cyber-Physical Systems}}}, year = {{2014}}, } @techreport{20909, author = {{Becker, Steffen and Dziwok, Stefan and Gerking, Christopher and Schäfer, Wilhelm and Heinzemann, Christian and Thiele, Sebastian and Meyer, Matthias and Priesterjahn, Claudia and Pohlmann, Uwe and Tichy, Matthias}}, title = {{{The MechatronicUML Design Method - Process and Language for Platform-Independent Modeling}}}, year = {{2014}}, } @inproceedings{20910, author = {{Pohlmann, Uwe and Meyer, Matthias and Dann, Andreas Peter and Brink, Christopher}}, booktitle = {{Proceedings of the 2Nd Workshop on View-Based, Aspect-Oriented and Orthographic Software Modelling}}, pages = {{23:23--23:30}}, publisher = {{ACM, New York, NY, USA}}, title = {{{Viewpoints and Views in Hardware Platform Modeling for Safe Deployment}}}, year = {{2014}}, } @inproceedings{20912, abstract = {{Mechatronics is the close interaction of mechanics, electronics, control engineering and software engineering. The increasing complexity of mechatronic systems results in a challenging development process and particularly requires a consistent comprehension of the tasks between all the engineers involved. Especially during the early design phases, the communication and cooperation between the mechanical, electrical, control and software engineers is necessary to establish a basis for efficient and effective product development. The approach of Model-Based Systems Engineering focuses on this aspect by means of an abstract but superordinate system model. It enables a holistic view of the system. The system model can be specified using the Systems Modeling Language (SysML). The language allows many degrees of freedom to specify a fact, bearing in mind that different system architects can specify the same fact in different ways. This leads to system models that can be interpreted in many ways. Thus, these models are hard to consistently compare and interpret, resulting in communication issues. In order to tackle this problem, we present a concept that uses modeling rules supporting model comparability. We formalize them by means of checks implemented in the programming language Java and the Object Constraint Language (OCL) in order to automatically verify the system model’s compliance with these rules.}}, author = {{Kaiser, Lydia and Dumitrescu, Roman and Holtmann, Jörg and Meyer, Matthias}}, booktitle = {{Volume 2B: 33rd Computers and Information in Engineering Conference}}, isbn = {{9780791855867}}, title = {{{Automatic Verification of Modeling Rules in Systems Engineering for Mechatronic Systems}}}, doi = {{10.1115/detc2013-12330}}, year = {{2014}}, } @inproceedings{28529, abstract = {{Mechatronics is the close interaction of mechanics, electronics, control engineering and software engineering. The increasing complexity of mechatronic systems results in a challenging development process and particularly requires a consistent comprehension of the tasks between all the engineers involved. Especially during the early design phases, the communication and cooperation between the mechanical, electrical, control and software engineers is necessary to establish a basis for efficient and effective product development. The approach of Model-Based Systems Engineering focuses on this aspect by means of an abstract but superordinate system model. It enables a holistic view of the system. The system model can be specified using the Systems Modeling Language (SysML). The language allows many degrees of freedom to specify a fact, bearing in mind that different system architects can specify the same fact in different ways. This leads to system models that can be interpreted in many ways. Thus, these models are hard to consistently compare and interpret, resulting in communication issues. In order to tackle this problem, we present a concept that uses modeling rules supporting model comparability. We formalize them by means of checks implemented in the programming language Java and the Object Constraint Language (OCL) in order to automatically verify the system model’s compliance with these rules. }}, author = {{Kaiser, Lydia and Dumitrescu, Roman and Holtmann, J{\"o}rg and Meyer, Matthias}}, booktitle = {{Proceedings of the ASME International Design Engineering Technical Conferences & Computers and Information in Engineering Conference}}, publisher = {{ASME}}, title = {{{Automatic Verification of Modeling Rules in Systems Engineering for Mechatronic Systems}}}, year = {{2013}}, }