Use of m-scripts in SIMULINK

Ideally it is possible to develop an entire simlink model with embedded m-scripts functions which could be used in place of SIMULINK blocks or STATEFLOW. As per design guidelines which are (recommended i.e. not mandatory) we know that the preferred approach is to use stateflow for modeling flow diagrams/state machines and Simulink blocks for contiuous time parts of the algorithms like PID controllers etc.

My question is: Are there any inherent flaws in developing a model enitirely with embedded m-scripts ?

The MAAB guidelines does not necessarily say something like : Do not use m-script for developing functionality which is more than 60 lines . It only says that one function need to be restricted to 60 lines but there could be any number of sub functions.

Answer 1

[Mark McBroom]

There is nothing wrong with using Simulink to architect a system comprised entirely of MATLAB Function blocks. NASA has developed some guidelines for when to use Simuilnk vs. Stateflow vs. MATLAB. See section Appendix 5.1: https://www.mathworks.com/content/dam/mathworks/mathworks-dot-com/solutions/aerospace-defense/standards/FltDyn-CEV-08-148_MATLAB_Standards_v9_20111202.pdf