Unified Business Process Model Iterative Refinement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current business process solutions either cater to business analysts, providing simulation tools, or to software developers, offering IT-centric executable processes, but fail to bridge the gap between the two, leading to inefficient iterations and fidelity loss due to the need for translation between different models.

Innovation Solution

A method that uses a single business process model to allow multiple classes of users to participate in its refinement, iteratively updating the model based on input from business analysts and software developers, with the model being augmented and refined progressively across different phases, and providing multiple viewpoints to users relevant to their roles, while maintaining traceability and accessibility controls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If two different tools with two different underlying models are used to address needs of both business analysts and software developers, then both user groups can participate in business process modeling, but iterations between business analysts and software developers become difficult and fidelity loss occurs during model translation

Engineering Contradiction:
ImproveAbility to serve both business analysts and software developersVSAvoidFidelity loss during model translation
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent merges the previously separate analyst model and developer model into a single unified business process model. This unified model serves as a common foundation that both business analysts and software developers can work with, eliminating the need for translation between different models and preventing fidelity loss while maintaining the ability to serve both user groups

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If two different tools with two different underlying models are used, then both user groups can participate in business process modeling, but the approach requires translation between the two models which is inefficient

Engineering Contradiction:
ImproveAbility to serve both business analysts and software developersVSAvoidTime consumed in model translation
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent combines separate modeling tools and models into a single unified business process modeling tool and model. This eliminates the time-consuming translation process between different models while maintaining adaptability to serve both business analysts and software developers through a common modeling framework

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If a single unified business process model is used to allow iterative refinement by multiple user classes, then model fidelity is maintained and collaboration is improved, but the device complexity increases to manage multiple viewpoints and accessibility controls

Engineering Contradiction:
ImproveModel fidelityVSAvoidSystem complexity for managing multiple viewpoints
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the unified business process model into different viewpoints that can be selectively presented to different user classes. This segmentation allows the system to manage complexity by providing simplified, role-specific views while maintaining the complete unified model in the background, thus preserving model fidelity without overwhelming users with unnecessary complexity

Inventive Principle:
Principle #1Segmentation

4Productivity

If iterative refinement is enabled for multiple user classes on a single model, then collaboration between business analysts and software developers is seamless, but the ease of operation decreases due to need for managing iterative updates and viewpoints

Engineering Contradiction:
ImproveCollaboration efficiencyVSAvoidEase of managing iterative refinements
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent implements dynamic viewpoint presentation that adapts to the current user and their role. The system dynamically determines which viewpoint to present based on the user class, allowing business analysts to work with high-level process views while software developers access implementation details. This dynamic adaptation maintains ease of operation by automatically adjusting the interface to match user needs while enabling seamless collaboration through shared model access

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7809597B2Progressive refinement model for business processes
Publication Date: 2010.10.05 ORACLE AMERICAN INC
  • US7809597B2 patent drawing
  • US7809597B2 patent drawing
  • US7809597B2 patent drawing

AI summary

In one embodiment, a method for refining a business process model includes receiving business process data pertaining to a first phase of a business process definition from a first class of users, creating a model of a business process using the business process data received from the first class of users, receiving business process data pertaining to a second phase of the business process definition from a second class of users, and augmenting the model of the business process based on the business process data received from the second class of users. The method further includes iteratively refining the model of the business process in response to input provided by the first class of users and/or the second class of users.