ERP Test Scenario Template Generation via Module Customization Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current testing approaches for complex software systems, such as ERP systems, require each organization to develop its own testing suite, leading to inefficiencies and prolonged testing processes due to the need for organizations to learn which tests are effective and how to conduct them in a cost-effective manner, despite many organizations using similar software modules and customizations.
Innovation Solution
A method and system for generating and suggesting test scenario templates based on data collected from crowd users, utilizing a computer system that analyzes similarities in software module customizations and components across organizations to create reusable test scenarios, while removing proprietary data to ensure security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each organization develops its own testing suite independently, then the testing can be customized to specific organizational needs, but the testing effort and time are significantly increased
Solution Approach 1:
The patent creates test scenario templates by copying and adapting test scenarios from similar organizations. Instead of creating tests from scratch, organizations can leverage pre-existing test templates that have been validated in similar contexts, significantly reducing testing time while maintaining relevance to organizational needs through customization options.
Solution Approach 2:
The patent establishes a universal test scenario template framework that can serve multiple organizations with similar software systems. The templates are designed to be multi-functional, accommodating different organizational contexts through parameterization and customization, thus reducing redundant testing efforts across organizations while maintaining adaptability.
2Productivity
If organizations share their testing data, then collective testing knowledge can be leveraged to improve efficiency, but proprietary data security risks increase
Solution Approach 1:
The patent extracts and removes proprietary data elements from test scenarios before sharing them across organizations. By separating the valuable testing logic and methodology from organization-specific sensitive data, the system enables knowledge sharing while protecting proprietary information through selective extraction and removal of confidential elements.
Solution Approach 2:
The patent introduces an intermediary processing layer that anonymizes and sanitizes test data before sharing. This intermediary mechanism transforms proprietary test data into generic templates that retain testing value while removing organization-specific sensitive information, thus enabling efficient knowledge transfer without exposing proprietary data.
3Measurement precision
If test scenarios are highly customized for each organization's specific software configuration, then testing accuracy is improved, but the complexity of creating and maintaining tests increases
Solution Approach 1:
The patent segments test scenarios into modular templates with distinct components that can be independently configured. By dividing complex test scenarios into reusable segments organized by software module and customization type, the system maintains testing accuracy for specific organizational configurations while reducing overall complexity through modularization and systematic organization.
Data Source
AI summary
System, method, and non-transitory medium for generating a test scenario template from data collected from users running test scenarios to test vendor-customized packaged application modules. Analysis by a module analyzer of descriptions of vendor-customized packaged application modules is utilized to identify similar customizations to the modules. Additionally, a component analyzer identifies, based on the similar customizations, similar components in the modules. Given a specific run of a test scenario run to test a second instance of a certain module, and a description of similar components that include an indication of at least one component of the second instance that is similar to at least one component of a first instance of the certain module, a template generator may generate a test scenario template for testing the first instance. A data cleaner may be used to remove from the generated test scenario template proprietary data.