Developing an Internet of Things (IoT) enabled product is a complicated task, whether it’s an autonomous vehicle, a vehicle user interface like a car infotainment system, or a connected factory. IoT-enabled products contain hundreds, if not millions, of lines of embedded software code. And many of these products — and the systems and software that control them — are mission- or safety-critical. Therefore, developers must have confidence that the software code controlling these devices is 100% accurate and responds in the intended manner.
You’ve probably seen studies that confirm that the number of safety-critical systems in IoT-enabled devices is growing due to higher level of integration and interaction between systems and the software that controls them. These trends, combined with the increasing functionality, volume and complexity of safety-related software, have resulted in a staggering level of complexity that many product developers find nearly impossible to negotiate using conventional manual software development methods.
Many of the safety-critical software developers that I’ve talked with have addressed these difficulties by changing to a model-based design process in which a graphical model of the embedded software and systems becomes the cornerstone of the development process. (I recently hosted a webinar on exactly this topic that’s available on-demand.)
With a model-based process, engineers can simulate the behavior of the model on a PC workstation and immediately view the results, making it possible to gain critical insights early in the systems design process and to rapidly improve the model’s performance. Engineers also can link the model’s predicted behavior to specific customer requirements. Finally, the model can be used to automatically generate the embedded code, thus eliminating the need for manual coding.
Compliance with safety-related standards enables developers of safety-critical applications to demonstrate that they use consistent, auditable processes for designing safety-related systems. There are a number of these standards that apply to different industry segments, for example DO-178C for aeronautics and ISO 26262 for automotive.
With the ANSYS SCADE products, you have access to all of the functionality that is needed to develop embedded software for safety-critical software that controls many of today’s most complex products, including autonomous vehicles. SCADE’s automatic code generator takes the guesswork out of how to automatically produce code that complies with a wide range of industry standards. With SCADE’s automatic code generator, you can substantially reduce the embedded software development time and cost. The code generator is offered as part of a complete end-to-end model-based systems engineering (MBSE) solution for the development of safety-related systems that has been proven through its use in the development of many safety-critical systems.
Now, take a look at the how Piaggio Aerospace has used ANSYS SCADE to turn a manned aircraft into an unmanned vehicle in just seven months!
And don’t forget, if you’d like to learn more about how ANSYS SCADE and its automatic code generator can reduce your development time and cost, check out the webinar, From Drones to Connected Cars: Safe and Secure Embedded Software Development for IoT Devices.