Function Variable Processing System for User-Defined Token Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional software programs and IDE environments fail to distinguish between erroneous and unrecognized user input, leading to user frustration as they often require users to modify input to fit predefined contexts, making the development of mathematical functions inefficient and cumbersome.

Innovation Solution

A method and system that detect user-definable tokens in input, allow users to define these tokens, and associate definitions with them, providing an interactive interface for users to modify and understand the context of their input, thereby simplifying the development process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional software programs use error detection routines to detect unrecognized user input, then error detection capability is improved, but user frustration increases and input modification requirement worsens

Engineering Contradiction:
Improveerror detection capabilityVSAvoiduser frustration and input modification requirement
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments error detection into two distinct categories: erroneous input (syntax errors, invalid operations) and unrecognized input (user-defined variables, custom functions). By separating these detection paths, the system can provide appropriate responses for each type, reducing unnecessary user frustration while maintaining reliable error detection.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary classification layer between error detection and user response. This intermediary identifies whether unrecognized input should be treated as an error or as a user-defined element requiring further processing, thereby mediating between strict error detection and user-friendly operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If software programs require users to modify input to fit predefined contexts, then input validation is improved, but function development efficiency deteriorates

Engineering Contradiction:
Improveinput validationVSAvoidfunction development efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent makes the input validation context dynamic rather than static. Instead of requiring all input to fit predefined contexts immediately, the system allows users to define custom variables and functions, then adapts the validation rules to recognize these user-defined elements in subsequent processing stages.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent performs preliminary classification of input before full validation. By first identifying whether input is erroneous or unrecognized (potentially user-defined), the system can prepare appropriate validation rules in advance, avoiding repeated modification requirements and improving development efficiency.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If software programs treat all unrecognized input as errors, then error detection completeness is improved, but user-defined element recognition deteriorates

Engineering Contradiction:
Improveerror detection completenessVSAvoiduser-defined element recognition
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies different quality standards to different types of unrecognized input. Rather than uniformly treating all unrecognized elements as errors, the system applies local quality assessment: syntax-level unrecognized input is flagged as errors, while semantic-level unrecognized input (potential user-defined variables/functions) is marked for further recognition processing.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent changes the parameter of input recognition from binary (recognized/not recognized) to multi-state (erroneous, unrecognized but valid, user-defined). This parameter change allows the system to maintain complete error detection while simultaneously recognizing user-defined elements through distinct classification paths.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7559028B2Method and apparatus for user function variable processing system and prompt
Publication Date: 2009.07.07 ORACLE INT CORP
  • US7559028B2 patent drawing
  • US7559028B2 patent drawing
  • US7559028B2 patent drawing

AI summary

A user inputs information, such as a mathematical function, composed of variable strings, functions, characters, expressions, etc., into an information input field connected to a function variable processing system. In one embodiment, the function variable processing system breaks down the information into tokens. The tokens are then processed to detect any undefined user definable tokens, e.g., tokens that the user may add and/or change the definitions associated therewith. The function variable processing system generates a display of the undefined user definable tokens along with any associated token definition input fields and/or menus of token definitions. The user may input token definitions using the token definition input fields and/or may select the token definitions from the menus. The function variable processing system associates the undefined user definable tokens with the definitions inputted by the user to convert the undefined user definable tokens to defined user definable tokens. The user definable tokens and associated user inputted definitions are stored and displayed to the user thereof.