Forecasting Reusable Software Assets via Domain Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques for software asset reuse in enterprises lack the ability to forecast software assets with high reusability potential, failing to provide insights into future requirements and competitive advantages.
Innovation Solution
A system and method for forecasting reusable software assets by creating a domain map with prioritized and tagged domain constituents, allowing users to submit forecasts which are mapped to the domain map, enabling decision-making for the development of forecasted assets based on market demand and existing inventory coverage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If software assets are collated and stored in repositories for reuse, then software asset availability for reuse is improved, but the ability to forecast future software asset requirements is lost
Solution Approach 1:
The system performs preliminary actions by collecting forecasts from users about future software asset requirements before actual development occurs. These forecasts are stored and processed to identify gaps in existing software asset repositories, enabling proactive development of high-demand reusable assets before they are needed.
Solution Approach 2:
The system segments the software asset management process into distinct components: forecast collection from multiple users, forecast processing and analysis, gap identification against existing repositories, and prioritized development recommendations. This segmentation allows each component to be optimized independently while maintaining overall system functionality.
2Adaptability or versatility
If forecasts are collected and processed to identify development needs, then software asset reusability is improved, but system complexity increases
Solution Approach 1:
The system achieves universality by creating a multi-functional platform that handles forecast collection from diverse users, processes various types of forecast data, compares against existing software asset repositories, generates prioritized development recommendations, and provides feedback to users. This single system performs multiple functions that would otherwise require separate tools and processes.
Solution Approach 2:
The system acts as an intermediary between software asset users and developers. It collects forecasts from users, processes this information through analysis algorithms, and generates development recommendations that are returned to users. This intermediary layer simplifies the interaction between users and the complex software asset management process.
3Quantity of substance
If software development projects expand in size and number, then software asset creation volume increases, but time-to-market for new projects increases
Solution Approach 1:
The system performs preliminary identification of high-demand software assets through forecast collection and processing before actual development projects begin. By identifying gaps and priorities in advance, organizations can proactively develop reusable software assets that will be needed for future projects, reducing time-to-market when those projects are initiated.
Solution Approach 2:
The system provides dynamic, real-time feedback to users about software asset gaps and development priorities based on collected forecasts. This dynamic information allows organizations to adapt their development plans and resource allocation in real-time, optimizing the balance between asset creation volume and time-to-market delivery.
Data Source
AI summary
Systems and methods for forecasting reusable software assets are described. In one embodiment, the method comprises receiving a forecast comprising forecast information pertaining to at least one forecasted software asset. Further, the method comprises mapping the forecast to a domain map based on the forecast information, wherein the domain map includes a plurality of domain constituents. Based in part on the mapping, a development request for creation of the at least one forecasted software asset is generated.