2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED)最新文献

Technology Enabled Continuous Software Development 技术支持持续软件开发

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1145/2896941.2896943

Paul M. Clarke, Peter Elger, Rory V. O'Connor

引用次数: 7

From Requirements to Continuous Re-prioritization of Hypotheses 从需求到假设的持续重新排序

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1145/2896941.2896955

H. H. Olsson, J. Bosch

引用次数: 6

Enhanced Playback of Automated Service Emulation Models Using Entropy Analysis 利用熵分析增强自动服务仿真模型的回放

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1145/2896941.2896950

Steven Versteeg, Miao Du, J. Bird, Jean-Guy Schneider, J. Grundy, Jun Han

引用次数: 10

Context-Aware User Feedback in Continuous Software Evolution 持续软件演进中的上下文感知用户反馈

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1145/2896941.2896952

Dora Dzvonyar, Stephan Krusche, Rana Alkadhi, B. Bruegge

引用次数: 24

From Ideas to Implementations: Closing the Gaps between Technical Experts and Software Solutions 从想法到实现:缩小技术专家和软件解决方案之间的差距

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1145/2896941.2896945

Karen Smiley, Jeff Harding, Pankesh Patel

{"title":"From Ideas to Implementations: Closing the Gaps between Technical Experts and Software Solutions","authors":"Karen Smiley, Jeff Harding, Pankesh Patel","doi":"10.1145/2896941.2896945","DOIUrl":"https://doi.org/10.1145/2896941.2896945","url":null,"abstract":"Rapid delivery strategies strive to balance critical performance qualities vs. reducing the time between an idea and deployment of a software implementation of that idea. For industrial software solutions that encapsulate expertise in deliverable components, technical SMEs (Subject Matter Experts) with ideas and knowledge have traditionally partnered as requirements providers with software development teams. These human processes are not optimally fast, are vulnerable to errors in translating or interpreting requirements, and do not scale when software teams need to integrate the knowledge of many SMEs into multiple software solutions and deployments. To address these limitations, ABB has pursued an industrial research initiative for innovative SME toolsets with focus on two goals: to accelerate the creation, evolution, reuse, and delivery of expert algorithms, and to streamline the deployment of these algorithms into releases and fielded solutions. The vision underpinning the initiative is to empower technical SMEs as “end-user developers” to convert their knowledge into reusable software solution components without having to learn, perform, or partner on traditional software development, integration, or deployment. In this paper, we summarize our experiences and lessons learned to date from this initiative, key continuing challenges, and some positional thoughts on how end-user development by technical SMEs aligns with emerging approaches for rapid delivery and evolution.","PeriodicalId":438234,"journal":{"name":"2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-05-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129220895","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}

引用次数: 0

Will My Tests Tell Me If I Break This Code? 如果我破坏了代码，测试会告诉我吗?

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1145/2896941.2896944

Rainer Niedermayr, Elmar Jürgens, S. Wagner

{"title":"Will My Tests Tell Me If I Break This Code?","authors":"Rainer Niedermayr, Elmar Jürgens, S. Wagner","doi":"10.1145/2896941.2896944","DOIUrl":"https://doi.org/10.1145/2896941.2896944","url":null,"abstract":"Automated tests play an important role in software evolution because they can rapidly detect faults introduced during changes. In practice, code-coverage metrics are often used as criteria to evaluate the effectiveness of test suites with focus on regression faults. However, code coverage only expresses which portion of a system has been executed by tests, but not how effective the tests actually are in detecting regression faults. Our goal was to evaluate the validity of code coverage as a measure for test effectiveness. To do so, we conducted an empirical study in which we applied an extreme mutation testing approach to analyze the tests of open-source projects written in Java. We assessed the ratio of pseudo-tested methods (those tested in a way such that faults would not be detected) to all covered methods and judged their impact on the software project. The results show that the ratio of pseudo-tested methods is acceptable for unit tests but not for system tests (that execute large portions of the whole system). Therefore, we conclude that the coverage metric is only a valid effectiveness indicator for unit tests.","PeriodicalId":438234,"journal":{"name":"2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED)","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-05-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125135578","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}

引用次数: 24

Towards Applying a Safety Analysis and Verification Method Based on STPA to Agile Software Development 基于STPA的安全分析与验证方法在敏捷软件开发中的应用

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1145/2896941.2896948

Yang Wang, S. Wagner

{"title":"Towards Applying a Safety Analysis and Verification Method Based on STPA to Agile Software Development","authors":"Yang Wang, S. Wagner","doi":"10.1145/2896941.2896948","DOIUrl":"https://doi.org/10.1145/2896941.2896948","url":null,"abstract":"Agile methodologies are becoming widespread in modern software development. However, due to a lack of safety assurance activities, agile methods are criticized for being inadequate for the development of safe software. Safety analysis and safety verication are complementary methods for safety assurance. Yet, both usually rely on traditional, waterfall-like processes. Therefore, it is strongly needed to integrate an appropriate safety analysis approach into agile software development processes driving architecture design and verify the safe design at the code level. This paper presents a novel agile process model \"S-Scrum\" based on the existing development process \"Safe Scrum\"and extended by a safety analysis method and a safety verica- tion approach based on STPA (System-Theoretic Process Analysis). The proposed agile development process S-Scrum can be separated into three parts: (1) performing safety-guided de- sign by STPA inside each sprint. (2) Verifying safety re- quirements at the code level by using model checking. (3) Replacing traditional RAMS (Reliability, Availability, Main- tainability, Safety) validation on thenal product by STPA safety analysis. We adopt other aspects from the original Safe Scrum. Finally, the feasibility of S-Scrum is illustrated with the example of an airbag system.","PeriodicalId":438234,"journal":{"name":"2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED)","volume":"78 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-05-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121800295","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}

引用次数: 8

Software Security in DevOps: Synthesizing Practitioners’ Perceptions and Practices DevOps中的软件安全:综合实践者的认知和实践

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1145/2896941.2896946

A. Rahman, L. Williams

{"title":"Software Security in DevOps: Synthesizing Practitioners’ Perceptions and Practices","authors":"A. Rahman, L. Williams","doi":"10.1145/2896941.2896946","DOIUrl":"https://doi.org/10.1145/2896941.2896946","url":null,"abstract":"In organizations that use DevOps practices, software changes can be deployed as fast as 500 times or more per day. Without adequate involvement of the security team, rapidly deployed software changes are more likely to contain vulnerabilities due to lack of adequate reviews. The goal of this paper is to aid software practitioners in integrating security and DevOps by summarizing experiences in utilizing security practices in a DevOps environment. We analyzed a selected set of Internet artifacts and surveyed representatives of nine organizations that are using DevOps to systematically explore experiences in utilizing security practices. We observe that the majority of the software practitioners have expressed the potential of common DevOps activities, such as automated monitoring, to improve the security of a system. Furthermore, organizations that integrate DevOps and security utilize additional security activities, such as security requirements analysis and performing security configurations. Additionally, these teams also have established collaboration between the security team and the development and operations teams.","PeriodicalId":438234,"journal":{"name":"2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED)","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-05-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132479914","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}

引用次数: 71

Semi-automatic Generation of Audience-Specific Release Notes 半自动生成针对特定受众的发行说明

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1145/2896941.2896953

Sebastian Klepper, Stephan Krusche, B. Brügge

{"title":"Semi-automatic Generation of Audience-Specific Release Notes","authors":"Sebastian Klepper, Stephan Krusche, B. Brügge","doi":"10.1145/2896941.2896953","DOIUrl":"https://doi.org/10.1145/2896941.2896953","url":null,"abstract":"Agile development methodologies encourage frequent releases. However, many releases can overwhelm clients, testers and users if they do not understand what the actual difference is between two versions. Every release raises questions like whether they need to update right away, whether functionality has been added or problems have been fixed and finally whether it is worth their time to try out a new version. Release notes can alleviate this problem by informing their audience about the contents of a particular release, but the creation of high quality release notes takes time and effort. A release manager needs to have the release`s target audience in mind, access information from project management, issue tracker, and build system and might even need input from designers and developers. We describe a semi-automated approach for generating targeted, informative release notes. Our solution is designed from the point of view of a release manager who acts as an editor of auto-generated content based on information gathered from both build server and issue tracker. Furthermore, it allows release notes to be tailored to a specific audience depending on their specific information needs.","PeriodicalId":438234,"journal":{"name":"2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED)","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-05-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117100175","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}

引用次数: 14

Continuous Delivery: Overcoming Adoption Obstacles 持续交付:克服采用障碍

2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery (CSED) Pub Date : 2016-05-14 DOI: 10.1109/CSED.2016.023

Lianping Chen

引用次数: 4