Integrated Software Feedback Module for Error Prioritization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current error reporting methods for software applications are cumbersome, disorganized, and inefficient, often leading to critical issues being lost in high volumes of unorganized forum posts, and require distracting and difficult remote system interactions for users to provide feedback.

Innovation Solution

A system and method for collecting software development feedback that includes an integrated feedback module within the application user interface, allowing users to easily report issues with a software object, categorize feedback, and prioritize problems, with a feedback data server that publishes user feedback in an interactive forum for public rating and display.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If users report problems through online forums, then feedback can be collected from customers, but the feedback becomes disorganized and critical issues are lost in high volume of posts

Engineering Contradiction:
Improvevolume of feedbackVSAvoidcritical issues lost
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The feedback system segments feedback into different priority levels (critical, high, medium, low) and categories (bug report, feature request, usability issue). This segmentation allows critical issues to be separated from general feedback and receives prioritized attention, preventing them from being lost in the volume of posts.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements automated feedback mechanisms where the application automatically detects errors and generates structured feedback messages. This feedback loop ensures that critical issues are systematically captured and transmitted to developers without relying on manual user reporting.

Inventive Principle:
Principle #23Feedback

2Reliability

If users contact customer service call center, then feedback can be collected, but the process becomes cumbersome and requires remote system interaction

Engineering Contradiction:
Improvefeedback collectionVSAvoiduser interaction complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The application provides self-service feedback mechanisms embedded directly in the user interface. Users can report issues by simply selecting affected elements and providing brief descriptions, without needing to navigate complex forms or communicate with call centers. The system automatically captures error information and transmits it to developers.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The feedback mechanism is merged with the application's user interface, combining the functionality of error detection, feedback collection, and data transmission into a single integrated system. This eliminates the need for separate customer service interactions and remote system connections.

Inventive Principle:
Principle #5Merging (Combining)

3Loss of information

If developers sort through hundreds of forum posts, then all feedback can be reviewed, but the process becomes time-consuming and inefficient

Engineering Contradiction:
Improvefeedback completenessVSAvoiddeveloper efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The system segments feedback by priority level and category, allowing developers to first address critical issues before reviewing other feedback. This segmentation dramatically reduces the time required to identify and address important problems while maintaining completeness of feedback review.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary sorting and categorization of feedback automatically before it reaches developers. Critical issues are pre-identified and prioritized, so developers receive feedback already organized by importance rather than having to sort through unorganized posts.

Inventive Principle:
Principle #10Preliminary action

4Quantity of substance

If users report problems after the fact, then feedback can be provided, but reliance on memory makes sufficient detail difficult to provide

Engineering Contradiction:
Improvefeedback volumeVSAvoidfeedback detail accuracy
Core Design Contradiction:
Quantity of substanceVSMeasurement precision

Solution Approach 1:

The system captures error information and feedback details automatically at the moment the error occurs, before the user needs to remember it. The application records stack traces, error messages, and contextual information automatically, eliminating reliance on user memory for accurate detail provision.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses automated error detection mechanisms as intermediaries between the application and the feedback collection system. These intermediaries capture precise technical details about errors, including stack traces and error messages, and transmit them to developers without requiring users to manually provide such detailed information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8271951B2System and methods for collecting software development feedback
Publication Date: 2012.09.18 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8271951B2 patent drawing
  • US8271951B2 patent drawing
  • US8271951B2 patent drawing

AI summary

A system and method are disclosed for collecting software development feedback. In one embodiment, the method includes collecting a user feedback message associated with a software object. The software object may define a portion of an application user interface. The method may also include categorizing the user feedback message according to a feedback categorization criterion. Additionally, the method may include displaying the user feedback message in a display arranged by a category identified by the categorization criterion.