Intellisys Business Rules Extraction

Business Rules Extraction

Use a web based platform to analyze extracted information and derive your applications’ built-in rules and processes.

Every application undergoes a life cycle of maintenance, rationalization, optimization and modernization. When an application is unable to adapt to technology advances or new business requirements, it becomes a “weak link” in the application portfolio and becomes a candidate for modernization. However, there are multiple choices available on how to modernize an application:


    • Should the application be re-written from scratch in a modern language?

    • Should the application be replaced by an off-the-shelf product (COTS) like a business rules engine, a Business Process Management (BPM) tool or an Enterprise Resource Planning (ERP) platform?

    • Can the business rules of the application be integrated into an existing more modern application?

OR


    • Should the application remain stand-alone and be migrated from its current language to a modern language, and be re-platformed to a more efficient technology stack?

To select the right path to modernization, a more fundamental question needs to be answered:

Is the application understood well enough to make an informed decision?

The answer to this question begins with understanding the connectivity, logic and data structures embedded within the application (i.e. documentation), and ends with extracting the business rules (BRE) that are executed by that application.


An organization will not consider re-writing an application from scratch unless a large number of the existing rules within an application are going to be irrelevant going forward.


An organization will not consider replacing an application with an off-the-shelf product (COTS) unless most of the extracted rules can be easily implemented in that product.


An organization will not merge the business rules of an application into another application unless a majority of those rules can be integrated into the existing rules of the surviving application, or the rules share the same operational domain as the ones in the surviving application.


Therefore, extracting business rules from an application’s documentation is an excellent way to come to a conclusive decision on the future of that application.

A recipe for successful extraction and modernization of business rules requires the following ingredients:


    • Availability of source code meta-data, including embedded business logic (documentation)

    • Subject matter experts (SMEs)

    • A tool with features to consolidate the business logic into business rules and processes

    • A tool to export the business rules and processes to modern platforms

EvolveWare’s Intellisys™ Platform provides both the data and the features required to extract and modernize business rules by:


    • Automating meta-data extraction from source code, including the embedded business logic

    • Providing features to consolidate the business logic into business rules and processes

    • Automating the export of the extracted rules and processes into third-party products such as business rules engines, BPM and ERP products

The Intellisys Platform not only allows IT departments to gather information about their application portfolio and maintain it, but coupled with SMEs, the platform provides the information required to plan and take that portfolio into the future.

R

Sources Supported

ADABAS/Natural | ADSO | ASP | Assember | C | C# (.Net) | CA Gen | COBOL (AS/400, HP3000, z/OS, Unisys, etc.) | Easytrieve | Forte | FoxPro | Java |
PACBASE | PL/1 | PL/SQL | PowerBuilder | T SQL | Universe Basic | VB 5.0 & 6.0. | VB (.Net)

R

Deliverables

Files Inventory | Source Code Logistics | Source Code Complexity | Dead Code Details | Data Dictionary | System Details Diagram | Business Logic Connectivity Diagrams | Data Flow Diagram | Program Flow Diagram | Data Model in SQL/DDL Format | Program Logic | Business Logic.

R

Features

Trace execution of statements | Trace flow of variables and entities | Deactivate statements & business logic | Merge & split business logic | Rename variables in derived business rules and processes | Rename derived rules to better describe their functionality | Catalog and sub-catalog derived rules

Case Study

Customer

Department of Health Services
U.S. State Government

Country or Region

United States

Industry

Health Services

Major Areas Served in this Study

Business Rules Extraction (BRE) from COBOL systems.

Environments

Source System:

  • IBM 3090 MVS
  • VSAM Flat Files / DB2
  • COBOL, JCL/Procs.

Business Scenario

The Department of Health Care Services’ (DHCS) of every State finances and administers a number of individual health care service delivery programs, including Medicaid, Children’s Services program, Child Health and Disability Prevention program and Genetically Handicapped Persons Program.

These programs are run by very old legacy systems that are undocumented and hence no longer maintainable. Unfortunately, they need to remain current not only to deal with changing legislative requirements but also changing accessibility requirements. Hence it is imperative that these programs be modernized so that they can be maintained and scaled with changing requirements.

As a first step, the Federal Govt. has mandated that the State must extract and validate the embedded rules in these legacy systems against the policy manual of each program. The goal would be to transform these rules into modern code or exported into a business rules engine or a process management tool.

Challenge

Every State’s Medicaid system contains several modules that support the filing, authorizations, adjudications and processing of Medicaid claims from all the residents and agencies within that State.

The first phase of modernizing this system was the extraction of embedded business rules. The State began this process by selecting the patient billing module of the system for BRE.

This module deals with patient validation, claims, billing calculations and adjudications. The billing module, comprising of multiple sub-modules, receives data files for processing from various counties, agencies and departments within the State. These files are processed nightly as batch processes by the billing module and its sub-modules, producing claim files that are passed as input to other modules within the Medicaid system.

This module was considered mission critical because it contained rules that validated claims data and performed adjudication of claims submitted by Medicaid beneficiaries. Unless these rules were extracted with a high degree of accuracy, the target system could not be developed to ensure proper payment to claimants.

Business Objective

The State had awarded the project to modernize and maintain its legacy Medicaid system to a large domestic outsourcing company. A fundamental requirement of the contract was the delivery of the business rules embedded in the existing system.

This would allow the State to compare the extracted rules with the most current policy manual, thereby allowing only relevant rules to be used in the proposed modernized system.

The modernization project was in its second year and the State was finding that there seemed to be many missing rules in the system modules which were deemed “complete” by the outsourcing company from a rules extraction standpoint. Without proper documentation of the current system it was impossible for the State to:

  1. determine if the current system was meeting the State’s legislative laws and
  2. validate any target system that the outsourcing company would produce.

Further, with subject matter experts of the current system retiring, the situation was becoming dire as in a few years it would become impossible for the State to ensure that they were getting a valid system to run their Medicaid program. The State needed a solution that:
 

  1. was highly automated
  2. could accurately extract the system’s business logic
  3. had features to derive business rules from business logic and
  4. had the ability to export the derived rules in the desired format.

Solution

In keeping with the parameters required for the solution to be a success, the State selected a solution built around EvolveWare’s Legacy Modernizer tool because this product:

  1. automated the extraction of source meta-data
  2. had features to facilitate derivation of business rules and
  3. was flexible enough to accommodate the delivery of extracted rules in a format that met the State’s requirements.

The solution included the services of subject matter experts (SMEs) that could review the extracted business logic; and with the aid of the tool’s features deactivate unwanted rules, merge and split business logic to derive rules relevant to the policy manual and rename variables and rule names to reflect each rule’s functionality.

Additionally, to describe each rule in plain English, each rule could be annotated in the tool, thereby providing an abstract explanation for the benefit of business analysts. Finally, the derived rules could be exported in Word or Excel format to facilitate validation with the State’s policy manual.

The combination of Legacy Modernizer and SMEs became a compelling solution in processing almost 860,000 lines of code to meet the State’s requirements in terms of automation, accuracy and delivery of extracted rules; and all this in 6 months at a fixed cost.

From a time perspective, the solution was implemented in a time frame that allowed the State to not only retrieve business rules and create a working catalog for validating their deliverables from the prime contractor, but also a seamless way to document and manage their entire legacy system in a single product exposed as a single repository.

Project Deliverables & Time Lines

The project included the following deliverables:

  • Documentation – Code Logistics, dead code, system level diagrams, program logic and business logic.
  • Business Rules derived from extracted business logic.
  • Single platform and central repository that kept the extracted documentation and rules updated with code changes and accessible to authorized users at anytime.

The source code was received for processing and the complete set of business rules assembled in catalogs/sub-catalogs were delivered 6 months later. During the period of 6 months, an average of 8 personnel, including 2 SMEs, extracted and derived business rules from almost 860,000 lines of legacy code using EvolveWare’s Legacy Modernizer. The following statistics provide the calendar time spent on each of the major project tasks performed in the course of the BRE project.
 

  1. Extraction of embedded information – 4 weeks.
  2. Derivation of business rules, applying keywords/constant dictionary and adding annotations for business analysts – 18 weeks.
  3. Classifying rules into catalogs / sub-catalogs – 2 weeks.
  4. Exporting rules in RTF (Word) format – 2 weeks.

Business Benefit

The State succeeded in identifying a solution that extracted business rules from their Medicaid system with a very high level of accuracy. The project was completed on time and within budget. The success with the patients claims processing module was compelling enough for the State to move forward with extracting business rules from the remaining modules of the Medicaid system.

From a value-add standpoint, the solution, once completely implemented, not only provides the State with documentation and an understanding of their current system but also gives them a platform to keep the documentation updated on an on-going basis. This is a major step forward for the State, considering the large amounts of money being allocated for maintenance of their systems.

While the benefits will take some time to be quantified, the hurdle to modernization of the Medicaid system has been removed as the State can now match the extracted rules to their policy manual and determine which rules will feature in the target system, otherwise the target system would have had to be written from scratch based solely on the policy manual, and this effort would have been very risky and time-consuming considering the size and complexity of such a system.

EvolveWare, Inc. has been awarded 5 U.S. Patents and 1 Australian Patent for the technology that is incorporated into Legacy Modernizer and its successor, Intellisys™. The U.S. Patent numbers are 7,769,704, 7,774,290, 7,917,457, 8,051,410 and 8,412,653 respectively. The Australian Patent number is 2007348312. No part of this document may be copied, circulated or reprinted in any form without the prior written permission of EvolveWare, Inc. For questions and additional information please e-mail [email protected] or call +1.408.748.8301

Using EvolveWare’s Legacy Modernizer solution helped us in achieving our target of extracting business rules from the patient claims processing module of the State’s Medicaid system. The tool’s automated extraction abilities and feature set allowed subject matter experts to identify the embedded rules with a very high level of accuracy. The project met a very aggressive schedule and was completed in time on a fixed budget.

BRE Project Manager, Department of Health Services U.S. State Government

We want to hear from you