Main Content


Suppress incompleteness issues for output in Requirements Table block

Since R2024a




    anyValue suppresses incompleteness issues for a design model output. You can use anyValue only as an equality in a postcondition cell of a Requirements Table block requirement row.


    Using anyValue does not suppress incompleteness issues globally. See Suppress Incompleteness Issues.


    collapse all

    This example shows how to suppress incompleteness issues in a Requirements Table block.

    In a Requirements Table block, create two parent requirements and two child requirements for each parent requirement. Define precondition expressions that check the values of u1 and u2 as shown in the example table. Define postcondition expressions that check the value of y for requirement 1.1, 1.2, and 2.2 as shown in the example table. In this example, when u1 and u2 are less than or equal to 0, the model output is not within the design scope. Define the postcondition of requirement 2.1 as y == anyValue.

    Requirements Table with two parent requirements. Each parent requirement has two child requirements.

    Version History

    Introduced in R2024a