Analysis and Improvement of Model Architectures for Safety Related Systems

Doerr, Heiko; Bachmann, Ferry

doi:10.4271/2018-01-1077

Cited by 2 publications

(5 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…"agree" "strongly agree" "disagree" "strongly disagree" "don't know" find reference to it in the literature (Doerr & Bachmann 2018). Perhaps, a rewritten hypothesis with more information, such as thus, diminishing testing efforts would have had a higher agreement rate.…”

Section: Hypotheses With High Disagreement Ratementioning

confidence: 99%

“…From prior literature suggestions (Doerr & Bachmann 2018;Eessaar & Käosaar 2019;Gerlitz et al 2015), we derived hypotheses on possible refactorings of problematic buses to further answer RQ4. For instance, hypothesis H22, which states that a bus should be made up of at least two elementary signals, was developed from the "superfluous bus signal" smell from Gerlitz et al (Gerlitz et al 2015).…”

Section: Literature Guidelinesmentioning

confidence: 99%

“…Buses should not be used when testing models; signals should be used instead. Doerr et al mentions that, in testing, all signals of a bus will be created, even when they are not used elsewhere (Doerr & Bachmann 2018). This superfluous signal creation adds to the cognitive load of the tester.…”

Section: Rq3 When Should Bus Usage Be Avoided?mentioning

confidence: 99%

“…It is also easier to discern which signals of a bus are used (Doerr & Bachmann 2018), or more concretely "to show on which signals the sub-model really relies on" (P10). Participants do not use buses "if [they] want to model very clearly how submodules interact with each other (through which signals)" (P6), and "don't often remove buses, but if it benefits understanding at the higher level, [they] can select signals from the bus and route as scalars into the subsystems" (P18).…”

Section: Rq3 When Should Bus Usage Be Avoided?mentioning

confidence: 99%

“…The hypotheses in this section were developed either from analyzing publicly available Simulink models or from suggested refactorings of (Eessaar & Käosaar 2019) and (Doerr & Bachmann 2018).…”

Section: Rq4 What Are Best Practices For Bus Sizes?mentioning

confidence: 99%

See 4 more Smart Citations

Simulink bus usage in practice: an empirical study.

Amorim¹,

Boll²,

Bachman³

et al. 2023

JOT

View full text Add to dashboard Cite

Matlab/Simulink is a graphical modeling environment that has become the de facto standard for the industrial model-based development of embedded systems. Practitioners employ different structuring mechanisms to manage Simulink models' growing size and complexity. One important architectural element is the so-called bus, which can combine multiple signals into composite ones, thus, reducing a model's visual complexity. However, when and how to effectively use buses is a non-trivial design problem with several trade-offs. To date, only little guidance exists, often applied in an ad-hoc and subjective manner, leading to suboptimal designs. Using an inductive-deductive research approach, we conducted an exploratory survey among Simulink practitioners and extracted bus usage information from a corpus comprising 433 open-source Simulink models.We elicited 22 hypotheses on bus usage advantages, disadvantages, and best practices from the data, whose validity was later tested through a confirmatory survey. Our findings serve as requirements for static analysis tools and pave the way toward guidelines on bus usage in Simulink.

show abstract

Section: Hypotheses With High Disagreement Ratementioning

confidence: 99%

Section: Literature Guidelinesmentioning

confidence: 99%

Section: Rq3 When Should Bus Usage Be Avoided?mentioning

confidence: 99%

Section: Rq3 When Should Bus Usage Be Avoided?mentioning

confidence: 99%

Section: Rq4 What Are Best Practices For Bus Sizes?mentioning

confidence: 99%

See 3 more Smart Citations

Simulink bus usage in practice: an empirical study.

Amorim¹,

Boll²,

Bachman³

et al. 2023

JOT

View full text Add to dashboard Cite

show abstract

Devising Guidelines and Architecture for Efficient Auto-Generation of HIS Compliant Code

Abraham

2024

SAE Technical Paper Series

View full text Add to dashboard Cite

<div class="section abstract"><div class="htmlview paragraph">Ensuring compliance with the ISO 26262 automotive functional safety standard involves meeting specific quality and complexity standards for automotive source code. However, achieving compliance becomes challenging when dealing with auto-generated code, as the code generator may not consider the required product metrics. This often leads to high metric values that exceed the permissible range. Assessing the impact of design on Hersteller Initiative Software (HIS) metrics within the visual modeling environment becomes difficult, with metrics reports only available after code generation. This makes it hard to achieve compliance through model reworking and regeneration. To address this problem, a methodology is proposed. It defines modeling guidelines and an architecture for generating HIS-compliant code. The HIS metrics are translated into corresponding model implementations, such as mapping the “Number of Function Parameters” metric to the number of subsystem ports and the guideline recommends dividing the logic into subsystems with fewer than five ports to meet the allowable range. The aim is to establish similar modeling guidelines for each attribute and create a balanced skeletal architecture diagram that ensures compliance with HIS metrics. To demonstrate the effectiveness of the proposed guidelines, two models calculating steering motor torque are compared—one designed with the guidelines and one without. By separating decision points into distinct functions, the proposed approach reduces cyclomatic complexity, with all other HIS metrics expected to fall within the acceptable range. Adhering to the guidelines enables auto-generated code to meet HIS metrics, facilitating more efficient automotive software design.</div></div>

show abstract

Analysis and Improvement of Model Architectures for Safety Related Systems

Cited by 2 publications

References 4 publications

Simulink bus usage in practice: an empirical study.

Simulink bus usage in practice: an empirical study.

Devising Guidelines and Architecture for Efficient Auto-Generation of HIS Compliant Code

Contact Info

Product

Resources

About