Reusable Process Code Generation with Parameterized Templates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current methodologies for generating code are complex and resource-intensive, as each unique process requires separate code bases with distinct data and logic, leading to inefficient resource consumption and lack of code reusability across non-similar products.

Innovation Solution

A computing system transforms a set of unique processes into a single reusable process by generating a non-executable code template, integrating project-specific variables and logic, and compiling executable code for efficient reuse.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate code bases are used for each unique process, then each process can be independently developed and maintained, but resource consumption increases significantly and code reusability is lost

Engineering Contradiction:

Improvecode reusabilityVSAvoidresource consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent implements a universal codebase that serves multiple unique processes through parameterization. A single codebase is designed to handle different projects by accepting project-specific parameters and logic, eliminating the need for separate codebases for each process while maintaining the ability to adapt to different requirements.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses parameter changes to adapt a single codebase to different unique processes. By varying parameters such as project variables, logic configurations, and operational settings, the same codebase can generate different executable codes tailored to specific project requirements without duplicating the entire code structure.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If hundreds of unique processes are maintained with separate code bases, then each process has its own distinct data and logic, but the complexity of development and maintenance increases

Engineering Contradiction:

Improveprocess uniquenessVSAvoidcode base complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the codebase into modular components: a universal template structure, project-specific variables, and project-specific logic. This segmentation allows the system to maintain process uniqueness through configurable elements while keeping the overall structure simple and manageable through repetition of the same template across different projects.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of creating entirely separate codebases for each process, the system creates copies of a standardized template structure and populates them with project-specific parameters. This copying approach maintains process distinctness while avoiding the complexity of independent codebase development for each process.

Inventive Principle:

Principle #26Copying

3Ease of operation

If individual code bases are updated separately for each product, then each product can be updated independently, but the time and resources required for updates multiply across all products

Engineering Contradiction:

Improveindependent updatingVSAvoidupdate time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The universal codebase allows updates to be performed once at the template level, and the changes automatically propagate to all project instances. This maintains the ability to update independently while dramatically reducing update time and resources compared to updating separate codebases for each process.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Use of energy by moving object

If a single reusable process is created from multiple unique processes, then resource consumption is reduced, but the ability to handle project-specific variations must be maintained

Engineering Contradiction:

Improveresource consumptionVSAvoidproject-specific customization

Core Design Contradiction:

Use of energy by moving objectVSAdaptability or versatility

Solution Approach 1:

The system uses parameter changes to enable project-specific customization within a single reusable process. By allowing parameters such as variables, logic configurations, and operational settings to be customized per project, the system maintains full adaptability while benefiting from the resource efficiency of a single codebase.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS20250328321A1System and techniques for generating a reusable process

Publication Date: 2025.10.23 CERNER INNOVATION INC

AI summary

A method is performed by one or more processors. The method includes generating a non-executable code template that includes reusable code that defines a set of operations; determining project variables that pertain to a plurality of projects of the set of operations; determining project logic that pertains to the plurality of projects; generating an executable code by integrating the project variables and the project logic into the non-executable code template; and generating a plurality of results by executing the executable code. The plurality of results of the plurality of projects are attained by using the reusable code populated with the project variables and the project logic respectively corresponding to each of the plurality of projects.