Architectural Framework for a System-of-Systems

Caffall, Dale Scott; Michael, J.B.

doi:10.1109/icsmc.2005.1571420

Cited by 7 publications

(3 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The behavior of SoS is hardly predictable [3] during development and only emerges at runtime when interacting with the actual environment, i.e., hardware, third-party systems, or legacy systems. Thus, SoS need to be monitored to analyze their behavior and to check whether they adhere to their requirements.…”

Section: Introductionmentioning

confidence: 99%

A requirements monitoring infrastructure for systems of systems

Vierhauser

2014

Proceedings of the 29th ACM/IEEE International Conference on Automated Software Engineering

View full text Add to dashboard Cite

An increasing number of software systems today are systems of systems (SoS) that have been developed by diverse teams over many years. Such systems emerge gradually and it is hard to analyze or predict their behavior due to their scale, complexity, and heterogeneity. In particular, certain behavior only emerges at runtime due to complex interactions between the involved systems and their environment. Requirements monitoring has been proposed as a solution for checking at runtime whether systems adhere to their requirements. However, existing requirements monitoring approaches have been designed for single systems and therefore do not adequately consider the characteristics of SoS. More specifically, requirements in SoS exist at different levels, across different systems, and are owned by diverse stakeholders. Furthermore, requirements monitoring for SoS has to be flexible with respect to technologies and architectural patterns. This thesis will identify the capabilities required for requirements monitoring of SoS. It will further provide a flexible and tailorable infrastructure to support engineers and maintenance staff in observing and analyzing the behavior of a SoS at runtime. We plan to evaluate our work by assessing its usefulness in the context of an industrial SoS.

show abstract

Section: Introductionmentioning

confidence: 99%

A requirements monitoring infrastructure for systems of systems

Vierhauser

2014

Proceedings of the 29th ACM/IEEE International Conference on Automated Software Engineering

View full text Add to dashboard Cite

show abstract

“…Caffall and Michael propose in [7] the concept of service-oriented contract interfaces for an architectural framework for SoSs. Contract interfaces are based on the principles of Design-by-Contract (DbC) and demand an explicit definition of interfaces among CSs that formalize assumptions about the services provided by a CS to achieve goals of the SoS.…”

Section: Related Workmentioning

confidence: 99%

Interfaces in Evolving Cyber-Physical Systems-of-Systems

Frömel

Kopetz

2016

Cyber-Physical Systems of Systems

View full text Add to dashboard Cite

“…Thus, we included for analysis only the INCOSE studies available in the aforementioned basis. The criteria considered for their selection were availability of primary studies, (Kaiser et al, 2003) Quantifiable Architecting of Dependable Systems of Embedded Systems (Liang and Luqi, 2003) Automated generation of integrated architectures and end-to-end network models (Bonilla et al, 2005) Architectural framework for a system-of-systems (Caffall and Michael, 2005) A unifying framework for systems modeling, control systems design,and system operation (Dvorak et al, 2005) System software framework for system of systems avionics (Ferguson et al, 2005) Systems of systems and coordinated atomic actions (Schaefer, 2005) An adaptable outdoor robotic platform: architecture, communications, and control (Briggs et al, 2006) Architecture-Based Interoperability Evaluation in Evolutions of Networked Enterprises (Chen, 2006) Rapid systems of systems integration -Combining an architecture-centric approach with enterprise service bus infrastructure (Kruger et al, 2006) A distributed simulation approach for modeling and analyzing systems of systems (Sharawi et al, 2006) Quality assurance of the timing properties of real-time, reactive system-of-systems (Shing et al, 2006) Safety, software architecture and MIL-STD-1760 (Squair, 2006) DDSOS: A dynamic distributed service-oriented simulation framework (Tsai et al, 2006) (Sloane et al, 2007) Data fusion enabled networks (Vila, 2007) Architecting communication network of networks for Space System of Systems (Bhasin and Hayden, 2008b) A System-of-Systems Engineering GEOSS: Architectural Approach (Butterfield et al, 2008) A Method for Collaborative Development of Systems of Systems in the Office Domain (Carbon et al, 2008) Architecture Principles and the GEOSS Clearinghouse (Christian, 2008) Applying Object Oriented Systems Engineering to Complex Systems (Cloutier and Griego, 2008) A Rich Services Approach to CoCoME (Demchak et al, 2008) Precision guidance of agricultural tractors for autonomous farming (Eaton et al, 2008) Aspect-oriented modeling ap...…”

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

Architectural Framework for a System-of-Systems

Cited by 7 publications

References 6 publications

A requirements monitoring infrastructure for systems of systems

A requirements monitoring infrastructure for systems of systems

Interfaces in Evolving Cyber-Physical Systems-of-Systems

Supporting architectural design of acknowledged SoS

Contact Info

Product

Resources

About