mahindra uses model-based development for converting traditional in-vehicle networking (ivn) textual specifications to executable specifications. these executable specifications consist of all the mahindra ivn network management logics modeled using matlab®, simulink®, and stateflow®. simulink design verifier™ checks for any design errors and finds dead logic. simulink verification and validation™ does requirement traceability. vector canoe toolbox is used for integrating canoe with matlab so as to take can messages and signals as input for checking the network management logic. finally, simulink report generator™ creates scripts to generate automated reports from the developed models, which are shared as executable specifications to mahindra’s suppliers. the reason for this migration was because the ivn team was facing very serious problems with a few suppliers on their software deliveries. these deliveries would have huge development time and numerous bugs. on investigation, mahindra realized these bugs were mainly on account of not being able to understand their specifications. numerous phone calls and discussions would be required for the suppliers to understand. the solution to this was to convert specifications into industry standards using model-based design.
note: simulink verification and validation transitioned to simulink check, simulink coverage, and requirements toolbox in r2017b.
