Centralized Object Change Tracking for IT Landscapes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In object-based software environments, it is difficult to efficiently track and manage changes made to software objects across large IT landscapes, as conventional systems lack the ability to timely and accurately record and retrieve object change data.
Innovation Solution
A system comprising an update handler, change data manager, and query handler that determines and stores object change data in a tracking database with object identifiers, allowing for efficient querying and retrieval of specific change data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional object-based software environments are used to manage large IT landscapes with multiple users making changes, then the software environment supports frequent and diverse changes, but the ability to track and determine object change data in a timely and efficient manner deteriorates
Solution Approach 1:
The patent introduces a centralized change tracking system that acts as an intermediary between software objects and users. This system intercepts and records all changes to software objects in a centralized database, providing a mediator layer that enables efficient tracking without disrupting the existing object-based software environment. The tracking system captures change data including object identifiers, change timestamps, and user information, allowing timely retrieval of change history.
2Measurement precision
If a centralized tracking system is implemented to monitor all software object changes, then change tracking capability improves, but system complexity increases
Solution Approach 1:
The centralized change tracking system is designed to be universal and multi-functional, serving multiple purposes within the IT landscape. It tracks changes across diverse software objects (applications, databases, files) using a unified tracking mechanism. The system provides multiple functions including change detection, user attribution, timestamp recording, and query capabilities, all through a single integrated infrastructure, thereby reducing overall system complexity despite the comprehensive tracking capability.
3Loss of information
If detailed object change data is stored for all software objects, then change information completeness improves, but data storage requirements increase
Solution Approach 1:
The patent extracts only the essential change data from software objects without duplicating the entire object state. It captures specific change attributes such as object identifiers, change timestamps, user information, and change descriptions, separating this metadata from the actual software objects. This extraction approach maintains complete change information while minimizing storage requirements by storing only the necessary tracking data rather than full object copies.
Data Source
AI summary
An update handler may determine object change data characterizing changes made to software objects. A change data manager store the object change data in a tracking database in conjunction with an object identifier for each changed software object. A query handler may receive an object-specific query requesting a subset of the object change data, and a response generator may provide the subset of the object change data from the tracking database, based on the corresponding object identifiers.