Business Concept Registry for Cross-Domain Mapping

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

There is a skills gap between business analysts who model business processes and integration developers who implement them, as existing tools lack sufficient mapping information between business process modeler and implementation domains, leading to inefficient handoffs and difficulties in interpreting exported artifacts.

Innovation Solution

A computer-implemented method and system using a business concept registry to create and export models from a business process modeler domain to an implementation domain, enabling cross-domain mapping by storing and mapping business concepts across different abstraction levels, allowing business analysts to generate IT solutions based on predefined business concepts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If business process models are exported using existing modeling tools, then the models can be transferred to implementation domain, but the exported artifacts are difficult to interpret and insufficient to meet customer needs due to lack of mapping information

Engineering Contradiction:

Improvemapping information between domainsVSAvoidinterpretation of exported artifacts

Core Design Contradiction:

Loss of informationVSEase of operation

Solution Approach 1:

A business concept registry is introduced as an intermediary component that stores and manages mapping information between business process modeler domain and implementation domain. The registry contains business concepts with their corresponding artifacts in both domains, enabling accurate translation and interpretation of exported models without loss of mapping context.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

Mapping relationships between business concepts and implementation artifacts are pre-established and stored in the business concept registry before the actual model export process. This preliminary preparation ensures that when models are exported, the mapping information is already available, eliminating interpretation difficulties.

Inventive Principle:

Principle #10Preliminary action

2Productivity

If business analysts handoff models as guidelines for integration developers to create integrated solutions from scratch, then the skills gap between business analysts and integration developers is addressed, but the process becomes inefficient and time-consuming

Engineering Contradiction:

Improveefficiency of handoff processVSAvoidtime for creating integrated solutions

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

Instead of requiring integration developers to create integrated solutions from scratch, the system copies and transforms business process models into implementation domain artifacts using pre-defined mappings in the business concept registry. This copying process with automated transformation significantly reduces the time and effort required while maintaining accuracy.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system automatically changes parameters and transforms business process model elements into implementation domain equivalents by retrieving corresponding mappings from the business concept registry. This parameter transformation enables efficient conversion without manual recreation, improving productivity while reducing time loss.

Inventive Principle:

Principle #35Parameter changes

3Measurement precision

If detailed mapping information is maintained between business process modeler and implementation domains, then accurate cross-domain mapping is achieved, but the system complexity increases

Engineering Contradiction:

Improveaccuracy of cross-domain mappingVSAvoidcomplexity of mapping system

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The business concept registry serves as a universal repository that handles multiple functions: storing business concepts, maintaining mapping relationships, and providing access to both business process modeler and implementation domain artifacts. This multi-functional approach consolidates complexity into a single centralized system rather than distributing it across multiple components.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11315208B2Conceptual representation of business processes for cross-domain mapping

Publication Date: 2022.04.26 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A computer-implemented method, system, and computer program product for cross-domain mapping between a business process modeler domain and an implementation domain are provided. The method includes accessing a business concept registry on a data storage device including business concepts with mapping for the business process modeler domain and the implementation domain. The method also includes creating a model with one or more of the business concepts interconnected to represent a business process in the business process modeler domain, and exporting the model from the business process modeler domain to the implementation domain according to the business concept mapping of the business concept registry.