A Meta-model for Tests of Avionics Embedded Systems

Testing embedded software systems on the control units of vehicles is a safety-relevant task, and developing the test suites for performing the tests on test benches is time-consuming. We present the foundations and results of a case study to automate the generation of tests for control software of vehicle control units based on a specification of requirements in terms of finite state machines. This case study builds upon our previous work on generation of tests for physical systems based on relational behavior models. In order to apply the respective algorithms, the finite state machine representation is transformed into a relational model. We present the transformation, the application of the test generation algorithm to a real example, and discuss the results and some specific challenges regarding software testing.

2012

The world of in-the-loop testing of avionic embedded systems is heterogeneous, consisting mostly of in-house test languages. A synthetic view of the different features possessed by these languages was deemed necessary, in order to allow reflections towards some homogenization. We considered a sample of six languages. Four of them 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. We begin with the presentation of the specificities of the in-theloop testing activity and the related needs for test languages. Afterwards, we discuss the different test languages in our sample, focusing on the features that they possess and how they fulfill the needs. We end the article with a proposal for a model-driven solution, homogenizing the different industrial test practices into domain-specific models from which test code is generated.

Lecture Notes in Computer Science, 2007

Deployment of model-based testing involves many difficulties that have slowed down its industrial adoption. The leap from traditional scripted testing to model-based testing seems as hard as moving from manual to automatic test execution. Two key factors in the deployment are the language used to define the test models, and the language used for defining the test objectives. Based on our experience, we survey the different types of languages and sketch solutions based on different approaches, considering the testing organization, the system under test, etc. The types of languages we cover include among others domain-specific, test-specific as well as generic design languages. We note that there are no best practices, but provide general guidelines for various cases.

2011 IEEE 34th Software Engineering Workshop, 2011

We have applied Fastest, an implementation of the Test Template Framework, to five real case studies of aerospace software. This involved the formalization in the Z notation of nontrivial parts of each system. One of these models, for instance, formalizes a significant portion of the ECSS-E-70-41A aerospace standard. The models were then fed into Fastest, which automatically generated detailed functional abstract test cases. Since these test cases are independent of any implementation, they can be used to test any of them. Furthermore, we were able to semi-automatically translate them into English so they can be used by domain experts performing independent validation and verification activities.

2009 Third International Conference on Research Challenges in Information Science, 2009

The test phase is one of the most important phases in software development. However, in practice, little research has been carried out in this field. Model-Driven Engineering is a new paradigm that can help to minimize test cases generation costs and can ensure quality of results. This paper presents the application of the MDE paradigm in the systematic, even automatic, generation of System Test Software.

2010

This paper presents MATERA, a framework that integrates modeling in the Unified Modeling Language (UML), with requirement traceability across a model-based testing (MBT) process. The Graphical User Interface (GUI) of MAT-ERA is implemented as a plug-in in the NoMagic's MagicDraw modeling tool, combining existing capabilities of MagicDraw with custom ones. MATERA supports graphical specification of the requirements using SysML and tracing of them to the UML models specifying the SUT. Model validation is performed in MagicDraw using both predefined and custom validation rules. The resulting models are automatically transformed into input for the Conformiq Qtronic tool, used for automated test generation. Upon executing the test scripts generated by Qtronic in the NetHawk's East execution environment, the results of statistic analysis of the test run are presented in the GUI. The back-traceability of the covered requirements from test to models is also provided in the GUI to facilitate the identification of the source of possible errors in the models. The approach we present shows that existing model-based languages and tools are an enabler for model-based testing and for providing integrated tool support across the MBT process.

Proceedings of the 7th International Workshop on Model-Based Methodologies for Pervasive and Embedded Software - MOMPES '10, 2010

The scope of Model-Driven Engineering is not limited to Model-Based Development (MBD), i.e. the generation of code from system models, but involves also Model-Based Testing (MBT), which is the automatic generation of efficient test procedures from corresponding test models. Both MBD and MBT include activities such as model creation, model checking, and use of model compilers for the generation of system/test code. By reusing these common activities, the efficiency of MBT can be significantly improved for those organizations which have already adopted MBD, since one of the major efforts in MBT is the creation of test models. In this work, we propose to exploit modeling activity efforts by deriving test models from system models. In this respect, we present a case study in which the Executable and Translatable UML system models are used for automatically generating test models in the QTronic Modeling Language using horizontal model transformations. In turn, the derived artefacts can be used to produce test cases which result to be appropriate for the system under development.

2006

Abstract: The approach towards system engineering compliant to Model-Driven Architecture (MDA) implies an increased need for research on the automation of the model-based test generation. This applies especially to embedded real-time system development where ...

Lecture Notes in Computer Science, 2003

This paper discusses a model-based approach to testing as a vital part of software development. It argues that an approach using models as central development artifact needs to be added to the portfolio of software engineering techniques, to further increase efficiency and flexibility of the development as well as quality and reusability of results. Then test case modeling is examined in depth and related to an evolutionary approach to model transformation. A number of test patterns is proposed that have proven helpful to the design of testable object-oriented systems. In contrast to other approaches, this approach uses explicit models for test cases instead of trying to derive (many) test cases from a single model. Software has become a vital, but often invisible part of our lives. Embedded forms of software are part of almost any technical device. The average household uses several computers, and the internet and telecommunication world has considerably changed our lives. Software is used for a variety of jobs. It can be as small as a simple script or as complex as an entire operating or enterprise resource planning system.

Gateway to the New Millennium. 18th Digital Avionics Systems Conference. Proceedings (Cat. No.99CH37033), 1999

Traditional approaches to unit testing involve establishing test vectors from the source code and establishing expected results that can be used to determine if a particular case has been addressed. This approach is time consuming and expensive. The availability of Computer Aided Control System Design (CACSD) tools for software modeling has permitted expected values to be automatically established from an executable specification. Further automation and implementation independence can be achieved by generating test vectors directly from the executable specification. A model driven automatic unit testing tool architecture and specification has been established. This paper discusses the architecture and requirements of such a tool. Topics include control coverage, data flow coverage, domain coverage, path sensitizing and test management.