Wrapper-Based Runtime Customization of Generic Help Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Automated design and implementation of help systems in graphical user interfaces often result in generic content that does not reflect specific aspects of a product's deployment environment, making customization challenging, especially when features are removed or disabled by resellers or users.

Innovation Solution

A method involving a wrapper that modifies help content files with system-specific information, allowing for customization of help systems while leveraging automated design tools, by instantiating the help system and using wrapper methods to incorporate system-specific details into the generic content.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If automated design tools are used to create help systems, then productivity and ease of manufacture are improved, but the help system content becomes generic and lacks system-specific customization

Engineering Contradiction:
Improvehelp system creation efficiencyVSAvoidhelp system customization capability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The help system is segmented into template content (generated by automated tools) and customizable content (modified by the wrapper). The wrapper separates the generic help system structure from system-specific information, allowing automated generation of the base help system while enabling targeted customization of specific sections without regenerating the entire help system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The wrapper acts as an intermediary between the automated help system generation process and the final customized help system. It receives the generic help system from automated tools and systematically modifies it by injecting system-specific information, thereby bridging the gap between automated efficiency and customization requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If help systems are designed to reflect specific deployment environments, then adaptability and information accuracy are improved, but device complexity and difficulty of manufacture increase

Engineering Contradiction:
Improvehelp system environment specificityVSAvoidhelp system configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

System-specific information is prepared in advance as parameters before the help system is instantiated. The wrapper is pre-configured with methods to inject this information into appropriate locations within the help system template, eliminating the need for complex post-generation customization and reducing overall system complexity.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If help content is customized for removed or disabled features, then information accuracy and reliability are improved, but manufacturing complexity and time increase

Engineering Contradiction:
Improvehelp content accuracyVSAvoidhelp system customization effort
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The wrapper automatically performs the customization task by systematically comparing the target system's feature set against the generic help system template. It self-services the customization process by automatically removing or disabling help content corresponding to removed features, without requiring manual review and editing of each help article, thereby maintaining accuracy while reducing manufacturing effort.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9690444B1Custom help systems by runtime modification of generic help files
Publication Date: 2017.06.27 EMC IP HLDG CO LLC
  • US9690444B1 patent drawing
  • US9690444B1 patent drawing
  • US9690444B1 patent drawing

AI summary

A method delivers a help process customized for a particular operating environment using a help system that initially has more generic content. The method includes obtaining system-specific information about a target system. A wrapper is instantiated by invoking it with the system-specific information as invocation parameters, the wrapper providing wrapper methods for modifying help content files of the help system that initially store the more generic content. The wrapper then (1) instantiates the help system, and (2) uses the wrapper methods to modify the help content files based on the invocation parameters to include the system-specific information instead of or in addition to the more generic content. The help system subsequently uses the help content files as modified in subsequent operation. In operation, the help system reflects the system-specific information, providing desirable customized functionality while leveraging automated design tools used to generate the more generic help system content.