Software Asset Management via Application Wrapper Standardization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing software assets in a large enterprise poses challenges, including updating and ensuring compliance with license agreements, which existing systems fail to address effectively through a centralized and standardized method.
Innovation Solution
A system comprising a receiving manager unit for verifying the source and creating an application wrapper file, a build manager unit for distributing files into a predetermined folder structure, and a peer review manager unit for peer review and presentation to a software library, providing a single portal tool for the life cycle management of software assets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized system for managing software assets is implemented, then compliance with license agreements and standardization are improved, but system complexity and implementation difficulty increase
Solution Approach 1:
The system segments software asset management into distinct functional modules: receiving manager unit for asset intake and verification, build manager unit for processing and packaging, and peer review manager unit for quality assurance. This modular segmentation reduces overall system complexity by making each component independent and manageable while maintaining centralized control for compliance.
Solution Approach 2:
The patent introduces intermediary components such as the application wrapper file that mediates between raw software assets and the library system, and peer review manager units that act as intermediaries between build manager and final library inclusion. These intermediaries simplify compliance verification by standardizing the interface and review process.
2Reliability
If a standardized process for software asset management is implemented, then consistency and reliability are improved, but processing time and operational complexity increase
Solution Approach 1:
The system performs preliminary actions by verifying the source of software assets and creating application wrapper files with standardized folder structures during the build phase, before peer review and library inclusion. This preliminary standardization reduces processing time later by eliminating the need for repeated verification and formatting operations.
Solution Approach 2:
The patent changes parameters by transforming raw software assets into standardized application wrapper files with specific folder structures and metadata. This parameter transformation (from unstandardized to standardized format) enables consistent processing while reducing time through automated transformations rather than manual standardization.
3Manufacturing precision
If manual verification and review processes are used for software assets, then quality control is improved, but productivity and efficiency decrease
Solution Approach 1:
The system implements self-service through automated verification of software asset sources by the receiving manager unit and automated creation of application wrapper files by the build manager unit. These automated self-verification processes maintain quality control while significantly improving productivity by eliminating manual verification steps for routine checks.
Solution Approach 2:
The patent incorporates feedback mechanisms where peer review manager units evaluate application wrapper files and provide feedback on compliance and quality. This structured feedback loop maintains high quality control standards while improving efficiency by automating the feedback collection and analysis process, reducing manual review time.
Data Source
AI summary
A system for managing a software asset including asset files for inclusion in a library includes: (a) a receiving manager configured for receiving the asset, verifying source of the asset and reading an installer package into the asset to establish a received asset; (b) a build manager coupled with the receiving manager and configured for creating an application wrapper file for the received asset; the build manager creating folders in a folder structure and distributing the asset files among the folders to establish a distributed folder file; the build manager using the distributed folder file to create the application wrapper file; and (c) a peer review manager coupled with the build manager and effecting a peer review process with the application wrapper file to establish a reviewed application wrapper file; the peer review manager unit cooperating with the build manager to present the reviewed application wrapper file to the library.