The business logic scripting stage involves performing the following steps:
Create the formula based on the calculation requirements defined in the design phase. The formulas defined are all the unique formulas to be used in their various permutations in the Contract's Metrics, each as a Business Logic module.
For example, if the contract holds three Metrics for calculating the average ticket resolution time and one Metric for each ticket priority, then a single formula is developed for calculating the ticket resolution time, and having the ticket priority as its parameter. This formula, once tested, is defined as a module and is attached to all of the relevant Metrics.
Tests are performed to ensure that the formula is defined correctly and without errors, and the calculations produce the expected result. It is important to cover all extreme end cases and boundary conditions as part of the testing. The Business Logic scope is where the formula is executed for the purposes of testing. When initially defined, the formula is tested in its entirety. Then, once it is applied to all the Metrics as a module, it is important to run each Metric in the scope at least once to see that it receives Events (that is, that the registration is correct) and produces a reasonable result.
Each module is a unique Business Logic calculation and with its parameter definition can be applied to all the relevant Metrics. During the definition of the module, it is important that the module is thoroughly tested and documented in detail; what does the module do (calculation description), which parameters does it expect (name, meaning and use), etc.
For each Metric in the defined Contracts, a link to the relevant Business Logic module should be defined. It should then be executed in the Business Logic scope to ensure that the link was implemented correctly and that the registration is working properly by receiving the relevant Events and producing the expected results.
|
Copyright © 2013 CA.
All rights reserved.
|
|