Business Process Modeling Method for SOA Alignment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current business transformation methods lack effective integration of legacy business models and reference models, leading to a disconnection between business goals and IT implementation, and fail to efficiently generate IT solutions from business models using Service-Oriented Architecture (SOA).
Innovation Solution
A method and system that constructs a first analysis model from legacy business process models, analyzes it with business process reference models, derives a second analysis model, and refines it to obtain a design model, thereby aligning business processes with industry best practices and ensuring seamless integration with IT solutions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If BPM approaches are used to create business process models from scratch, then business-oriented view on functional units of work is achieved, but existing model-based assets are not preserved and modeling and development initiatives remain separated
Solution Approach 1:
The patent applies preliminary action by constructing an AS-IS analysis model from existing legacy business process models before creating the TO-BE model. This preserves existing model-based assets by analyzing and documenting current processes before redesign, ensuring that valuable information from legacy systems is not lost during transformation.
Solution Approach 2:
The patent implements nesting by integrating multiple modeling layers within a unified framework. The AS-IS analysis model, TO-BE analysis model, and design model are nested within each other, with each layer building upon and incorporating elements from previous layers, thereby preserving existing assets while enabling progressive transformation.
2Productivity
If top-down approach is used in BPM to derive TO-BE business process model, then business process improvement is achieved, but connection to IT-driven design and implementation process is lost
Solution Approach 1:
The patent introduces the TO-BE analysis model as an intermediary between the AS-IS analysis model and the design model. This intermediary layer serves as a bridge that connects business process improvement objectives with IT-driven design and implementation, ensuring that business goals are properly translated into technical specifications without losing connection between domains.
Solution Approach 2:
The patent segments the modeling process into distinct phases: AS-IS analysis, TO-BE analysis, and design model creation. Each segment serves a specific purpose and produces deliverables that feed into the next phase, creating a structured pathway that maintains connection between business and IT domains while enabling efficient process improvement.
3Device complexity
If legacy business process models are not integrated with reference models, then modeling simplicity is maintained, but disconnection between business goals and IT implementation occurs
Solution Approach 1:
The patent merges legacy business process models with business process reference models by analyzing both together in the AS-IS analysis phase and integrating their elements in the TO-BE analysis phase. This combination ensures that existing organizational knowledge from legacy models is preserved while incorporating industry best practices from reference models, thereby aligning business goals with IT implementation without excessive complexity.
Data Source
AI summary
A method for modeling business transformation includes steps of: constructing a first analysis model based on at least one legacy-business-process-model; and analyzing the first analysis model in conjunction with at least one business-process-reference-model. The method further includes deriving a second analysis model in response to analyzing the first analysis model in conjunction with the at least one business-process-reference-model and refining the second analysis model to obtain a design model.