MANAGEMENT OF NON-FUNCTIONAL REQUIREMENTS FOR SOFTWARE PRODUCTS IN THE FIELD OF FINANCIAL TECHNOLOGIES

Abstract

Approaches to software development management depend on many aspects. The area for which software products are developed is of great importance. In the process of developing software products, an important stage is defining requirements. The article considers aspects of defining non-functional requirements for software products in the field of financial technologies. The methods of classification, generalization and comparison were used in the study. It is noted that software products in the field of financial technologies are systems with a complex architecture and logic. A list of categories of non-functional requirements for software products in the field of financial technologies is determined. It is noted that when developing software products in this area, it is important to take into account requirements related to performance, fault tolerance, data security, compliance with legal requirements, documentation, as well as an approach to the deployment of software products. The influence of the listed requirements on the stages of development, deployment and operation of software products is determined. It is noted that when using flexible iterative approaches to the development of software products, it is important to monitor the performance indicators of the system after each iteration in order to promptly identify signs of its degradation. It has been established that in addition to the product's program code, the infrastructure required for the correct operation of the product is of great importance. International regulatory documents governing data and payment security issues are provided, and their key aspects that should be taken into account when developing software products in the field of financial technologies are highlighted. It is noted that when documenting software products, the description of the API (Application Programming Interface), which is used for integration with external systems, is of great importance. It has been established that in order to accelerate the development of API, integration with API and preparation of API documentation, it is advisable to use tools that allow the automation of these actions. Comparisons of the main approaches to the deployment of software products are performed and criteria for their selection are defined. A general conclusion is made that non-functional requirements are no less important than functional requirements.