| 1. |
- Antinyan, Vard, 1984, et al.
(författare)
-
Monitoring Evolution of Code Complexity in Agile/Lean Software Development - A Case Study at Two Companies
- 2013
-
Ingår i: 13th Symposium on Programming Languages and Software Tools, SPLST 2013 - Proceedings. - 9789633062289 ; , s. 1-15
-
Konferensbidrag (refereegranskat)abstract
- One of the distinguishing characteristics of Agile and Lean software development is that software products “grow” with new functionality with relatively small increments. Continuous customer demands of new features and the companies’ abilities to deliver on those demands are the two driving forces behind this kind of software evolution. Despite the numerous benefits there are a number of risks associated with this kind of growth. One of the main risks is the fact that the complexity of the software product grows slowly, but over time reaches scales which makes the product hard to maintain or evolve. The goal of this paper is to present a measurement system for monitoring the growth of complexity and drawing attention when it becomes problematic. The measurement system was developed during a case study at Ericsson and Volvo Group Truck Technology. During the case study we explored the evolution of size, complexity, revisions and number of designers of two large software products from the telecom and automotive domains. The results show that two measures needed to be monitored to keep the complexity development under control - McCabe’s complexity and number of revisions.
|
|
| 2. |
|
|
| 3. |
|
|
| 4. |
|
|
| 5. |
- 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.
|
|
| 6. |
- Staron, Miroslaw, 1977, et al.
(författare)
-
Identifying Implicit Architectural Dependencies using Measures of Source Code Change Waves
- 2013
-
Ingår i: 39th Euromicro Conference Series on Software Engineering and Advanced Applications, SEAA 2013; Santander; Spain; 4 September 2013 through 6 September 2013. - 9780769550916 ; , s. 325-332
-
Konferensbidrag (refereegranskat)abstract
- The principles of Agile software development are increasingly used in large software development projects, e.g. using Scrum of Scrums or combining Agile and Lean development methods. When large software products are developed by self-organized, usually feature-oriented teams, there is a risk that architectural dependencies between software components become uncontrolled. In particular there is a risk that the prescriptive architecture models in form of diagrams are outdated and implicit architectural dependencies may become more frequent than the explicit ones. In this paper we present a method for automated discovery of potential dependencies between software components based on analyzing revision history of software repositories. The result of this method is a map of implicit dependencies which is used by architects in decisions on the evolution of the architecture. The software architects can assess the validity of the dependencies and can prevent unwanted component couplings and design erosion hence minimizing the risk of post-release quality problems. Our method was evaluated in a case study at one large product at Saab Electronic Defense Systems (Saab EDS) and one large software product at Ericsson AB.
|
|
| 7. |
- Al Sabbagh, Khaled, 1987, et al.
(författare)
-
Improving Data Quality for Regression Test Selection by Reducing Annotation Noise
- 2020
-
Ingår i: Proceedings - 46th Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2020. ; , s. 191-194
-
Konferensbidrag (refereegranskat)abstract
- Big data and machine learning models have been increasingly used to support software engineering processes and practices. One example is the use of machine learning models to improve test case selection in continuous integration. However, one of the challenges in building such models is the identification and reduction of noise that often comes in large data. In this paper, we present a noise reduction approach that deals with the problem of contradictory training entries. We empirically evaluate the effectiveness of the approach in the context of selective regression testing. For this purpose, we use a curated training set as input to a tree-based machine learning ensemble and compare the classification precision, recall, and f-score against a non-curated set. Our study shows that using the noise reduction approach on the training instances gives better results in prediction with an improvement of 37% on precision, 70% on recall, and 59% on f-score.
|
|
| 8. |
- Al Sabbagh, Khaled, 1987, et al.
(författare)
-
Selective Regression Testing based on Big Data: Comparing Feature Extraction Techniques
- 2020
-
Ingår i: IEEE Software. - 1937-4194 .- 0740-7459. ; , s. 322-329
-
Konferensbidrag (refereegranskat)abstract
- Regression testing is a necessary activity in continuous integration (CI) since it provides confidence that modified parts of the system are correct at each integration cycle. CI provides large volumes of data which can be used to support regression testing activities. By using machine learning, patterns about faulty changes in the modified program can be induced, allowing test orchestrators to make inferences about test cases that need to be executed at each CI cycle. However, one challenge in using learning models lies in finding a suitable way for characterizing source code changes and preserving important information. In this paper, we empirically evaluate the effect of three feature extraction algorithms on the performance of an existing ML-based selective regression testing technique. We designed and performed an experiment to empirically investigate the effect of Bag of Words (BoW), Word Embeddings (WE), and content-based feature extraction (CBF). We used stratified cross validation on the space of features generated by the three FE techniques and evaluated the performance of three machine learning models using the precision and recall metrics. The results from this experiment showed a significant difference between the models' precision and recall scores, suggesting that the BoW-fed model outperforms the other two models with respect to precision, whereas a CBF-fed model outperforms the rest with respect to recall.
|
|
| 9. |
- Antinyan, Vard, 1984, et al.
(författare)
-
Identifying risky areas of software code in Agile/Lean software development: An industrial experience report
- 2014
-
Ingår i: 2014 Software Evolution Week - IEEE Conference on Software Maintenance, Reengineering, and Reverse Engineering, CSMR-WCRE 2014 - Proceedings. - : IEEE. - 9781479941742
-
Konferensbidrag (refereegranskat)abstract
- Modern software development relies on incremental delivery to facilitate quick response to customers' requests. In this dynamic environment the continuous modifications of software code can cause risks for software developers; when developing a new feature increment, the added or modified code may contain fault-prone or difficult-to-maintain elements. The outcome of these risks can be defective software or decreased development velocity. This study presents a method to identify the risky areas and assess the risk when developing software code in Lean/Agile environment. We have conducted an action research project in two large companies, Ericsson AB and Volvo Group Truck Technology. During the study we have measured a set of code properties and investigated their influence on risk. The results show that the superposition of two metrics, complexity and revisions of a source code file, can effectively enable identification and assessment of the risk. We also illustrate how this kind of assessment can be successfully used by software developers to manage risks on a weekly basis as well as release-wise. A measurement system for systematic risk assessment has been introduced to two companies. © 2014 IEEE.
|
|
| 10. |
- Antinyan, Vard, 1984, et al.
(författare)
-
Monitoring Evolution of Code Complexity and Magnitude of Changes
- 2014
-
Ingår i: Acta Cybernetica. - 0324-721X. ; 21:3, s. 367-382
-
Tidskriftsartikel (refereegranskat)abstract
- Background: Complexity management has become a crucial activity in continuous software development. While the overall perceived complexity of a product grows rather insignificantly, the small units, such as functions and files, can have noticeable complexity growth with every increment of product features. This kind of evolution triggers risks of escalating fault-proneness and deteriorating maintainability. Goal: The goal of this research was to develop a measurement system which enables effective monitoring of complexity evolution. Method: An action research has been conducted in two large software development organiza-tions. We have measured three complexity and two change properties of code for two large industrial products. The complexity growth has been measured for five consecutive releases of products. Different patterns of growth have been identified and evaluated with software engi-neers in industry. Results: The results show that monitoring cyclomatic complexity evolution of functions and number of revisions of files focuses the attention of designers to potentially problematic files and functions for manual assessment and improvement. A measurement system was developed at Ericsson to support the monitoring process.
|
|
| 11. |
- Antinyan, Vard, et al.
(författare)
-
Monitoring evolution of code complexity and magnitude of changes
- 2014
-
Ingår i: Acta Cybernetica. - : University of Szeged, Institute of Informatics. - 0324-721X. ; 21:3, s. 367-382
-
Tidskriftsartikel (refereegranskat)abstract
- Complexity management has become a crucial activity in continuous software development. While the overall perceived complexity of a product grows rather insignificantly, the small units, such as functions and files, can have noticeable complexity growth with every increment of product features. This kind of evolution triggers risks of escalating fault-proneness and deteriorating maintainability. The goal of this research was to develop a measurement system which enables effective monitoring of complexity evolution. An action research has been conducted in two large software development organizations. We have measured three complexity and two change properties of code for two large industrial products. The complexity growth has been measured for five consecutive releases of the products. Different patterns of growth have been identified and evaluated with software engineers in industry. The results show that monitoring cyclomatic complexity evolution of functions and number of revisions of files focuses the attention of designers to potentially problematic files and functions for manual assessment and improvement. A measurement system was developed at Ericsson to support the monitoring process.
|
|
| 12. |
- Berbyuk Lindström, Nataliya, 1978, et al.
(författare)
-
Understanding Metrics Team-Stakeholder Communication in Agile Metrics Service Delivery
- 2021
-
Ingår i: APSEC (Asian Pacific Software Engineering conference), December 6-10, Taiwan-Virtual.. ; 2021-December, s. 401-409
-
Konferensbidrag (refereegranskat)abstract
- In this paper, we explore challenges in communication between metrics teams and stakeholders in metrics service delivery. Drawing on interviews and interactive workshops with team members and stakeholders at two different Swedish agile software development organizations, we identify interrelated challenges such as aligning expectations, prioritizing demands, providing regular feedback, and maintaining continuous dialogue, which influence team-stakeholder interaction, relationships and performance. Our study shows the importance of understanding communicative hurdles and provides suggestions for their mitigation, therefore meriting further empirical research.
|
|
| 13. |
- 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.
|
|
| 14. |
- Ochodek, M., et al.
(författare)
-
Automated Code Review Comment Classification to Improve Modern Code Reviews
- 2022
-
Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. ; 439 LNBIP, s. 23-40
-
Konferensbidrag (refereegranskat)abstract
- Modern Code Reviews (MCRs) are a widely-used quality assurance mechanism in continuous integration and deployment. Unfortunately, in medium and large projects, the number of changes that need to be integrated, and consequently the number of comments triggered during MCRs could be overwhelming. Therefore, there is a need for quickly recognizing which comments are concerning issues that need prompt attention to guide the focus of the code authors, reviewers, and quality managers. The goal of this study is to design a method for automated classification of review comments to identify the needed change faster and with higher accuracy. We conduct a Design Science Research study on three open-source systems. We designed a method (CommentBERT) for automated classification of the code-review comments based on the BERT (Bidirectional Encoder Representations from Transformers) language model and a new taxonomy of comments. When applied to 2,672 comments from Wireshark, The Mono Framework, and Open Network Automation Platform (ONAP) projects, the method achieved accuracy, measured using Matthews Correlation Coefficient, of 0.46–0.82 (Wireshark), 0.12–0.8 (ONAP), and 0.48–0.85 (Mono). Based on the results, we conclude that the proposed method seems promising and could be potentially used to build machine-learning-based tools to support MCRs as long as there is a sufficient number of historical code-review comments to train the model.
|
|
| 15. |
- 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.
|
|
| 16. |
- 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.
|
|
| 17. |
- Staron, Miroslaw, 1977, et al.
(författare)
-
Consequences of Mispredictions of Software Reliability: A Model and its Industrial Evaluation
- 2014
-
Ingår i: IWSM Mensura 2014.
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- Predicting reliability of software under development is an important part of estimations in software engineering projects. In many organizations as the goal is that software products are released with no known defects, the process of finding and removing defects correlates with the effort for software projects. Software development projects estimate the resources needed to design, develop, test and release software products, and the number of defects which have to be handled. In this paper we present a model for consequence analysis of inaccurate predictions of quality in software projects. The model is a result of multiple case studies and is evaluated at two companies. The model recognizes the most common mispredictions – e.g. over- and under-prediction, early- and late-predictions – and the combination of theses. The results from the industrial evaluation show that the consequences can be grouped according to under- and over-predictions and that the late- and early-predictions have the same consequences. The results show also that mispredicting the shape of the reliability curve has a significant consequence with regard to assessment of release readiness and resource planning.
|
|
| 18. |
- Staron, Miroslaw, 1977, et al.
(författare)
-
Dashboards for continuous monitoring of quality for software product under development
- 2014
-
Ingår i: System Qualities and Software Architecture (SQSA). - Amsterdam : Elsevier. - 9780124171688
-
Bokkapitel (refereegranskat)abstract
- This chapter contributes with a systematic overview of good examples on how dashboards are used to monitor quality of software products under development – both using multiple measures and a single indicator which combines quality and development progress. In this chapter we extract recommendations for building such dashboards for practitioners by exploring how three companies use dashboards for monitoring and controlling external and internal quality of large software products under development. The dashboards presented by each company contain a number of indicators each, and have different premises due to the domain of the product, its purpose and the organization. We describe a number of common principles behind a set of measures, which address the challenge of quantifying readiness to deliver of software products to their end customers. The experiences presented in this chapter come from multiple case studies at Ericsson, two studies at Volvo Car Corporation (VCC) and one at Saab Electronic Defense Systems in Sweden. All companies have a long experience with software development and have undergone a transition into Agile and Lean software development; however the experience with these new paradigms differs from two to five years depending on the company. The difference in the experience provide a possibility to observe that companies with longer experience tend to focus on using measures to support self-organized teams whereas companies with shorter experience tend to focus on using measures to communicate the status from teams to management.
|
|
| 19. |
- Staron, Miroslaw, 1977, et al.
(författare)
-
Improving Quality of Code Review Datasets – Token-Based Feature Extraction Method
- 2021
-
Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. ; 404, s. 81-93
-
Konferensbidrag (refereegranskat)abstract
- Machine learning is used increasingly frequent in software engineering to automate tasks and improve the speed and quality of software products. One of the areas where machine learning starts to be used is the analysis of software code. The goal of this paper is to evaluate a new method for creating machine learning feature vectors, based on the content of a line of code. We designed a new feature extraction algorithm and evaluated it in an industrial case study. Our results show that using the new feature extraction technique improves the overall performance in terms of MCC (Matthews Correlation Coefficient) by 0.39 – from 0.31 to 0.70, while reducing the precision by 0.05. The implications of this is that we can improve overall prediction accuracy for both true positives and true negatives significantly. This increases the trust in the predictions by the practitioners and contributes to its deeper adoption in practice.
|
|
| 20. |
- Staron, Miroslaw, 1977, et al.
(författare)
-
Measuring and Visualizing Code Stability - A Case Study at Three Companies
- 2013
-
Ingår i: IWSM/Mensura, Conference proceedings, IEEE. - : IEEE.
-
Konferensbidrag (refereegranskat)abstract
- Monitoring performance of software development organizations can be achieved from a number of perspectives – e.g. using such tools as Balanced Scorecards or corporate dashboards. However, automated monitoring through quantitative metrics usually gives the best cost-benefit trade-off. In this paper we present results from a study on using code stability indicators as a tool for product stability and organizational performance, conducted at three different software development companies – Ericsson AB, Saab AB Electronic Defense Systems (Saab) and Volvo Group Trucks Technology (Volvo Group). The results show that visualizing the source code changes using heatmaps and linking these visualizations to defect inflow profiles provide indicators of how stable the product under development is and whether quality assurance efforts should be directed to specific parts of the product. Observing the indicator and making decisions based on its visualization leads to shorter feedback loops between development and test, thus resulting in lower development costs, shorter lead time and increased quality. The industrial case study in the paper shows that the indicator and its visualization can show whether the modifications of software products are focused on parts of the code base or are spread widely throughout the product.
|
|
