Search

International audience; —The development of real-time embedded systems is quite complex because of the wide range of execution platforms and of the importance of non-functional requirements. Further-more, Model Driven Engineering is particularly suitable for han-dling the diversity of implementation targets. Therefore, several real-time embedded systems development suites leverage Model Driven Engineering by automatically generating platform-specific code from high-level design models. Such tools may also take non-functional requirements into account by integrating verification activities. These activities typically rely on the generation of formal models from the same high-level design descriptions used for code generation. However, few tool suites support both code and formal model generation. Furthermore, among these, most overlook real-time operating systems mechanisms. Therefore, both code and formal models generated by these tool suites may not behave as specified in the high-level design descriptions. The present work extends the SExPIsTools code generator tool suite with a support for the generation of formal models. The proposed strategy relies on the composition of formal model fragments described using an extension of the classical Time Petri Nets. This paper presents a formalization of this composition that generically considers the behavior of platforms. As an illustration, we then give the formal model describing the behavior of an application on two different platforms (OSEK/VDX and VxWorks) and check a safety property on both models.

International audience; Faced with the growing problems of complexity, heterogeneity and upgradability of Real-Time Embedded Systems (RTESs), model-based frameworks dedicated to the application deployments facilitate the design and the development of such systems. Within these frameworks, taking into account the Real-Time Operating Systems (RTOSs) has become essential. These frameworks include transformation tools able to generate a code that is portable to the specified RTOS. Moreover, certain tools can generate formal models that are used for the verification and validation of the RTESs. However, the RTOSs technological concepts are considered in an implicit way, which involves a lack of genericity of the transformations. Some works have focused on the explicit description of the RTOSs. Such a description offers the possibility to take into account a model entirely dedicated to a targeted RTOS as a parameter of the transformation. Nevertheless, this method does not allow to verify the expected properties on the application, since the RTOSs behavior is not observable. The methodology presented in this paper tends to explicitly consider the formal description of the RTOSs behavior during an application deployment. This approach aims both at making each transformation generic and at verifying the deployment correctness.