| ILOG JRules User Guide > Testing Rules with Rule Scenario Manager > Concepts > Simulations |
Simulations |
PREVIOUS NEXT |
A simulation is a collection of information needed to execute a number of scenario suites:
Simulations can be defined in XML files governed by an XML schema (XSD), or within the Rule Scenario Manager Console. Simulation XML files can also be generated in Rule Studio by way of a wizard. Simulation definitions can be imported into and downloaded from the Console as part of an RSM archive.
Simulation execution is controlled by a configuration file. A configuration, defined at the scenario, scenario suite, or simulation level, specifies the Java classes required to execute the scenarios, such as the executor class and input and output databinding classes. A simulation definition can point to a configuration file that would apply to all suites in the simulation, but configurations are otherwise independent of simulation definitions.
Configurations specified at a more granular level than the simulation, that is, at the scenario suite or scenario level, take precedence over the simulation configuration.
When a simulation is executed, it effects the execution of all member scenario suites, and the calculation of the KPI over the scenario suite execution results. The execution traces, tests, and test results of all scenarios contained in all scenario suites are collected into a simulation report, along with the simulation's KPI and the KPI results.
The results of a simulation execution are contained in a structured simulation report in a specified format, such as XML or Excel, using the required databinding class. Simulation reports produced in the Rule Scenario Manager Console can be viewed graphically in the Console and exported in several formats.
A simulation key performance indicator (KPI) is a global test applied to the results of scenario suite executions, returning a set of numeric values that can be used to evaluate the relative performance of scenario suites.
KPIs are applied in simulations to track the evolution of rules over time and modification, and also over different sets of input data.
A simulation report contains the scenario suite reports for the scenario suites executed as part of the simulation. Also included is the KPI applied to the scenario suite results and its calculated value.
Reports are commonly stored as structured XML files or as an Excel workbook, depending on the databinding implemented.
Several formats of reports, such as XML and HTML, can be customized using a BIRT project in Eclipse. Simulation reports produced by executing simulations in the Rule Scenario Manager Console can be viewed graphically within the Console and exported as XML, Excel, and HTML.
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |