System of systems (SoS) engineering is an emerging approach to deal with complex systems that have low or no control over their constituents. An SoS must adapt itself not only to the willingness of its constituents to participate or disengage, but also to evolving needs. As reconfiguration is a routine task, the SoS architect needs specific assistance, especially to easily identify reusable solution principles and to track her/his decisions in the design of reconfiguration. To address these issues, we propose to introduce the concept of reconfiguration pattern based on prior design and architectural patterns. These patterns constitute well-documented, principled and adaptable solution building blocks. We illustrate our approach with one reconfiguration pattern applied on an example based on the French communication system for emergency services.
{"title":"Assisting the evolutionary development of SoS with reconfiguration patterns","authors":"F. Petitdemange, I. Borne, J. Buisson","doi":"10.1145/2993412.3004845","DOIUrl":"https://doi.org/10.1145/2993412.3004845","url":null,"abstract":"System of systems (SoS) engineering is an emerging approach to deal with complex systems that have low or no control over their constituents. An SoS must adapt itself not only to the willingness of its constituents to participate or disengage, but also to evolving needs. As reconfiguration is a routine task, the SoS architect needs specific assistance, especially to easily identify reusable solution principles and to track her/his decisions in the design of reconfiguration. To address these issues, we propose to introduce the concept of reconfiguration pattern based on prior design and architectural patterns. These patterns constitute well-documented, principled and adaptable solution building blocks. We illustrate our approach with one reconfiguration pattern applied on an example based on the French communication system for emergency services.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122352242","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Learning the vocabulary of a new language is a very slow and time consuming process which can take many years of dedicated study. Free reading is known to be important for improving vocabulary and so are optimally timed repetitions of learned concepts. However, these two have not been put together until now. This paper presents the architecture of a monitoring ecosystem of applications which tracks the reading activities of a learner and builds a model of their evolving knowledge. Based on this model it can steer their future reading and studying sessions in such a way as to accelerate the speed with which they acquire new vocabulary. The paper describes several requirements for such an ecosystem, together with a prototpye implementation, and component applications. Finally a series of open questions that highlight opportunities for future research are discussed.
{"title":"Bootstrapping an ubiquitous monitoring ecosystem for accelerating vocabulary acquisition","authors":"M. Lungu","doi":"10.1145/2993412.3003389","DOIUrl":"https://doi.org/10.1145/2993412.3003389","url":null,"abstract":"Learning the vocabulary of a new language is a very slow and time consuming process which can take many years of dedicated study. Free reading is known to be important for improving vocabulary and so are optimally timed repetitions of learned concepts. However, these two have not been put together until now. This paper presents the architecture of a monitoring ecosystem of applications which tracks the reading activities of a learner and builds a model of their evolving knowledge. Based on this model it can steer their future reading and studying sessions in such a way as to accelerate the speed with which they acquire new vocabulary. The paper describes several requirements for such an ecosystem, together with a prototpye implementation, and component applications. Finally a series of open questions that highlight opportunities for future research are discussed.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125638724","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
The digital transformation of nearly all industrial sectors leads and will lead to a disruptive change. Instead of traditional linear value chains, we will move towards networked, interconnected value creation - digital ecosystems where multiple organizations and their software systems interact with each other. We can observe an increasing number of ecosystems that strongly gain value by contributions added by other organizations. However, what does this mean for engineering skills needed to initiate and grow an ecosystem with software systems being developed, evolved and operated? In this position paper, we introduce new roles and skill profiles required for engineering software ecosystems. We derived the initial role description based on practical experiences in projects we conducted over the past five years and found these roles to be crucial for the overall success of the organization within a digital ecosystem. Key capabilities we found are strength in business and technology at the same time, the ability to think end-to-end in the ecosystem, and interdisciplinarity regarding software engineering disciplines.
{"title":"Engineering roles for constructing ecosystems","authors":"Steffen Hess, J. Knodel, Matthias Naab, M. Trapp","doi":"10.1145/2993412.3003385","DOIUrl":"https://doi.org/10.1145/2993412.3003385","url":null,"abstract":"The digital transformation of nearly all industrial sectors leads and will lead to a disruptive change. Instead of traditional linear value chains, we will move towards networked, interconnected value creation - digital ecosystems where multiple organizations and their software systems interact with each other. We can observe an increasing number of ecosystems that strongly gain value by contributions added by other organizations. However, what does this mean for engineering skills needed to initiate and grow an ecosystem with software systems being developed, evolved and operated? In this position paper, we introduce new roles and skill profiles required for engineering software ecosystems. We derived the initial role description based on practical experiences in projects we conducted over the past five years and found these roles to be crucial for the overall success of the organization within a digital ecosystem. Key capabilities we found are strength in business and technology at the same time, the ability to think end-to-end in the ecosystem, and interdisciplinarity regarding software engineering disciplines.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122515954","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Honeypot systems are an effective method for defending production systems from security breaches and to gain detailed information about attackers' motivation, tactics, software and infrastructure. In this paper we present how different types of honeypots can be employed to gain valuable information about attacks and attackers, and also outline new and innovative possibilities for future research.
{"title":"Honeypot utilization for analyzing cyber attacks","authors":"Otto Hrad, Simo Kemppainen","doi":"10.1145/2993412.2993415","DOIUrl":"https://doi.org/10.1145/2993412.2993415","url":null,"abstract":"Honeypot systems are an effective method for defending production systems from security breaches and to gain detailed information about attackers' motivation, tactics, software and infrastructure. In this paper we present how different types of honeypots can be employed to gain valuable information about attacks and attackers, and also outline new and innovative possibilities for future research.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"56 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128606668","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
J. Buckley, Jacek Rosik, Sebastian Herold, A. Wasala, Goetz Botterweck, C. Exton
A functional perspective of software systems, at the architectural level allows developers to maintain a consistent understanding of the relationships between different functionalities of their system as it evolves, and allows them to analyze the system at a functional-chunk level rather than at the traditional, structural levels more typically presented by IDEs. This paper describes the derivation, implementation and evaluation of a prototype tool built to obtain this functional perspective from existing systems. The tool supports developers as they first attempt to locate specific functionalities in the source code. This support is based on preliminary design principles identified by observing experienced software developers in-vivo, as they performed this task manually. After the code associated with several such functionalities is located in the code, a graphical view allows the developer to assess the source code dependencies between the identified features and with the rest of the system. This helps developers understand the inter-functional interfaces and can be reviewed over time, as features are added and removed, to ensure on-going consistency between the architect's perspective of the features in the system and the code-base.
{"title":"FLINTS: a tool for architectural-level modeling of features in software systems","authors":"J. Buckley, Jacek Rosik, Sebastian Herold, A. Wasala, Goetz Botterweck, C. Exton","doi":"10.1145/2993412.3003390","DOIUrl":"https://doi.org/10.1145/2993412.3003390","url":null,"abstract":"A functional perspective of software systems, at the architectural level allows developers to maintain a consistent understanding of the relationships between different functionalities of their system as it evolves, and allows them to analyze the system at a functional-chunk level rather than at the traditional, structural levels more typically presented by IDEs. This paper describes the derivation, implementation and evaluation of a prototype tool built to obtain this functional perspective from existing systems. The tool supports developers as they first attempt to locate specific functionalities in the source code. This support is based on preliminary design principles identified by observing experienced software developers in-vivo, as they performed this task manually. After the code associated with several such functionalities is located in the code, a graphical view allows the developer to assess the source code dependencies between the identified features and with the rest of the system. This helps developers understand the inter-functional interfaces and can be reviewed over time, as features are added and removed, to ensure on-going consistency between the architect's perspective of the features in the system and the code-base.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"14 3","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120918248","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Software ecosystems - a topic with increasingly growing interest in academia and industry in the past decade - arguably revolutionized many aspects of industrial software engineering (business models, architectures, platforms, project executions, collaboration models, distribution of assets, to name a few). Software ecosystems enable the contribution of external actors with distinct center a common technology and the potential distribution of the actor contributions to an existing user set. Reference architectures have been proven successful and beneficial for software product lines and traditional software development within distinct domains. They arguably come with a set of benefits that severely counterweights the additional effort of design and implementation. But what is the role of reference architectures in an ecosystem setting? In this position paper, we argue for the use of reference architecture as a means of facilitating the operation of software ecosystems, supporting not only the technical aspects but also business and organizational. Thus, we propose that reference architectures can be used as a tool to facilitate software ecosystem orchestration and promote the ecosystem health. In this work, we identify a set of challenges and propose a research agenda for the further development of the field towards efficiently improving the existing means of ecosystem orchestration.
{"title":"Towards reference architectures as an enabler for software ecosystems","authors":"J. Knodel, K. Manikas","doi":"10.1145/2993412.3003387","DOIUrl":"https://doi.org/10.1145/2993412.3003387","url":null,"abstract":"Software ecosystems - a topic with increasingly growing interest in academia and industry in the past decade - arguably revolutionized many aspects of industrial software engineering (business models, architectures, platforms, project executions, collaboration models, distribution of assets, to name a few). Software ecosystems enable the contribution of external actors with distinct center a common technology and the potential distribution of the actor contributions to an existing user set. Reference architectures have been proven successful and beneficial for software product lines and traditional software development within distinct domains. They arguably come with a set of benefits that severely counterweights the additional effort of design and implementation. But what is the role of reference architectures in an ecosystem setting? In this position paper, we argue for the use of reference architecture as a means of facilitating the operation of software ecosystems, supporting not only the technical aspects but also business and organizational. Thus, we propose that reference architectures can be used as a tool to facilitate software ecosystem orchestration and promote the ecosystem health. In this work, we identify a set of challenges and propose a research agenda for the further development of the field towards efficiently improving the existing means of ecosystem orchestration.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"106 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124100986","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Package-based software ecosystems are composed of thousands of interdependent software packages. Many empirical studies have focused on software packages belonging to a single software ecosystem, and suggest to generalise the results to more ecosystems. We claim that such a generalisation is not always possible, because the technical structure of software ecosystems can be very different, even if these ecosystems belong to the same domain. We confirm this claim through a study of three big and popular package-based programming language ecosystems: R's CRAN archive network, Python's PyPI distribution, and JavaScript's NPM package manager. We study and compare the structure of their package dependency graphs and reveal some important differences that may make it difficult to generalise the findings of one ecosystem to another one.
{"title":"On the topology of package dependency networks: a comparison of three programming language ecosystems","authors":"Alexandre Decan, T. Mens, Maëlick Claes","doi":"10.1145/2993412.3003382","DOIUrl":"https://doi.org/10.1145/2993412.3003382","url":null,"abstract":"Package-based software ecosystems are composed of thousands of interdependent software packages. Many empirical studies have focused on software packages belonging to a single software ecosystem, and suggest to generalise the results to more ecosystems. We claim that such a generalisation is not always possible, because the technical structure of software ecosystems can be very different, even if these ecosystems belong to the same domain. We confirm this claim through a study of three big and popular package-based programming language ecosystems: R's CRAN archive network, Python's PyPI distribution, and JavaScript's NPM package manager. We study and compare the structure of their package dependency graphs and reveal some important differences that may make it difficult to generalise the findings of one ecosystem to another one.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121333454","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Tobias Olsson, Daniel Toll, Morgan Ericsson, Anna Wingkvist
Static architectural conformance checking can be used to find architectural violations, cases where the implementation does not adhere to the architecture, and prevent architectural erosion. We implement a software service for automated conformance checking and investigate the effect this has on the number of architectural violations in software projects. The service is implemented using our heuristic-based approach to static architecture conformance checking of the Model-View-Controller pattern. The service is integrated in the source code management system of each project, so a report is generated every time the source code is modified. The service was evaluated in a field experiment that consisted of eight student projects. We found that the four projects that used the service produced significantly fewer violations compared to those that did not.
{"title":"Evaluation of an architectural conformance checking software service","authors":"Tobias Olsson, Daniel Toll, Morgan Ericsson, Anna Wingkvist","doi":"10.1145/2993412.3003391","DOIUrl":"https://doi.org/10.1145/2993412.3003391","url":null,"abstract":"Static architectural conformance checking can be used to find architectural violations, cases where the implementation does not adhere to the architecture, and prevent architectural erosion. We implement a software service for automated conformance checking and investigate the effect this has on the number of architectural violations in software projects. The service is implemented using our heuristic-based approach to static architecture conformance checking of the Model-View-Controller pattern. The service is integrated in the source code management system of each project, so a report is generated every time the source code is modified. The service was evaluated in a field experiment that consisted of eight student projects. We found that the four projects that used the service produced significantly fewer violations compared to those that did not.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122830109","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Software architecture reconstruction techniques may be used to understand and maintain software systems, especially in these cases where architectural documentation is outdated or missing. Reconstruction of layers is interesting, since the Layers pattern is commonly used in practice. Layers reconstruction algorithms are based on dependency analysis. In this paper, we define two dependency related parameters and explore their impact on the results of a layer reconstruction algorithm. The first parameter concerns the types of dependencies between software units included in the algorithm. The second parameter concerns the maximum ratio of allowed back-call dependencies between two software units in different layers. By means of experiments on a case system, and by means of conformance checking results, we explain and illustrate the impact of differences in parameter settings. We show that these parameters have a big impact. Consequently, exact specification of used parameter values is relevant in publications. Furthermore, parameter configuration options may be considered to improve tool support.
{"title":"Dependency related parameters in the reconstruction of a layered software architecture","authors":"Leo Pruijt, W. Wiersema","doi":"10.1145/2993412.3003394","DOIUrl":"https://doi.org/10.1145/2993412.3003394","url":null,"abstract":"Software architecture reconstruction techniques may be used to understand and maintain software systems, especially in these cases where architectural documentation is outdated or missing. Reconstruction of layers is interesting, since the Layers pattern is commonly used in practice. Layers reconstruction algorithms are based on dependency analysis. In this paper, we define two dependency related parameters and explore their impact on the results of a layer reconstruction algorithm. The first parameter concerns the types of dependencies between software units included in the algorithm. The second parameter concerns the maximum ratio of allowed back-call dependencies between two software units in different layers. By means of experiments on a case system, and by means of conformance checking results, we explain and illustrate the impact of differences in parameter settings. We show that these parameters have a big impact. Consequently, exact specification of used parameter values is relevant in publications. Furthermore, parameter configuration options may be considered to improve tool support.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128814688","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Jessica Díaz, Jennifer Pérez, Jorge E. Pérez, J. Garbajosa
Cyber-physical systems (CPS) refer to the next generation of embedded ICT systems that are interconnected, collaborative and that provide users and businesses with a wide range of smart applications and services. Software in CPS applications ranges from small systems to large systems, aka. Systems of Systems (SoS), such as smart grids and cities. CPSoS require managing massive amounts of data, being aware of their emerging behavior, and scaling out to progressively evolve and add new systems. Cloud computing supports processing and storing massive amounts of data, hosting and delivering services, and configuring self-provisioned resources. Therefore, cloud computing is the natural candidate to solve CPSoS needs. However, the diversity of platforms and the low-level cloud programming models make difficult to find a common solution for the development and deployment of CPSoS. This paper presents the architectural foundations of a cloud-centric framework for automating the development and deployment of CPSoS service applications to converge towards a common open service platform for CPSoS applications. This framework relies on the well-known qualities of the microservices architecture style, the autonomic computing paradigm, and the model-driven software development approach. Its implementation and validation is on-going at two European and national projects.
{"title":"Conceptualizing a framework for cyber-physical systems of systems development and deployment","authors":"Jessica Díaz, Jennifer Pérez, Jorge E. Pérez, J. Garbajosa","doi":"10.1145/2993412.3004852","DOIUrl":"https://doi.org/10.1145/2993412.3004852","url":null,"abstract":"Cyber-physical systems (CPS) refer to the next generation of embedded ICT systems that are interconnected, collaborative and that provide users and businesses with a wide range of smart applications and services. Software in CPS applications ranges from small systems to large systems, aka. Systems of Systems (SoS), such as smart grids and cities. CPSoS require managing massive amounts of data, being aware of their emerging behavior, and scaling out to progressively evolve and add new systems. Cloud computing supports processing and storing massive amounts of data, hosting and delivering services, and configuring self-provisioned resources. Therefore, cloud computing is the natural candidate to solve CPSoS needs. However, the diversity of platforms and the low-level cloud programming models make difficult to find a common solution for the development and deployment of CPSoS. This paper presents the architectural foundations of a cloud-centric framework for automating the development and deployment of CPSoS service applications to converge towards a common open service platform for CPSoS applications. This framework relies on the well-known qualities of the microservices architecture style, the autonomic computing paradigm, and the model-driven software development approach. Its implementation and validation is on-going at two European and national projects.","PeriodicalId":409631,"journal":{"name":"Proccedings of the 10th European Conference on Software Architecture Workshops","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125787239","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：