Hierarchical Personalization Data Management for Software Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large computer systems face challenges in managing and maintaining personalization data for multiple end-users, requiring significant resources for data transfer, harmonization, and maintenance, with existing methods being inflexible and not addressing the origin of personalization data effectively.
Innovation Solution
Implementing a system with two levels of personalization - administrative and individual - where default values are determined at program start-up, allowing end-users and administrators to set personalized data in a hierarchical structure, with automatic determination options, reducing redundancy and complexity through a personalization hierarchy and dialog interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If personalization data is stored for each end-user in large computer systems, then user-specific software execution is improved, but resource usage for data transfer and harmonization increases significantly
Solution Approach 1:
The patent segments personalization data into two distinct levels: administrative personalization data (set by administrators) and individual personalization data (set by end-users). This segmentation allows the system to manage personalization data more efficiently by separating concerns between centralized configuration and user-specific preferences, reducing the overall resource burden while maintaining user-specific execution capabilities
Solution Approach 2:
The patent implements preliminary determination of default values for personalization data at program start-up. By pre-determining these default values before actual software execution, the system reduces the need for extensive data transfer and harmonization during runtime, thereby lowering resource usage while still enabling user-specific personalization
2Adaptability or versatility
If end-users maintain their own personalization data, then user flexibility is improved, but user effort and time expenditure increase
Solution Approach 1:
The patent provides administrators with the capability to pre-configure administrative personalization data for multiple end-users before they access the software. This preliminary action by administrators significantly reduces the time and effort end-users would otherwise spend on personalization, while users retain the flexibility to modify their individual preferences when needed
Solution Approach 2:
The patent implements a hybrid approach where end-users can maintain and modify their own individual personalization data through simplified interfaces, while administrative personalization data is managed by administrators. This self-service capability for users maintains flexibility while reducing overall effort through the administrative pre-configuration layer
3Stability of the object's composition
If administrators manage personalization data for all end-users, then system-wide consistency is improved, but administrative complexity increases
Solution Approach 1:
The patent divides personalization data management into two distinct segments: administrative personalization data managed by administrators and individual personalization data managed by end-users. This segmentation reduces administrative complexity by limiting administrators' responsibilities to the administrative layer, while system-wide consistency is maintained through the administrative personalization framework
Solution Approach 2:
The patent creates a universal administrative personalization framework that can serve multiple end-users simultaneously. This multi-functional administrative layer establishes system-wide consistency through centralized configuration that applies across the organization, reducing the complexity of managing individual user preferences at the administrative level
Data Source
AI summary
Systems and methods are provided for personalizing software programs in a computer system. In accordance with one implementation, default values for personalization data adapted to or harmonized with the individual needs or preferences of the end-user are provided to a plurality of end-users at start-up of a program. Further, two personalization levels are provided, including a first personalization level containing administrative personalization data which can be set by a system administrator, and a second personalization level containing individual personalization data, which can be set by the end-user. A data filing system for this personalization data may be of a hierarchical structure.