Personal tools
You are here: Home Community Help Center Reference Manuals RiskAnalytics Developer's Guide Components Conventions

Conventions

Note: Return to reference manual view.

WORK IN PROGRESS: IT technical issue to develop components and models.

1. Naming convention

Beside clean code and higher readableness naming convention, increase coding speed in modern IDE (integrated development environment) as code completion is supported.

A component may have several properties. There exist four prefixes to be used:

  • parm: whenever a variable name starts with parm. It is displayed on the parameterization user interface automatically.
  • in: all in variables of type PacketList receive packets from other components
  • out: all out variables of type PacketList send packets to other components. It is displayed on the result template user interface and optionally on the result page automatically.
  • sub: a component may have sub components. Their name has to start with sub.

Remark: If a component is written in Java, variables starting with any of these prefixes need a public setter and getter method.

2. Grouping of Components and Parameters in the GUI

The order in which you write the parameters, out channels and sub components in a component determines the order in the GUI.

RiskAnalytics comes with a powerful way of deriving a default user interface for all models, components and its parameters - a model or component developer does not have to write any GUI code. Yet he can group the parameters.

The order in which subcomponents, parameters and out channels in a component are displayed is the order in which they appear in the corresponding code.

Example of a Model and its Visualization in the Parameter View

class PodraModel extends Model {
    DynamicUnderwritingSegments underwriting
    DynamicClaimsGenerators claimsGenerators
    DynamicDependencies correlations
    DynamicMultipleDependencies eventCorrelations
    DynamicConfigurableLobs linesOfBusiness
    MultiLineDynamicReinsuranceProgram reinsuranceProgram
...
}

 Component Order

 

 

Document Actions