Learn More
Model-based testing relies on behavior models for the generation of model traces: input and expected output---test cases---for an implementation. We use the case study of an automotive network controller to assess different test suites in terms of error detection, model coverage, and implementation coverage. Some of these suites were generated automatically(More)
The idea of model-based testing is to compare the I/O behavior of an explicit behavior model with that of a system under test. This requires the model to be valid. If the model is a simplification of the SUT, then it is easier to check the model and use it for subsequent test case generation than to directly check the SUT. In this case, the different levels(More)
For behavior models expressed in statechart-like formalisms, we show how to compute semantically equivalent yet structurally different models. These refactorings are defined by user-provided logical predicates that partition the system’s state space and that characterize coherent parts – modes or control states–of the behavior. We embed the refactorings(More)
The construction of reliable (embedded) software can be significantly improved using explicit model-based tool-supported development process. Research results suggest that such a process can contribute essentially to increase the quality of the developed product as well as to better efficiency of the development itself: • [Jon91] shows that more than 50 %(More)
Capturing the system requirements and integrating them into a well balanced system architecture is a key issue in the development of reactive software systems. In this report, we explore by means of a case study how an architecture can be derived systematically for systems whose communication model is based on broadcasting. We are especially interested in(More)