Solution-Specific Business Object Views via Metadata Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application platforms expose complex business object models that are not user-friendly for customers, as they are designed for internal use and contain more functionality than needed by small- and medium-sized companies, making it difficult for customers to develop user interfaces and applications without direct access to the business object model.
Innovation Solution
The implementation of a metadata repository system that provides solution-specific views of business objects, using a Meta Data Solution View (MDSV) API to filter and simplify metaobject instances, allowing developers to focus on use-case specific views and interactions, while maintaining solution-specific annotations and annotations for filtering and reducing complexity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a complete business object model is exposed to customers, then comprehensive functionality is provided, but complexity increases making it difficult for customers to use
Solution Approach 1:
The patent segments the complex business object model into multiple simplified views, each tailored to specific customer needs and use cases. Instead of exposing the entire model, the system divides it into manageable portions that customers can consume based on their specific requirements, thereby reducing perceived complexity while maintaining comprehensive functionality.
Solution Approach 2:
The patent applies local quality by providing different levels and types of simplification for different customer segments or use cases. Each view of the business object model is customized with appropriate granularity and detail level suited to its specific purpose, allowing customers to work with only the relevant portion of the model at the appropriate level of abstraction.
2Extent of automation
If normalized business objects focused on service provisioning are used, then platform functionality is optimized, but ease of use by customers deteriorates
Solution Approach 1:
The patent introduces simplified views as intermediary layers between the normalized business objects and customers. These views act as mediators that translate the technical service-oriented model into customer-friendly representations, allowing customers to interact with business objects in intuitive ways without requiring understanding of the underlying normalized structure.
3Adaptability or versatility
If all business object functionality is made available, then flexibility for application development is improved, but difficulty of operation for customers increases
Solution Approach 1:
The patent implements dynamic views that can be adapted and configured based on specific customer requirements and use cases. Rather than providing static comprehensive or simplified views, the system allows dynamic adjustment of view characteristics such as granularity, included entities, and relationships, enabling customers to tailor the complexity level to their specific operational needs.
Data Source
AI summary
A computer-implemented system may include one or more storage devices storing first metadata defining an instance of a first metaobject, second metadata defining an instance of a solution supplement metaobject, wherein the second metadata comprises annotations to the first metadata, and wherein the first metaobject and the solution supplement metaobject are instances of a meta-metaobject. Also stored is executable program code of a service to determine merged metadata based on the first metadata and the annotations to the first metadata. A processor is included to execute the executable program code.