[Review] Software Engineering Techniques for the Development of Systems of Systems

Abstract
It seems that existing SE technologies can be used to develop SoS. This framework demonstrates the development of SoSs with a variety of CS interactions. And this framework seems to be a case study to develop dynamic and automated interface required for interaction and to develop data-center SoS.

1. Introduction

SoS is different from a single system. There is a fairly broad consensus on the characteristics of SoS (see previous papers). This paper shows how existing software engineering technologies can contribute to SoS development. I actually prototyped this.

2. Software engineering techniques for SoS Development

We present existing SE technologies that can be used for the difficulties associated with SoS development.
2.1. Service-oriented architectures (SOA): A component of the framework is made up of a web service. Because CSs are often in an unknown state until run time, the policy engine provides a run-time configuration. Dynamic proxy generation is easy to manage and developed in .NET.
2.2. Policy-based autonomic computing: global objectives can be expressed as incentive, reward, penalty, etc.
2.3. Formal analysis and verification: PRISM was used to calculate the probability of well-managed workloads.
2.4. Model-driven development and code generation: join and leave dynamically. Model-driven development and runtime code generation
2.5. Component-based development: integration
2.6. Dynamic reconfiguration: continuous change. When a new system model comes in, the policy engine can manage previously unknown IT components that are featured in the model.
2.7. Online machine learning
2.8. Resource discovery: CS finds a partner to dynamically collaborate with. Resource discovery Includes web service.

3. A framework for System-of-Systems Development

3.1. Overview
We have developed a framework for SoS development using all of the above technologies. Details that correspond to the techniques mentioned above follow (this is summarized together in Chapter 2).
3.2. System model and standard autonomic computing polices
The model and policy of the system are well organized by formulas.
3.3. Resource-definition policies for runtime interface generation
We discuss runtime interface generation using model and policy as summarized in Section 3.3.

4. Prototype implementation

5. System of systems development

6. Conclusion

Our framwork can identify SoS component inter-operate in real time. The features of SoS can be shown using technology such as real-time code generation. However, only the asynchronous mode component can create an interface.

References
Calinescu, Radu, and Marta Kwiatkowska. "Software engineering techniques for the development of systems of systems." Monterey Workshop. Springer Berlin Heidelberg, 2008.

Comments

Post a Comment

Popular posts from this blog

[Review] Architecting Principles for Systems-of-Systems

Abstract We suggest the definition, classification, and structure of a system of systems. The system of systems is also called collaborative systems. The structure of the system of systems is mostly communications. 1. Summary Is there a difference between a complex large-scale system and systems of systems? There is operational / managerial independence as a method to classify them. Systems of systems or collaborative systems must fulfill two requirements. First, it has a valid purpose and works for it. Second, component systems are managed by their own purposes, not the whole purpose. SoS is defined on an interface basis. 2. Discussion 2.1. What is a "System of Systems"? "Assemblages of components that are themselves significantly more complex, so much so that they may be regarded as systems and assembled into a larger system" Collaborative system, federated system Examples: wide area networks (such as TCP / IP), integrated air defense: centralized co
Read more

[Review] Systems of Systems Engineering: Basic Concepts, Model-Based Techniques, and Research Directions

This is a general description of Systems of Systems (SoS). It is a huge amount of 41 pages, but the most important thing is to understand the SoS definition and the 8 dimensions that it has. So I wrote only the definitions of SoS and 8 dimensions. SoS Definition System of Systems (SoS) is a system made up of independent constituent systems (CS). SoS is part of system engineering and deals with boundaries such as interface, integration, testing, and communication between independent and distributed CSs. The arrangement of the theoretical systems and constructs in a hierarchy of complexity. A set of connections or associated systems to produce results that could not have been achieved with individual systems 5 principal features by Maier (OMGEE) Operational independence: All systems that are part of SoS operate independently. Managerial independence: self-governance and management of cooperation. Geographic distribution: Each system is remote. Evolutionary development: can
Read more

[Review] System-of-Systems Engineering Management

abstract We review the SoS literature and look at SoS features and SoS as networks. And network management methods can be applied to SoSE. We have created an efficient SoSE management framework using this, and changed the network management principles of fault, configuration, accounting, performance, and security (FCAPS). Introduction The system is a set of elements that satisfy the user's needs. And system engineering is aimed at dealing with the complexities and the difficulties that arise when systems of the system increase. We need to concentrate on the engineering of many complex systems to be integrated and this is called SoSE. There is no agreed definition altogether, but researchers have focused on its features instead. It also includes the principles of networks. Shenhar first described SoS as a network of systems. A network-centric system is an example of a collaborative SoS. In this paper, we will connect the features of SoS and two points of view of SoS to the net
Read more