Methodology for assessing satisfaction with requirements at the early stages of the software development process

The subject matter of the research is the process of satisfaction with requirements during software development. A qualitative requirements engineering stage for the system being designed to fulfill all business goals, please the client, and eventually satisfy the end user, is one of the key prerequisites for effective implementation of any IT project. The level of satisfaction with requirements must rise as a prerequisite for the project's success through requirement engineering. To ensure that a product or service meets the needs and expectations of its users or consumers, it is critical to satisfy these requirements. The primary purpose of the proposed study is to establish a methodology for quantitatively assessing the satisfaction with requirement level considering various characteristics of requirements before the development phase begins. The tasks to be solved are: to investigate the up-to-date state of the subject area; to develop a methodology for assessing satisfaction with requirements; to provide and investigate the proposed methodology on the real-life example; to recommend actions to increase the level of satisfaction with requirements. The suggested methodology, as opposed to others, considers such characteristics of the requirements as atomic, completeness, consistentness, conciseness, feasibility, unambiguousness, testability, prioritized, understandability, security, and performance to obtain a quantitative assessment of satisfaction with requirements level. The result of this paper is a methodology for quantitative assessing the satisfaction with requirements considering different characteristics of requirements before the development phase begins. This study is significant and necessary since, in the majority of cases, previous research does not offer comprehensive quantitative and measurable methods for determining the degree to which requirements for certain characteristics are satisfied. Also, it is demonstrated how the created methodology may be used with actual requirements. There are additionally recommendations for strengthening satisfaction with requirements. Conclusions. The proposed methodology is extensible, unlike others, which means that the characteristics and rating scale can actually change depending on the requirements, goals, and other features of the IT project.