Runtime Functional Block Analysis for Business Code Alignment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a disconnect between individuals writing code for automated processes and those designing business models, lacking effective means to bridge this gap during development of business process models and corresponding software code.

Innovation Solution

A method and system that generate product behavior information based on functional blocks executed from source code at runtime, allowing for the creation of product behavior documents that provide a high-level view of the flow of processes, facilitating cooperation between software developers and business model developers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If source code is executed to implement automated processes, then productivity is improved, but the disconnect between code developers and business model designers worsens due to lack of visible process flow information

Engineering Contradiction:
Improveautomated process executionVSAvoidprocess flow information
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system introduces an intermediary mechanism that captures execution data from functional blocks during runtime and transforms it into product behavior documents. This intermediary layer bridges the gap between code execution and business process visibility, allowing both developers and business model designers to access the same process flow information without disrupting the automated execution pipeline.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates a copy of the execution information by generating product behavior documents that mirror the actual runtime behavior of the source code. These documents serve as a faithful representation of the process flow, making invisible execution dynamics visible to stakeholders who need to understand business processes without modifying the executing code.

Inventive Principle:
Principle #26Copying

2Manufacturing precision

If detailed source code is used to implement business processes, then manufacturing precision is improved, but ease of operation worsens due to difficulty in understanding process flows

Engineering Contradiction:
Improveprocess implementation accuracyVSAvoidprocess flow understanding
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The system segments the complex source code execution into discrete functional block information that can be individually tracked and documented. By breaking down the execution flow into manageable units with embedded identifiers, the system maintains precise tracking of each operation while presenting a simplified, high-level view of the overall process flow to users.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system adds another dimension to process visibility by creating product behavior documents that represent execution information in a different format and level of abstraction. Instead of viewing raw source code, users access a dimensional transformation of the same information that highlights business process flows, making complex code operations understandable without losing precision.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Productivity

If functional blocks are executed during runtime, then productivity is improved, but device complexity increases due to need for embedded information tracking

Engineering Contradiction:
Improveruntime execution efficiencyVSAvoidinformation tracking system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by embedding functional block information into the source code before execution. This advance preparation includes inserting identifiers and metadata that enable automatic tracking during runtime without requiring complex real-time analysis. The embedding step simplifies the runtime processing by pre-organizing the information structure needed for document generation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11842126B2System for generating a high-level product behavior document based on embedded information in functional blocks executed during runtime of source code
Publication Date: 2023.12.12 DELL PROD LP
  • US11842126B2 patent drawing
  • US11842126B2 patent drawing
  • US11842126B2 patent drawing

AI summary

A method, system and computer-usable medium are disclosed for generating product behavior information based on functional blocks executed from source code at runtime during a product use scenario. Certain embodiments of the method may include: executing source code in a product use scenario, where the source code includes a plurality of functional blocks executed to implement the product use scenario, where the plurality of functional blocks are configured with embedded functional block information; and generating product behavior information for the product use scenario using the embedded functional block information of functional blocks executed during run time of the source code in the product use scenario. In certain embodiments, the product behavior information may be used to generate one or more product behavior documents for one or more of the product use scenarios.