Object-Oriented Data Deprecation Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing object-oriented data models face disruptions when changes are made, such as updating or deleting classes, which can break compatibility and require significant updates or patches to applications, leading to disruptions in both existing and new applications.
Innovation Solution
A method for deprecating classes in an object-oriented data model, allowing data migration from deprecated classes to replacement classes, enabling existing applications to continue functioning without changes until the deprecated classes are deleted or updated, while new applications can use the replacement classes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If changes are made to the object-oriented data model (updating or deleting classes), then the data model can adapt to new technologies and evolving standards, but existing applications become incompatible and require significant updates or patches
Solution Approach 1:
The patent applies preliminary action by creating a deprecated class that serves as a transition mechanism before fully removing or updating the original class. This deprecated class is prepared in advance with mappings to new classes, allowing existing applications to continue functioning while gradually transitioning to the new data model structure.
Solution Approach 2:
The patent uses an intermediary approach by introducing a deprecated class that acts as a mediator between the old and new data models. This intermediary class maintains compatibility with existing applications while providing pathways to the new class structure, enabling smooth transition without breaking existing systems.
2Adaptability or versatility
If changes are made to the data model, then new technologies and standards can be incorporated, but disruption occurs to both consumers and providers of the CMDB
Solution Approach 1:
The patent applies dynamics by making the data model transition flexible and progressive rather than abrupt. The deprecated class allows the system to dynamically handle both old and new class structures during a transition period, enabling gradual adoption of new technologies while maintaining operational continuity.
Solution Approach 2:
By preparing deprecated classes with predefined mappings to new classes before the transition, the patent enables smooth operational continuity. Existing applications can continue to operate using the deprecated class interface while the system gradually migrates to the new structure without disruption.
3Reliability
If applications are patched after changes to the CDM, then compatibility is restored, but significant time and resources are required for updates
Solution Approach 1:
The patent uses copying by creating a deprecated class that replicates the interface and functionality of the original class. This copy allows existing applications to continue operating without modification while the system transitions to the new class structure, eliminating the need for time-consuming patches and updates.
Data Source
AI summary
Techniques are described to allow the deprecation of classes in an object-oriented data model, such as a CDM for a CMDB. When a class is deprecated and replaced by another existing or new class, data associated with instances of the deprecated class may be migrated to the replacement class. A mapping between the deprecated class and its replacement class may be provided to allow existing applications to continue to access data using the deprecated class without change until the deprecated class is finally deleted or the application is updated to use the replacement class. New applications written to use the object-oriented data model after the deprecation may use the replacement class to access data instances created using the original data model.