Every design, whether it is a Simulink® model or a project, requires a set of files and products to run
successfully. Dependencies include data files, model references, linked libraries,
C/C++ code, Stateflow® charts, and requirements documents.
You perform a dependency analysis to analyze project structure and discover required files and products. You can use the dependency graph to identify all required files and products, and perform an impact analysis.
On the Project tab, click the down arrow to expand the Tools gallery. Under Apps, click Dependency Analyzer. For more details, see Run a Dependency Analysis.
With the Dependency Analyzer, you can:
Find required products and add-ons. See Find Required Products and Add-Ons.
Check project dependencies and problems before sharing, packaging, or submitting your project to source control. See Check Dependency Results and Resolve Problems.
Perform an impact analysis to find the impact of changing particular files. See Perform an Impact Analysis.
Export the dependency analysis results as workspace variables, or
.graphml files, or send the files for custom task
processing. Exporting the results enables further processing or
archiving. See Export Dependency Analysis Results.
For an example showing how to perform file-level impact analysis to find and run the tests affected by modified files, see Perform Impact Analysis with a Project.
You perform a dependency analysis to examine models, subsystems, and libraries referenced directly or indirectly by the model. You can use the dependency graph to identify all required files and products.
On the Modeling tab, on the far right of the Design section, click the arrow. Under Dependencies, click Dependency Analyzer.
You can explore model dependencies using the model hierarchy or the model instances views. For more details, see Analyze Model Dependencies.
To package, share, or put your design under source control, create a project from your model. For more details, see Create a Project from a Model. Perform a project dependency analysis to explore the dependency graph using source control and project-specific views.