Dynamic Usage Checker for Real-Time Software Output Validation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Software testing, particularly in the realm of software quality assurance, faces challenges in exhaustively checking for spelling, grammar, and usage errors, especially in dynamically generated output from running programs, which conventional tools cannot effectively address due to their static nature and the subjective aspects of software quality.

Innovation Solution

A system and method that dynamically checks the output of executing programs for spelling, grammar, and usage errors, providing real-time feedback and logging for potential updates, utilizing a computer program product that includes a processor to execute instructions for analyzing and annotating output, thereby extending beyond conventional static checks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional static spell and grammar checkers are used, then basic language errors can be detected, but they cannot effectively check dynamically generated output from running programs

Engineering Contradiction:

Improvecapability to check dynamically generated outputVSAvoideffectiveness of error detection

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system transitions from static spell checking to dynamic real-time checking by integrating a usage checker that continuously monitors output generated during program execution. The checker receives output dynamically generated by the executing program and provides real-time feedback, making the checking process adaptive to changing program states and dynamically generated content.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

A usage checker is introduced as an intermediary component between the executing program and the user. This mediator captures output from the program, analyzes it for usage errors using contextual information, and provides feedback without interfering with the program's normal operation. The checker acts as a bridge that enables error detection in dynamic content while maintaining program functionality.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Manufacturing precision

If exhaustive testing is performed to ensure software quality, then comprehensive error detection is achieved, but the testing process becomes infeasible for even relatively simple products

Engineering Contradiction:

Improvesoftware qualityVSAvoidtesting feasibility

Core Design Contradiction:

Manufacturing precisionVSProductivity

Solution Approach 1:

The system enables self-service quality assurance by automatically checking output for usage errors during program execution without requiring manual intervention. The usage checker autonomously analyzes dynamically generated output, identifies errors, and provides feedback, allowing the software to self-validate its output quality while maintaining development productivity.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Real-time feedback is provided to users during program execution when usage errors are detected in dynamically generated output. The system immediately notifies users of errors and can suggest corrections, enabling continuous quality improvement without requiring exhaustive post-development testing. This feedback loop allows for iterative quality enhancement throughout the software lifecycle.

Inventive Principle:

Principle #23Feedback

3Measurement precision

If real-time checking of dynamically generated output is implemented, then comprehensive error detection is achieved, but system complexity increases

Engineering Contradiction:

Improveerror detection accuracyVSAvoidchecking system complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The usage checker is designed as a universal component that can check various types of dynamically generated output from different programs using the same interface and processing logic. Rather than requiring separate checking mechanisms for different output types, the system uses a single multi-functional checker that adapts to different contexts, reducing overall system complexity while maintaining comprehensive error detection capability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10169204B2Real-time usage checking of dynamically generated program output

Publication Date: 2019.01.01 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

Receive output dynamically generated by a running program and check that output for spelling, grammar, and/or other usage errors, providing notice to a user of any errors found. The dynamically generated output includes an assembly of component parts not statically assigned in a predetermined configuration or with predetermined content, but rather generated and/or configured by the executing program as it runs.