SOLID AS A SYSTEM OF ENGINEERING CONSTRAINTS IN SOFTWARE ARCHITECTURAL DESIGN
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.