Interactive Checkpoint Sequence Fallout Metrics Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web analytics tools lack the ability to efficiently manage and display path analysis data, particularly in web analytics, as they do not retain memory of previous work, leading to redundant report building and inefficient user interaction.

Innovation Solution

The development of tools and techniques that allow for interactive configuration of checkpoint sequences in a user interface, enabling users to modify checkpoints and automatically display corresponding fallout metrics without regenerating data, using software that reuses previously calculated metrics and provides real-time feedback.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the report builder regenerates reports from scratch each time checkpoints are modified, then the report accuracy is maintained, but the time consumption and computational resources increase significantly

Engineering Contradiction:
Improvereport accuracyVSAvoidreport generation time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system pre-calculates and stores fallout metrics for all possible checkpoint pairs in advance. When users modify checkpoints, the system retrieves pre-computed metrics rather than regenerating them, dramatically reducing report generation time while maintaining accuracy through selective validation of affected metrics.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of regenerating entire reports from scratch, the system identifies and updates only the specific fallout metrics affected by checkpoint modifications. This localized update approach maintains report accuracy for modified sections while avoiding redundant calculations for unchanged portions.

Inventive Principle:
Principle #3Local quality

2Device complexity

If the report builder has no memory of previous work, then the system simplicity is maintained, but the productivity decreases due to redundant report building

Engineering Contradiction:
Improvesystem simplicityVSAvoidreport building efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system performs preliminary calculation of all fallout metrics upfront and stores them in memory. This allows the system to quickly retrieve and display metrics when checkpoints are modified, eliminating redundant calculations while maintaining a relatively simple architecture through efficient data caching.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If users can interactively modify checkpoint sequences, then the ease of operation improves, but the device complexity increases due to real-time metric management requirements

Engineering Contradiction:
Improvecheckpoint modification capabilityVSAvoidreal-time metric management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system provides real-time feedback by automatically updating fallout metrics displayed in the user interface whenever checkpoints are modified. This feedback mechanism maintains ease of operation by immediately showing users the impact of their changes without requiring complex manual recalculations, as the system handles metric updates automatically based on pre-computed data.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8006187B1Checkpoint sequence fallout metrics management during path analysis
Publication Date: 2011.08.23 ADOBE INC
  • US8006187B1 patent drawing
  • US8006187B1 patent drawing
  • US8006187B1 patent drawing

AI summary

Tools and techniques are provided for interactive fallout analysis. Checkpoints, such as web pages visited, are defined through user input. As the second and subsequent checkpoints are added, fallout metrics are automatically calculated and displayed for the checkpoint pairs. The user receives fallout information interactively, in response to each change in the sequence of checkpoints, rather than being forced to define all checkpoints and then wait while the fallout metrics are calculated for a batch of checkpoint definition changes. Special coloring or other visualization highlights indicate when the fallout between two checkpoints is total.