# Difference between revisions of "Modeling"

From T-VEC Wiki

(→Model Types) |
(→Model Representation) |
||

Line 8: | Line 8: | ||

==Model Representation== | ==Model Representation== | ||

− | At the lowest-level of representation there are '''Domain Convergence Paths (DCPs)''' that are conjunctions of predicates, each associated with a functional relationship that is also treated as a predicate. Sets of DCPs are grouped | + | At the lowest-level of representation there are '''Domain Convergence Paths (DCPs)''' that are conjunctions of predicates, each associated with a functional relationship (FR) that is also treated as a predicate. Sets of DCPs are grouped into subsystems. The grouping is derived from the modeling constructs of TTM (e.g., condition tables) and Simulink subsystems. A DCP can represent a simple precondition/postcondition relationship, but the DCP can represent a complex relationship over time. This supports the ability to generate [[Test Sequence Vectors|Test Sequence Vectors]]. |

− | The underlying specification language of T-VEC supports traditional logical and relational operators, but provides also support for mathematical operators (e.g., trigonometric, intrinsic, integrators, quantization, matrix) | + | The underlying specification language of T-VEC supports traditional logical and relational operators, but provides also support for mathematical operators (e.g., trigonometric, intrinsic, integrators, quantization, matrix) to specify functional behavior supporting various applications domains. |

==Tool Flow== | ==Tool Flow== |