Agile systems engineering is not new. Work has progressed on this for many years to the point that criteria has been established regarding best practice as well as a means of quantifying adherence. The future of systems engineering (FuSE) initiative is reexamining how agile systems engineering fits into the FuSE (Willette et al. 2021). As model-based systems engineering (MBSE) is also a FuSE theme, it is only proper to look at how agile systems engineering and MBSE complement and enable each other. This article examines some of the aspects of MBSE–specifically the Systems Modeling Language® (SysML) – and show at how an agile approach to MBSE can help with the concepts of stakeholder engagement, continual integration, and dynamic learning and evolution. For reasons of space, the article will only provide minimal definitions and explanations of the basics of MBSE, agile, and SysML and as these are well known concepts.
The significant shift happening today towards more connected, more automated, and more autonomous systems is bringing software inside all systems, and at the same time agile practices. Our experience of large-scale agile deployments in companies building or operating complex systems in automotive and aerospace shows that, whereas both approaches can easily coexist in isolated teams within the same company, major problems arise when coordinating them at the leadership level, where they are perceived as antagonist, and create misalignments, friction and quality issues. In this article, we propose to describe why it is important to make agile and systems engineering work together, how to do it, and how this impacts how we see value, systems, digital twins, and leadership. The following concepts of the FuSE agile roadmaps are addressed:
Systems engineering faces ongoing challenges due to the pace of change in technology and needs as well as the complexity, resilience, and adaptability demanded of solutions. System security needs and challenges are a prominent factor in the increasing demands placed on solutions and the systems engineers who design and develop them. The adoption of program level agile execution is one strategy for addressing these escalating challenges. In this article we describe how the broadly adopted technical processes from the ISO/IEEE/IEC 15288:2015 standard can be executed using agile methods to realize a large complex solution. In addition, we provide specific recommendations for executing these processes in a manner that enables systems to be sustainably secure – that is, to retain the desired level of security throughout the life cycle.
Systems engineering must necessarily have the agility to anticipate and effectively respond to an increasingly dynamic and uncertain environment. Agile systems engineering, agile software engineering, and agile any-kind-of engineering share common goals and leverage common agility-enabling strategies. This article succinctly describes eight strategic aspects with application discussions at the systems engineering level.
Model-based systems engineering (MBSE) with agility can help systems engineering programs which deal with both increasing complexity and frequent changes in environment and usages, shorter time-to-market, uncertainty of the needs, and more sophisticated industrial schemes. Agile approaches originated in software engineering can be extended and tailored to a certain extent to complex systems engineering and particularly to MBSE. Main benefits of agility are provision of a minimum viable product as early as possible in the schedule, early capture of changes of needs, enabling to deliver a system answering to the real needs, and securing of the value proposal. It includes also potential reduction in rework of the final system through regular customer feedback throughout development (left shift for the defect correction with early exposure), and efficiency of the use of resources. Concerning MBSE, the use of models as a single source of truth for completeness and consistency is useful to share and secure the design by improving communication within engineering teams and the building and support of the development strategy, and to help to automate some tasks such as model exchange and synchronization. In addition to the benefits of each approach, combining them may help to:
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：