Business Rules Engine ETL Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In traditional Extract-Transform-Load (ETL) environments, business rule changes are lengthy and time-consuming due to the intermingling of business rules with data processing code, requiring involvement of software developers and a lengthy Software Development Lifecycle (SDLC), limiting the ability of business analysts to directly control and implement rule changes.
Innovation Solution
Implementing a Business Rules Engine-based ETL Development system that allows business analysts to create, test, and deploy business rules independently through a Business Rules Management System (BRMS), separating rule changes from application code and managing them within a Rule Development Lifecycle (RDLC), enabling quicker implementation of rule changes without relying on costly IT resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If business rules are intermingled with data processing code in traditional ETL environments, then the system maintains structural integrity and control through centralized SDLC, but business rule changes become lengthy and time-consuming requiring software developer involvement
Solution Approach 1:
The patent segments the system into distinct components: a Business Rules Management System (BRMS) for rule creation and management, and an ETL processing system for data execution. This separation allows business analysts to work independently on rules without affecting code structure, reducing change time from days to hours while maintaining system reliability through defined interfaces.
Solution Approach 2:
The patent extracts business rules from the data processing code and places them in a separate BRMS. This extraction enables business analysts to create, modify, and deploy rules independently without requiring software developer involvement in the SDLC, directly addressing the time loss issue while preserving system control through the extraction mechanism.
2Productivity
If business analysts directly control and implement rule changes through a Business Rules Management System, then the time frame for rule changes is reduced from days to hours, but the complexity of the system increases due to separation of rule management from application code
Solution Approach 1:
The patent introduces an intermediary layer (the BRMS) that sits between business analysts and the ETL processing system. This intermediary handles rule creation, validation, and deployment, allowing business analysts to directly control rule changes with improved productivity while the intermediary manages the complexity of integrating rules with the underlying data processing code.
3Ease of manufacture
If business rules are separated from application code and managed independently through a Rule Development Lifecycle, then costly IT resources are minimized and operational efficiency is enhanced, but the difficulty of integrating rule changes with data processing increases
Solution Approach 1:
The patent creates a universal BRMS that can manage various types of business rules across different data processing contexts. This multi-functional system handles rule creation, validation, versioning, and deployment in a standardized way, reducing integration complexity despite the separation of rules from application code, while minimizing the need for costly IT resources.
Data Source
AI summary
Methods and systems for processing and integrating data. A data file containing data describing a source transaction, associated with an identifier, is received. A type of the source transaction is identified based on a key indicator associated with the data file. The data contained in the data file is mapped to an object model based on the type of the source transaction identified. Output transaction objects are created by processing the data contained in the data file, mapped to the object model, using business rules. The business rules are selected based on a type of the object model. The output transaction objects are received and matched to the source transaction. A target system to receive the output transaction objects is identified based on the identifier associated with the data file.