GUI Prototype Interaction Scenario Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for designing graphical user interfaces (GUIs) face challenges in effectively delivering and understanding interaction scenarios, leading to inefficiencies and increased costs due to the complexity of interactions and the need for separate documentation.
Innovation Solution
A method and apparatus for generating and reproducing interaction scenarios of GUI prototypes, which include detecting triggers and responses during user demonstrations, storing and transmitting these scenarios, and allowing for the visualization and reproduction of interactions, enabling clear delivery of changes and improvements to interaction scenarios.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If separate documents describing interactions are delivered along with the prototype, then the developer can understand the interaction details, but time and money are wasted in the documentation process
Solution Approach 1:
The patent merges the interaction documentation with the prototype itself by embedding interaction scenario data directly into the prototype file format. This allows interaction information to be delivered alongside the visual prototype without requiring separate documentation files, thus resolving the contradiction between complete information delivery and time-efficient documentation.
Solution Approach 2:
The patent creates a structured data representation (interaction scenario) that copies and formalizes the interaction behavior observed during prototype demonstration. This copied interaction data is then stored in a machine-readable format within the prototype, enabling automated processing and elimination of manual documentation while preserving complete interaction information.
2Ease of manufacture
If the prototype includes only visual objects without interaction documentation, then the prototype is simple to create, but the developer cannot identify which interactions are included or understand the operation principle
Solution Approach 1:
The patent segments the prototype information into distinct components: visual object data and interaction scenario data. Each interaction scenario is further segmented into triggers, responses, and conditions. This segmentation allows the prototype to maintain simplicity in visual creation while systematically organizing interaction information for complete developer understanding.
Solution Approach 2:
The patent introduces an interaction scenario data structure as an intermediary between the visual prototype and the developer. This intermediary component bridges the gap by providing structured, machine-readable interaction information that enhances developer understanding without complicating the visual prototype creation process.
3Loss of information
If manual documentation of interactions is performed, then detailed interaction information can be provided, but a lot of time and money is wasted
Solution Approach 1:
The patent enables the prototype system to automatically generate and manage interaction documentation through self-service mechanisms. The interaction scenario data is automatically extracted, structured, and stored during the prototype creation process without requiring manual documentation efforts, thus eliminating the trade-off between detailed information delivery and documentation efficiency.
Solution Approach 2:
The patent transforms interaction information from an unstructured or semi-structured format into a standardized parameter-based data structure. By defining interactions in terms of specific parameters (triggers, responses, conditions), the system enables automated processing and storage of interaction details, dramatically improving productivity while maintaining complete information delivery.
Data Source
AI summary
A method for providing an interaction scenario for a prototype of a graphical user interface (GUI) is provided. The method for providing the interaction scenario for the prototype of the graphical user interface (GUI) according to an embodiment of the present inventive concept may include identifying, by a prototype viewing device, a difference between a first version and a second version of the prototype, and generating, by the prototype viewing device, based on the difference, a second version of the interaction scenario by updating a first version of the interaction scenario pre-generated for the first version of the prototype, in which the prototype includes information on the trigger and a response caused by the trigger, and in which the interaction scenario pre-generated for the first version includes information on a plurality of triggers detected during a user's demonstration of the first version of the prototype.