Source has a set of Assurance Rules that provide optional checks of models, accessible via Edit » Scenario Options. Assurance Rules define and detect unacceptable states in the model, increasing the confidence that the user can have in the model and the output data. Users can customize Assurance Rules in Source by choosing the severity of the notification if an Assurance Rule is not met by the model. Further customization is possible by creation of plugins that define custom Assurance Rule(s). Functions with Custom Logs may also be used for validation and logging at custom notification levels.
...
| Notification level | Symbol | Outcome |
|---|---|---|
| Off | – | The rule is not checked. This will improve performance. |
| Info | Message logged in the Log Reporter for each instance in which the rule is not met. | |
| Warning | Message logged in the Log Reporter for each instance in which the rule is not met. | |
| Error | Message logged in the Log Reporter for each instance in which the rule is not met. | |
| Fatal | If the rule is not met, the model will stop running. |
Assurance Rules and their associated notification levels apply to all model elements in the Scenario. If custom validation and/or differing notification levels are required on a per model basis, then Functions with Custom Logs may be used in addition to Assurance Rules.
Each Assurance Rule is described in Table 2.
...