Cube
Mint
Sugar
Accession
> Need to register?
Instructions on how to register
> Forget your password?
> Your account
Cube Base
Details: Scenario Manager
The purpose of Scenario Manager is to allow an application to be conveniently executed with a varying set of inputs. This allows the user to compare the affects that different input values have on the results. A set of input values is a scenario. Scenario Manager provides a convenient interface for defining scenarios, editing and running them, and reviewing input data and output results by scenario.
The basis of Cube scenario management is the catalog. This contains information on what applications you want to run, the varying inputs to the application(s) which are called “keys,” and scenarios that definevalues for those keys for a particular test case.
A catalog allows running of an application. An application is either what Application Manager outputs, namely a flow chart style view defining a sequence of programs/scripts to run, or a Script. A Script is a Cube Voyager or TP+ script, written by the user in a text editor.
Each application has a set of keys that can be applied to it. The keys to the application can represent whatever you choose, such as a file, a number, a Boolean flag, or a string. Application Manager and Scenario Manager provide an interface for defining keys, but it is also possible to write them directly into a script using a text editor.
A scenario is used to define a value for each of the keys. Multiple scenarios can be defined to allow variations in the inputs to be run and compared. The scenarios are hierarchical in nature. Hence you start with a Base scenario. Then you can introduce scenarios representing variations on the base situation. Then you can introduce variations on those variations,
and so on.
The catalog represents how its applications are used for a particular data set. Thus the same application could be used in several different catalogs. It is the catalog that defines what data is used to run the application by assigning suitable values to its keys.
When a catalog is complete, the Cube Scenario Manager will be displayed in a panel. The display is customizable but the default arrangement is that the top section shows the scenarios. The next section shows the applications followed by a Data section. Finally there is a list of keys.
The purpose of Scenario Manager is to allow an application to be conveniently executed with a varying set of inputs. This allows the user to compare the affects that different input values have on the results. A set of input values is a scenario. Scenario Manager provides a convenient interface for defining scenarios, editing and running them, and reviewing input data and output results by scenario.
The basis of Cube scenario management is the catalog. This contains information on what applications you want to run, the varying inputs to the application(s) which are called “keys,” and scenarios that definevalues for those keys for a particular test case.
A catalog allows running of an application. An application is either what Application Manager outputs, namely a flow chart style view defining a sequence of programs/scripts to run, or a Script. A Script is a Cube Voyager or TP+ script, written by the user in a text editor.
Each application has a set of keys that can be applied to it. The keys to the application can represent whatever you choose, such as a file, a number, a Boolean flag, or a string. Application Manager and Scenario Manager provide an interface for defining keys, but it is also possible to write them directly into a script using a text editor.
A scenario is used to define a value for each of the keys. Multiple scenarios can be defined to allow variations in the inputs to be run and compared. The scenarios are hierarchical in nature. Hence you start with a Base scenario. Then you can introduce scenarios representing variations on the base situation. Then you can introduce variations on those variations,
and so on.
The catalog represents how its applications are used for a particular data set. Thus the same application could be used in several different catalogs. It is the catalog that defines what data is used to run the application by assigning suitable values to its keys.
When a catalog is complete, the Cube Scenario Manager will be displayed in a panel. The display is customizable but the default arrangement is that the top section shows the scenarios. The next section shows the applications followed by a Data section. Finally there is a list of keys.
Scenario Manager
Find a product
2009-03-11
2009-03-19
2008-05-31
