An interdisciplinary network of influencing factors is derived that makes explicit the dependencies between consistency mechanisms, organizational and technical conditions, and key agility outcomes such as responsiveness, transparency, and the realizability of development increments.
Results indicate that inconsistency scenarios effectively raise awareness of inconsistency-related risks, support self-assessment, and facilitate structured discussion of (in)consistency management in complex CPS development contexts.
Thomas Alexander Voelk, Eva-Maria Grote, Razieh Dehghani et al.· 0 citations
Agile methods have produced significant gains in productivity and delivery speed for software‐intensive systems, yet their application to complex cyber‐physical systems has not yielded comparable results. This gap reflects not merely cultural resistance, but fundamental structural constraints associated with hardware development, manufacturing, long‐lead components, integration, certification, and system‐level test. Attempts to optimize for software flow alone therefore fail to improve overall value delivery.
This article suggests that product line engineering (PLE) provides a structural mechanism for enabling meaningful agility in complex cyber‐physical systems by organizing solutions into stable core assets and controlled variability that explicitly respects physical and organizational constraints. By aligning product line scoping decisions with system bottlenecks and delivery objectives, organizations can preserve throughput while enabling rapid adaptation and learning.
The article presents key challenges encountered when applying agile practices to cyber‐physical systems, outlines PLE principles tailored for such environments, and introduces practical alignment patterns for integrating PLE with agile systems engineering. Illustrative practitioner examples are provided to demonstrate how these patterns support faster, more reliable delivery without sacrificing system integrity. The result is a pragmatic framework for achieving cyber‐physical agility grounded in architectural discipline rather than software‐centric optimization.
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.
Milana S. Shapieva, Muhammad A. Agamirzaev· EKONOMIKA I UPRAVLENIE: PROB...· 0 citations
Dynamic operational environments and accelerating technological disruption are reshaping how systems engineering must be practiced. Traditional lifecycle models assume stability in requirements and context; however, modern socio‐technical systems particularly those incorporating artificial intelligence operate under persistent uncertainty, rapid feedback cycles, and evolving mission demands. This article argues that systems engineering must shift from a control‐centric discipline to one grounded in disciplined adaptability. Integrating agile principles, model‐based systems engineering (MBSE), modular open systems architecture (MOSA), and AI‐enabled capabilities, the paper proposes an adaptive systems engineering operating model for sustained mission relevance. It differentiates the constraints of hardware, software, and AI‐driven systems, examines AI as both engineering tool and system component, and outlines infrastructure requirements including digital threads, continuous validation architectures, and adaptive governance. A cross‐industry aerospace case study demonstrates how modularity, concurrent engineering, and digital twins enable iterative delivery in safety‐critical domains. Practical guidance is provided for systems engineering practitioners seeking to anticipate and respond effectively to dynamic and uncertain operating environments.
This paper presents a realistic case study showing how the implementation of DevOps principles in cross-functional teams, with the help of the standardized pipelines and integrated automation, facilitates cooperation, reduces cycle times, enhances quality assurance and accelerates delivery outcomes.
Karthik Allam· International Journal of Eme...· 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.
