Finally, analysts should consider that year 2000 projects serve as solid foundation for a rule extraction project. Many organizations had to inventory their systems and document which functions that those systems support. This documentation effort established the basis for rule extraction and reuse. Your year 2000 investment is a cost-effective launching point for a business rule extraction project. A parachutist would never jump from an airplane without the proper training, equipment, crew, weather analysis or other setup procedures.
Rule extraction requires setup work as well.
Prior to undertaking the business rule extraction process, project teams should consider several preliminary steps. Business rule extraction requires a high level assessment of the existing environment so that analysts can segment systems in preparation for rule extraction. Analysts should segment a subset inventory of system components to be fed into the extraction process. Architecturally, analysts should determine how systems share data to refine the population of systems targeted for rule extraction. Any system updating a shared database or master file should be included in project.