Pub Date : 2020-03-01DOI: 10.1109/ICSA-C50368.2020.00026
C. Castellanos, B. Pérez, D. Correal, Carlos A. Varela
Big data analytics (BDA) applications use machine learning to extract valuable insights from large, fast, and heterogeneous data sources. The architectural design and evaluation of BDA applications entail new challenges to integrate emerging machine learning algorithms with cutting-edge practices whilst ensuring performance levels even in the presence of large data volume, velocity, and variety (3Vs). This paper presents a design process approach based on the Attribute-Driven Design (ADD) method and Architecture tradeoff analysis method (ATAM) to specify, deploy, and monitor performance metrics in BDA applications supported by domain-specific modeling and DevOps. Our design process starts with the definition of architectural drivers, followed by functional and deployment specification through integrated high-level modeling which enables quality scenarios monitoring. We used two use cases from avionics to evaluate this proposal, and the preliminary results suggest advantages by integrating multiple views, automating deployment and monitoring compared to similar approaches.
{"title":"A Model-Driven Architectural Design Method for Big Data Analytics Applications","authors":"C. Castellanos, B. Pérez, D. Correal, Carlos A. Varela","doi":"10.1109/ICSA-C50368.2020.00026","DOIUrl":"https://doi.org/10.1109/ICSA-C50368.2020.00026","url":null,"abstract":"Big data analytics (BDA) applications use machine learning to extract valuable insights from large, fast, and heterogeneous data sources. The architectural design and evaluation of BDA applications entail new challenges to integrate emerging machine learning algorithms with cutting-edge practices whilst ensuring performance levels even in the presence of large data volume, velocity, and variety (3Vs). This paper presents a design process approach based on the Attribute-Driven Design (ADD) method and Architecture tradeoff analysis method (ATAM) to specify, deploy, and monitor performance metrics in BDA applications supported by domain-specific modeling and DevOps. Our design process starts with the definition of architectural drivers, followed by functional and deployment specification through integrated high-level modeling which enables quality scenarios monitoring. We used two use cases from avionics to evaluate this proposal, and the preliminary results suggest advantages by integrating multiple views, automating deployment and monitoring compared to similar approaches.","PeriodicalId":202587,"journal":{"name":"2020 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"105 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134290365","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}
Pub Date : 2020-03-01DOI: 10.1109/ICSA-C50368.2020.00035
Vlad Stirbu, T. Mikkonen
As digital transformation affects more and more industries, the increased role of software and the skills required to develop software trigger a ripple effect. Entire industries, where regulations and government standards play an important role (e.g. health care, avionics, etc.), have used long development cycles that relied on detailed up-front planning before advancing to any detailed decision. In contrast to this mindset, agile software development has proven to deliver results that satisfy customers needs faster than traditional waterfall methodologies. The lack of detailed upfront planning and fast delivery cycles have led to situations where the use of agile became synonymous with lack of documentation and poor quality, and hence the perception that the approach is not suitable for regulated systems. In this experience paper we describe the implementation of a service that integrates medical device software compliance specific activities such as architectural design and limited risk management into the daily agile practices of a software development team.
{"title":"CompliancePal: A Tool for Supporting Practical Agile and Regulatory-Compliant Development of Medical Software","authors":"Vlad Stirbu, T. Mikkonen","doi":"10.1109/ICSA-C50368.2020.00035","DOIUrl":"https://doi.org/10.1109/ICSA-C50368.2020.00035","url":null,"abstract":"As digital transformation affects more and more industries, the increased role of software and the skills required to develop software trigger a ripple effect. Entire industries, where regulations and government standards play an important role (e.g. health care, avionics, etc.), have used long development cycles that relied on detailed up-front planning before advancing to any detailed decision. In contrast to this mindset, agile software development has proven to deliver results that satisfy customers needs faster than traditional waterfall methodologies. The lack of detailed upfront planning and fast delivery cycles have led to situations where the use of agile became synonymous with lack of documentation and poor quality, and hence the perception that the approach is not suitable for regulated systems. In this experience paper we describe the implementation of a service that integrates medical device software compliance specific activities such as architectural design and limited risk management into the daily agile practices of a software development team.","PeriodicalId":202587,"journal":{"name":"2020 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"35 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114516938","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}
Pub Date : 2020-03-01DOI: 10.1109/ICSA-C50368.2020.00029
A. Abreu, E. Coutinho
Blockchain technology was developed initially for the creation of a crypto-currency. Now it is being exploited for several other applications, such as health, agriculture, IoT and education. Adding blockchain technology to existing systems requires a careful planning of integration between the different environments and technologies. Building blockchain-based applications enables a software which is executed in a decentralized, trustless, transparent and tamper-proof environment, generally called decentralized applications. This article aims to motivate systems modeling activity, specifically between web and blockchain applications. This is an initial study, and as preliminary results we suggest the use of sequence diagrams for modeling the integration between technologies.
{"title":"Motivating Web and Blockchain Application Modeling","authors":"A. Abreu, E. Coutinho","doi":"10.1109/ICSA-C50368.2020.00029","DOIUrl":"https://doi.org/10.1109/ICSA-C50368.2020.00029","url":null,"abstract":"Blockchain technology was developed initially for the creation of a crypto-currency. Now it is being exploited for several other applications, such as health, agriculture, IoT and education. Adding blockchain technology to existing systems requires a careful planning of integration between the different environments and technologies. Building blockchain-based applications enables a software which is executed in a decentralized, trustless, transparent and tamper-proof environment, generally called decentralized applications. This article aims to motivate systems modeling activity, specifically between web and blockchain applications. This is an initial study, and as preliminary results we suggest the use of sequence diagrams for modeling the integration between technologies.","PeriodicalId":202587,"journal":{"name":"2020 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"238 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116105497","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}
Pub Date : 2020-03-01DOI: 10.1109/ICSA-C50368.2020.00052
Leo Silva, Luíis Anunciado Silva, U. Kulesza, Djalma Antony Rodrigues, Felipe A. P. Pinto
This paper presents PerfMinerArch, a tool to visualize and analyze performance deviations from subsequent evolutions of a software system. It provides architecture views that allow developers to identify scenarios and system packages/modules that have variations in their performance. It also allows exploring performance deviations of each scenario to a more detailed perspective that shows the methods and commits in repositories that are responsible for them. The tool has been applied to identify performance deviations in existing open-source software systems.
{"title":"PerfMinerArch - A Tool to Visualize and Analyze Performance Deviations","authors":"Leo Silva, Luíis Anunciado Silva, U. Kulesza, Djalma Antony Rodrigues, Felipe A. P. Pinto","doi":"10.1109/ICSA-C50368.2020.00052","DOIUrl":"https://doi.org/10.1109/ICSA-C50368.2020.00052","url":null,"abstract":"This paper presents PerfMinerArch, a tool to visualize and analyze performance deviations from subsequent evolutions of a software system. It provides architecture views that allow developers to identify scenarios and system packages/modules that have variations in their performance. It also allows exploring performance deviations of each scenario to a more detailed perspective that shows the methods and commits in repositories that are responsible for them. The tool has been applied to identify performance deviations in existing open-source software systems.","PeriodicalId":202587,"journal":{"name":"2020 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"19 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115154121","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}
Pub Date : 2020-03-01DOI: 10.1109/ICSA-C50368.2020.00050
S. Lopes, Iohan Gonçalves Vargas, A. L. Oliveira, R. Braga
Context: System of Systems (SoS) is a set of independent systems that cooperate to achieve an emergent behavior. SoSs have been used in different domains such as defense, transportation, energy, and health care, which directly impact on the society. The critical nature of SoS, in which a failure in one of its Constituent Systems (CSs) may lead to catastrophic damages to the property, environment, injuries or loss of human’s life, demands risk management activities. Existing risk management practices applied to SoS are extensions of risk management techniques at the CS level. Objective: in this paper, we present an overview of risk management approaches and tools for SoS. Method: we performed a Systematic Mapping (SM) study by searching into five databases to identify primary studies. We identified 22 primary studies related to risk management practices for SoS. Results: from the analysis of these primary studies, we identified a set of risks and risk management practices for SoS and their differences to risk management techniques at the CS level. Conclusion: the identified approaches and support tools for risk management in the SoS level are not well established yet.
{"title":"Risk Management for System of Systems: A Systematic Mapping Study","authors":"S. Lopes, Iohan Gonçalves Vargas, A. L. Oliveira, R. Braga","doi":"10.1109/ICSA-C50368.2020.00050","DOIUrl":"https://doi.org/10.1109/ICSA-C50368.2020.00050","url":null,"abstract":"Context: System of Systems (SoS) is a set of independent systems that cooperate to achieve an emergent behavior. SoSs have been used in different domains such as defense, transportation, energy, and health care, which directly impact on the society. The critical nature of SoS, in which a failure in one of its Constituent Systems (CSs) may lead to catastrophic damages to the property, environment, injuries or loss of human’s life, demands risk management activities. Existing risk management practices applied to SoS are extensions of risk management techniques at the CS level. Objective: in this paper, we present an overview of risk management approaches and tools for SoS. Method: we performed a Systematic Mapping (SM) study by searching into five databases to identify primary studies. We identified 22 primary studies related to risk management practices for SoS. Results: from the analysis of these primary studies, we identified a set of risks and risk management practices for SoS and their differences to risk management techniques at the CS level. Conclusion: the identified approaches and support tools for risk management in the SoS level are not well established yet.","PeriodicalId":202587,"journal":{"name":"2020 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"27 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126393278","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}
Pub Date : 2020-03-01DOI: 10.1109/ICSA-C50368.2020.00041
Jean-Philippe Stoldt, J. Weber
Initiatives leveraging the emerging SMART on FHIR standard are promising healthcare system improvements while reducing information technology costs with reusable system components. Previously closed Electronic Medical Record systems are gradually opened to third party applications through FHIR-enabled APIs. While this allows for technical interoperability, patient safety concerns from data quality issues with the underlying system data remain unsolved. We propose to apply a “Data Quality by Contract” approach to pre- and post-conditions of data use cases to assure safe operation of SMART on FHIR apps. We demonstrate how a cardiac risk scoring app could leverage data quality probes to validate several data quality concerns.
{"title":"Safety Improvement for SMART on FHIR Apps with Data Quality by Contract","authors":"Jean-Philippe Stoldt, J. Weber","doi":"10.1109/ICSA-C50368.2020.00041","DOIUrl":"https://doi.org/10.1109/ICSA-C50368.2020.00041","url":null,"abstract":"Initiatives leveraging the emerging SMART on FHIR standard are promising healthcare system improvements while reducing information technology costs with reusable system components. Previously closed Electronic Medical Record systems are gradually opened to third party applications through FHIR-enabled APIs. While this allows for technical interoperability, patient safety concerns from data quality issues with the underlying system data remain unsolved. We propose to apply a “Data Quality by Contract” approach to pre- and post-conditions of data use cases to assure safe operation of SMART on FHIR apps. We demonstrate how a cardiac risk scoring app could leverage data quality probes to validate several data quality concerns.","PeriodicalId":202587,"journal":{"name":"2020 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133191556","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}
Pub Date : 2020-03-01DOI: 10.1109/ICSA-C50368.2020.00007
Alberto Avritzer
The goal of this tutorial is to provide an overview of challenges and approaches for architecture/dependability assessment in the context of DevOps and microservices. Specifically, we present approaches that employ operational data obtained from production-level application performance management (APM) tools, giving access to operational workload profiles, architectural information, failure models, and security intrusions. We use this data to automatically create and conFigure architecture assessments based on models, load tests, and resilience benchmarks. The focus of this tutorial is on approaches that employ production usage, because these approaches provide more accurate recommendations for microservice architecture dependability assessment than approaches that do not consider production usage.We present an overview of (1) the state-of-the-art approaches for obtaining operational data from production systems using APM tools, (2) the challenges of dependability for DevOps and microservices, (3) selected approaches based on operational data to assess dependability. The architecture assessment focus of this tutorial is on scalability, resilience, survivability, and security. Particularly, we present a demo of the automated approach for the evaluation of a domain-based scalability and security metric assessment that is based on the microservice architecture ability to satisfy the performance requirement under load and/or intrusions. We illustrate the approach by presenting experimental results using a benchmark microservice architecture.
{"title":"Challenges and Approaches for the Assessment of Micro-Service Architecture Deployment Alternatives in DevOps : A tutorial presented at ICSA 2020","authors":"Alberto Avritzer","doi":"10.1109/ICSA-C50368.2020.00007","DOIUrl":"https://doi.org/10.1109/ICSA-C50368.2020.00007","url":null,"abstract":"The goal of this tutorial is to provide an overview of challenges and approaches for architecture/dependability assessment in the context of DevOps and microservices. Specifically, we present approaches that employ operational data obtained from production-level application performance management (APM) tools, giving access to operational workload profiles, architectural information, failure models, and security intrusions. We use this data to automatically create and conFigure architecture assessments based on models, load tests, and resilience benchmarks. The focus of this tutorial is on approaches that employ production usage, because these approaches provide more accurate recommendations for microservice architecture dependability assessment than approaches that do not consider production usage.We present an overview of (1) the state-of-the-art approaches for obtaining operational data from production systems using APM tools, (2) the challenges of dependability for DevOps and microservices, (3) selected approaches based on operational data to assess dependability. The architecture assessment focus of this tutorial is on scalability, resilience, survivability, and security. Particularly, we present a demo of the automated approach for the evaluation of a domain-based scalability and security metric assessment that is based on the microservice architecture ability to satisfy the performance requirement under load and/or intrusions. We illustrate the approach by presenting experimental results using a benchmark microservice architecture.","PeriodicalId":202587,"journal":{"name":"2020 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122630960","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}
Pub Date : 2020-03-01DOI: 10.1109/ICSA-C50368.2020.00022
Sebastián Vergara, Laura González, R. Ruggia
Microservices have recently emerged as an architectural style in which applications are composed of small services, each running on its own process and communicating with others using lightweight mechanisms. In order to guide the construction of such applications, microservices architectural patterns have been proposed to document knowledge and address recurring situations. However, these patterns are mostly described in an informal way which may lead to ambiguity as well as to their incorrect usage. This paper proposes a formal approach to deal with these issues by formalizing microservices architectural patterns with the Event-B modeling language. The approach aims to provide formal models of these patterns and related results (e.g. formal proofs, visualizations), with the goal of contributing not only to their precise comprehension but also to the development of correct-by-construction microservices applications.
{"title":"Towards Formalizing Microservices Architectural Patterns with Event-B","authors":"Sebastián Vergara, Laura González, R. Ruggia","doi":"10.1109/ICSA-C50368.2020.00022","DOIUrl":"https://doi.org/10.1109/ICSA-C50368.2020.00022","url":null,"abstract":"Microservices have recently emerged as an architectural style in which applications are composed of small services, each running on its own process and communicating with others using lightweight mechanisms. In order to guide the construction of such applications, microservices architectural patterns have been proposed to document knowledge and address recurring situations. However, these patterns are mostly described in an informal way which may lead to ambiguity as well as to their incorrect usage. This paper proposes a formal approach to deal with these issues by formalizing microservices architectural patterns with the Event-B modeling language. The approach aims to provide formal models of these patterns and related results (e.g. formal proofs, visualizations), with the goal of contributing not only to their precise comprehension but also to the development of correct-by-construction microservices applications.","PeriodicalId":202587,"journal":{"name":"2020 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"95 3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124562442","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}
Pub Date : 2020-03-01DOI: 10.1109/ICSA-C50368.2020.00016
J. Nupponen, D. Taibi
Serverless, the new buzzword, has been gaining a lot of attention from the developers and industry. Cloud vendors such as AWS and Microsoft have hyped the architecture almost everywhere, from practitioners’ conferences to local events, to blog posts. In this work, we introduce serverless functions (also known as Function-as-a-Service or FaaS), together with on bad practices experienced by practitioners, members of the Tampere Serverless Meetup group.
{"title":"Serverless: What it Is, What to Do and What Not to Do","authors":"J. Nupponen, D. Taibi","doi":"10.1109/ICSA-C50368.2020.00016","DOIUrl":"https://doi.org/10.1109/ICSA-C50368.2020.00016","url":null,"abstract":"Serverless, the new buzzword, has been gaining a lot of attention from the developers and industry. Cloud vendors such as AWS and Microsoft have hyped the architecture almost everywhere, from practitioners’ conferences to local events, to blog posts. In this work, we introduce serverless functions (also known as Function-as-a-Service or FaaS), together with on bad practices experienced by practitioners, members of the Tampere Serverless Meetup group.","PeriodicalId":202587,"journal":{"name":"2020 IEEE International Conference on Software Architecture Companion (ICSA-C)","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127657590","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
扫码关注我们
求助内容：
应助结果提醒方式：