use a requirements table block to create formal requirements -凯发k8网页登录

define formal requirements

formal requirements are a set of unambiguous specifications that you express mathematically and execute through simulation. each formal requirement executes if at least one condition is true for a specified duration. when the requirement executes, the block verifies specified simulation behavior and produces additional simulation data.

to define formal requirements, add a requirements table block to your model.

opening a new requirements table block displays a blank requirement. by default, the block opens on the requirements tab. each row of the table represents a requirement. the columns specify information used to evaluate each requirement. the columns are:

you can create multiple requirements, preconditions, postconditions, and actions. to manage columns and requirements, use options available in the table tab. you can also access additional options with the context menu by right-clicking the requirement index or column header cell.

you can also specify assumptions that define physical constraints of the system in the assumptions tab. see .

create expressions for formal requirements

you define preconditions, postconditions, and actions with expressions. use boolean expressions for preconditions and postconditions, and use a single equal sign = to define actions. the expressions in each precondition and postcondition cell must evaluate to a scalar logical.

use data in your expressions to manage information, such as signal values, workspace variables, or constant values. expressions can also include numerical values and functions. for example, the precondition u >= 0 checks if the data u is greater than or equal to 0, and the action y = 0 sets the data y equal to 0.

you can define preconditions, postconditions, and actions by explicitly listing each full expression in the requirement cells or by listing the left-hand side of the expression in the column header and defining the right-hand side of the expression in the requirement. to write boolean expressions that use headers in precondition and postcondition columns, use the boolean relational operator of interest, leave the left side blank, and enter the value of interest. to write actions that use headers, enter the value of the action into the cell.

for example, in this table the first postcondition specifies the data y1 in the header, the second specifies y2 in the requirement cell, and the action sets y3 equal to a vector of values.

you can also check if a scalar header equals a single value, multiple values, or a range of values in the precondition and postcondition columns. use these syntaxes to specify the checked values:

in this table, the precondition checks if u is equal to 1, 2, or 3. the postcondition evaluates the data y1 and y2 by using the same boolean expression but with different notation. the first postcondition uses header data with interval notation and the second postcondition uses explicit boolean operators without header data.

to evaluate header data against multiple intervals, combine them with the logical or operator. for example, [0.3, 0.5] || (0.1, 0.2) is valid. in addition to real numbers, you can also use inf in an interval to evaluate a bound that goes to infinity. intervals including inf must be preceded or followed by a parenthesis. intervals including inf can be simplified if the cell contains only one interval. for example, (0.3, inf) is equivalent to > 0.3.

to specify that the header data should not equal an expression, use the logical not operator by entering ~= or ~ to the left of the cell values. you can apply this operator to single values, comma-separated values, or intervals. for example, if you did not want the header data u to fall within the interval [0.3, 0.5], enter ~[0.3, 0.5] or ~=[0.3, 0.5]. for comma-separated values, use only ~.

if your requirement cells contain a lot of content, the cell size can obstruct the expression. to view all of the content, you can adjust the size of the cell or add a new line. to add a new line, finish the first line with ... and then press alt enter.

use functions in requirements table blocks

you can use functions and operators in requirements table blocks in the requirement cells or column headers. enter data as arguments to the function or operator like you do with variables in matlab^®. in this table, the cell u1 u2 == 2 and the cell below the header u3 u4 both check if the sum of the two input data equals 2.

the requirements table block does not support functions in headers that write to global variables or an internal state. for example, you cannot use the function in a header because rand writes to an internal state each time it generates a number.

define block data

in order to use data in the block, you must enter them in your requirements and define them in the symbols pane. to open the symbols pane, open a requirements table block. in the modeling tab, in the design data section, click symbols pane.

in the symbols pane, the icon in the type column indicates the scope of your data. you can set the data scope to be input, output, local, constant, or parameter. you can also change the name, the initial data value, and the port number. to modify additional properties, right-click the data name and select inspect to open the property inspector. for more information, see .

as you edit your requirements, the requirements table block detects undefined data and marks them in the symbols pane with the undefined symbol icon . unresolved data can cause errors during compilation. to resolve data, click the resolve undefined symbols button .

observe or generate model behavior

you can use the requirements table block to check model requirements by observing the model behavior, or by generating behavior that can be compared to the model behavior.