Modular UML Task Interaction Patterns for Flexible UI Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing UML modeling techniques lack flexibility in linking class diagrams to activity diagrams, as they rely on fixed task interaction patterns, limiting the ability to modularize steps within activity diagrams and customize user interfaces.
Innovation Solution
A method and apparatus for generating UML activity diagrams that selectively include or omit nodes based on subtask information from the class diagram, allowing for modular construction of task interaction patterns and enhanced flexibility in user interface design.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If fixed task interaction patterns are used to link class diagrams to activity diagrams, then the modeling process is simplified, but the flexibility and customizability of user interfaces is reduced
Solution Approach 1:
The patent segments task interaction patterns into modular subtask nodes that can be independently selected and configured. Instead of using fixed, monolithic interaction patterns, the system breaks down tasks into reusable subtask components that can be selectively included in activity diagrams, enabling both simplified modeling through reuse and flexible customization through selective composition.
Solution Approach 2:
The patent introduces dynamic configurability to task interaction patterns by allowing selective inclusion or omission of subtask nodes based on specific modeling needs. The system transitions from static, fixed patterns to dynamic, adaptable patterns where the composition of activity diagrams can be customized while still leveraging predefined subtask building blocks.
2Reliability
If all subtask nodes are included in activity diagrams, then completeness of task modeling is improved, but the complexity and number of tasks required increases
Solution Approach 1:
The patent extracts only the necessary subtask nodes from the complete set of available subtasks and includes them selectively in activity diagrams. This extraction approach allows the system to maintain completeness for required tasks while omitting unnecessary subtasks, thereby reducing overall complexity and the number of tasks that need to be managed.
Solution Approach 2:
The patent applies partial action by including only the subset of subtask nodes that are relevant to specific modeling scenarios, rather than incorporating all possible subtasks. This selective inclusion achieves sufficient completeness for each use case without the excessive complexity of comprehensive task coverage.
3Adaptability or versatility
If modular construction of task interaction patterns is implemented, then flexibility in user interface design is improved, but the complexity of linking class diagrams to activity diagrams increases
Solution Approach 1:
The patent segments the linking process into manageable operations: selecting subtask nodes from class diagrams and mapping them to corresponding nodes in activity diagrams. This segmentation of the linking process into discrete, reusable subtask units simplifies the overall complexity by breaking down the mapping task into standardized, modular operations.
Solution Approach 2:
The patent introduces subtask nodes as intermediary elements that facilitate the linking between class diagrams and activity diagrams. These subtask nodes serve as standardized mediators that simplify the mapping process, providing a common interface and structure that reduces the complexity of direct linking operations.
Data Source
AI summary
User modeling facilitates use of a UML user model to define roles, goals, and tasks inside an organization, and defines how the roles, goals, and tasks relate to business entities within the organization. This information can be used to generate a user interface (UI) that facilitates management of the defined business entities within the organization. Each task defined inside the model, which may be represented as a stereotyped class in the UML class diagram, has a number of explicit steps associated with the task. These steps are outlined in UML activity diagrams and defined in a task interaction pattern. A modular approach to constructing UML activity diagram using the task interacting pattern to reduce the size of the model permits greater flexibility in generating the UI.


