The MobSTr dataset contains a number of artifacts for an autonomous driver assistance system, ranging from textual requirements to models for system design and models relevant to safety assurance. The artifacts provided are connected with traceability links created and managed with Eclipse Capra, an open source traceability management tool. The dataset builds upon a custom traceability information model that provides type safety and semantics for the trace links. MobSTr is intended for researchers that work on software and systems traceability as well as on model-based safety assurance. It is already being used in a number of studies, including research on trace link consistency, change impact analysis, and automated analysis of safety and timing requirements.

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.

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.

S.285-292

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, for example, into specific requirements for the embedded software. Because 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. Copyright © 2016 John Wiley & Sons, Ltd.

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.