Abstract

The components and the structure of an open system-of-systems (SoS) cannot be completely predicted at the design phase. An open SoS dynamically connects to collectively provide a superordinate functionality, which could not be provided by a single system. In addition, open systems' boundaries, functions, and structures are continuously evolving and perceived differently depending on stakeholders. Preventing them from becoming vague figures requires a particular effort. Therefore, for designers and systems engineers to realize open systems dependability in a company, they need to describe how they recognize the open SoS. This study aims to propose an assurance case (AC) description method that clarifies the objects to reduce misunderstanding of managed objects at the designing phase of an open SoS. We evaluate the method to confirm whether the subjects can describe the managed objects as an open SoS. Additionally, to confirm the utility of the proposed AC description method, we confirm whether the subjects can explain the managed objects as an open SoS using the proposed method. As a result, this study suggested that the proposed AC description method is effective for systems designers and systems engineers to recognize the open SoS.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call