Difference between revisions of "Configuration Management"

From T-VEC Wiki
Jump to: navigation, search
 
 
Line 1: Line 1:
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.
+
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 structured ASCII, XML, or HTML formats. This allows any company or project to use their own Configuration Management tools and processes to be applied when using the T-VEC tools.
  
 
==TTM Sources==
 
==TTM Sources==
Line 8: Line 8:
  
 
All other files are completely reproducible from the sources, but any individual project may want to configuration manage generated artifacts.
 
All other files are completely reproducible from the sources, but any individual project may want to configuration manage generated artifacts.
 +
 +
These artifacts directly related to the work that is involved for [[Measurement|Project and Product Measurement]].
  
 
==Simulink Tester Sources==
 
==Simulink Tester Sources==
When using the Simulink Tester for T-VEC, there are
+
When using the Simulink Tester for T-VEC, the following types of files should be CM'd
*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
+
*Simulink Model file (.mdl) - this is important to CM as it is used also as the specification of the design, and often used to support code generation; there can be one or more .mdl files
*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
+
*Signal Range file (XML) - 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.
+
*Configuration file (XML) - 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
 
Optionally there are other files that might be used as source inputs to support the Simulink translation and test generation process
Line 19: Line 21:
 
*Test sequences file - stored in XML - specifies test sequences; there can be one-or-more test sequence files
 
*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.
 
*Assertion files - stored in structure ASCII - specifies assertions that can be used for modeling checking or various type of test generation.
 +
*Make files, including LDRA or other types of automation applied for test driver generation and test execution

Latest revision as of 20:45, 17 January 2007