Towards integrated rule-driven software development for IT ecosystems

Mensing, Benjamin; Goltz, Ursula; Aniculăesei, Adina; Herold, Sebastian; Rausch, Andreas; Gärtner, Stefan; Schneider, Kurt

doi:10.1109/dest.2012.6227951

Cited by 6 publications

(5 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The primary challenge of an IT ecosystem is to provide control mechanisms that ensure the group’s survival through effective evolution while ensuring the individual autonomy of its component system. In recent years, cases of implementing IT ecosystems have been introduced in various types of application domains [ 11 , 12 , 13 , 14 , 15 ], but these are only example cases that show the feasibility of the IT ecosystem concept; no empirical evaluation results have yet been provided.…”

Section: Introductionmentioning

confidence: 99%

An Architecture Framework for Orchestrating Context-Aware IT Ecosystems: A Case Study for Quantitative Evaluation

Park

2018

Sensors

View full text Add to dashboard Cite

With the emergence of various forms of smart devices and new paradigms such as the Internet of Things (IoT) concept, the IT (Information Technology) service areas are expanding explosively compared to the provision of services by single systems. A new system operation concept that has emerged in accordance with such technical trends is the IT ecosystem. The IT ecosystem can be considered a special type of system of systems in which multiple systems with various degrees of autonomy achieve common goals while adapting to the given environment. The single systems that participate in the IT ecosystem adapt autonomously to the current situation based on collected data from sensors. Furthermore, to maintain the services supported by the whole IT ecosystem sustainably, the configuration of single systems that participate in the IT ecosystem also changes appropriately in accordance with the changed situation. In order to support the IT ecosystem, this paper proposes an architecture framework that supports dynamic configuration changes to achieve the goal of the whole IT ecosystem, while ensuring the autonomy of single systems through the collection of data from sensors so as to recognize the situational context of individual participating systems. For the feasibility evaluation of the proposed framework, a simulated example of an IT ecosystem for unmanned forest management was constructed, and the quantitative evaluation results are discussed in terms of the extent to which the proposed architecture framework can continuously provide sustainable services in response to diverse environmental context changes.

show abstract

Section: Introductionmentioning

confidence: 99%

An Architecture Framework for Orchestrating Context-Aware IT Ecosystems: A Case Study for Quantitative Evaluation

Park

2018

Sensors

View full text Add to dashboard Cite

show abstract

“…Among these studies, there is an agreement on the application of this strategy for predicting emergent behaviors in the complex operational structure of SoS. Regarding the employment of technologies and tools from traditional software engineering, we observed some the use and adaptation of approaches to support design processes of SoS software architectures such as MDD techniques (e.g., common modeling languages, model transformations, and frameworks) used on different levels of abstraction (Mensing et al, 2012), SOA as an architectural style in which the constituent systems can collaborate as service providers/consumers (Chigani and Balci, 2012), and Petri-nets applied as a strategy to allow architecture simulation to support design (Ge et al, 2013;Griendling and Mavris, 2010).…”

Section: Rq1 -Activities and Artifacts On Construction Of Sos Softwarmentioning

confidence: 94%

“…Even though the drawn conclusions may have been influenced by the researchers' B.3. SLR: List of Selected Studies Two-level process model for integrated system development (Rossak et al, 1994) Quantifiable software architecture for dependable systems of systems (Liang and Luqi, 2003) A System-of-Systems Engineering GEOSS: Architectural approach (Butterfield et al, 2008) A process for systems-of-systems architecting (Griendling and Mavris, 2010) A design methodology for real-time distributed software architecture based on the behavioral properties and its application to advanced automotive software (Aoyama and Tanabe, 2011) A method for the generation and evaluation of architecture alternatives on the cloud (Iacobucci and Mavris, 2011) Architecting ultra-large-scale green information systems (Chen and Kazman, 2012) The process of architecting for software/system engineering (Chigani and Balci, 2012) Scaling up software architecture analysis Towards integrated rule-driven software development for IT ecosystems (Mensing et al, 2012) A data-centric capability-focused approach for system-of-systems architecture modeling and analysis (Ge et al, 2013) Supporting architectural decision making for systems-of-systems design under uncertainty (Lytra and Zdun, 2013) Goncalves2015 A meta-process to construct software architectures for system of systems (Gonçalves et al, 2015) tails of activities while managers can be more interest in general aspects and results of ongoing work. It is also possible to structure different levels of abstraction in the same process, allowing project managers to choose how complete is the process that they need.…”

Section: B2 Threats To Validitymentioning

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%

“…The authors also describe quality attribute scenarios as a description of how a system is required to respond to possible stimulus and provide a set of parts that it must contain, i.e., source; stimulus; system's stimulated part; condition to the stimulus occurrence; system's response; and metric to measure this response. Mensing et al (2012) propose the concept of "architectural rules" that consists of several properties representing crosscutting architectural concerns. These rules come from the refinement of SoS requirements, i.e., "requirements rules".…”

mentioning

confidence: 99%

See 2 more Smart Citations

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