KPIT engineers established a software development workflow for their client based on AUTOSAR and Model-Based Design.
In this workflow, engineers began by analyzing system requirements and defining an architecture comprising individual AUTOSAR software components.
Next, the team defined the software requirements of the individual components, using an AUTOSAR authoring tool to set up interfaces and add other configuration details.
Following a top-down approach, the team exported software component description ARXML files from the authoring tool. They imported these files directly into Simulink to create a skeleton Simulink model that contains interface blocks and the AUTOSAR-related settings defined in the authoring tool.
Working in Simulink and Stateflow®, they elaborated this skeleton model of the application software, adding sequential logic and other blocks to implement new features.
After checking the model for compliance with MathWorks Automotive Advisory Board (MAAB) guidelines, the team ran model-in-the-loop simulations to test the functionality of the design against requirements.
The team generated AUTOSAR-compliant C code together with updated software component description ARXML files using Embedded Coder® and the Embedded Coder Support Package for AUTOSAR Standard.
They used the generated C code to conduct software-in-the-loop tests, verifying that the results from these tests match the simulation results from the Simulink model.
The team imported the updated ARXML files back into the AUTOSAR authoring tool so that the new application software can be integrated with other AUTOSAR software components before deployment to the ECU.
Using this workflow, KPIT and its client successfully completed the aftertreatment system software, which is currently undergoing final testing. KPIT's client is now using Model-Based Design on other AUTOSAR projects.