Web Service UI Annotation Repository for Automated Interface Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The development of user interfaces for web service-based applications is time-consuming and expensive, as existing technical service descriptions lack sufficient information to generate reasonably usable UIs, requiring manual creation of UI annotations which is inefficient.

Innovation Solution

A computer-implemented method that receives a technical service description and UI annotations, refines UI elements based on edits, and stores these annotations in a repository, allowing for automatic generation of UIs by selecting and ranking annotations based on usage frequency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual creation of UI annotations is performed, then UI quality and usability are improved, but development time and cost increase

Engineering Contradiction:
ImproveUI usabilityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system copies existing annotations from the annotation repository to the current UI element being developed. Instead of manually creating annotations from scratch, the system retrieves and reuses pre-defined annotations that have been previously created and stored, significantly reducing development time while maintaining consistent UI quality across the application.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

Annotations are pre-defined and stored in the annotation repository before actual UI development occurs. This preliminary creation of annotations allows developers to simply reference and apply them during UI development, rather than creating them manually during the development process, thus reducing development time and cost.

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If manual creation of UI annotations is performed, then annotation accuracy is improved, but productivity decreases

Engineering Contradiction:
Improveannotation accuracyVSAvoidannotation creation efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system copies proven, pre-tested annotations from the repository rather than manually creating new ones. This ensures annotation accuracy is maintained through reuse of validated annotations while dramatically improving productivity by eliminating repetitive manual creation work.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system automatically retrieves and applies annotations from the repository based on UI element properties, reducing the need for manual annotation creation. The system serves itself by automatically matching UI elements with appropriate pre-defined annotations, improving both accuracy and productivity.

Inventive Principle:
Principle #25Self-service

3Reliability

If technical service descriptions are enhanced with detailed information, then UI generation quality is improved, but system complexity increases

Engineering Contradiction:
ImproveUI generation qualityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments UI annotation information into separate, reusable annotation objects stored in the repository. Instead of embedding all annotation details within the technical service description, the system separates concerns by storing annotations independently and linking them to UI elements, improving UI generation quality without significantly increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The annotation repository acts as an intermediary between the technical service description and the UI generation process. It provides the necessary detailed information for high-quality UI generation while shielding the technical service description from direct complexity, as annotations are retrieved through standardized interfaces rather than being embedded in the service description itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If UI annotations are created manually for each web service, then customization is improved, but time consumption increases

Engineering Contradiction:
ImproveUI customizationVSAvoidannotation creation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system copies annotations from the repository that can be customized for specific web services. Pre-defined annotation templates provide a foundation that can be adapted to different UI requirements, maintaining customization capability while reducing the time needed to create annotations from scratch for each web service.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The annotation repository stores universal annotation templates that can be applied across multiple different web services and UI elements. These multi-functional annotations reduce the need to create custom annotations for each individual service, thereby reducing time consumption while maintaining the ability to customize UIs as needed.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8914738B2Community-based web service user interface annotations
Publication Date: 2014.12.16 SAP SE
  • US8914738B2 patent drawing
  • US8914738B2 patent drawing
  • US8914738B2 patent drawing

AI summary

Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for receiving, at a computing device, a technical service description associated with a web service, receiving, from an annotation repository, one or more first annotations to one or more user interface (UI) elements associated with the technical service description, the annotation repository electronically storing annotations to UI elements, refining at least one of the one or more UI elements based on one or more edits to the one or more UI elements, extracting one or more second annotations based on the one or more edits, and providing the one or more second annotations for storage in the annotation repository.