Parameterized Code Templates for Reusable Project Process Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate 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 variables and logic, and compiling executable code for efficient reuse across projects.

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 versatilityVSLoss of energy

Solution Approach 1:

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

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

Solution Approach 2:

The patent transforms fixed codebases into parameterized codebases where process-specific variations are achieved through parameter changes rather than code modifications. By defining processes in terms of adjustable parameters and configurations, the system enables a single codebase to generate multiple unique processes dynamically, reducing resource consumption while preserving adaptability.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If hundreds of unique code bases are maintained, then each process has dedicated functionality, but development and maintenance complexity increases

Engineering Contradiction:
Improveprocess functionalityVSAvoidcodebase management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple separate codebases into a single unified codebase that serves all unique processes. By combining previously separate codebases into one parameterized system, the patent reduces management complexity while maintaining dedicated functionality for each process through parameter-specific configurations and process definitions.

Inventive Principle:
Principle #5Merging (Combining)

3Ease of operation

If individual updating processes are executed for each code base, then each process can be updated independently, but time and resource intensity increases

Engineering Contradiction:
Improveindependent updatingVSAvoidupdate time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent enables a single updating process to update all processes simultaneously through the universal parameterized codebase. By designing the codebase to handle multiple processes universally, updates can be applied once to the shared codebase and automatically benefit all processes, eliminating the need for repetitive individual updating while preserving independent process functionality.

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

Data Source

PatentUS12373176B2System and techniques for generating a reusable process
Publication Date: 2025.07.29 CERNER INNOVATION INC
  • US12373176B2 patent drawing
  • US12373176B2 patent drawing
  • US12373176B2 patent drawing

AI summary

In some aspects, a method can be performed by a processor of a computing device. The method includes generating a non-executable code template that includes code that defines a set of operations. Additionally, the method includes accessing data about a particular project. Further, the method includes determining a set of project variables that pertain to the particular project and determining a set of project logic that pertains to the particular project. Furthermore, the method includes generating an executable code by integrating the set of project variables and the set of project logic into the non-executable code template. Moreover, the method includes compiling the executable code and generating a result by executing the compiled executable code.