Dynamic Business Logic Database Decouples HMI Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Human Machine Interface (HMI) applications require significant resources and incur risks due to the need to finalize business logic before developing the HMI, leading to inefficient development cycles and a lack of proficiency in managing changes between business logic and user interface.
Innovation Solution
A dynamic Business Logic (BL) Database (DB) system that receives BL specifications, generates state charts, and updates BL data, allowing for integration with HMI applications without requiring complete redevelopment, enabling decoupling of business logic from the HMI and independent updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If business logic is finalized before HMI development, then HMI development can proceed without frequent changes, but the entire HMI application must be changed when business logic changes, leading to huge resource consumption
Solution Approach 1:
The patent segments the HMI application into distinct modules: HMI scene development module and business logic module. The business logic is extracted into a separate database that can be independently developed, updated, and managed without affecting the HMI scenes. This segmentation allows parallel development and independent updates of business logic while maintaining stable HMI interfaces.
Solution Approach 2:
The patent extracts business logic from the HMI application and stores it in a separate database. This extraction enables the business logic to be independently modified, updated, and managed without requiring changes to the HMI application structure. The HMI scenes reference business logic through identifiers rather than embedded code, allowing logical decoupling.
2Adaptability or versatility
If HMI is changed according to changes in business logic, then the HMI remains up-to-date with business requirements, but the entire HMI application has to be changed even for minor business logic updates
Solution Approach 1:
The patent divides the system into independent HMI scene modules and business logic database modules. Changes in business logic only affect the database portion, while HMI scenes remain structurally intact. The segmentation allows selective updates without propagating changes throughout the entire HMI application.
Solution Approach 2:
The patent implements dynamic loading of business logic from the database at runtime. The HMI application can adapt to business logic changes without requiring recompilation or structural modifications. The system dynamically references updated business logic through identifiers, enabling flexible adaptation while maintaining stable HMI structures.
3Ease of manufacture
If business logic and HMI are tightly integrated, then development is straightforward with direct mapping, but changes in either require changes in the other, incurring huge resource costs
Solution Approach 1:
The patent extracts business logic into a separate database entity that can be independently developed and maintained. The HMI scenes reference business logic through logical identifiers rather than direct code integration. This extraction eliminates the coupling that causes cascading changes, allowing independent updates without time-consuming synchronization across the entire system.
Solution Approach 2:
The patent introduces a business logic database as an intermediary layer between HMI scenes and actual business logic implementation. This intermediary decouples the direct relationship, allowing changes in one layer without affecting the other. The database acts as a buffer that absorbs changes and provides stable interfaces to HMI scenes.
4Productivity
If business logic is finalized early to avoid changing HMI, then HMI development can proceed smoothly, but risks are involved while finalizing business logic before HMI development
Solution Approach 1:
The patent enables preliminary development of HMI scenes with placeholder references to business logic identifiers. The actual business logic can be developed, tested, and refined in the database independently before full integration. This preliminary action allows HMI development to proceed without waiting for business logic finalization, reducing risks while maintaining productivity.
Solution Approach 2:
The patent implements a dynamic architecture where business logic can be updated in the database at any stage without affecting HMI structure. The system dynamically loads and applies business logic from the database, allowing continuous refinement and updates. This dynamic approach eliminates the need for early finalization while maintaining development momentum.
Data Source
AI summary
The present disclosure discloses a method and system for integrating a dynamic Business Logic (BL) Database (DB) with a Human Machine Interface (HMI) application. The method comprises receiving a Business Logic (BL) specification. The BL specification comprises BL data and one or more parameters associated with the BL data. Further, one or more state charts of the BL data are generated from the BL specification. Thereafter, a dynamic BL DB is developed based on the one or more parameters and the one or more state charts. Furthermore, the BL data in the dynamic BL DB is updated when the BL data in the BL specification is updated. Lastly, the dynamic BL DB is integrated with a HMI application utilizing the BL data to implement the BL. The HMI application retrieves the updated BL data from the dynamic BL DB for implementing updated BL.