The benefits of any tool in the absence of a well defined transformation process is limited. Rule extraction is a subset of the transformation analysis, improvement, extraction and reuse cycle. This cycle involves technical, architectural and functional analysis to segment systems in preparation for rule extraction and reuse. As Kidder Peabody's Leonard emphasizes, skipping this process can lead to focusing on irrelevant patches of logic. Technical analysis identifies weaknesses in the current system that should be corrected prior to rule extraction.
Corrective measures includes code stabilization, data name rationalization and remodularization.
Architectural and functional analysis identify candidate source code for rule extraction and isolates programs and systems to be targeted for corrective measures. Removal of code flaws, such as recursion, and restructuring of convoluted logic simplifies rule extraction because some rule extraction tools have difficulty with legacy code constructs. Remodularization is selectively used to split cumbersome modules into more streamlined routines. If a rule extraction tool does not support DNR as part of the process, it should be applied as a prerequisite step. While code improvement techniques are prerequisite to business rule capture, common sense coupled with comprehensive front-end analysis dictates the degree of effort applied.