graph theory

Model for Evaluating the Quality of Interface Prototyping

This article is devoted to the development and substantiation of a comprehensive model for evaluating the quality of interface prototyping in software systems. The relevance of the study is determined by the increasing complexity of modern interfaces and the need to make well-founded design decisions prior to the software implementation stage. The paper addresses the problem of formalizing the evaluation of prototype quality while accounting for the multidimensional nature of evaluation criteria and the significant proportion of subjective qualitative characteristics.

The Impact of Key Aspects on Admin Panel Design for Online Media Site

This article examines and describes research on determining the priority of influencing factors in designing the administrative part of the site for online media. Since this process cannot be described using mathematical formulas, we decided to use the method of analyzing hierarchies and graph theory in this case. In the course of the conducted survey among managers and editors of online media of the Lviv region, seven main factors were identified and systematized.

A Graph-Based Model for Automatic Test Case Generation from Textual Requirements with Hierarchical Coverage

The automation of software test case generation from natural language requirements remains a critical challenge in software engineering.  While large language models (LLMs) demonstrate impressive generation capabilities, they suffer from high discrepancy rates (up to 57% for direct generation), hallucinated test steps, and lack formal verification mechanisms for safety-critical constraints.  This paper presents a novel algorithmic framework that addresses these limitations through five principal contributions.  First, we introduce the Neuro-Symbolic Requirements Graph (

Analysis and development of a conceptual model for lifecycle management of specialized safety-oriented software

A comprehensive examination of the process of developing specialized safety-oriented software is conducted. The incongruity of the presently known development methodologies with the circumstances in which innovative safety-oriented software systems are created is unveiled.