Object Level Hierarchy Analysis for Software Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional software testing methods are time-intensive and resource-heavy, often generating false positives when minor UI changes are made, leading to unnecessary detection of bugs during the development process.
Innovation Solution
An object level hierarchy analysis system that compares current and baseline versions of software applications to identify differences, regressions, and bugs by analyzing assembly code data and parent-child relationships between objects, reducing resource usage and improving accuracy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional software testing methods are used to validate applications, then quality control and quality assurance can be achieved, but the process becomes time-intensive and consumes significant computational resources
Solution Approach 1:
The patent segments the application into hierarchical object structures (view hierarchy, object hierarchy) that can be independently analyzed. By dividing the monolithic testing process into object-level comparisons, the system achieves faster validation without sacrificing quality control, directly resolving the contradiction between reliability and time consumption
Solution Approach 2:
The patent creates baseline versions of application hierarchies that serve as reference copies for comparison. Instead of performing exhaustive traditional testing, the system compares current application versions against these copied baseline structures, significantly reducing testing time while maintaining quality assurance through systematic difference analysis
2Reliability
If traditional software testing methods are used to validate applications, then quality control and quality assurance can be achieved, but significant computational resources are consumed
Solution Approach 1:
By segmenting the application into discrete hierarchical objects and comparing only relevant object levels, the system dramatically reduces computational resource consumption. The patent analyzes specific object hierarchies (view, object, element levels) rather than performing full-application traditional testing, achieving quality assurance with minimal energy expenditure
Solution Approach 2:
The patent extracts and analyzes only the critical hierarchical structure elements (view hierarchy, object hierarchy, parent-child relationships) from the complete application. This extraction approach focuses computational resources on essential quality-critical components rather than processing the entire application, reducing overall resource consumption while maintaining quality assurance
3Reliability
If traditional testing methods are used, then software validation can be performed, but false positives of errors or bugs are generated when minor UI changes are made
Solution Approach 1:
The patent segments UI changes into specific hierarchical object categories (view-level changes, object-level changes, element-level changes). By analyzing changes at the appropriate hierarchy level, the system distinguishes between significant functional changes and cosmetic UI modifications, reducing false positives while maintaining accurate bug detection through context-aware hierarchical comparison
4Measurement precision
If detailed analysis of assembly code data and parent-child relationships is performed, then actual bugs can be identified with high accuracy, but the complexity of the validation system increases
Solution Approach 1:
The patent segments the complex validation task into three distinct hierarchical analysis levels: view hierarchy comparison, object hierarchy comparison, and element-level attribute comparison. This segmentation allows detailed bug identification through systematic parent-child relationship analysis while managing system complexity by organizing the validation process into structured, modular hierarchy levels with clear separation of concerns
Data Source
AI summary
Application validation is performed based on object level hierarchy data associated with the application. An application is executed on a physical or emulated host device, and assembly code is generated for the executing application. The assembly code is analyzed to identify objects associated with the application, and to identify relationships between the objects. Based on the object and relationship data, an object level hierarchy is generated for the application. Validation of the application may be performed by comparing an object level hierarchy for a current version of the application to a previously generated hierarchy for a previous version of the application to identify differences between the two hierarchies.