Extending VDM-RT to enable the formal modelling of System of Systems

Nielsen, Claus Ballegaard; Larsen, Peter Gorm

doi:10.1109/sysose.2012.6384156

Cited by 6 publications

(3 citation statements)

References 13 publications

(10 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In these approaches, the structure of a system is defined as a concrete Bigraph, while dynamics are represented by reaction (transition) rules. On the other hand, authors in (Nielsen and Larsen, 2012) proposed a formal approach based on the extension of an objectoriented technique, the Vienna Development Method Real-Time (VDM-RT). This extension allows the initial architecture of a SoS to be changed during run-time through dynamic reconfiguration operations.…”

Section: Introductionmentioning

confidence: 99%

A Formal Language for Modelling and Verifying Systems-of-Systems Software Architectures

Seghiri

Belala²,

Hameurlain

2022

International Journal of Systems and Service-Oriented Engineering

View full text Add to dashboard Cite

Systems of systems (SoS) are a set of independent systems that are constantly evolving. These systems cooperate in order to achieve a common goal, known as an SoS mission. It is difficult to capture their behaviours while operating in a hierarchical, cooperative and evolutionary structure. Thus, a software architecture based approach is defined in order to model and analyze these systems, reducing their increasing complexity. It ought to describe an SoS on both structural and behavioural levels. In this paper, ArchSoS, an ADL dedicated to describe SoS software architectures, is extended with a syntax-driven formal description, based on Bigraphic Reactive Systems (BRS). SoS defined via ArchSoS have both a graphical and a textual view. For this syntax to be executable, and to verify SoS evolutions, an operational semantic for ArchSoS is defined. It is implemented in Maude language to permit ArchSoS behavioural simulations, and its formal analysis is done through Linear Temporal Logic (LTL). The proposed approach is illustrated through a Crisis Response SoS as a case study.

show abstract

Section: Introductionmentioning

confidence: 99%

A Formal Language for Modelling and Verifying Systems-of-Systems Software Architectures

Seghiri

Belala²,

Hameurlain

2022

International Journal of Systems and Service-Oriented Engineering

View full text Add to dashboard Cite

show abstract

“…DeLaurentis (2005a) describes how transportation systems can be developed as SoS and argues that the SoS characteristics, such as emergent behaviors and evolutionary development, are suitable for transportation sector. Nielsen and Larsen (2012) present an SoS for vehicle monitoring that is designed to improve road safety by making available the traffic information to drivers. In this scenario, vehicles are constituent systems with independence of movement, resulting in high dynamicity for generating and sharing traffic information.…”

Section: Illustrative Examplesmentioning

confidence: 99%

“…Engineering Lessons for Systems of Systems Learned from Service-Oriented Systems (Simanta et al, 2010) Assessing system software performance in complex system of systems environments (Wessel and Meyer, 2010) Measuring the architectural complexity of military Systems-of-Systems (Domerçant and Mavris, 2011) Agile development for system of systems: Cyber security integration into information repositories architecture (Farroha and Farroha, 2011) Singleton to sandwich chunking into buslets for better system development (Hodges et al, 2011) Service Orientation and Systems of Systems (Lewis et al, 2011) Software engineering of component-based systems-of-systems: A reference framework (Loiret et al, 2011) Executable system architecting using systems modeling language in conjunction with colored Petri nets in a model-driven systems development process (Wang and Dagli, 2011) The process of architecting for software/system engineering (Chigani and Balci, 2012) COAST: An Architectural Style for Decentralized On-Demand Tailored Services (Gorlick et al, 2012) System of Systems to provide Quality of Service monitoring, management and response in Cloud Computing environments (Hershey et al, 2012) Supporting Awareness during Collaborative and Distributed Configuration of Multi Product Lines (Holl et al, 2012) Architecting the Human Space Flight Program with Systems Modeling Language (SysML) (Jackson et al, 2012) Scaling Up Software Architecture Analysis Towards integrated rule-driven software development for IT ecosystems (Mensing et al, 2012) Multi-agent architecture with space-time components for the simulation of urban transportation systems (Nguyen et al, 2012) Extending VDM-RT to enable the formal modelling of System of Systems (Nielsen and Larsen, 2012) Interface specification for system-of-systems architectures (Payne et al, 2012) Reengineering legacy systems towards system of systems development (Ramos et al, 2012) Appendix A. Systematic Mapping on SoS Software Architectures: Study Protocol and List of Included Primary Studies…”

Section: A11 Research Questionsmentioning

confidence: 99%

Supporting architectural design of acknowledged SoS

Gonçalves¹

View full text Add to dashboard Cite

System-of-Systems (SoS) refer to complex, large-scale, and sometimes critical software-intensive systems that has raised as a promising class of systems in several application domains. In parallel, software architectures play a significant role in the development of software-intensive systems, dealing with both functional and non-functional requirements. In particular, systematic processes to design SoS software architectures can tackle challenges from SoS development, including to handle collaboration of independent constituent systems with different owners, missions, and interests. Despite the relevance and necessity of software-intensive SoS for diverse application domains, most of their software architectures have been still developed in an ad hoc manner. In general, there is a lack of structured processes for architecting SoS, hindering the secure adoption of SoS, reducing possibilities of sharing common architectural solutions, and negatively impacting in the success rate for these systems. This thesis presents SOAR ("General Process for Acknowledged SoS Software Architectures") that supports the establishment of architectural design processes for acknowledged SoS. Conceived to provide different levels of support according to each SoS development context, it comprises a high level kernel that describes what must be done when architecting SoS and also three practices with specific activities and work products to guide how to perform architectural analysis, synthesis, and evaluation. To evaluate SOAR, three surveys, a viability study, and an experiment were conducted. Results achieved in these evaluation studies indicate that SOAR can positively support the instantiation of architecting processes for acknowledged SoS and, as a consequence, contribute to the development and evolution of these complex, software-intensive systems.

show abstract