|
AEM™ Task 4. Business Rule Harvesting
During Business Rule Harvesting, we extract conditions from within the source code as a first step toward identifying business rules embedded within the software. These conditions are specified in a readable format and gathered into a searchable database, with links back to the source code containing the condition.
Variable Translation also takes place during this stage. We translate each variable into a real word using proper English syntax. This process creates the vocabulary necessary to understand the extracted conditions in plain English versus the cryptic abbreviations that are commonly used as program variables. Once translated names are available, they are automatically inserted into the extracted conditions to replace the original, cryptic variable names. The translated variables provide a clearer understanding of the meaning of each term.
Our iSAT interface enables anyone to search rule conditions according to business function or variable. Imagine being able to instantly identify all conditions in your software related to a given business term. Business rule harvesting makes it possible for you to do just that.
Business Rule Harvesting Output:
- Variable translation and standardization
- Documentation of all conditions extracted from the source code
- The business function and business activity associated with each condition
From Conditions to Business Rules
Documenting a complete and accurate set of business rules can be extremely valuable for an organization. This process makes the rules inherent in business operations visible, and enables the rules to be managed directly without having to manipulate program code. When legacy applications are present, however, the logic that underlies the rules can be locked away inside the source code. Trinity’s Business Rule Harvesting process accesses this logic and makes it available for business rule analysis.
|
