Metadata-Driven ERP Testing Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Custom ERP software development is costly and time-consuming due to the need for developers to modify and test software features, which is prohibitive for companies with varying needs and frequent changes.

Innovation Solution

A no-code testing system that allows users to modify and test custom ERP software by identifying metadata chunks and executing test actions within a test framework, highlighting any unexpected results, thereby reducing the need for developer intervention and costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom ERP software is developed to meet specific company needs, then the software can be tailored to individual requirements, but the cost and development time increase significantly

Engineering Contradiction:
Improvesoftware customizationVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments ERP functionality into reusable metadata templates and action flows that can be independently configured. Instead of building custom software from scratch, companies select and configure pre-defined metadata templates (e.g., user profiles, workflows, dashboards) and action flows (e.g., data synchronization, report generation), significantly reducing development time while maintaining customization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system allows dynamic parameter changes through metadata-driven configuration. Companies can modify software behavior by changing metadata parameters (e.g., field names, data types, workflow steps) rather than rewriting code. This enables rapid adaptation to different company requirements using the same core platform, reducing both development time and cost.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If custom software is built for each client, then specific needs are met, but upgrading and fixing common software elements becomes difficult and time-consuming

Engineering Contradiction:
Improveclient-specific customizationVSAvoidsoftware maintenance
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal ERP platform where common software elements are implemented as reusable metadata templates and action flows that serve multiple clients. Instead of building separate custom applications for each client, the same metadata templates (e.g., standard user management, approval workflows) can be deployed across different clients with minimal configuration, simplifying maintenance and upgrades.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses metadata templates as copyable blueprints that can be replicated across different client implementations. When updates are needed, the metadata templates are updated once and automatically propagate to all client instances, eliminating the need to manually update each custom application and reducing maintenance complexity.

Inventive Principle:
Principle #26Copying

3Reliability

If traditional ERP software is used with superfluous features, then standard functionality is provided, but unnecessary features increase cost and complexity

Engineering Contradiction:
Improvestandard ERP functionalityVSAvoidsoftware feature set
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by enabling companies to activate only the metadata templates and action flows relevant to their specific needs. Instead of implementing all standard ERP features universally, the system allows selective configuration of local functionalities (e.g., manufacturing modules for manufacturing companies, retail modules for retail companies), reducing overall system complexity while maintaining necessary standard functionality.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12253938B2Automated testing for metadata-driven custom applications
Publication Date: 2025.03.18 NEXTWORLD LLC
  • US12253938B2 patent drawing
  • US12253938B2 patent drawing
  • US12253938B2 patent drawing

AI summary

In non-limiting examples of the present disclosure, systems, methods and devices for assisting with testing custom application software are provided. An input that modifies an application action may be received. A request to execute a test action corresponding to the application may be received. One or more test steps for executing the test action may be identified. Each of the one or more test steps may be executed in a test framework utilizing test metadata. A determination may be made as to whether an unexpected result occurred during the execution of the one or more steps. If an unexpected result is determined to have occurred, a graphical representation of the unexpected result may be caused to be displayed.