Model for Quantitative Estimation of Functionality Influence on the Final Value of a Software Product

The gap between software development requirements and available resources of software developers continues to widen. This requires changes in the development and organization of software development. This study introduced a quantitative software development management methodology that estimates the relative importance and risk of functionality retention or abundance, which determines the final value of the software product. The final value of a software product is interpreted as a function of its requirements and functionalities, represented as a computational graph (called a software product graph). The software product graph allows the relative importance of functionalities to be estimated by calculating the corresponding partial derivatives of the value function. The risk of not implementing functionality was estimated by reducing the product's final value. This model was applied to two EU projects, CareHD and vINCI. In vINCI, functionalities with the most significant added value to the application are developed based on the implemented model, and those related to the least value are abandoned. Optimization was not implemented in the CareHD project, and proceeded as initially designed. Consequently, only 71% of the CareHD potential value was achieved. The proposed model enables rational management and organization of software product development with real-time quantitative evaluation of functionalities impacts and, assessment of the risks of omitting them without a significant impact. Quantitative evaluation of the impacts and risks of retention or abundance is possible based on the proposed algorithm, which is the core of the model. This model is a tool for the rational organization and development of software products.