You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

Should I Stay or Should I Go? How Constituent Systems Decide to Join or Leave SoS Constellations

Fulltext:


Authors:

Pontus Svenson , Jakob Axelsson

Research groups:

Industrial Software Engineering
Systems-of-systems

Publication Type:

Conference/Workshop Paper

Venue:

16th Annual System of Systems Engineering Conference

DOI:

10.1109/SOSE52739.2021.9497474

Abstract

A collaborative system of systems (SoS) is formed when independent organizations decide to cooperate to achieve mutual benefits, while retaining independence of their respective systems. Each constituent system (CS) of the SoS has a set of capabilities, some of which they agree to potentially use in active collaboration with others. Such an active collaboration is called a constellation and can be seen as an instantiation of the SoS which is created to provide a joint capability. Constellations are thus the working-horses of the SoS, but due to the operational independence of the CS, they have a choice whether to join a certain constellation or not. This paper discusses the reasoning and world model that is necessary for a CS to make well-informed decisions to join and leave constellations. We argue that it is necessary for the CS to understand not only the surrounding environment, but also to have models of other CS' world models as well as of their probable future actions. It must be possible to predict whether other participants will uphold their parts of the collaboration or may defect from it to join another more rewarding constellation despite the agreements made when joining the SoS. The reasoning in the paper is illustrated using examples from two different collaborative SoS in the transportation domain.

Bibtex

@inproceedings{Svenson6352,
author = {Pontus Svenson and Jakob Axelsson},
title = { Should I Stay or Should I Go? How Constituent Systems Decide to Join or Leave SoS Constellations},
isbn = {978-1-6654-4454-5},
pages = {179--184},
month = {June},
year = {2021},
booktitle = {16th Annual System of Systems Engineering Conference},
url = {http://www.es.mdu.se/publications/6352-}
}