Difference between revisions of "Modeling"

From T-VEC Wiki
Jump to: navigation, search
(Model Representation)
(Tool Flow)
Line 13: Line 13:
  
 
==Tool Flow==
 
==Tool Flow==
The [[T-VEC_Vector_Generation_System#Test_Vector_Generation|test vector generator]] performs [[Formal_Methods_and_Theorem_Provers#Model Checking Supports Testing|model checking]] on a DCP at each level in the hierarchy, and DCPs that are error free produces as a byproduct a test vector. The tools integrate with a [[T-VEC_Vector_Generation_System#Test_Driver_Generation|test driver generator]] to produce test drivers that automate test execution for most any language and test environment with automated test results analysis.
+
The [[T-VEC_Vector_Generation_System#Test_Vector_Generation|test vector generator]] performs [[Formal_Methods_and_Theorem_Provers#Model Checking Supports Testing|model checking]] on a DCP at each level in the hierarchy during test vector generation, and T-VEC VGS creates reports identifying the defects. A simple example of a model defect is a logical contradiction, where a constraint such as (x > 0) & (x < 0) is in the DCP specification. Model checking hierarchically composed subsystems involves checking the satisfiability of constraint or function references between higher-level (i.e., grandparent) and lower-level (i.e., child) subsystems. For example, as conceptually shown the figure, if there is a constraint, x > 0 in a DCP thread from the grandparent subsystem to a child subsystem, there must be at least one DCP through the parent and child that permits x > 0. If such a constraint in the grandparent cannot be satisfied, then the input space for that DCP of the grandparent is empty (i.e., null), and no test inputs can be selected; this is a model defect.
 +
 
 +
If the DCPs are error free, VGS produces as a byproduct a test vector. The tools integrate with a [[T-VEC_Vector_Generation_System#Test_Driver_Generation|test driver generator]] to produce test drivers that automate test execution for most any language and test environment with automated test results analysis.

Revision as of 13:36, 15 February 2007