Business Object Management via XML Abstraction Layer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business Process Management (BPM) systems face challenges in simplifying data and service manipulation for non-technical users, as high-level abstraction often breaks down when XML artifacts are involved, making processes difficult for users to understand and manage.
Innovation Solution
A system and method for creating and managing business objects that presents simplified user interfaces for defining attributes and methods, allowing users to interact with technical assets from a business perspective, while automatically handling underlying XML details and converting between simplified and standard expressions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If high-level abstraction is used in BPM systems, then ease of operation is improved, but device complexity increases when XML artifacts are involved
Solution Approach 1:
The patent introduces business objects as an intermediary layer between the high-level BPM process definition and the underlying XML artifacts. These business objects encapsulate data structures and operations, allowing users to work with simplified representations while the system automatically handles the complex XML transformations and artifacts in the background, thus resolving the contradiction between ease of operation and device complexity
Solution Approach 2:
The patent segments the BPM system into distinct layers: the process definition layer (BPMN), the business object layer (customizable data structures), and the implementation layer (XML artifacts). This segmentation allows each layer to operate independently with its own complexity level, enabling users to work at the simple process definition level while the system manages the complexity of lower layers automatically
2Ease of operation
If simplified user interfaces are presented, then ease of operation is improved, but loss of information increases regarding implementation details
Solution Approach 1:
Business objects serve as an intermediary that preserves implementation information while presenting simplified interfaces. The business objects maintain complete data structures and method definitions internally, allowing the simplified UI to operate without exposing XML complexity to users, thus preventing information loss while maintaining ease of operation
Solution Approach 2:
The patent creates simplified copies or representations of the underlying XML data structures through business objects. These copies present user-friendly interfaces and data models that mirror the essential functionality without exposing the complex XML syntax and structure, allowing users to work with simplified representations while the system maintains the complete implementation details
Data Source
AI summary
A system and method of creating and managing one or more business objects is provided. The method can include receiving a request to create a business object and presenting a first user interface that is used to create a business object. The user interface can include one or more fields that define attributes and methods in the business object. The method can further include presenting a second user interface that is used to add documentation information for the business object, and storing the business object. The attributes and methods of the business object can be stored in separate files.


