Testing Embedded Real Time Systems with TTCN-3

Grossmann, Juergen; Serbanescu, Diana Alina; Schieferdecker, Ina

doi:10.1109/icst.2009.37

Cited by 14 publications

(3 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In general, we distinguish between the four verdicts Passed (v 1 ), Probably Passed (v 2 ), Inconclusive (v 3 ) and Failed (v 4 ). The test verdicts Passed, Inconclusive and Failed are based on TTCN-3's verdict set [8], extended by the new test verdict Probably Passed. We justify the extension of the classical verdict set to signal the existence of aspects which cannot be evaluated due to the abstract nature of this approach.…”

Section: Results To Verdict Mappingmentioning

confidence: 99%

Abstract Test Execution for Early Testing Activities in Model-Driven Scenarios

Pröll

Hagemann

Bauer

2021

Communications in Computer and Information Science

View full text Add to dashboard Cite

The continuous improvement of the performance of computing units makes it possible to cope with increasingly complex tasks. This results in more complex software systems. However, the development of such highly complex systems is difficult to achieve using traditional approaches. Concepts like model-driven software development can weaken this problem in these constructive phases. However, new challenges arise for the testing of development artifacts. In order to be able to perform a real shift left of verification and validation tasks towards early phases of development, we present a semi-formal approach that enables users to execute test cases against the system under development (SUD) on the model-level. Grounded on an Integrated Model Basis which is created and maintained during development, test reports are automatically derived. This opens up a wide range of possibilities for early and targeted troubleshooting.

show abstract

Section: Results To Verdict Mappingmentioning

confidence: 99%

Abstract Test Execution for Early Testing Activities in Model-Driven Scenarios

Pröll

Hagemann

Bauer

2021

Communications in Computer and Information Science

View full text Add to dashboard Cite

show abstract

“…Finally, the results captured during the joint analysis of an abstract test case and a system model path are categorized as one of the four test verdicts to determine the quality-level of the afflicted model artifacts. Three of those verdicts are based on the test verdict set introduced by TTCN-3 (Grossmann et al, 2009). A fourth test verdict is made up to state the abstract computability of a test case (see Section 3.3).…”

Section: The Abstract Test Execution Conceptmentioning

confidence: 99%

Towards Abstract Test Execution in Early Stages of Model-driven Software Development

Hagemann

Pröll

Bauer

2020

Proceedings of the 8th International Conference on Model-Driven Engineering and Software Development

View full text Add to dashboard Cite

Over the last decades, systems immanent complexity has significantly increased. In order to cope with the emerging challenges during the development of such systems, modeling approaches become an indispensable part. While many process steps are applicable to the model-level, there are no sufficient realizations for test execution yet. As a result, we present a semi-formal approach enabling developers to perform abstract test execution straight on the modeled artifacts to support the overarching objective of a shift left of verification and validation tasks. Our concept challenges an abstract test case (derived from test model) against a system model utilizing an integrated set of domain-specific models, i.e. the omni model. Driven by an optimistic dataflow analysis based on a combined view of an abstract test case and its triggered system behavior, possible test verdicts are assigned. Based on a prototypical implementation of the concept, the proof of concept is demonstrated and further on put in the context of related research.

show abstract

“…It addresses functional issues of distributed systems and merely offers basic timer operations using the local clock of components. Note that real-time extensions have been proposed [12,13], with a time stamping of communication events and a timed control of events, although they are not yet part of the standard.…”

Section: Time Managementmentioning

confidence: 99%

Test Languages for In-the-Loop Avionics Tests

Guduvan

Waeselynck

Wiels³

et al. 2015

Journal of Aerospace Information Systems

View full text Add to dashboard Cite

The current state of the art of in-the-loop testing of avionics embedded systems is very heterogeneous, with many different in-house test languages, and it is unable to respond to the evolving needs of the stakeholders in this field. To lay the foundations of more homogeneous test development solutions, this paper offers an overview and analysis of the features of six different test languages. Best practices and pitfalls to avoid are discussed. The analysis focuses on four major categories of features: test organization, abstraction of and access to the system under test interfaces, test language instructions, and time management. Four of the test languages in the sample set are currently employed in the field of avionics. The other two, used, respectively, in the automotive and telecommunications industries, have been chosen for comparison purposes. The paper reports the key findings of the analysis and presents the resulting ongoing research work.

show abstract

Testing Embedded Real Time Systems with TTCN-3

Cited by 14 publications

References 8 publications

Abstract Test Execution for Early Testing Activities in Model-Driven Scenarios

Abstract Test Execution for Early Testing Activities in Model-Driven Scenarios

Towards Abstract Test Execution in Early Stages of Model-driven Software Development

Test Languages for In-the-Loop Avionics Tests

Contact Info

Product

Resources

About