论文标题
超大规模系统系统中的系统和软件架构统一实践
System and Software architecting harmonization practices in ultra-large-scale Systems of Systems
论文作者
论文摘要
背景:系统体系(SOS)构建所带来的挑战激发了该地区的大量研究工作。但是,在架构过程中涉及的学科之间的相互作用方面缺乏文献,这是解决这些挑战的关键因素。目标:本文旨在通过确认和扩展以前特征的架构协调实践来为这项研究做出贡献,该实践从系统和软件工程中进行了,以超级大规模的规模构成。方法:我们对方公里阵列(SKA)项目进行了验证性案例研究,以评估和扩展我们对Lofar/Lofar2.0 Radio-TeleScope项目的探索性案例的发现。在此过程中,进行了预研究,以绘制先前研究的发现。然后设计了一项调查,通过该调查收集并分析了46位SKA工程师的观点。结果:该研究在各种程度上证实了探索性案例中确定的四种实践,并提供了进一步的见解,即:(1)长期系统需求引起的学科之间的摩擦,以及如何通过中间的短期,短期需求来改善它们; (2)对多个敏捷团队产生跨切割影响的设计选择对系统体系结构有间接影响; (3)这些设计选择通常是由指导早期系统分解的标准引起的; (4)缺乏有关界面动态元素的细节的看似复发的问题; (5)使用机器可读接口规格来对齐硬件/软件开发过程。
Context: The challenges posed by the architecting of System of Systems (SoS) has motivated a significant number of research efforts in the area. However, literature is lacking when it comes to the interplay between the disciplines involved in the architecting process, a key factor in addressing these challenges.Objective: This paper aims to contribute to this line of research by confirming and extending previously characterized architecting harmonization practices from Systems and Software Engineering, adopted in an ultra-large-scale SoS. Method: We conducted a confirmatory case study on the Square-Kilometre Array (SKA) project to evaluate and extend the findings of our exploratory case on the LOFAR/LOFAR2.0 radio-telescope projects. In doing so, a pre-study was conducted to map the findings of the previous study with respect to the SKA context. A survey was then designed, through which the views of 46 SKA engineers were collected and analyzed. Results: The study confirmed in various degrees the four practices identified in the exploratory case, and provided further insights about them, namely: (1) the friction between disciplines caused by long-term system requirements, and how they can be ameliorated through intermediate, short-term requirements; (2) the way design choices with a cross-cutting impact on multiple agile teams have an indirect impact on the system architecture; (3) how these design choices are often caused by the criteria that guided early system decomposition; (4) the seemingly recurrent issue with the lack of details about the dynamic elements of the interfaces; and (5) the use of machine-readable interface specifications for aligning hardware/software development processes.