Workflow Recommendation Mapping for Synonym and Polysemy Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing requirements engineering methods face challenges in accurately mapping requirement entities to workflow entities due to synonyms, polysemous words, and differing granularities, leading to inefficiencies in workflow recommendation.
Innovation Solution
Establishing determinate mappings between requirement and workflow entities using 'using' and 'used' connections, enabling efficient search and recommendation of candidate workflow entities based on pre-established relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If keyword mapping is used to map requirement entities to workflow entities, then the mapping process is simple and fast, but the mapping accuracy deteriorates due to synonyms, polysemous words, and differing granularities
Solution Approach 1:
The patent introduces an intermediary mapping structure that connects requirement entities to workflow entities through multiple intermediate layers. Instead of direct keyword matching, the system uses intermediate mapping relationships that capture semantic connections, allowing it to handle synonyms and polysemous words effectively while maintaining mapping speed through pre-established mapping tables.
Solution Approach 2:
The patent transforms the traditional one-dimensional keyword matching approach into a multi-dimensional mapping structure. By introducing additional mapping dimensions and intermediate entities, the system can capture complex semantic relationships that simple keyword matching cannot handle, thereby improving accuracy without sacrificing too much speed.
2Adaptability or versatility
If different user groups set different labels for the same meaning or same label for different meanings, then the system can accommodate diverse user preferences, but the feasibility of unified keyword mapping deteriorates
Solution Approach 1:
The patent creates a universal mapping structure that can handle multiple user groups and their different labeling conventions simultaneously. The intermediate mapping layers act as a universal interface that translates between different user group terminologies and the standardized workflow entities, allowing the system to maintain both user flexibility and mapping reliability.
3Adaptability or versatility
If entity categories partially overlap or are different between requirement entities and workflow entities, then the system can represent complex relationships, but the difficulty of using unified labels deteriorates
Solution Approach 1:
The patent segments the mapping process into multiple independent layers and stages. Instead of attempting to unify all entity categories and labels in a single step, the system divides the mapping into intermediate stages that handle different aspects of the relationship separately, making the overall process more manageable and less complex.
Data Source
AI summary
Various embodiments of the teachings herein include a workflow recommendation method. An example includes: receiving a current requirement entity; based on a pre-established determinate mapping between each requirement entity and each workflow entity, using the current requirement entity as a keyword to search the determinate mappings, in order to obtain at least one candidate workflow entity, where a determinate mapping has been established between this at least one candidate workflow entity and the current requirement entity; in the determinate mapping, establishing a connection between the requirement entity and the corresponding workflow entity by a “using” and “used” mapping; and recommending the candidate workflow entity.