Customization Abstraction for Software Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Customization of software applications often results in unexpected outputs due to varying user needs and experience levels, as existing systems provide a single level of customization options that are either too complex or too simplistic for different users.

Innovation Solution

A system that determines a user's authorization level to provide customizable operations at appropriate complexity levels, using an abstraction engine and view generator to present visual representations of customizable operations, allowing users to toggle between abstraction levels for tailored customization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a standard software package is extensively customized to meet specific user needs, then the software can be adapted to particular requirements, but the likelihood of unexpected output increases

Engineering Contradiction:
Improvecustomization capabilityVSAvoidoutput predictability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments customization options into multiple levels (first level showing basic options, second level showing advanced options). This segmentation allows users to access detailed customization capabilities when needed while maintaining simplicity for standard operations, thus preserving reliability for common use cases while providing adaptability when required.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The interface dynamically adjusts the level of detail presented based on user interaction. When users select items from the first level, additional customization options at the second level are revealed. This dynamic adaptation allows the system to maintain simplicity by default while providing comprehensive customization when users actively seek it, balancing reliability and adaptability.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If all customization options are presented to every user, then complete customization capability is available, but new or basic users are overwhelmed beyond their understanding

Engineering Contradiction:
Improvecustomization option completenessVSAvoiduser interface simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

Customization options are segmented into a first level showing basic, commonly-used options and a second level showing advanced, detailed options. New and basic users interact only with the first level, maintaining ease of operation. Experienced users can access the second level when needed, preserving complete customization capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by pre-organizing customization options into hierarchical levels before user interaction. The first level presents only essential options that new users need, while advanced options are prepared in the second level for when users require them. This preliminary organization eliminates the need for users to navigate through all options immediately, maintaining simplicity while preserving completeness.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If basic users are presented with advanced customization options, then complete functionality is available, but user efficiency decreases due to information overload

Engineering Contradiction:
Improvefunctionality availabilityVSAvoidcustomization efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the interface into a first level showing basic options and a second level showing advanced options. Basic users can complete their tasks using only the first level, improving productivity by avoiding information overload. Advanced functionality remains available in the second level for when users need it, preserving adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies partial action by presenting only the necessary subset of customization options (first level) to basic users, rather than all available options. This partial presentation improves efficiency for basic users while the complete set of options remains available in the second level for advanced users or when specifically accessed, maintaining full functionality availability.

Inventive Principle:
Principle #16Partial or excessive action

4Ease of operation

If experienced users are presented with basic customization options only, then interface simplicity is maintained, but customization depth is insufficient for their needs

Engineering Contradiction:
Improveinterface simplicityVSAvoidcustomization depth
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The interface is dynamic, allowing experienced users to access the second level of customization options when needed while maintaining the simple first level for routine operations. This dynamic structure preserves interface simplicity for everyday use while providing customization depth when experienced users require it.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system prepares both levels of customization options in advance. Experienced users can quickly access the second level when they need advanced customization without navigating through basic options, maintaining interface simplicity for standard operations while providing customization depth when required.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8209638B2Customization abstraction
Publication Date: 2012.06.26 SAP SE
  • US8209638B2 patent drawing
  • US8209638B2 patent drawing
  • US8209638B2 patent drawing

AI summary

Which one of a plurality of customization levels of a customizable operation of a software application is to be provided to a customizing user of the customizable operation may be determined, wherein each of the plurality of customization levels represents a different level of customization abstraction for customizing the customizable operation at an associated level of complexity. A maintenance view including a visual representation of the customizable operation may be provided, the visual representation corresponding to the determined customization level. A customization to the customizable operation may be received and applied to the customization to the customizable operation to cause the software application to implement the customization during an execution thereof.