Modularize Analysis

Modularize your projects into smaller parts and specify how to analyze each part

Divide your projects into smaller parts for easier analysis:

Classify the source files in your project into various file sets and specify how to analyze them using the option -classification.
Create a separate Polyspace^® project or options file for each binary created in your makefile by using polyspace-configure.
Identify libraries and specify how to analyze them using the option Libraries used (-library).

You can stub code you do not own to run a faster analysis. Use these options to circumvent scaling issues.

Functions

polyspace-configure (System Command) Create Polyspace Platform project, workspace, or options file from build command or compilation database

`Inline (-inline)`	Specify functions that must be cloned internally for each function call
`Depth of verification inside structures (-k-limiting)`	Limit the depth of analysis for nested structures
`Set depth of verification inside structures`	Specify that depth of verification inside structures must be specified (Since R2023b)
`-classification`	Control precisely which files to include in Polyspace analysis and how to analyze them (Since R2025a)
`Libraries used (-library)`	Specify libraries that you use in your program

Classify Project Files into File Sets for Precise Control of Polyspace Analysis
Control precisely which files to include in analysis and how to analyze them.
Select Files for Polyspace Project Using Pattern Matching
Select files to include in Polyspace project or options file using expressions with glob patterns.

Modularize Polyspace Projects by Using Makefile Builds
Create a separate Polyspace project or options file for each binary in makefile build.
Modularize Polyspace Analysis at Command Line Based on an Initial Interdependency Analysis
Break down Polyspace analysis into smaller and relatively independent modules for faster module verification.