In a project, you can analyze project structure and discover files required by your project in the Dependency Analysis view.
To help you set up your project with all required files, you can use dependency analysis.
In a Simulink® model, on the Simulation tab, select New > Project > New Project from this Model.
Simulink runs dependency analysis on your model to identify required files and a project root location that contains all dependencies. See Create a Project from a Model.
Alternatively, you can manually add models to your project, analyze the model dependencies, and then add all dependent files to your project. See Run Dependency Analysis.
You can use the Impact graph view of a dependency analysis to analyze the structure of a project visually. You can perform impact analysis to find the impact of changing particular files. In the graph, you can examine your project structure; find required toolboxes for the whole project or for selected files; open, edit, and run files; add labels and export files. See Perform Impact Analysis.
Impact analysis can show you how a change affects other files before you make the change. For example:
Investigate the potential impact of a change in requirements by finding the design files linked to the requirements document.
Investigate change set impact by finding upstream and downstream dependencies of modified files before committing the changes. Finding these dependencies can help you identify design and test files that need modification and help you find the tests you need to run.
You can run dependency analysis at any point in your workflow when you want to check that the project has all required files. For example, check dependencies before submitting a version of your project to source control. To work with results, see Check Dependency Results and Resolve Problems.
You can search for requirements documents in a project. See Find Requirements Documents in a Project.
After performing dependency analysis, you can open or label the files, export the results as workspace variables, images, or reloadable files, or send files for custom task processing. Exporting the results enables further processing or archiving of impact analysis results. You can add the exported list of files to reports or artifacts that describe the impact of a change. See Save, Open, and Compare 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.
Use a project to analyze file dependencies for your entire project. For detailed dependency analysis of a specific model, use the manifest tools to control more options. Use the manifest tools if you want to:
Analyze a model that is not in a project.
Save the list of the model dependencies to a manifest file.
Create a report to identify where dependencies arise.
Control the scope of dependency analysis.