Main Content

complexityinfo

Retrieve cyclomatic complexity coverage information from cvdata object

collapse all in page

    Syntax

    complexity = complexityinfo(cvdo,modelObject)
    complexity = complexityinfo(cvdo,modelObject,simMode)

    Description

    complexity = complexityinfo(cvdo,modelObject) returns complexity coverage results from the cvdata object cvdo for the model component modelObject.

    complexity = complexityinfo(cvdo,modelObject,simMode) returns complexity coverage results from the cvdata object cvdo for the model component modelObject for the simulation mode simMode.

    Examples

    collapse all

    Open Script

    This example shows how to retrieve cyclomatic complexity information for the Gain subsystem of the slvnvdemo_cv_small_controller model.

    Load the slvnvdemo_cv_small_controller model.

    modelName = 'slvnvdemo_cv_small_controller';
load_system(modelName);

    Create a test specification object and enable decision, condition, and MCDC coverage. Then, simulate the model using cvsim.

    testObj = cvtest(modelName);
testObj.settings.decision = 1;
testObj.settings.condition = 1;
testObj.settings.mcdc = 1;
covData = cvsim(testObj);

    Retrieve cyclomatic complexity information for the Gain subsystem.

    gainPath = [modelName,'/Gain'];
gainComplexity = complexityinfo(covData,gainPath)

    gainComplexity =

     1     0

    The Gain subsystem itself does not record cyclomatic complexity, but the contents of the subsystem do. This can be seen in the results because the total complexity is 1, which includes the subsystem and all of its descendants. In contrast, the local complexity is 0, indicating that the one point of complexity comes from one of the descendants, in this case a Switch block.

    switchPath = [modelName,'/Gain/Switch'];
switchComplexity = complexityinfo(covData,switchPath)

    switchComplexity =

     1     1

    Input Arguments

    collapse all

    Coverage data, specified as a cvdata object.

    Data Types: cvdata

    Model object, specified as a character array, string array, Simulink handle, Stateflow ID, or cell array.

    To specify a model object, such as a block or a Stateflow chart, use one of these formats:

    Object SpecificationDescription

    BlockPath

    Full path to a model or block

    BlockHandle

    Handle to a model or block

    slObj

    Handle to a Simulink API object

    sfID

    Stateflow ID

    sfObj

    Handle to a Stateflow API object from a singly instantiated Stateflow chart

    {BlockPath, sfID}

    Cell array with the path to a Stateflow chart or atomic subchart and the ID of an object contained in that chart or subchart

    {BlockPath, sfObj}

    Cell array with the path to a Stateflow chart or subchart and a Stateflow object API handle contained in that chart or subchart

    {BlockHandle, sfID}

    Cell array with a handle to a Stateflow chart or atomic subchart and the ID of an object contained in that chart or subchart

    To specify an S-Function block or its contents, use one of these formats:

    Object SpecificationDescription

    {BlockPath, fName}

    Cell array with the path to an S-Function block and the name of a source file

    {BlockHandle, fName}

    Cell array with an S-Function block handle and the name of a source file

    {BlockPath, fName, funName}

    Cell array with the path to an S-Function block, the name of a source file, and a function name

    {BlockHandle, fName, funName}

    Cell array with an S-Function block handle, the name of a source file, and a function name

    To specify a code coverage result, such as coverage data collected during software-in-the-loop (SIL) or processor-in-the-loop (PIL) analysis, use one of these formats:

    Object SpecificationDescription

    {fileName, funName}

    Cell array with the name of a source file and a function name

    {Model, fileName}

    Cell array with a model name or model handle and the name of a source file

    {Model, fileName, funName}

    Cell array with a model name or model handle, the name of a source file, and a function name

    Data Types: char | string | cell | Stateflow.State | Stateflow.Transition

    Simulation mode during coverage analysis, specified as one of these options:

    Object SpecificationDescription

    "Normal"

    Model in normal simulation mode.

    "SIL" or "PIL"

    Model in software-in-the-loop (SIL) or processor-in-the-loop (PIL) simulation mode.

    "ModelRefSIL" or "ModelRefPIL"

    Model reference in SIL or PIL simulation mode.

    "ModelRefTopSIL" or "ModelRefTopPIL"

    Model reference in SIL or PIL simulation mode with the code interface set to top model.

    Data Types: char | string

    Output Arguments

    collapse all

    Cyclomatic complexity, returned as a two-element array of the form [total_complexity,local_complexity] if cvdo contains cyclomatic complexity coverage results, or an empty array if it does not.

    total_complexityCyclomatic complexity coverage for modelObject and its descendants (if any)
    local_complexityCyclomatic complexity coverage for modelObject

    If modelObject has variable-size signals, complexity also contains the variable complexity.

    Data Types: double

    Alternatives

    Use the coverage settings to collect and display cyclomatic complexity coverage results in the coverage report:

    1. Open the model.

    2. In the Simulink Editor, select Model Settings on the Modeling tab.

    3. On the Coverage pane of the Configuration Parameters dialog box, select Enable coverage analysis.

    4. Under Coverage metrics, select MCDC as the structural coverage level.

    5. Click OK to close the Configuration Parameters dialog box and save your changes.

    6. Simulate the model.

    7. In the docked Coverage Details pane, the coverage report shows the cyclomatic complexity for the model as well as each model object.

    Version History

    Introduced in R2011a

    See Also

    | | | | | | | | | |

    Topics