There is an old saying: A picture is worth a thousand words.  A model allows you to lay out the system;  identify interfaces;  interactions and identify risk areas.  You can then use this in the generation of requirements.  For SW you can ensure you are addressing all of the functions the SW is to perform and insure coverage of system requirements. I think it can be easier to review a model versus reviewing requirement text.

See https://www.mathworks.com/solutions/model-based-design/, or read the papers from Jon Friedman.

Conference Paper MATLAB/Simulink for automotive systems design.

Conference Paper Development of AUTOSAR Software Components

Using model-based design, it is possible to generate automatically an embedded software.