Linking Unit Tests and Properties

QuickCheck allows us to verify software against particular proper- ties. A property can be regarded as an abstraction over many unit tests. QuickCheck uses generated random input data to test such properties. If a counterexample is found, it becomes immediately clear what we have tested. This is not the case when all tests pass, since we do not (and shall not) see the actual generated test cases. How can we be sure about what is tested? QuickCheck has the ability to gather statistics about the test cases, which is insightful. But still it does not tell us whether the particular unit test scenarios we have in mind are included. For this reason, we have developed a tool that can answer this question. It checks if a given unit test can be generated by a property, making it easier to judge the property’s quality. We have applied our tool to an industrial use case of testing the AUTOSAR basic software modules and shows that it can handle complex models and large unit tests

AUTOSAR and SysML – A Natural Fit?

International audienceThis paper should give some ideas on how the UML 2 and the SysML can help defining the different AUTOSAR artifacts and later applying the specified AUTOSAR part to real implementations. The AUTOSAR definitions are currently being defined on top of the UML 2.0. In parallel, the OMG started in 2003 a Request for Proposal to define a UML-based visual modeling language for Systems Engineering. This SysML is also an addition to the UML 2.0, so comparing the aims and ideas from AUTOSAR and from SysML is an obvious idea. This paper will show that using the AUTOSAR concepts for automotive modeling and adding SysML concepts will lead to complete picture of the automotive domain

Model-Based Design for AUTOSAR Software Components

International audienceThe AUTOSAR initiative is without doubt one of the most forward-looking and important developments in the automotive industry. Tool support is essential for efficient software development according to AUTOSAR, particularly for developing the actual application software in the form of AUTOSAR software components. This paper deals with the adaptation of model-based design and automatic production code generation techniques to the proposed AUTOSAR workflow. It shows that existing approaches are well suited for the development of AUTOSAR software, preserving all the advantages of model-based design such as early testability, precise specifications, and last but not least, automatic production code generation