Public Solution Model for Enterprise Service Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The direct exposure of a complex business process platform model to application developers is inefficient due to irrelevant complexity, requiring each application to constrain and simplify the model, and lacks fine-granular lifecycle management and efficient navigation paths.
Innovation Solution
A public solution model is introduced, which provides a subset of platform services, simplifying the model by restricting cardinalities, enabling lifecycle management, and offering shortcuts for navigation paths, facilitating application development with a simplified view of business objects and reuse UI blocks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the complete platform model is exposed to application developers, then flexibility and completeness of data access is improved, but device complexity and difficulty of operation increase due to irrelevant complexity
Solution Approach 1:
The platform model is segmented into multiple specialized views (sales view, service view, provisioning view, etc.), each exposing only the subset of business objects and relationships relevant to that domain. This allows developers to work with simplified models tailored to specific application needs while the complete platform model remains intact in the background.
Solution Approach 2:
Specialized views act as intermediaries between the complete platform model and application developers. These views filter and present only the necessary business objects and relationships for specific domains, reducing complexity while maintaining access to the underlying complete model when needed.
2Ease of operation
If each application constrains the platform model to its specific parameters, then ease of operation is improved, but loss of time increases due to redundant simplification work
Solution Approach 1:
The specialized views are pre-configured with domain-specific constraints and relationships (e.g., sales view has 1:1 employee-work agreement relationship). Developers can directly use these pre-simplified models without spending time recreating constraints, while the views are already optimized for their specific domains.
Solution Approach 2:
The platform model framework provides universal mechanisms for defining views, constraints, and relationships that can be applied across multiple domains. The same infrastructure supports sales views, service views, provisioning views, and others, reducing redundant development effort while maintaining domain-specific optimizations.
3Measurement precision
If complete navigation paths are used to reference data, then measurement precision is improved, but loss of time increases due to cumbersome navigation
Solution Approach 1:
The specialized views extract and present only the necessary navigation paths and relationships for their domain. Instead of requiring developers to traverse complete navigation paths through the entire platform model, the views provide direct access to relevant data with simplified paths, maintaining precision while reducing traversal time.
4Reliability
If the platform model allows fine-granular lifecycle management, then reliability is improved, but device complexity increases
Solution Approach 1:
Lifecycle management is segmented and applied at the view level rather than requiring complete platform model management. Each specialized view can independently manage its own lifecycle states (draft, active, deprecated, etc.) for the business objects it exposes, providing fine-grained control without the complexity of managing the entire platform model lifecycle.
Data Source
AI summary
A computer-implemented system may include an application platform comprising a platform model of a plurality of business objects, each of the business objects comprising a model of data and associated logic, and a public solution model comprising a subset of the platform model. The system may also include a business application, wherein a data model and access logic of the business application are defined based on the public solution model, and wherein the application platform is to provide services to the business application based on the data model, the access logic and the platform model.