Logical Physical Domain Model Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise Application Software faces representational gaps between the user interface and the domain layer, and the domain layer and the data source, leading to complex and inefficient mappings due to the tug-of-war between user interface demands and database complexities.
Innovation Solution
The system splits the domain model into a logical and physical model, internalizing representational gaps within the domain layer, allowing the user interface to be close to the domain and the domain to be close to the data source through object-relational mapping, thereby simplifying object mapping and reducing complexity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a bottom-up approach is used to implement design models, then the database structure is favored and can be easily persisted, but the user interface becomes overly complicated and complex mappings between the user interface and the design model are required
Solution Approach 1:
The patent divides the domain model into two distinct layers: a logical model that represents the pure object-oriented design and a physical model that represents the database structure. This segmentation allows each layer to be optimized independently - the logical model for UI simplicity and the physical model for database persistence, eliminating the need for complex mappings between UI and design model.
2Ease of operation
If a top-down approach is used to implement design models, then the conceptual model is favored and the user interface becomes simpler, but complex database mappings from the design model to the database are required
Solution Approach 1:
By segmenting the domain model into logical and physical layers, the patent allows the logical model to remain simple and close to the user interface while introducing a physical model layer that handles the complex database mappings. This resolves the contradiction by isolating mapping complexity in a dedicated layer rather than propagating it to the UI layer.
Solution Approach 2:
The physical model acts as an intermediary layer between the logical model and the database. It translates the simple logical model into database-specific structures, handling all the complexity of database mappings while allowing the logical model to remain clean and UI-friendly.
3Adaptability or versatility
If the domain model is compromised to satisfy both user interface demands and database complexities, then both UI and database requirements can be met, but the purity of the object model is lost and complexity increases
Solution Approach 1:
The patent resolves this contradiction by segmenting the domain model into two pure layers - a logical model that maintains object-oriented purity for UI compatibility and a physical model that adapts to database requirements. Neither layer needs to be compromised because they serve different purposes and can be independently optimized.
Solution Approach 2:
The patent adds a vertical dimension to the domain model by introducing the physical model layer between the logical model and the database. This dimensional change allows the system to satisfy both UI and database requirements without compromising the purity of either the object model or the database schema, as the transformation happens in the new physical layer.
Data Source
AI summary
Methods and systems for simplifying object mapping for a client request for action. A client request for action may be received from an external interface. The external interface may comprise a human being or a computer program. The client request may be associated to a logical object in order to minimize a representational gap between the client request and a physical object using the logical object. The query request may be responded to using object relational mapping in order to simplify the external interface by minimizing the representational gap between the external interface and the physical object using the logical object.