Skip to main content

Best practices

Creating tables​

  1. Each Table should have a complete description.
  2. Whenever possible, it is best to create a table, one-to-one mapping its paper/Excel etc. version to the version expected in the Algorithms. The focus should be on arranging the keys and values in as similar a matter as possible.

Thanks to this:

  1. Along with updates, we can see what has changed and where more easily,
  2. This will enable us to efficiently paste values from Excel format.

Recommended - If there is no need to follow the point above:

  1. number of table columns should not exceed six,

  2. with a large number of elements, the table should be higher rather than wider.

  3. All descriptions of the columns (grey fields) should be filled in and should give a business-like description (maximum three words) of what is in a given column.

  4. The exception to this rule is a single column with the key “All”. Here, the description field should be left blank.

Obraz 137

Naming in the version server​

  1. We use capital letter to name the models, without national characters.
  2. Model names are preceded by a prefix denoting the algorithm they belong to (e.g. CL INSURER).
  3. It very often happens that the model needs to be updated. In this case, in the naming of the model version, we provide the date of its update.

image

The table is valid from...​

If there was a need to make changes to the table, and the new version of the table must take effect from a specific point in time, this can be set in advance. Using version management, you can set the time - Valid From.

image

See also​

Business tests

Algorithms