Difference between revisions of "T-VEC Tablular Modeler"

From T-VEC Wiki
Jump to: navigation, search
Line 90: Line 90:
 
The [[Examples|Examples]] section covers some general approaches that take advantage of the latests TTM features, which are important to using modeling from a project and team oriented perspective.
 
The [[Examples|Examples]] section covers some general approaches that take advantage of the latests TTM features, which are important to using modeling from a project and team oriented perspective.
 
==Guidelines==
 
==Guidelines==
===Strong Typing===
+
The following provides a few guidelines for modeling.
 +
===Define the Interface for the Model===
 +
*Identify the interface boundaries of the component; the architecture at any level of the system is the context for the component under test.
 +
*Create new types and constants whenever they are needed in the course of the model development.
 +
*Identify the input (monitored) and output (controlled) variables:
 +
**Identify modes and terms.
 +
*Define the variables:
 +
**Define types for numeric variables so that the legal range of values can be specified.
 +
**Define types for enumerated variables.
 +
**Define Boolean variables (e.g., a flag) directly.
 +
 
 +
====Strong Typing====
 
Good modeling practices grew out of good programming practices. TTM combined with VGS try to help user attain greater assurance of correctness. Like any variable, strong typing of variables provides greater assurance that the semantics of the relationships where arrays are referenced are correct. An array element ultimately relates to something in the domain, or a particular hardware element that will have a fixed value. If it’s an integer, the integer will be associated with some type of object in the domain (e.g., altitude – the altitude takes on a value that has a range related to what the sensor can represent). Users are encouraged to define all of the types first, then any variable created should use one of those types.
 
Good modeling practices grew out of good programming practices. TTM combined with VGS try to help user attain greater assurance of correctness. Like any variable, strong typing of variables provides greater assurance that the semantics of the relationships where arrays are referenced are correct. An array element ultimately relates to something in the domain, or a particular hardware element that will have a fixed value. If it’s an integer, the integer will be associated with some type of object in the domain (e.g., altitude – the altitude takes on a value that has a range related to what the sensor can represent). Users are encouraged to define all of the types first, then any variable created should use one of those types.
  

Revision as of 15:07, 29 May 2008