Configuration Management (CM) should be performed on those files that are the sources. All artifacts derived from those sources can be reproduced automatically from a specific set of tools, commonly referred to as the configuration index. All source artifacts and derived (or generated) artifacts used or produced by the T-VEC tools (e.g., TTM, VGS, and the Simulink Tester) are in ASCII, XML, or HTML formats. This allows any company or project to use their own Configuration Management tools to be applied when using the T-VEC tools.
When using TTM there are three source files that should be configuration managed:
- TTM Model - stored in XML
- Object Mapping - stored in structured ASCII
- Test Driver Schema - stored in structured ASCII
All other files are completely reproducible from the sources, but any individual project may want to configuration manage generated artifacts.
When using the Simulink Tester for T-VEC, there are
- Simulink Model file - this is important to CM as it is also used as the specification of the design, and often used to support code generation
- Signal Range file - this provides the signal range information that is used as part of the translation process. It specifies the ranges of the signal for the Simulink model inputs and outputs
- Configuration file - this defines the configuration parameters for the Simulink to T-VEC translation; there may be one-or-more of these files that specify different types of translation.
Optionally there are other files that might be used as source inputs to support the Simulink translation and test generation process
- Test sequences file - stored in XML - specifies test sequences; there can be one-or-more test sequence files
- Assertion files - stored in structure ASCII - specifies assertions that can be used for modeling checking or various type of test generation.