The existing approach to requirements extraction is that the requirements are formed by the system developer through direct interaction with the customer using a number of methods (for example, interviewing; prototyping; analysis of use cases; user stories; seminars, etc.). In this case, most often the requirements are formed by the developer himself, taking into account the opinion of the customer’s representative. The disadvantage of the existing approach is the problem of loss of knowledge transferred from the customer’s representatives to the developer, which results in the failure of projects, which is recorded by the existing statistics. As statistical studies show, more than half of projects for the creation of information systems (IS) are failures or require changes (in terms of budget, time and customer satisfaction). In modern research in the field of__ design and development of information systems, there is a tendency to involve the end user (customer) in the design process. To develop this idea, an approach is proposed to involve the user in the process of extracting requirements, where the developer will no longer be the person forming the requirements. The main idea of the approach is to develop special tools that allow you to independently transform the customer’s natural language into such a form of representation of the model of the process of solving professional problems, from which an interface will be built, which will allow extracting functional requirements from the unity (process model and interface).
Ontology evolution: a process-centric survey
