English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Modern trends in the development of IT sector pay special attention to reducing unproductive expenses of IT projects. One way to reduce these costs is to maximally accurately identify the content of an IT project during its initiation and planning [1]. Solving this task is typically considered as part of the work to build and analyze the requirements of rightsholders to the created system [2]. A modern paradigm for describing and modeling system requirements is based on the publication of the requirements in the form of scripts to perform certain activities. An example of the implementation of a given paradigm using visual models of the Unified Modeling Language (UML) is a model of the requirement provided by Microsoft Corporation [3]. However, the application of a given paradigm is complicated when solving the tasks on a system requirements analysis. Using a scenario approach to the description and publication of requirements is seriously complicated while defining the boundaries for a created or upgraded system. In addition, the use of UML, and, in particular, the Use Case diagrams for the description of scenarios for meeting the requirements by rightsholders requires the development of special models, methods, and information technologies to formalize and automate the work on a requirements analysis. Running an analysis of scenarios for meeting the requirements by rightsholders manually inevitably causes a high risk of error going undetected. These errors can be caused by an incorrect definition of the scenarios for implementing individual requirements of rightsholders, as well as synthesis of the descriptions of the system architecture without aligning the descriptions of scenarios for implementing individual requirements to the functions of a given system. The base method for scenario analysis of the rightsholders’ requirements to a system was considered in [4] as a sequence of the following stages. Stage 1. Selection of a base scenario for a functional requirement, which describes activities of the system that occur most frequently regardless of the type of a request by an actor and the conditions for implementing these queries. Stage 2. Description of relationships among requirements based on the Use Case diagrams. IMPROVEMENT OF THE METHOD OF SCENARIO ANALYSIS OF FUNCTIONAL REQUIREMENTS TO AN INFORMATION SYSTEM

Improvement of the method of scenario analysis of functional requirements to an information system