Parameter Definition Propagation in Business Process Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Software development is inefficient due to the complexity of maintaining data definitions and their associated values, which burdens software developers and increases the cost of developing customized software programs.

Innovation Solution

A method and system for automatically propagating parameter definitions between computer elements by selecting a subroutine, determining unknown parameter definitions, incorporating them into the calling unit, and binding them based on contexts, thereby reducing manual effort and increasing efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software developers manually maintain data definitions and their associated values for sub-routines, then the software can be customized to meet business needs, but the complexity of software development increases and development efficiency decreases

Engineering Contradiction:

Improvesoftware customization capabilityVSAvoiddata definition maintenance complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system enables automatic propagation of parameter definitions from calling units to sub-routines. The computer processor automatically determines unknown parameter definitions, incorporates them, and binds them based on contexts, eliminating the need for manual developer intervention in maintaining data definitions while preserving software customization capability

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary automatic incorporation of parameter definitions into the calling unit before execution. By pre-determining and incorporating unknown parameter definitions and binding them based on contexts, the system prepares the necessary data definitions in advance, reducing the complexity burden during the development and maintenance phases

Inventive Principle:

Principle #10Preliminary action

2Reliability

If software developers manually allocate parameter definitions to sub-routines, then data definitions can be properly associated with routines, but the time and cost of software development increase

Engineering Contradiction:

Improveparameter definition association accuracyVSAvoidparameter definition maintenance time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system uses contextual information from the calling unit as feedback to automatically determine and bind parameter definitions to sub-routines. The computer processor analyzes contexts in the calling unit and uses this feedback to accurately associate parameter definitions without manual intervention, maintaining reliability while reducing time investment

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system replaces the manual mechanical process of allocating parameter definitions with an automated computer processor-based system. The processor automatically determines unknown parameter definitions, incorporates them into the calling unit, and binds them to sub-routines based on contexts, eliminating manual time investment while ensuring accurate associations

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Ease of operation

If developers define data definitions as variables to reduce maintenance burden, then variable usage becomes simpler, but different terminology and concepts are required for program code versus business processes

Engineering Contradiction:

Improvevariable usage simplicityVSAvoidconceptual framework complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system creates a universal parameter definition propagation mechanism that works across both program code and business process management contexts. The computer processor handles parameter definition incorporation and binding using consistent contextual analysis regardless of whether the calling unit is program code or business process logic, eliminating the need for separate conceptual frameworks while maintaining ease of variable usage

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8448194B2Value container propagation in development tools, business process management, and business rules management solutions

Publication Date: 2013.05.21 SAP SE

AI summary

Systems and methods consistent with the invention include propagating parameter definitions between computer elements and may include at least one memory device containing computer readable instructions. Also included is a computer processor executing the instructions on the memory device to perform the steps of selecting a sub-routine to be called by a calling unit. The processor may determine whether a definition for a parameter in the selected sub-routine is known to the calling unit using the computer processor, the calling unit also containing a definition for a parameter. The definitions for the parameters that are unknown to the calling unit are incorporated into the selected sub-routine using the computer processor. The process of the calling unit is executed. The computer processor is used to bind the definition for the parameter in the sub-routine to the definition of the parameter contained in the calling unit.