Software Asset Management via Placeholder Model Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional software asset management systems face challenges in managing software programs when the publisher has not provided identification information, leading to errors and client dissatisfaction, especially with newly released or latest versions.
Innovation Solution
A management server generates placeholder data structures to facilitate asset management by creating new software models linked to unrecognized software program identifiers, allowing for analysis and management even without publisher-derived information, and enables collaboration across client instances to reduce data duplication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional software asset management systems rely on publisher-derived identification information, then they can accurately manage known software programs, but they fail to manage newly released or latest versions when publisher information is not yet available
Solution Approach 1:
The system performs preliminary actions by generating placeholder data structures and software models in advance before publisher-derived identification information is available. This allows the system to proactively manage newly released software versions immediately upon detection, rather than waiting for publisher information to become available
Solution Approach 2:
The system introduces an intermediary mechanism - a placeholder software model with placeholder data structures - that mediates between the detection of new software and the eventual receipt of publisher information. This intermediary allows continuous asset management while maintaining the possibility of future accuracy improvement when publisher data arrives
2Productivity
If the system generates placeholder data structures for unrecognized software, then it can provide continuous asset management, but it increases system complexity
Solution Approach 1:
The system creates simplified copies or placeholders of the actual software models when publisher information is unavailable. These placeholder data structures replicate the essential structure needed for asset management operations while deferring the complexity of complete software identification to a later time when publisher information becomes available
Solution Approach 2:
The system implements dynamic software models that can transition between different states - from placeholder models with limited information to complete models with full publisher-derived information. This dynamic nature allows the system to adapt its complexity level based on the availability of information, maintaining productivity while managing complexity
3Ease of operation
If multiple client instances maintain separate software model data, then each instance has complete local information, but data duplication increases storage costs
Solution Approach 1:
The system merges the software model data storage across multiple client instances by implementing a shared repository or common data structure that all instances can access. This consolidation eliminates redundant storage of identical software model information while maintaining local accessibility through the shared resource
Solution Approach 2:
The system creates a universal software model repository that serves multiple client instances simultaneously. This single data structure performs the function of providing software model information to all instances, replacing the need for separate duplicate data stores at each instance
Data Source
AI summary
A management system to facilitate improved software asset management includes a management server coupled to a client instance and certain databases. The client instance stores identifiers associated with software programs accessible to users through the client instance. To enable software asset management features, the management server receives the identifiers and determines, based on the certain databases, whether the identifiers are associated with software models of the software programs. Notably, in response to an identifier of a particular software program not being associated with a software model, the management server generates a software model for the particular software program, and further, stores entries or relationships within the certain databases. Thus, the management server may output the software model to the client instance to enable a client to provide attributes to be included in the software model, further improving a quality of the software asset management features accorded by the management system.