In industries such as Space, Avionics, Railway or Automotive, when designing your system, you take great care that the proper actions are not triggered too late (e.g. automatic emergency braking after the detection of an obstacle), even in the worst case. But the complexity of real time analysis (jitter, latency, deadline, scheduling policies, deadlocks among other funny things) added to the complexity of those systems make this worst case response time impossible to calculate by hand. Eventually, the problems are only detected at the end of the development phase when the system is tested under realistic conditions, which can be very costly and time-consuming to correct; in some cases, it even ends up with the whole project to be canceled. That’s why engineers have designed software to analyze or simulate the behavior of those systems before they go into production. However, each software requires particular conditions to be applicable (preemptive scheduling policies, multi or mono-processor, etc.) and quite specific skills to be properly used by engineers.
In this talk, we are going to see how Polarsys Time4Sys will support you in the timing verification of your real-time system even in early design phase. On the way, we will give insights into some of the challenges we faced:
- Reducing the complexity of designing a real-time systems for system engineers, as it turns out that they are seldom real-time specialists
- Bridging with existing specific analysis & simulation tools, and even better, being able to know how relevant they are for a given design
- Hiding Time4Sys inner complexity, by allowing to visualize the results of our analysis or simulation independent of the software used