Product Testing Quality Scoring System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Product testing is often lengthy and complex, and existing systems fail to comprehensively evaluate the quality of testing, potentially missing critical aspects of a product's functionality.

Innovation Solution

An electronic system that connects product developers with a network of testers, utilizing data retrievers to gather usage and testing data, and a processing unit to compute a score indicating the quality of testing based on actual usage and testing metrics, ensuring thorough coverage of product features.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If comprehensive product testing is performed covering all aspects of the product, then the quality of product testing is improved, but the time required for testing increases

Engineering Contradiction:
Improvequality of product testingVSAvoidtesting duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements feedback by continuously monitoring actual product usage data and comparing it with testing coverage data. This feedback loop enables the system to identify gaps between what has been tested and what is actually used, allowing for targeted improvements in testing quality without requiring comprehensive re-testing of all product aspects.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system applies partial action by focusing testing efforts on the most critical and frequently used product features based on actual usage data. Rather than uniformly testing all aspects equally, the system concentrates resources on areas with highest impact, achieving adequate testing quality for essential functions while reducing overall testing time.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If product testing covers all technical features under different parameters, then the completeness of testing is improved, but the complexity of the testing process increases

Engineering Contradiction:
Improvecompleteness of testing coverageVSAvoidtesting process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the product into distinct technical features and functionality areas, allowing independent tracking and evaluation of testing coverage for each segment. This segmentation enables the complex testing process to be broken down into manageable units that can be monitored and evaluated separately, reducing overall process complexity while maintaining comprehensive coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements a universal evaluation framework that can assess testing coverage across diverse product features and parameters using a common methodology. This multi-functional approach allows the same system to evaluate various types of product features (software, hardware, integration) through unified metrics and processes, simplifying the management of complex testing requirements.

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

3Measurement precision

If detailed tracking of actual product usage is implemented, then the accuracy of testing evaluation is improved, but the amount of data processing required increases

Engineering Contradiction:
Improveaccuracy of testing evaluationVSAvoiddata volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system extracts and isolates only the most relevant usage data points that directly impact testing evaluation accuracy. Rather than processing all available usage data, the system identifies and extracts key metrics such as feature usage frequency, critical path interactions, and anomaly patterns, reducing data volume while maintaining evaluation precision.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies different levels of data collection and processing intensity to different product features based on their importance and usage patterns. High-criticality features receive detailed tracking and analysis, while lower-priority features use summarized metrics, optimizing the balance between evaluation accuracy and data processing requirements across the product portfolio.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11947447B2Systems and methods for evaluating product testing
Publication Date: 2024.04.02 RAINFOREST QA INC
  • US11947447B2 patent drawing
  • US11947447B2 patent drawing
  • US11947447B2 patent drawing

AI summary

An electronic system includes a first data retriever to communicate with a first database associated with an analytic tool, and a second data retriever to communicate with a second database associated with an electronic testing device; wherein the analytic tool is configured to store information regarding actual usage of a product in the first database; wherein the electronic testing device is configured to store product testing data for the product in the second database; wherein the first data retriever comprises a first communication interface to electronically receive the information; wherein the second data retriever comprises a second communication interface to electronically receive the product testing data; and wherein the electronic system further comprises a processing unit configured to compute a score indicating a quality of product testing for the product based on the information regarding the actual usage of the product and/or the product testing data.