Capturing UI Structure for Reusable Business Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In model-based software systems, identifying and reusing business rules across various actions is time-consuming and challenging due to the granularity of business logic, making it difficult for design engineers to implement efficient software design.
Innovation Solution
A method is introduced to capture user interface structure and identify pattern signatures in model-based software systems, allowing for the mapping of user interface elements and events to pattern signatures, which enables the generation of device-independent service and method interfaces, facilitating the reuse of business rules across different actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional data modeling approach is used to capture all business rules and entities, then completeness of system representation is improved, but design complexity and time consumption increase significantly
Solution Approach 1:
The patent segments the monolithic data modeling task into distinct phases: schema design phase for structural modeling and usage phase for business rule identification and reuse. This segmentation allows each phase to focus on specific objectives, reducing overall design complexity while maintaining completeness.
Solution Approach 2:
The patent performs preliminary schema design and data structure establishment before detailed business rule analysis. By preparing the foundational data model first, subsequent business rule identification becomes more efficient, as the structure is already in place to accommodate the rules.
2Manufacturing precision
If detailed business rules are captured at granular level, then implementation accuracy is improved, but difficulty of identifying reusable rules increases
Solution Approach 1:
The patent introduces an intermediary layer of pattern signatures that bridge detailed business rules and reusable patterns. These signatures act as mediators that capture essential characteristics of business rules without requiring full detailed analysis, making reuse identification easier while maintaining implementation accuracy.
Solution Approach 2:
The patent creates simplified copies or representations of business rules in the form of pattern signatures. These signatures capture the essential structure and logic of business rules in a condensed form that is easier to compare and identify for reuse, while the full detailed rules remain available for accurate implementation.
3Reliability
If comprehensive schema design is performed, then system coverage is improved, but time consumption and effort increase
Solution Approach 1:
The patent divides comprehensive schema design into manageable segments: core entity modeling, relationship definition, and business rule integration. This segmented approach allows the design team to cover the entire system while working on smaller, more manageable portions sequentially, reducing overall time consumption.
Solution Approach 2:
The patent designs schema elements with universal applicability in mind, creating data structures and relationships that can serve multiple business rules and functions. This multi-functionality reduces the total number of design elements needed, thereby reducing time consumption while maintaining comprehensive system coverage.
Data Source
AI summary
Method and system for capturing device-independent user interface structure in a model based software system are disclosed. In one embodiment, at least one entry point is received from a user by a business system. Further, a user interface corresponding to the at least one entry point is provided. Furthermore, user interface meta-data associated with the user interface is captured. Also, at least one event associated with user interface elements is identified as a response to user actions based on the captured user interface meta-data. In addition, a pattern signature is identified in the model based software system for reuse in one or more model based software systems based on an expected behavior of the user interface when the identified at least one event occurs. Then, the identified at least one event is mapped to the identified pattern signature.