2026· EKONOMIKA I UPRAVLENIE: PROBLEMY, RESHENIYA· Vol 4/15, pp. 185-193· 0 citations
TL;DR
A practical approach to using the SOLID principles as a system of engineering constraints is proposed, which ensures sustainable development of a software product and reduces architectural risks throughout its life cycle.
Abstract
The article examines the role of the SOLID principles in ensuring the quality of software architecture and the manageability of its evolution under continuously changing requirements. The influence of object-oriented design principles on the level of coupling and cohesion of software components is considered, as well as their interrelation with architectural approaches and design patterns. An analysis of various types of coupling encountered in modern software systems is performed, including structural, conceptual, and evolutionary coupling. Special attention is paid to the practical aspects of applying the SRP, OCP, LSP, ISP, and DIP principles, as well as to the risks arising from their formal or excessive use. It is shown that the effectiveness of architectural decisions is determined not only by compliance with design principles but also by the use of objective quality evaluation criteria based on metrics of coupling, cohesion, and code complexity. The possibilities of applying hexagonal architecture, contract testing, and dependency inversion mechanisms to improve the maintainability of software systems are considered. Based on the research results, a practical approach to using the SOLID principles as a system of engineering constraints is proposed, which ensures sustainable development of a software product and reduces architectural risks throughout its life cycle.
The intent of this paper publication is to address Software (SW) Safety Architecture Analysis and to provide an approach for conducting the architecture analysis Level of Rigor task utilizing software architecture patterns. While there are many architecture analysis techniques commonly used in practice today (e.g., Architecture Tradeoff Analysis Method (ATAM), Software Architecture Analysis Method (SAAM), Scenario based Architecture Level UsabiliTy Analysis (SALUTA), etc.), they seem to concentrate on the architecture of the system rather than the structure of the system’s software. By analyzing software architecture patterns, the safety practitioner can pay close attention to the true architecture of the software. The methodology described within further details the safety concerns associated with each of the patterns. The general safety concerns are stability/robustness, data handling, maintainability, testability, and security. Each of these concerns are broken down to more specificity in the brief. By identifying the software architecture pattern(s) employed in a system and understanding the safety concerns and potential mitigations, system safety practitioners have a basis for an in-depth, repeatable software architecture analysis methodology.
Myesha Dabney, Carla Adams, LaTasha Bagby et al.· Journal of System Safety· 0 citations
Findings indicate that software correctness is the primary objective in language design, supported by robust type systems, compile time verification, and expressive abstractions that help reduce errors and improve code reliability.
The article is dedicated to examining how contemporary design systems support the scalability of digital products through architectural principles, tokenization practices, and component modeling. The relevance of the study stems from the rapid expansion of multi-platform ecosystems, where fragmented interfaces undermine product coherence and increase development overhead. The novelty lies in treating the design system not as a static guideline set but as an evolving architectural structure that shapes consistency through modular organization, semantic token frameworks, and stable component hierarchies. The work describes the interplay between these elements and studies how they collectively sustain visual and behavioral alignment across distributed teams. Special attention is paid to the role of system governance, bottom-up evolution, and design-to-code convergence. The work sets itself a goal of identifying mechanisms through which design systems maintain cohesion as products and teams scale. To achieve this, analytical and comparative methods are applied. The conclusion describes the stabilizing effect of unified design architectures and their value for long-term product development. The article will be useful for researchers, UX architects, product designers, and engineering teams involved in large-scale digital systems.
Volkodav Vladyslav· Universal Library of Innovat...· 0 citations
It was concluded that Clean Architecture cannot be viewed solely as an ally or a villain, as its effectiveness depends on project characteristics, team experience, and the proportionate application of its principles.
It is demonstrated that multiple architectural views, continuous monitoring, domain-driven decomposition, and AI-assisted design techniques contribute significantly to improving scalability, maintainability, adaptability, and long-term software sustainability.
