Automated Subroutine Repository Maintenance via Usage Log Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Manual maintenance of subroutines in software testing is inefficient and impractical for large software products with numerous and continuously updated subroutines, requiring significant manual intervention and time.
Innovation Solution
An automated system that analyzes logs of subroutine usage to identify and update a repository of subroutines, comparing identified subroutines against a repository of applicable subroutines, and designating matching subroutines, thereby reducing manual intervention and increasing efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual maintenance of subroutines is performed, then accuracy of subroutine repository can be maintained, but productivity and time consumption deteriorate significantly
Solution Approach 1:
The system automatically maintains the subroutine repository by analyzing logs and identifying subroutines used by the application under test, eliminating the need for manual intervention. The system serves itself by continuously updating the repository based on observed usage patterns.
Solution Approach 2:
The patent replaces the manual mechanical process of creating and maintaining subroutines with an automated computer-based system that analyzes logs and generates subroutines automatically, substituting human effort with computational processes.
2Adaptability or versatility
If the number of subroutines increases with large software products, then functionality improves, but device complexity and difficulty of maintenance increase
Solution Approach 1:
The system segments the large software product into individual subroutines by analyzing logs and identifying distinct functional units. Each subroutine represents a discrete, manageable component that can be independently maintained and reused.
Solution Approach 2:
The patent creates a universal subroutine repository that can serve multiple testing scenarios and applications. Subroutines are designed to be reusable across different test cases, reducing overall system complexity through consolidation of common functionality.
3Adaptability or versatility
If manual creation of new subroutines is performed, then adaptability to new functions improves, but loss of time and productivity worsen
Solution Approach 1:
The system performs preliminary analysis of application logs to identify potential subroutines before they are explicitly needed for testing. By proactively analyzing usage patterns and pre-defining subroutines, the system eliminates the time required for manual creation when new testing scenarios arise.
Solution Approach 2:
The system continuously monitors application logs and uses feedback from actual usage patterns to automatically create and update subroutines. This closed-loop feedback mechanism ensures the repository remains current with minimal manual intervention.
Data Source
AI summary
Embodiments of the invention relate to maintaining a repository of subroutines used by a software program under test based on an analysis of subroutine usage logs. One aspect of the invention concerns a system for analyzing a log of subroutine usage by an application under test to identify subroutines used by the application based on actions in the subroutines, and comparing the identified subroutines against a repository of subroutines applicable to the application. The system may further designate a subroutine in the repository as a matching subroutine, modify or delete a subroutine, or add a new subroutine to the repository.