Graphical Editor for Business Process Ontology Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing business process design environments face challenges in creating and managing business architecture projects, as they often require building new model templates without a common ontology, leading to inefficiencies in defining business capabilities and processes.

Innovation Solution

A graphical editor is introduced within the business process design environment, comprising a model component, view component, and controller component, which allows users to create, edit, and link business architecture projects, business process management projects, and business processes using a common pool of metamodels with shared ontology, enabling attributes like goals, objectives, and value chains to be defined and synchronized.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a common pool of metamodels with shared ontology is introduced, then model creation efficiency and synchronization capability improve, but system complexity increases

Engineering Contradiction:
Improvemodel creation efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a common pool of metamodels that serves multiple purposes: defining business architecture projects, business process management projects, and business processes across different domains. This universal metamodel pool eliminates the need to create separate model templates for each project type, thereby improving model creation efficiency while managing complexity through standardized reusability.

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

Solution Approach 2:

The system segments the complex modeling task into distinct layers: the ontology layer (common pool of metamodels), the model layer (project-specific models), and the instance layer (actual business processes). This segmentation allows the common ontology to provide efficiency benefits while isolating complexity into manageable, reusable components that can be independently maintained.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple models are linked and synchronized, then collaboration capability improves, but data management complexity increases

Engineering Contradiction:
Improvecollaboration capabilityVSAvoiddata management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements synchronization mechanisms that provide feedback loops between linked models. When changes are made to one model, the system automatically detects and propagates relevant changes to connected models, ensuring consistency across the business architecture. This feedback-based approach enables seamless collaboration while automating the data management complexity that would otherwise require manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The common pool of metamodels acts as an intermediary layer between different project models. Instead of directly linking disparate models, the shared ontology serves as a mediator that standardizes connections and synchronization rules, thereby improving collaboration capability while managing data management complexity through a controlled interface layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9846849B2System and method for providing an editor for use with a business process design environment
Publication Date: 2017.12.19 ORACLE INT CORP
  • US9846849B2 patent drawing
  • US9846849B2 patent drawing
  • US9846849B2 patent drawing

AI summary

A system and method for providing an editor for use with a business process design environment. In accordance with an embodiment, the system provides an editor and framework that allows a user to create and edit business processes and business architecture projects. The editor can render or edit a model which is based on a metamodel or defined ontology, and can be provided, e.g., in computer applications, browsers and tablets. In accordance with an embodiment, the user can use the editor to define a business process and/or a business architecture project, including attributes such as goals, objectives, strategies, and value chains. Models can be synchronized as part of an overall business process development.