@inproceedings{65261, author = {{Trentinaglia, Roman and Koch, Thorsten and Bodden, Eric}}, booktitle = {{Proceedings of the 14th International Conference on Model-Based Software and Systems Engineering}}, publisher = {{SCITEPRESS - Science and Technology Publications}}, title = {{{Using Attack and Failure Propagation Analysis for Context-Aware Security Control Suggestions}}}, doi = {{10.5220/0014278000004058}}, year = {{2026}}, } @inproceedings{53811, abstract = {{Persistent security challenges plague DevOps teams due to a deficiency in expertise regarding security tools and methods, as evidenced by frequent security incidents. Existing maturity models fail to adequately address the specific needs of DevOps teams. In response, this paper proposes "Security Belts," a novel maturity model inspired by martial arts ranking systems. This model aims to assist DevOps teams in enhancing their security capabilities by providing a structured approach, starting with fundamental activities and progressing to more advanced techniques. Drawing from the experiences of monitoring 21 teams, the paper presents lessons learned and offers actionable advice for refining maturity models tailored to software quality improvement.}}, author = {{Taaibi, Samira and Dziwok, Stefan and Hermerschmidt, Lars and Koch, Thorsten and Merschjohann, Sven and Vollmary, Mark}}, keywords = {{Software security, maturity model}}, location = {{Salt Lake City}}, title = {{{Security Belts: A Maturity Model for DevOps Teams to Increase the Software Security of their Product - An Experience Report}}}, year = {{2024}}, } @inproceedings{29844, author = {{Koch, Thorsten and Trippel, Sascha and Dziwok, Stefan and Bodden, Eric}}, booktitle = {{Proceedings of the 10th International Conference on Model-Driven Engineering and Software Development}}, publisher = {{SCITEPRESS - Science and Technology Publications}}, title = {{{Integrating Security Protocols in Scenario-based Requirements Specifications}}}, doi = {{10.5220/0010783300003119}}, year = {{2022}}, } @inproceedings{33837, author = {{Piskachev, Goran and Dziwok, Stefan and Koch, Thorsten and Merschjohann, Sven and Bodden, Eric}}, title = {{{How far are German companies in improving security through static program analysis tools?}}}, year = {{2022}}, } @unpublished{23534, abstract = {{In recent years, the World Economic Forum has identified software security as the most significant technological risk to the world's population, as software-intensive systems process critical data and provide critical services. This raises the question of the extent to which German companies are addressing software security in developing and operating their software products. This paper reports on the results of an extensive study among developers, product owners, and managers to answer this question. Our results show that ensuring security is a multi-faceted challenge for companies, involving low awareness, inaccurate self-assessment, and a lack of competence on the topic of secure software development among all stakeholders. The current situation in software development is therefore detrimental to the security of software products in the medium and long term.}}, author = {{Dziwok, Stefan and Koch, Thorsten and Merschjohann, Sven and Budweg, Boris and Leuer, Sebastian}}, booktitle = {{arXiv:2108.11752}}, title = {{{AppSecure.nrw Software Security Study}}}, year = {{2021}}, } @inproceedings{20518, author = {{Koch, Thorsten and Dziwok, Stefan and Holtmann, Jörg and Bodden, Eric}}, booktitle = {{ACM/IEEE 23rd International Conference on Model Driven Engineering Languages and Systems (MODELS ’20)}}, publisher = {{ACM}}, title = {{{Scenario-based Specification of Security Protocols and Transformation to Security Model Checkers}}}, doi = {{10.1145/3365438.3410946}}, year = {{2020}}, } @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{21929, author = {{Altemeier, Katharina and Becker, Matthias and Dziwok, Stefan and Koch, Thorsten and Merschjohann, Sven}}, booktitle = {{Projektmanagement und Vorgehensmodelle 2019 (PVM 2019)}}, editor = {{Mikusz, Martin}}, publisher = {{Gesellschaft für Informatik e.V.}}, title = {{{Was fehlt (bisher) um Apps sicher zu entwickeln? - Prozesse, Werkzeuge und Schulungen für sichere Apps by Design}}}, year = {{2019}}, } @inbook{20782, abstract = {{Original equipment manufacturers (OEMs) build mechatronic, variant-rich systems using components from several suppliers in industry sectors like automation. The OEMs have to integrate the different components to the overall system based on a virtual layout. For this purpose, the suppliers provide geometrical information via the standardized exchange format STEP. Beyond the geometrical information, the OEMs need additional logical and technical information for the integration task as well as the variant handling. For that reason, STEP provides an extension mechanism for extending and tailoring STEP to project-specific needs. However, extending STEP requires extending several capabilities of all involved tools, which prevents the project-specific utilization of the STEP extensions mechanism. In order to cope with this problem, we presented in previous work a model-driven approach enabling the flexible specification of STEP extensions and particularly the automatic derivation of the required capability extensions for two involved tools. Nevertheless, the OEMs still need to apply several engineering tools from different domains to consider logical as well as geometrical constraints between product variants. In this paper, we hence combine our previous approach with extended feature models that consider conventional logical and particularly geometrical information, thereby enabling a holistic product line engineering for mechatronic systems. By means of an automation production system example, we illustrate how OEMs can orchestrate their overall supply and development processes through the combination of both approaches.}}, author = {{Koch, Thorsten and Holtmann, Jörg and Lindemann, Timo}}, booktitle = {{Revised Selected Papers of the 5th International Conference on Model-Driven Engineering and Software Development}}, editor = {{Pires, Luís Ferreira and Hammoudi, Slimane and Selic, Bran}}, pages = {{173--197}}, publisher = {{Springer International Publishing}}, title = {{{Model-Driven STEP Application Protocol Extensions Combined with Feature Modeling Considering Geometrical Information}}}, doi = {{10.1007/978-3-319-94764-8_8}}, volume = {{880}}, year = {{2018}}, } @inproceedings{20783, author = {{Koch, Thorsten}}, booktitle = {{International Workshop on Security for and by Model-Driven Engineering (SecureMDE 2018)}}, title = {{{Towards Scenario-based Security Requirements Engineering for Cyber-Physical Systems}}}, year = {{2018}}, } @inproceedings{20786, abstract = {{Distributed, software-intensive systems such as automotive electronic control units have to handle various situations employing message-based coordination. The growing complexity of such systems results in an increasing difficulty to achieve a high quality of the systems' requirements specifications. Scenario-based requirements engineering addresses the message-based coordination of such systems and enables, if underpinned with formal modeling languages, automatic analyses for ensuring the quality of requirements specifications. However, formal requirements modeling languages require high expertise of the requirements engineers and many manual iterations until specifications reach high quality. Patterns provide a constructive means for assembling high-quality solutions by applying reusable and established building blocks. Thus, they also gained momentum in requirements documentation. In order to support the requirements engineers in the systematic conception of formal, scenario-based requirements specification models, we hence introduce in this paper a requirement pattern catalog for a requirements modeling language. We illustrate and discuss the application of the requirement patterns with an example of requirements for an automotive electronic control unit.}}, author = {{Fockel, Markus and Holtmann, Jörg and Koch, Thorsten and Schmelter, David}}, booktitle = {{6th International Conference on Model-Driven Engineering and Software Development (MODELSWARD 2018)}}, title = {{{Formal, Model- and Scenario-based Requirement Patterns}}}, year = {{2018}}, } @techreport{20793, abstract = {{Scenario-based requirements engineering addresses the message-based coordination of software-intensive systems and enables, if underpinned with formal languages, automatic requirements validation techniques for improving the quality of a requirements specification. One of such requirements engineering approaches bases on a recent visual Live Sequence Chart variant compliant to the Unified Modeling Language, so-called Modal Sequence Diagrams (MSDs). The usage of patterns is known to be constructive thanks to assembling solutions by means of reusable building blocks that are proven in practice, so that recurring problems do not need to be solved over and over again. Thus, patterns also gained momentum in the area of requirements documentation. In this technical report, we introduce a model- and scenario-based pattern catalog for MSD requirements. Our MSD requirement pattern catalog consolidates and unifies 86 requirement patterns from three well-known, practice-oriented requirement pattern catalogs, each covering different aspects.}}, author = {{Fockel, Markus and Holtmann, Jörg and Koch, Thorsten and Schmelter, David}}, title = {{{Model-based Requirement Pattern Catalog}}}, year = {{2017}}, } @inproceedings{20801, abstract = {{Original equipment manufacturers (OEMs) build mechatronic systems using components from several suppliers in industry sectors like automation. The suppliers provide geometrical information via the standardized exchange format STEP, such that the OEM is able to virtually layout the overall system. Beyond the geometrical information, the OEM needs additional technical information for his development tasks. For that reason, STEP provides an extension mechanism for extending and tailoring STEP to project-specific needs. However, extending STEP moreover requires extending several capabilities of all involved tools, causing high development effort. This effort prevents the project-specific utilization of the STEP extension mechanism and forces the organizations to use awkward workarounds. In order to cope with this problem, we present a model-driven approach enabling the flexible specification of STEP extensions and particularly the automatic derivation of the required further capabilities for two involved tools. We illustrate and evaluate the approach with an automation production system example.}}, author = {{Koch, Thorsten and Holtmann, Jörg and Lindemann, Timo}}, booktitle = {{Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development}}, title = {{{Flexible Specification of STEP Application Protocol Extensions and Automatic Derivation of Tool Capabilities}}}, doi = {{10.5220/0006137400530064}}, year = {{2017}}, } @techreport{20823, abstract = {{In this technical report, we present the MechatronicUML requirements engineering method. The method encompasses a process and a scenario-based modeling language for the documentation and analysis of requirements on the message-based interaction behavior of software-intensive systems. The modeling language uses a scenario notation based on Modal Sequence Diagrams (MSDs), which borrows concepts of UML Interactions as well as of Live Sequence Charts. Furthermore, we introduce the so-called Emergency Braking & Evasion System (EBEAS) as a running example, which is based on current and upcoming real-world driver assistance systems. }}, author = {{Holtmann, Jörg and Fockel, Markus and Koch, Thorsten and Schmelter, David and Brenner, Christian and Bernijazov, Ruslan and Sander, Marcel}}, title = {{{The MechatronicUML Requirements Engineering Method: Process and Language}}}, doi = {{10.13140/RG.2.2.33223.29606}}, year = {{2016}}, } @inproceedings{20826, abstract = {{The development of today’s technical products (e.g., in automation) is characterized by high customer expectations regarding the product individualization, which causes a wide range of product variants. Original equipment manufacturers (OEMs) can apply classical approaches from product line engineering, like feature modeling, to cope with the variability and the induced development complexity. Our tool support for feature models integrates a variety of feature model extensions like feature attributes and properties, logical constraints between features and feature properties, and the distinction between features and feature realizations. Furthermore, technical products have geometrical dimensions. The OEM specifies Computer Aided Design (CAD) models to consider these geometric dimensions and to virtually layout particular product variants. Geometric assembly constraints specify how parts of the product can be arranged in a CAD model. However, a potential product customer cannot configure an individual product variant and virtually layout this variant in the same software tool since the respective information stems from different sources. In order to cope with this problem, we present in this paper an extension of our tool support for feature models to specify geometric assembly constraints. Based on the proposed extension, we outline our research roadmap to consider these constraints in an online shop of an e-commerce system, in which a potential customer shall be able to configure a product variant and to virtually layout it according to the assembly constraints. }}, author = {{Koch, Thorsten and Holtmann, Jörg and Schubert, David and Lindemann, Timo}}, booktitle = {{3rd International Conference on System-integrated Intelligence: New Challenges for Product and Production Engineering (SysInt 2016)}}, editor = {{Trächtler, Ansgar and Denkena, Berend and Thoben, Klaus-Dieter}}, pages = {{447--454}}, publisher = {{Elsevier}}, title = {{{Towards Feature-based Product Line Engineering of Technical Systems}}}, doi = {{10.1016/j.protcy.2016.08.057}}, year = {{2016}}, } @article{20828, abstract = {{In verschiedenen Unternehmen wird mit Anforderungen unterschiedlich umgegangen. Je nach Größe, Branche und Unternehmenskultur ist das Thema Requirements Engineering (RE) mal weniger, mal mehr etabliert. In einigen Unternehmen wird es als lästige Zusatzaufgabe betrachtet, während andere Unternehmen ganze Abteilungen mit RE als Kernkompetenz betreiben. RE wird allerdings in jedem Projekt - bewusst oder unbewusst - durchgeführt! RE ist die Basis für den weiteren Entwicklungsprozess, die Validierung/Verifikation und die Plan- und Messbarkeit des Projekts. Darüber hinaus können Fehler, die auf Anforderungsebene gefunden werden, weniger aufwendig und somit günstiger behoben werden als in späteren Entwicklungsphasen. Am Fraunhofer IEM beraten wir Unternehmen und erforschen neue Methoden bezüglich der Entwicklung von intelligenten technischen Systemen. In diesem Artikel berichten wir über unsere Erfahrungen aus Projekten, in denen wir Unternehmen aus verschiedenen Branchen und mit unterschiedlichem RE-Reifegrad zwecks Leistungssteigerung des RE begleitet haben. Auf Basis dieser Projekterfahrungen zeigen wir Wege auf, wie der Stand des RE mittels eines Reifegradmodells im eigenen Unternehmen verbessert werden kann.}}, author = {{Holtmann, Jörg and Fockel, Markus and Koch, Thorsten and Schmelter, David}}, journal = {{OBJEKTspektrum}}, number = {{RE/2016}}, title = {{{Requirements Engineering - Zusatzaufgabe oder Kernkompetenz?}}}, year = {{2016}}, } @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}}, } @inbook{20982, abstract = {{Real-time software-intensive embedded systems complexity, as in the automotive domain, requires rigorous Requirements Engineering (RE) approaches. Scenario-based RE formalisms like Modal Sequence Diagrams (MSDs) enable an intuitive specication and the simulative validation of functional requirements. However, the dependencies between events occurring in different MSD scenarios are implicit so that it is difficult to find causes of requirements defects, if any. The automotive architecture description language EAST-ADL addresses this problem by relying on event chains, which make dependencies between events explicit. However, EAST-ADL event chains have a low abstraction level, and their relationship to functional requirements has seldom been investigated. Based on the EAST-ADL functional architecture, we propose to use its central notion of event to conciliate both approaches. We conceived an automatic transformation from the high abstraction level requirements specified in MSDs to the low abstraction level event chains. }}, author = {{Koch, Thorsten and Holtmann, Jörg and DeAntoni, Julien}}, booktitle = {{Software Architecture}}, isbn = {{9783319099699}}, issn = {{0302-9743}}, title = {{{Generating EAST-ADL Event Chains from Scenario-Based Requirements Specifications}}}, doi = {{10.1007/978-3-319-09970-5_14}}, year = {{2014}}, } @misc{20985, abstract = {{Die in der Automobilindustrie verwendeten eingebetteten Systeme gehören zu den komplexesten eingebetteten Systemen. Die Automobilhersteller sind in der Entwicklung ständig bemüht sowohl die Sicherheit und den Komfort des Fahrers also auch der anderen Insassen zu verbessern. Die meisten der entwickelten Systeme sind sowohl zeit- als auch sicherheitskritisch. Einer Studie von Mercedes-Benz zufolge resultieren 80% der Innovationen in der Automobilbranche aus neuen Elektronikkomponenten, deren Funktionen zu 90% durch Software realisiert wird. Um die steigende Komplexität in der Entwicklung von eingebetteten Systemen zu beherrschen wird in der Automobilbranche immer öfter die modelbasierte Softwareentwicklung anstelle der klassischen Programmierung eingesetzt. Im Requirements Engineering, der ersten Phase der Entwicklung eines Produktes, werden die Anforderungen gesammelt und dokumentiert. Die Dokumentation erfolgt mittels natürlicher Sprache. Modellbasierte Ansätze werden heutzutage höchstens unterstützend eingesetzt. Während des Requirements Engineerings muss der Requirements Engineer sowohl die funktionalen Anforderungen an das zu entwickelnde System als auch seine zeitlichen Anforderungen spezifizieren und analysieren. Die funktionalen Anforderungen umfassen dabei insbesondere die Kommunikation zwischen den verschiedenen Teilsystemen. Szenarien stellen eine intuitive Möglichkeit zur Modellierung von funktionalen Anforderungen dar. Im Rahmen dieser Arbeit wird ein modellbasierter Ansatz zur Modellierung von Szenarien verwendet. Anforderungen an das zeitliche Verhalten werden innerhalb der Architektur spezifiziert. Dazu stehen in der Automobilbranche Architekturbeschreibungssprachen wie EAST-ADL zur Verfügung. Obwohl sowohl funktionale als auch zeitliche Anforderungen an das System spezifiziert und analysiert werden müssen, existiert bisher keine Methodik, die beide Ansätze miteinander kombiniert. Aus diesem Grund wurde im Rahmen dieser Arbeit eine neue Requirements Engineering Methodik entwickelt, die eine systematische und ganzheitliche Spezifikation und Analyse der funktionalen und zeitlichen Anforderungen bereitstellt. Wir haben zwei Modelltransformationen entwickelt, um den Requirements Engineer beim Übergang von den funktionalen zu den zeitlichen Anforderungen zu unterstützen. Die vorliegende Arbeit wird durch eine Evaluierung der Methodik, sowie der Modelltransformationen auf Basis eines Komfortsteuergerätes abgerundet. }}, author = {{Koch, Thorsten}}, publisher = {{University of Paderborn}}, title = {{{Combining Scenario-based and Architecture-based Timing Requirements}}}, year = {{2013}}, }