Personal tools

2.1. Concept

Up one level
If we think of components as claims generators, claims developers, reinsurance contracts, ... it's clear that each of these groups have common behaviour but different strategies how claims are generated, developed or ceded.

A claims generator produces claims according to a stochastic distribution. In order to avoid a component per distribution, there should be a possibility to trigger its behaviour with the parameterization.

Whereas dynamically composed components allow to specify an arbitrary number of subcomponents, strategies allow to trigger the behaviour of a single component. Furthermore they support the developer to share as much as possible of the implementation without using inheritance.

With the current implementation strategies are defined using a *Type extending form AbstractParameterObjectClassifier and a *StrategyFactory class.

On the user interface strategies are represented with combo boxes allowing the user to select a specific strategy. Switching the strategy will toggle the parameters in the tree.

Next: Distribution Previous: Strategy  
Document Actions