Systems of Systems (SoS) encompass a group of distributed and independent systems. This class of systems requires recurrent adaptation at runtime owing to the uncertainty and variability of the runtime environment. Thus, during their execution, SoS can deviate from the initial specification, which is often a consequence of successive evolutions. This problem occurs mainly due to (a) weak communication between the SoS analysis stage and architecture stage and (b) the lack of links between the operational planning in the SoS analysis stage and systems that must be involved in the SoS architecture stage. This paper proposes a model‐based process that strengthens the links between the SoS analysis stage and the architecture stage in the wave life cycle. We ensure that the mission and role concepts for the SoS definition are sufficiently abstract to allow adaptation to the variability of the environment. This definition is translated into an abstract architecture that guides the choices of the system architect during the design and evolution stages. The proposed language is an adaptation of the Systems Modeling Language (SysML). Furthermore, we define a crowd management SoS to illustrate the process.
The system of systems (SoS) is a system whose definition is based on pre-existing independent systems in the runtime environment. The latter is in perpetual evolution thus forcing a recurrent adaptation of the SoS. Thus, during their life cycle the SoS are very exposed to the problem related to the evolution mentioned above. This problem is mainly due to a poor communication between the requirement definition stage and the design stage. In this paper we propose a method for addressing SE for SoS using the concepts Mission and Role. The first one allows the definition of the SoS's behavior, while the second allows to abstract this definition with respect to the constituent systems that may actually exist in the environment. This definition will be translated into an abstract architecture. The later will serve as a guide and controller of the choices proposed by the system architect during the design and evolution stages. With our approach we have correctly defined an SoS concerning crowd management during a sport event.
In certain cases, such as secure humanitarian corridors in a conflict zone, a special type of SoS, needing a rapid deployment, has to be developed. Because of the tense time constraint, usually only a domain expert is responsible with this development. However, many such SoSs also have to take into account the security aspect. How to help a domain expert integrate the security aspect into the rapid development of an SoS? In this proposal paper, we present an approach and a tool suite that help the domain expert tag business assets using security properties, which are then used to identify vulnerabilities and to propose possible security control mechanisms. We illustrate our proposal on a case study. Index Terms-security, security model and architecture design, meta-modelling, domain model, causal chain
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.