Structuring the set of rules
IT projects usually contain more than one validation rule. Depending on the project size, a project can contain several 1000 rules. The complexity of the rules must also be kept in check. A good way to reduce complexity is a reasonable modularization concept. It is about dividing something big into small, modular components.
The following guidelines exist for structuring the entire set of rules. Some of them are mandatory and are therefore an integral part of the grammar. The others are optional and serve as recommendations.
The first recommendation is to save the entire set of rules in a file with the extension *.ov.
​
Global elements
A set of rules can consist of several rules:
1
the contract MUST be signed
2
​
3
the age of the applicant MUST be at LEAST 18
Copied!
We call rules, variables and comments global elements. These must always be separated from each other by a paragraph, whereby paragraphs consist of at least two line breaks without content.
1
the age of the applicant is LESS than 18 years.
2
AS underage
3
​
4
IF the applicant is underage
5
AND his place of residence is NOT Dortmund
6
THEN You must be at least 18 years old and come from Dortmund.
7
​
8
​
9
COMMENT Above me is a multiline paragraph
Copied!
The upper set of rules consists of three global elements:
- a variable ,
- a validation rule,
- and a comment
The separation of the Global Elements by a paragraph is mandatory and is therefore part of the grammar. In this way you can write as many rules, variables and comments as you like. It is recommended to write down all variables in the upper part of the set of rules.
Formatting complex rules
For a complex IF/ THEN rule to remain readable, it should be formatted as follows:
1
IF the applicant is underage
2
AND his place of residence is NOT Dortmund
3
THEN You must be at least 18 years old and come from Dortmund.
Copied!
​
- Within a rule, the conditions and the error message are to be separated by a line break
- The keywords, such as
IF,ANDandTHEN, should be right-aligned with the longest keyword - After the first keyword of the respective line there are at least two spaces (the number can vary. Consistency is important).
- Long conditions or error messages can be formatted again with a line break. It is important that the next line is flush with the beginning of the previous line, as is the case with the error message that comes after the
THENkeyword and contains a line break
​
Formatting variables
1
the age of the applicant is LESS than 18 years old
2
AS underage
Copied!
The keyword
AS and the name should be separated from the actual value of the variable by a line break. The value of the variable should be flush with the name of the variable. This formatting is optional and only serves to improve readability.Splitting the set of rules into several files
It is possible to split the entire set of rules into several files. For example, you can store the variables in a separate file and add external files using the keyword
IMPORT:variables.ov
1
the age of the applicant is LESS than 18 years old
2
AS underage
Copied!
rules.ov
1
IMPORT ./variables.ov
2
​
3
IF the applicant is underage
4
AND his place of residence is NOT Dortmund
5
THEN You must be at least 18 years old and come from Dortmund.
Copied!
Last modified 2yr ago