Rule elicitation is an ongoing activity you perform throughout the project. Collaboration with your stakeholders is
critical. They will change their minds as the project proceeds and that's perfectly fine.
The documentation of the rule may be done using different language. The natural language is initially used during
business conversations to describe the rule, informally, without trying to impose any structure. SMEs express their
ideas using a language very close to them, but they usually are not able to formalize their concepts in a clear and
unambiguous way. Using this language we may have redundancy and inconstancy in the rule ex-pression, in the business
terms, and overall by it may not be relevant and precise enough to be able to implement the decision logic.
Conceptualization and representation play fundamental roles in thinking, communicating, and modeling.
A second evolution is still in natural language, and is still consumable by both analysts and developers, but, we have
imposed some structure, and we made sure that they are relevant and have the right form, but may not be correct
semantically. We use the rule description template to log the rule.
The last type of expressiveness of the language to document the rule is precise and there are no ambiguities: the rule
refers exactly to information system objects. This language is parse-able and non-ambiguous. Semantics of Business
Vocabulary and Business Rules or SBVR from Object Management Group can be used at this stage to specify formally
representations of concepts, definitions, instances, and rules in natural language.