Frequently Asked Questions
Temporal engineering separates the control-flow from the data-flow. This separation eliminates spaghetti code, improves the quality of the product, and reduces overall costs.
Q: [What is Different about VSM - ETL?]
A: [The VSM - ETL application GUI is structured using numbered
buttons that sequence the ETL process. Each numbered button performs
a portion of the ETL. There is a complete mapping editor after the
source schema has been extracted and displayed. The source schema
can be copied in to the mapping editor to be modified or the mapping
editor can be used to create a completely new destination schema.
All of the logic in the ETL application is developed using temporal
engineering. That makes the ETL application easy to customize for
specific migration needs.]
[What is spaghetti code?]
A: [Software written using any computer language that uses
if-then-else and case-switch type statements with imbedded data
manipulation. The term 'spaghetti code' comes from the intermixed
control-flow logic with the data-flow manipulation routines.]
Q: [What makes spaghetti code bad?]
A: [From a maintanence or modification perspective the spaghetti
code logic is extremely difficult to follow. Even for the person
that develped the original code.]
What's the solution to spaghetti code?]
A:[Temporal engineering separates the control-flow from the
data-flow providing a model driven approach to the development of
software. The following shows an example of a control-flow logic
diagram.]
