Information technology for prediction of software quality level

Today, there is a contradiction between the rapid increase in the complexity and size of modern software while increasing responsibility for the performance of their functions, the increasing requirements of customers and users to the quality and efficiency of software use and the imperfection of models, methods, tools of predicting software quality at the early stages of the life cycle.Therefore, the task of predicting the software quality level based on requirements is relevant. The aim of this study is to solve this task by developing information technology for prediction software quality levels based on requirements. The proposed information technology for prediction software quality level based on requirements provides analysis of quality attributes in requirements, reflects the dependence (equations) of quality characteristics on attributes, forms a quantitative assessment of quality characteristics, reflects the dependence (equation) of quality on its characteristics, forms a quantitative assessment of quality, performs quality level prediction, provides all the listed services simultaneously and the model, methods, and tools underlying the IT belong to common methodological approaches and are integrated. The developed system of predicting the software quality level based on requirements provides the user with predicted estimates of eight software quality characteristics, geometric interpretation of the software quality characteristics’ values, a comprehensive indicator of the predicted software quality, and a conclusion about the future software quality level. On the basis of this, it is possible to compare sets of requirements for software and make a reasonable choice of a set of requirements for further implementation. The information technology and the system of predicting the software quality level based on requirements, developed in this paper, provide the possibility of comparing sets of requirements for software, justified selection of requirements for further implementation of quality software (as experiments have shown, this is only one of the four proposed sets), and rejection or revision of unsuccessful sets of requirements that cannot be used to develop quality software.