04 · Business validation
Let the business validate behavior
A domain expert can tell you whether the branch, longstanding customer, or holiday exception is missing. They should not need to read hundreds of lines of WLanguage to do it.
Translate the behavior into a decision
The Knowledge Base derives decision tables, flowcharts, and state diagrams from code. A decision table places conditions beside actions, so a reviewer can follow what the system does when a field is empty or a threshold is crossed. The code remains the source to inspect when a question arises.
Review the missing cases
Ask the business owner to walk through ordinary and exceptional cases. Does the discount also apply at a branch? What happens to an existing customer? Which status changes are allowed? These questions are easier to answer against a compact table than against a procedure read aloud in a meeting.
- Confirm that each condition reflects current policy.
- Identify cases the old implementation handled implicitly.
- Mark deliberate changes rather than silently reproducing them.
Carry the decision forward
The approved interpretation belongs beside the cataloged rule and the conversion work. That gives the later verifier a concrete behavior to check, rather than only a visual resemblance between old and new screens.