Simulink Interface Concepts
In Model-based Development and Embedded Software Engineering, the growing complexity requires concepts like modularization, ease of maintenance, or module reusability. In this context it is crucial to understand the interface in Simulink, which is defined by the data flow into and out of a subsystem. This blog article gives an overview about the different interfaces […]
Automatic Test of AUTOSAR Code Replacement Library Routines at Ford Motor Company
The Journey – from idea to solution It seems like every day more and more software teams are developing software in a model-based way, using Simulink models and auto-generated c-code… and Ford is no different. Many low-level math and interpolation routines have been developed by the central software team as libraries that can be used […]
3 Reasons to Consider Using a Floating-Point Model to Generate Fixed-Point Code
Despite the availability of fast processors with dedicated floating-point support, we still see many projects generating fixed-point code from Simulink. The reason for this is not only the resource usage, but also the more transparent and predictable mathematical behavior. You can read more about this in our previous articles “What you should know about fixed-point” […]
What You Should Know About Fixed-Point Code
Vocabulary: Floating-point code? – Fixed-point code? – Scaling? – Resolution? – LSB? Basically, we can distinguish between two kinds of datatypes in embedded code: Floating-point and Integer. An integer variable basically represents whole numbers and the value range is limited by the number of bits. For example, an (unsigned) 8bit Integer can represent 2^8=256 different values, by default […]
When and how to generate test cases automatically
The automatic test case generation has always been a controversial topic. While some people dream about stopping any manual test activities others say that test generation is not allowed. But who is right? Test Goals for automatic test case generation Let’s have a quick look at the possible test goals for which we can generate […]
Modular Model-based Software Architecture for Efficient Unit and Integration Test
Model-based design (MBD) is well established in automotive to develop embedded software but with the growing size and complexity of software, handling big sized model is often a challenge. MBD enables to easily craft a software application and from one step to another refine it, test it and generate the production code. However, it’s risky to start […]
4 Ways to Detect Undesired Changes During a Tool Version Migration
4) Software Requirements in ISO 26262 chapter 6 Software requirements are the result of a transformation process of the TSRs allocated to software parts and the HSIs into a set of requirements used to develop the software functions. In parallel, hardware requirements are also derived to develop the hardware elements. Software requirements describe the static […]
Should I test the Model or the Code?
Model-based software development (MBD) with tools like Simulink and TargetLink in the automotive industry has grown over the past years and is a well-established development methodology today. Despite all the advantages, it can’t be denied that MBD introduces one additional step in the development process. In addition to the production C code there is also […]
What you should know about floating-point
Floating-point code becomes more and more common in today’s automotive industry. Since development is often done model-based using tools such as Simulink and dSPACE TargetLink, the model serves as an additional abstraction layer and therefore is an additional stage in the development and testing process. In comparison to fixed-point, floating-point comes up with several advantages. […]