@inproceedings{21326, author = {{Holtmann, Jörg and Steghöfer, Jan-Phillipp and Rath, Michael and Schmelter, David}}, booktitle = {{Software Engineering 2021}}, editor = {{Koziolek, Anne and Schaefer, Ina and Seidl, Christoph}}, location = {{Remote / Braunschweig, Germany }}, pages = {{59--60}}, title = {{{Cutting through the Jungle: Disambiguating Model-based Traceability Terminology (Extended Abstract)}}}, doi = {{10.18420/SE2021_18}}, volume = {{P-310}}, year = {{2021}}, } @inproceedings{29715, author = {{Steghofer, Jan-Philipp and Koopmann, Bjorn and Steffen Becker, Jan and Stierand, Ingo and Zeller, Marc and Bonner, Maria and Schmelter, David and Maro, Salome}}, booktitle = {{2021 IEEE 29th International Requirements Engineering Conference (RE)}}, publisher = {{IEEE}}, title = {{{The MobSTr Dataset – An Exemplar for Traceability and Model-based Safety Assessment}}}, doi = {{10.1109/re51729.2021.00062}}, year = {{2021}}, } @inproceedings{20516, abstract = {{Traceability, a classic requirements engineering topic, is increasingly used in the context of model-based engineering. However, researchers and practitioners lack a concise terminology to discuss aspects of requirements traceability in situations in which engineers heavily rely on models and model-based engineering. While others have previously surveyed the domain, no one has so far provided a clear, unambiguous set of terms that can be used to discuss traceability in such a context. We therefore set out to cut a path through the jungle of terminology for model-based traceability, ground it in established terminology from requirements engineering, and derive an unambiguous set of relevant terms. We also map the terminology used in existing primary and secondary studies to our taxonomy to show differences and commonalities. The contribution of this paper is thus a terminology for model-based traceability that allows requirements engineers and engineers working with models to unambiguously discuss their joint traceability efforts.}}, author = {{Holtmann, Jörg and Steghofer, Jan-Philipp and Rath, Michael and Schmelter, David}}, booktitle = {{2020 IEEE 28th International Requirements Engineering Conference (RE)}}, isbn = {{9781728174389}}, publisher = {{IEEE}}, title = {{{Cutting through the Jungle: Disambiguating Model-based Traceability Terminology}}}, doi = {{10.1109/re48521.2020.00014}}, year = {{2020}}, } @inproceedings{20757, author = {{Fazal-Baqaie, Masud and Strüwer, Jan-Niclas and Schmelter, David and Dziwok, Stefan}}, booktitle = {{Projektmanagement und Vorgehensmodelle 2019 (PVM 2019)}}, editor = {{Mikusz, Martin}}, publisher = {{Lecture Notes in Informatics (LNI)}}, title = {{{Coaching on the Job bei Unternehmen des Maschinen- und Anlagenbaus - Wissenslücken schließen zur Weiterpflege modernisierter IT-Anwendungen}}}, year = {{2019}}, } @inproceedings{20785, abstract = {{Cyber-physical Systems are distributed, embedded systems that interact with their physical environment. Typically, these systems consist of several Electronic Control Units using multiple processing cores for the execution. Many systems are applied in safety-critical contexts and have to fulfill hard real-time requirements. The model-driven engineering paradigm enables system developers to consider all requirements in a systematical manner. In the software design phase, they prove the fulfillment of the requirements using model checking. When deploying the software to the executing platform, one important task is to ensure that the runtime scheduling does not violate the verified requirements by neglecting the model checking assumptions. Current model-driven approaches do not consider the problem of deriving feasible execution schedules for embedded multi-core platforms respecting hard real-time requirements. This paper extends the previous work on providing an approach for a semi-automatic synthesis of behavioral models into a deterministic real-time scheduling. We add an approach for the partitioning and mapping development tasks. This extended approach enables the utilization of parallel resources within a single ECU considering the verification assumptions by extending the open tool platform App4mc. We evaluate our approach using an example of a distributed automotive system with hard real-time requirements specified with the MechatronicUML method. }}, author = {{Geismann, Johannes and Höttger, Robert and Krawczyk, Lukas and Pohlmann, Uwe and Schmelter, David}}, booktitle = {{Model-Driven Engineering and Software Development}}, editor = {{Pires, Luís Ferreira and Hammoudi, Slimane and Selic, Bran}}, pages = {{72--93}}, publisher = {{Springer International Publishing}}, title = {{{Automated Synthesis of a Real-Time Scheduling for Cyber-Physical Multi-core Systems}}}, doi = {{10.1007/978-3-319-94764-8_4}}, volume = {{1}}, 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}}, } @article{20787, author = {{Wohlers, Benedict and Dziwok, Stefan and Schmelter, David and Lorenz, Wadim}}, journal = {{Advances in Manufacturing, Production Management and Process Control - AHFE 2018}}, pages = {{398--410}}, title = {{{Improving Quality Control of Mechatronic Systems Using KPI-Based Statistical Process Control}}}, year = {{2018}}, } @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}}, } @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{20795, abstract = {{Distributed, software-intensive systems such as fully automated cars 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, particularly w.r.t. the realizability of the specifications. Scenario-based requirements engineering addresses the message-based coordination of such systems and enables, if underpinned with formal languages, automatic requirements validation techniques for proving the realizability of a requirements specification. However, formal requirements modeling languages require a deep knowledge of requirements engineers and typically require many manual iterations until they find a realizable specification. In order to support requirements engineers in the stepwise development of scenario-based requirements specifications, we propose to evolve a high-quality specification from a (presumably unrealizable) manually created specification employing an evolutionary algorithm. In this paper, we show our results on automatically evolving new assumptions on the systems’ environment behavior that guarantee a realizable requirements specification. Based on this contribution, we outline our research roadmap toward our long-term goal of automatically supporting requirements engineers in finding high-quality requirements specifications.}}, author = {{Schmelter, David and Greenyer, Joel and Holtmann, Jörg}}, booktitle = {{4th International Workshop on Artificial Intelligence for Requirements Engineering (AIRE)}}, publisher = {{IEEE}}, title = {{{Toward Learning Realizable Scenario-based, Formal Requirements Specifications}}}, doi = {{10.1109/REW.2017.14}}, year = {{2017}}, } @inproceedings{20796, author = {{Wohlers, Benedict and Dziwok, Stefan and Bremer, Christian and Schmelter, David and Lorenz, Wadim}}, booktitle = {{Proceedings of the 24th International Conference on Production Research (ICPR)}}, publisher = {{DEStech Publications, Inc.}}, title = {{{Improving the Product Control of Mechatronic Systems Using Key Performance Indicators}}}, 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}}, } @inproceedings{20804, abstract = {{Modern Cyber-physical Systems are executed in physical environments and distributed over several Electronic Control Units using multiple cores for execution. These systems perform safety-critical tasks and, therefore, have to fulfill hard real-time requirements. To face these requirements systematically, system engineers de- velop these systems model-driven and prove the fulfillment of these requirements via model checking. It is important to ensure that the runtime scheduling does not violate the verified requirements by neglecting the model checking assumptions. Currently, there is a gap in the process for model-driven approaches to derive a feasible runtime scheduling that respects these assumptions. In this paper, we present an approach for a semi- automatic synthesis of behavioral models into a deterministic scheduling that respects real-time requirements at runtime. We evaluate our approach using an example of a distributed automotive system with hard real-time requirements specified with the MechatronicUML method.}}, author = {{Geismann, Johannes and Pohlmann, Uwe and Schmelter, David}}, booktitle = {{Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development}}, title = {{{Towards an Automated Synthesis of a Real-time Scheduling for Cyber-physical Multi-core Systems}}}, 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}}, } @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}}, } @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}}, } @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{20957, abstract = {{In this paper, we report on a new approach of aspect-oriented modelling, which is particularly suited for domains with naturally born aspects as part of that domain: MoDowA for Modelling Domains with Aspects. Though these models are on a very high level of abstraction and could be made early in the development process, these models are fully operational in that they can be executed by an interpreter. This way, we shed a light on Aspect-oriented Modelling from a new, different angle.}}, author = {{Kindler, Ekkart and Schmelter, David}}, booktitle = {{Proceedings of the 2008 AOSD workshop on Aspect-oriented modeling - AOM '08}}, isbn = {{9781605581453}}, title = {{{Aspect-oriented modelling from a different angle}}}, doi = {{10.1145/1404920.1404922}}, year = {{2008}}, }