SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "WFRF:(Meding Wilhelm) srt2:(2015-2019)"

Sökning: WFRF:(Meding Wilhelm) > (2015-2019)

  • Resultat 1-10 av 17
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Al Sabbagh, Khaled, 1987, et al. (författare)
  • Predicting Test Case Verdicts Using TextualAnalysis of Commited Code Churns
  • 2019
  • Ingår i: CEUR Workshop Proceedings. - 1613-0073. ; 2476, s. 138-153
  • Konferensbidrag (refereegranskat)abstract
    • Background: Continuous Integration (CI) is an agile software development practice that involves producing several clean builds of the software per day. The creation of these builds involve running excessive executions of automated tests, which is hampered by high hardware cost and reduced development velocity. Goal: The goal of our research is to develop a method that reduces the number of executed test cases at each CI cycle.Method: We adopt a design research approach with an infrastructure provider company to develop a method that exploits Ma-chine Learning (ML) to predict test case verdicts for committed sourcecode. We train five different ML models on two data sets and evaluate their performance using two simple retrieval measures: precision and recall. Results: While the results from training the ML models on the first data-set of test executions revealed low performance, the curated data-set for training showed an improvement on performance with respect to precision and recall. Conclusion: Our results indicate that the method is applicable when training the ML model on churns of small sizes
  •  
2.
  •  
3.
  • Antinyan, Vard, 1984, et al. (författare)
  • Identifying Complex Functions : By Investigating Various Aspects of Code Complexity
  • 2015
  • Ingår i: Proceedings of 2015 Science and Information Conference (SAI). - : IEEE Press. - 9781479985470 - 9781479985487 - 9781479985463 ; , s. 879-888
  • Konferensbidrag (refereegranskat)abstract
    • The complexity management of software code has become one of the major problems in software development industry. With growing complexity the maintenance effort of code increases. Moreover, various aspects of complexity create difficulties for complexity assessment. The objective of this paper is to investigate the relationships of various aspects of code complexity and propose a method for identifying the most complex functions. We have conducted an action research project in two software development companies and complemented it with a study of three open source products. Four complexity metrics are measured, and their nature and mutual influence are investigated. The results and possible explanations are discussed with software engineers in industry. The results show that there are two distinguishable aspects of complexity of source code functions: Internal and outbound complexities. Those have an inverse relationship. Moreover, the product of them does not seem to be greater than a certain limit, regardless of software size. We present a method that permits identification of most complex functions considering the two aspects of complexities. The evaluation shows that the use of the method is effective in industry: It enables identification of 0.5% most complex functions out of thousands of functions for reengineering.
  •  
4.
  • Calikli, Gul, et al. (författare)
  • Measure early and decide fast: Transforming quality management and measurement to continuous deployment
  • 2018
  • Ingår i: ACM International Conference Proceeding Series. - New York, NY, USA : ACM.
  • Konferensbidrag (refereegranskat)abstract
    • © 2018 Association for Computing Machinery. Continuous deployment has become software companies' inevitable response to the economic pressures of the market. At the same time, software quality is crucial in order to meet customers' expectations and hence succeed in the market. Therefore, current quality management processes require transformation in order to keep up with the fast pace of the market while at the same time meeting customers' expectations. In order to figure out how the current quality management process should be transformed to keep up with the fast pace of the market while ensuring both product quality and continuous deployment, we conducted a qualitative study at a large infrastructure provider company. During the interviews we conducted with the quality manager, developer and test architect, we used a metrics portfolio consisting of 59 candidate metrics that can be used in the transformed quality management process. Our findings show that, out of these candidate metrics, 9 metrics should be used in the internal quality measurement dashboard for quality check at the end of the software development life-cycle (SDLC) before the software is released to customer site, while 3 metrics should be used by quality manager to monitor earlier phases of SDLC and 5 metrics should also be delegated to earlier phases of SDLC but without the involvement of the quality manager. To summarize, our study support the claim that quality managers should not be only gatekeepers, but also proactive controllers of quality by monitoring earlier phases of the SDLC.
  •  
5.
  • Knauss, Eric, 1977, et al. (författare)
  • Supporting Continuous Integration by Code-Churn Based Test Selection
  • 2015
  • Ingår i: RCoSE - 2nd International Workshop on Rapid Continuous Software Engineering @ ICSE 2015 Florence, Italy.
  • Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
    • Continuous integration promises advantages in large-scale software development by enabling software development organizations to deliver new functions faster. However, implementing continuous integration in large software development organizations is challenging because of organizational, social and technical reasons. One of the technical challenges is the ability to rapidly prioritize the test cases which can be executed quickly and trigger the most failures as early as possible. In our research we propose and evaluate a method for selecting a suitable set of functional regression tests on system level. The method is based on analysis of correlations between test-case failures and source code changes and is evaluated by combining semi-structured interviews and workshops with practitioners at Ericsson and Axis Communications in Sweden. The results show that using measures of precision and recall, the test cases can be prioritized. The prioritization leads to finding an optimal test suite to execute before the integration.
  •  
6.
  • Ochodek, Miroslaw, 1980, et al. (författare)
  • Using Machine Learning to Design a Flexible LOC Counter
  • 2017
  • Ingår i: Workshop on Machine Learning Techniques for Software Quality Evaluation. - : IEEE. - 9781509065974
  • Konferensbidrag (refereegranskat)abstract
    • Abstract—Background: The results of counting the size of programs in terms of Lines-of-Code (LOC) depends on the rules used for counting (i.e. definition of which lines should be counted). In the majority of the measurement tools, the rules are statically coded in the tool and the users of the measurement tools do not know which lines were counted and which were not. Goal: The goal of our research is to investigate how to use machine learning to teach a measurement tool which lines should be counted and which should not. Our interest is to identify which parameters of the learning algorithm can be used to classify lines to be counted. Method: Our research is based on the design science research methodology where we construct a measurement tool based on machine learning and evaluate it based on open source programs. As a training set, we use industry professionals to classify which lines should be counted. Results: The results show that classifying the lines as to be counted or not has an average accuracy varying between 0.90 and 0.99 measured as Matthew’s Correlation Coefficient and between 95% and nearly 100% measured as the percentage of correctly classified lines. Conclusions: Based on the results we conclude that using machine learning algorithms as the core of modern measurement instruments has a large potential and should be explored further.
  •  
7.
  • Rana, Rakesh, et al. (författare)
  • Software defect prediction in automotive and telecom domain : A life-cycle approach
  • 2015
  • Ingår i: Software Technologies. - Cham : Springer. - 9783319255781 - 9783319255798 ; , s. 217-232
  • Bokkapitel (refereegranskat)abstract
    • Embedded software is playing an ever increasing role in providing functionality and user experience. At the same time, size and complexity of this software is also increasing which bring new challenges for ensuring quality and dependability. For developing high quality software with superior dependability characteristics requires an effective software development process with greater control. Methods of software defect predictions can help optimize the software verification and validation activities by providing useful information for test resource allocation and release planning decisions. We review the software development and testing process for two large companies from the automotive and telecom domain and map different defect prediction methods and their applicability to their lifecycle phases. Based on the overview and current trends we also identify possible directions for software defect prediction techniques and application in these domains. © Springer International Publishing Switzerland 2015.
  •  
8.
  • Staron, Miroslaw, 1977, et al. (författare)
  • A Key Performance Indicator Quality Model and Its Industrial Evaluation
  • 2016
  • Ingår i: IWSM Mensura 2016.
  • Konferensbidrag (refereegranskat)abstract
    • Background: Modern software development companies increasingly rely on quantitative data in their decisionmaking for product releases, organizational performance assessment and monitoring of product quality. KPIs (Key Performance Indicators) are a critical element in the transformation of raw data (numbers) into decisions (indicators). Goal: The goal of the paper is to develop, document and evaluate a quality model for KPIs – addressing the research question of What characterizes a good KPI? In this paper we consider a KPI to be ”good” when it is actionable and supports the organization in achieving its strategic goals. Method: We use an action research collaborative project with an infrastructure provider company and an automotive OEM to develop and evaluate the model. We analyze a set of KPIs used at both companies and verify whether the organization’s perception of these evaluated KPIs is aligned with the KPI’s assessment according to our model. Results: The results show that the model organizes good practices of KPI development and that it is easily used by the stakeholders to improve the quality of the KPIs or reduce the number of the KPIs. Conclusions: Using the KPI quality model provides the possibility to increase the effect of the KPIs in the organization and decreases the risk of wasting resources for collecting KPI data which cannot be used in practice.
  •  
9.
  • Staron, Miroslaw, 1977, et al. (författare)
  • A portfolio of internal quality metrics for software architects
  • 2017
  • Ingår i: Lecture Notes in Business Information Processing. Software Quality. Complexity and Challenges of Software Engineering in Emerging Technologies. SWQD 2017 (Winkler D., Biffl S., Bergsmann J., eds.). - Cham : Springer. - 1865-1348. - 9783319494203
  • Konferensbidrag (refereegranskat)abstract
    • Maintaining high quality software in the age of interconnected systems, systems of systems and Internet of things requires efficient management of the evolution of the software. Evolving the architecture of the software together with the evolution of the design is one of the key areas in maintaining the high quality. In this paper we present the results of our studies at Software Center (nine companies and five universities) with the goal to identify the main information needs and quality metrics for the role of software architects. As a result of our studies we can describe the most commonly used metrics in software engineering in general and in software architecting in particular – e.g. architectural stability or component coupling. We present these metrics and their interpretation (what should be done and why based on the values of metrics). The theoretical framing for this chapter is the ISO/IEC 15939 standard -- Systems and Software Engineering, Measurement Processes.
  •  
10.
  • Staron, Miroslaw, 1977, et al. (författare)
  • A portfolio of internal quality metrics for software architects
  • 2016
  • Ingår i: Software Quality Days 2017.
  • Konferensbidrag (refereegranskat)abstract
    • Maintaining high quality software in the age of interconnected systems, systems of systems and Internet of things requires efficient management of the evolution of the software. Evolving the architecture of the software together with the evolution of the design is one of the key areas in maintaining the high quality. In this paper we present the results of our studies at Software Center (nine companies and five universities) with the goal to identify the main information needs and quality metrics for the role of software architects. As a result of our studies we can describe the most commonly used metrics in software engineering in general and in software architecting in particular – e.g. architectural stability or component coupling. We present these metrics and their interpretation (what should be done and why based on the values of metrics). The theoretical framing for this chapter is the ISO/IEC 15939 standard -- Systems and Software Engineering, Measurement Processes.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-10 av 17

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy