Looking back and forward: A retrospective and future directions on Software Engineering for systems-of-systems
<|reference_start|>Looking back and forward: A retrospective and future directions on Software Engineering for systems-of-systems: Modern systems are increasingly connected and more integrated with other existing systems, giving rise to \textit{systems-of-systems} (SoS). An SoS consists of a set of independent, heterogeneous systems that interact to provide new functionalities and accomplish global missions through emergent behavior manifested at runtime. The distinctive characteristics of SoS, when contrasted to traditional systems, pose significant research challenges within Software Engineering. These challenges motivate the need for a paradigm shift and the exploration of novel approaches for designing, developing, deploying, and evolving these systems. The \textit{International Workshop on Software Engineering for Systems-of-Systems} (SESoS) series started in 2013 to fill a gap in scientific forums addressing SoS from the Software Engineering perspective, becoming the first venue for this purpose. This article presents a study aimed at outlining the evolution and future trajectory of Software Engineering for SoS based on the examination of 57 papers spanning the 11 editions of the SESoS workshop (2013-2023). The study combined scoping review and scientometric analysis methods to categorize and analyze the research contributions concerning temporal and geographic distribution, topics of interest, research methodologies employed, application domains, and research impact. Based on such a comprehensive overview, this article discusses current and future directions in Software Engineering for SoS.<|reference_end|>
@article{cavalcante2024looking,
    title={Looking back and forward: A retrospective and future directions on
  Software Engineering for systems-of-systems},
    author={Everton Cavalcante, Thais Batista, and Flavio Oquendo},
    journal={arXiv preprint arXiv:2403.16740},
    year={2024},
    archivePrefix={arXiv},
    eprint={2403.16740},
    primaryClass={cs.SE cs.SY eess.SY}
}