Page 1 of 1

Why must TTM table's name be unique?

PostPosted: Mon Jun 09, 2008 9:14 am
by kitbamrung
The term "Table" in TTM refers to the model elements that are visible in the Model Element Tree.

A snapshot of TTM Model Element Tree
ModelElement.PNG (2.91 KiB) Viewed 4464 times

The names of these model elements must be unique from other elements, with the exception of "Info" and the "Requirements" table. The main reason for this requirement is due to the limitation of the Windows operating system. When an Output table (Functions, Model Machines, Terms, and Outputs) is translated into a subsystem (SS files in VGS). One SS file is produced for each subsystem, so that they can be modified, debug, or export into another project. While TTM and the translator supports the translation of duplicated table names, the operating system does not allow files with duplicated names to be created.

Currently TTM provides basic duplication check during both model checking and data entry.

A snapshot of Invalid name error message box
Duplication_Check.PNG (12.2 KiB) Viewed 4472 times

Unique Identifiers

PostPosted: Mon Jun 09, 2008 9:39 am
by kitbamrung
In the programming world, an identifier can be unique by using letters in different cases. For example, it is completely valid to say that the identifiers "Boolean_Out" and "Boolean_OUT" are different. This is also a valid statement in Tabular Modeler and translation world as well. However, the interface between VGS and TTM can not currently support this types of naming schema due to the limitation of the Windows Operating system.

In general, using identifiers that are different only by the upper or lower case character is not a good identifier naming practice. In future releases of TTM this naming schema will no longer be valid. This is necessary to ensure that the translation and TTM to VGS interface will work properly.