After performing dependency analysis, the Impact View shows:
- Your project structure and its file dependencies, showing how files such as models,
libraries, functions, data files, source files, and derived files relate to each other. - Required products and toolboxes.
- Relationships between source and derived files (such as .m and .p files, , .slx
and .slxp, .ssc and .sscp, or .c and .mex files), and between C/C++ source and
header files. You can see what code is generated by each model, and find what code
needs to be regenerated if you modify a model. - Warnings about problem files, such as missing files, files not in the project, files with
unsaved changes, and out-of-date derived files.
To examine project dependencies and problem files, at the top right of the Dependency
Analysis view, click Table View.
After you run the first dependency analysis of your project, subsequent analyses are
incremental updates. However, if you update external toolboxes and want to discover
dependency changes in them, you must perform a complete analysis. To perform a
Analyze Project Dependencies