Widely used: Text

Describing logical relationships in text form is still widely used. Here is a typical example from the area of dunning procedures at an insurance company in Germany:

If no balance can be determined, no action is taken. If there is a balance of less than zero (negative credit balance, overpayment), it must be recorded as a log entry.

If the payment reminder deadline has not been reached yet, no action is taken even if there is a balance.

If a balance greater than zero can be determined and the reminder deadline has also been reached, there is only a log entry made for 'VIP' customers. For all other customers, it must be distinguished whether the outstanding amount is a minor contribution or not:

In the case of minor contributions for the transaction type 'first payment', an Article 38 reminder (initial first payment) is to be triggered and a contract termination must be scheduled.
In the case of minor contributions for the transaction type 'subsequent payment', an Article 39 reminder (subsequent payment) is triggered with immediate contract termination.

If the outstanding amount is not a minor contribution, again two possible transaction types must be differentiated:

In the case of subsequent payments, an Article 39 reminder is issued, although in this case no contract termination is triggered.
In the case of first payments, an Article 38 reminder is issued, also without contract termination.

Conclusion

The fundamental characteristics for evaluating the description are not immediately apparent in a text.

Each reader must read the entire text, possibly several times, in order to form their own individual picture of the task to be solved.

Is it a simple task or a difficult, complex one?
How many conditions and actions are included?
How many cases or use cases are included?
Is the description complete?
Are there any contradictions?
Are there any redundancies?