Model Based Requirements Analysis and Testing of Automotive Systems with Timed Usage Models

Siegl, Sebastian; Hielscher, Kai-Steffen; German, Reinhard

doi:10.1109/re.2010.49

Cited by 18 publications

(9 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This pattern is expected for model transformations, e.g. as in Case F [Nebut et al 2006] (use case transitions system → test objectives) or Case L [Siegl et al 2010] (time usage model → test cases). It also shows that transformation links from early RE phases to ST are not common.…”

Section: Summary Analysismentioning

confidence: 90%

“…We have applied the taxonomy, in total, on 13 alignment methods. In the remainder of this paper they are referenced as cases A-M: A [Güldali et al 2011], B [Flammini et al 2009 [Siegl et al 2010], and M [Metsa et al 2007].…”

Section: Methods Classificationmentioning

confidence: 99%

“…requirements, increases also the complexity of the software solution [Glass 2002], making therefore the testing more involved. Benefits of a strengthened link between RE and ST are, for example, improved product quality [Uusitalo et al 2008], cost-effective testing [Miller and Strooper 2010;Flammini et al 2009], high quality test-cases [de Santiago Júnior and Vijaykumar 2012], and early discovery of incomplete requirements [Siegl et al 2010].…”

Section: The Need For Alignmentmentioning

confidence: 99%

See 2 more Smart Citations

A taxonomy for requirements engineering and software test alignment

Unterkalmsteiner

Feldt

Gorschek

2014

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Requirements Engineering and Software Testing are mature areas and have seen a lot of research. Nevertheless, their interactions have been sparsely explored beyond the concept of traceability. To fill this gap we propose a definition of requirements engineering and software test (REST) alignment, a taxonomy that characterizes the methods linking the respective areas, and a process to assess alignment. The taxonomy can support researchers to identify new opportunities for investigation, as well as practitioners to compare alignment methods and evaluate alignment, or lack thereof. We constructed the REST taxonomy by analyzing alignment methods published in literature, iteratively validating the emerging dimensions. The resulting concept of an information dyad characterizes the exchange of information required for any alignment to take place. We demonstrate use of the taxonomy by applying it on five in-depth cases and illustrate angles of analysis on a set of thirteen alignment methods. In addition we developed an assessment framework (REST-bench), applied it in an industrial assessment, and showed that it, with a low effort, can identify opportunities to improve REST alignment. Although we expect that the taxonomy can be further refined, we believe that the information dyad is a valid and useful construct to understand alignment.

show abstract

Section: Summary Analysismentioning

confidence: 90%

Section: Methods Classificationmentioning

confidence: 99%

Section: The Need For Alignmentmentioning

confidence: 99%

See 1 more Smart Citation

A taxonomy for requirements engineering and software test alignment

Unterkalmsteiner

Feldt

Gorschek

2014

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…This allows for formal verification of the requirements that can guarantee that the implementation conform to specification [38]. This is of great importance in safety critical domains, such as the automotive industry, that must meet safety standards [39]. Improved traceability: Traceability is important to understand the impact of change during the development [40].…”

Section: Focus Of Research (Rq2)mentioning

confidence: 99%

What Do We Know about Alignment of Requirements Engineering and Software Testing?

Karhapää

Haghighatkhah

Oivo

2017

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering

View full text Add to dashboard Cite

Context:The alignment of different software engineering activities for coordinated functioning and optimized product development is of great importance, particularly in industrialscale development. The link between intermediate activities has been researched extensively, but the link between requirements engineering (RE) and software testing (ST) is a relatively less explored area. Objective: The objective of this study is to aggregate, structure, and classify all existing research regarding alignment of RE and ST published by the end of 2015. Method: We conducted a systematic mapping study (SMS) and aggregated all studies relevant to our scope. The primary studies are analyzed in terms of publication trend, focus area, i.e., how alignment is supported, the application domain and benefits and challenges, methodological data, and scientific rigor and industrial relevance. Results: There is a growing interest towards the topic. Several different techniques have been identified to improve RE and ST alignment. Test generation from requirements specification has received most attention. Alignment of RE and ST is particularly important for large safety-critical domains. While many challenges have been reported, the supporting evidence for benefits is scarce. Frameworks/methods/techniques is the most frequent contribution type. Solution proposal and evaluation research were the most frequently applied research type. Case study research was the most frequently applied research method, however, almost half of the studies did not clearly report any research method. Conclusion: Despite the numerous approaches that are proposed, it is not clear what approach is suitable in what context and why. To support industry in RE and ST alignment, guidelines and tool support are needed. The supporting evidence for claimed benefits is very limited. Overall, the research area is in its early stages and an increase in both the number and rigor of empirical studies are required.

show abstract

“…This tester receives the software in a binary form with the ECU in order to protect the corporate intellectual property (IP) rights, whereupon they perform black-box testing of each supplier's ECU and send the test results back to each relevant developer. Finally, each developer performs debugging based on these test results [5]. Unfortunately, there is relatively little information that is exchangeable between the OEM company and supplier companies because development and testing are performed in independent environments.…”

Section: Introductionmentioning

confidence: 99%

Fault Localization Method by Partitioning Memory Using Memory Map and the Stack for Automotive ECU Software Testing

2016

View full text Add to dashboard Cite

Abstract:Recently, the usage of the automotive Electronic Control Unit (ECU) and its software in cars is increasing. Therefore, as the functional complexity of such software increases, so does the likelihood of software-related faults. Therefore, it is important to ensure the reliability of ECU software in order to ensure automobile safety. For this reason, systematic testing methods are required that can guarantee software quality. However, it is difficult to locate a fault during testing with the current ECU development system because a tester performs the black-box testing using a Hardware-in-the-Loop (HiL) simulator. Consequently, developers consume a large amount of money and time for debugging because they perform debugging without any information about the location of the fault. In this paper, we propose a method for localizing the fault utilizing memory information during black-box testing. This is likely to be of use to developers who debug automotive software. In order to observe whether symbols stored in the memory have been updated, the memory is partitioned by a memory map and the stack, thus the fault candidate region is reduced. A memory map method has the advantage of being able to finely partition the memory, and the stack method can partition the memory without a memory map. We validated these methods by applying these to HiL testing of the ECU for a body control system. The preliminary results indicate that a memory map and the stack reduce the possible fault locations to 22% and 19% of the updated memory, respectively.

show abstract

Model Based Requirements Analysis and Testing of Automotive Systems with Timed Usage Models

Cited by 18 publications

References 6 publications

A taxonomy for requirements engineering and software test alignment

A taxonomy for requirements engineering and software test alignment

What Do We Know about Alignment of Requirements Engineering and Software Testing?

Fault Localization Method by Partitioning Memory Using Memory Map and the Stack for Automotive ECU Software Testing

Contact Info

Product

Resources

About