Deploying safe and secure automotive-grade embedded software is an inherently complex process.<\/p>\n\n\n\n
Now think of the connected automobile, the smart car, with all the advanced technologies required for advanced driver assistance systems (ADAS), automated driving systems (ADS) and of course, autonomous driving.<\/p>\n\n\n\n
To address these challenges, the automotive industry has been swamped with an ever-expanding number of specialized tools from different vendors which somehow must all work together. The good news is the model-driven development (MDD) methodology has evolved over the years and is now an effective means for embedded software development.<\/p>\n\n\n\n
Unfortunately, a common problem among teams that utilize the MDD approach is many of the tests are not reusable across the various \u201cModel-In-the-Loop\u201d (MIL), \u201cSoftware-In-the-Loop\u201d (SIL) and \u00a0\u201cHardware-In-the-Loop\u201d (HIL) testbenches. (Incidentally, when all of these testing environments are used together, it is often referred to as \u201cXIL.\u201d) \u00a0In order to be successful in terms of on-time, on-budget, and on-quality, it\u2019s essential that teams be able to reuse verification and validation (V&V) testbenches across the entire XIL project.<\/p>\n\n\n\n
No question, effective testing is one of the most challenging tasks undertaken when developing the electrical and electronic (E\/E) subsystems within an advanced vehicle.<\/p>\n\n\n\n
Download this Siemens automotive white paper<\/a> now.<\/strong><\/p>\n\n\n\n This paper explores industry standards, tools, and techniques that effectively support the reuse of V&V suites throughout an entire software development project. An overriding tenet is to not treat the different XIL configurations as useful only during certain workflow phases, but rather, treat them as different levels of abstraction of the E\/E system so they are useful throughout the systems engineering project. It\u2019s a fascinating as well as comprehensive read that\u2019s sure to answer some of your questions regarding the MIL->SIL->HIL workflow.<\/p>\n\n\n\n Factors that affect test reuse:<\/p>\n\n\n\n Key standards supporting the MDD\/XIL workflow:<\/p>\n\n\n\n This paper<\/a> puts forth a systematic and automated MDD\/XIL workflow that allows software teams to develop their electronic control unit (ECU) V&V suites early during software modeling, and reuse them through to production ECU testing, and ultimately for automatic regression testing of future software updates.<\/p>\n\n\n\n In addition to being able to reuse these test suites across the entire workflow, teams are also able to easily locate problems in the early phases where fixes are least expensive to correct. There are just so many advantages to talk about, it’s best to download the paper.<\/p>\n\n\n\n I hope you\u2019ll take a minute to download the paper, \u201cConsistent test reuse across MIL->SIL->HIL in a model-driven development workflow\u201d<\/a><\/em> now.<\/p>\n\n\n\nHow to achieve consistent test reuse across the entire MDD workflow <\/h3>\n\n\n\n
This paper also covers:<\/h4>\n\n\n\n
\n\n\n\n