UI Data Model Abstraction for Modular Storage Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage management software requires significant code modifications when updating underlying data models, and lacks efficiency in handling different user proficiency levels and data storage systems, leading to inefficiencies in user interface design and code reuse.
Innovation Solution
A system comprising a presentation technology service layer, user interaction template service layer, and user interface data model mapping service layer that communicates with business logic and data storage interface layers to perform data storage management tasks, allowing for modular design and code reuse by mapping data between different data models and rendering techniques, and adapting to user proficiency levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If software is developed to utilize a low-level data model and place it in a form appropriate for user interactions, then user interface functionality is achieved, but significant code modifications are required when the underlying data model changes
Solution Approach 1:
The system segments the software architecture into distinct layers: a presentation technology service layer for user interface rendering, a user interaction template service layer for processing user inputs, and a user interface data model mapping service layer for data transformation. This segmentation isolates the mapping logic from the underlying data model, so changes in the low-level data model do not propagate to the user interface code.
Solution Approach 2:
The patent introduces an intermediary mapping service layer that acts as a mediator between the low-level data storage data model and the user interface data model. This intermediary layer handles all data transformations and model conversions, shielding the user interface from changes in the underlying data model structure.
2Adaptability or versatility
If different data storage systems with different low-level data models are supported, then system versatility is improved, but code reuse across systems becomes difficult
Solution Approach 1:
The mapping service layer is designed with universal functionality to handle multiple different low-level data models from various data storage systems. It provides a standardized interface and common mapping patterns that work across different vendors and system types, enabling a single user interface codebase to support diverse storage systems without requiring system-specific code duplication.
3Ease of operation
If user interface is designed to accommodate different user proficiency levels, then user accessibility is improved, but interface complexity increases
Solution Approach 1:
The user interface is designed dynamically to adapt to different user proficiency levels. The mapping service layer can transform data models into different presentation formats based on user profiles, providing simplified views for novice users and detailed technical views for expert users without requiring separate interface code for each user type.
Data Source
AI summary
Described are techniques for performing a data storage management task. A presentation technology service layer renders a user interface for user interaction in accordance with one or more rendering techniques. A user interaction template service layer includes one or more templates. Each of the templates describes processing to perform the data storage management task. A user interface data model mapping service layer communicates with at least one of a business logic service layer and a data storage interface layer to perform one or more operations in connection with the data storage management task and to map data received therefrom in a form for use by the user interface in accordance with a user interface data model.