SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "WFRF:(Torkar Richard 1971) "

Sökning: WFRF:(Torkar Richard 1971)

  • Resultat 1-50 av 63
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Berntsson Svensson, Richard, 1978, et al. (författare)
  • Not all requirements prioritization criteria are equal at all times: A quantitative analysis
  • 2024
  • Ingår i: Journal of Systems and Software. - 0164-1212. ; 209
  • Tidskriftsartikel (refereegranskat)abstract
    • Requirement prioritization is recognized as an important decision-making activity in requirements engineering. Requirement prioritization is applied to determine which requirements should be implemented and released. In order to prioritize requirements, there are several approaches/techniques/tools that use different requirements prioritization criteria, which are often identified by gut feeling instead of an in-depth analysis of which criteria are most important to use. Therefore, in this study we investigate which requirements prioritization criteria are most important to use in industry when determining which requirements are implemented and released, and if the importance of the criteria change depending on how far a requirement has reached in the development process. We conducted a quantitative study where quantitative data was collected through a case study of one completed project from one software developing company by extracting 32,139 requirements prioritization decisions based on eight requirements prioritization criteria for 11,110 requirements. The results show that not all requirements prioritization criteria are equally important, and this change depending on how far a requirement has reached in the development process. For example, for requirements prioritization decisions before iteration/sprint planning, having high Business value had an impact on the decisions, but after iteration/sprint planning, having high Business value had no impact. Editor's note: Open Science material was validated by the Journal of Systems and Software Open Science Board.
  •  
2.
  • Berntsson Svensson, Richard, 1978, et al. (författare)
  • Quality Requirements in Industrial Practice - An Extended Interview Study at Eleven Companies
  • 2011
  • Ingår i: IEEE Transactions on Software Engineering. - 0098-5589 .- 1939-3520.
  • Tidskriftsartikel (refereegranskat)abstract
    • In order to create a successful software product and assure its quality, it is not enough to fulfill the functional requirements, it is also crucial to find the right balance among competing quality requirements (QR). An extended, previously piloted, interview study was performed to identify specific challenges associated with the selection, trade-off, and management of QR in industrial practice. Data was collected through semi-structured interviews with eleven product managers and eleven project leaders from eleven software companies. The contribution of this study is fourfold: First, it compares how QR are handled in two cases, companies working in business-to-business markets, and companies that are working in business-to-consumer markets. These two are also compared in terms of impact on the handling of QRs. Second, it compares the perceptions and priorities of QR by product and project management respectively. Third, it includes an examination of the interdependencies among quality requirements perceived as most important by the practitioners. Fourth, it characterizes the selection and management of QR in down-stream development activities.
  •  
3.
  • Berntsson Svensson, Richard, 1978, et al. (författare)
  • The unfulfilled potential of data-driven decision making in agile software development
  • 2019
  • Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. - 9783030190330 ; 355, s. 69-85
  • Konferensbidrag (refereegranskat)abstract
    • With the general trend towards data-driven decision making (DDDM), organizations are looking for ways to use DDDM to improve their decisions. However, few studies have looked into the practitioners view of DDDM, in particular for agile organizations. In this paper we investigated the experiences of using DDDM, and how data can improve decision making. An emailed questionnaire was sent out to 124 industry practitioners in agile software developing companies, of which 84 answered. The results show that few practitioners indicated a wide-spread use of DDDM in their current decision making practices. The practitioners were more positive to its future use for higher-level and more general decision making, fairly positive to its use for requirements elicitation and prioritization decisions, while being less positive to its future use at the team level. The practitioners do see a lot of potential for DDDM in an agile context; however, currently unfulfilled.
  •  
4.
  • Afzal, Wasif, et al. (författare)
  • On using grey literature and google scholar in systematic literature reviews in software engineering
  • 2020
  • Ingår i: IEEE Access. - United States. - 2169-3536. ; 8, s. 36226-36243
  • Tidskriftsartikel (refereegranskat)abstract
    • © 2013 IEEE. Context: The inclusion of grey literature (GL) is important to remove publication bias while gathering available evidence regarding a certain topic. The number of systematic literature reviews (SLRs) in Software Engineering (SE) is increasing but we do not know about the extent of GL usage in these SLRs. Moreover, Google Scholar is rapidly becoming a search engine of choice for many researchers but the extent to which it can find the primary studies is not known. Objective: This tertiary study is an attempt to i) measure the usage of GL in SLRs in SE. Furthermore this study proposes strategies for categorizing GL and a quality checklist to use for GL in future SLRs; ii) explore if it is feasible to use only Google Scholar for finding scholarly articles for academic research. Method: We have conducted a systematic mapping study to measure the extent of GL usage in SE SLRs as well as to measure the feasibility of finding primary studies using Google Scholar. Results and conclusions: a) Grey Literature: 76.09% SLRs (105 out of 138) in SE have included one or more GL studies as primary studies. Among total primary studies across all SLRs (6307), 582 are classified as GL, making the frequency of GL citing as 9.23%. The intensity of GL use indicate that each SLR contains 5 primary studies on average (total intensity of GL use being 5.54). The ranking of GL tells us that conference papers are the most used form 43.3% followed by technical reports 28.52%. Universities, research institutes, labs and scientific societies together make up 67.7% of GL used, indicating that these are useful sources for searching GL. We additionally propose strategies for categorizing GL and criteria for evaluating GL quality, which can become a basis for more detailed guidelines for including GL in future SLRs. b) Google Scholar Results: The results show that Google Scholar was able to retrieve 96% of primary studies of these SLRs. Most of the primary studies that were not found using Google Scholar were from grey sources.
  •  
5.
  • Afzal, Wasif, et al. (författare)
  • Software Test Process Improvement Approaches: A Systematic Literature Review and an Industrial Case Study
  • 2016
  • Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212. ; 111, s. 1-33
  • Tidskriftsartikel (refereegranskat)abstract
    • Software Test Process Improvement (STPI) approaches are frameworks that guide software development organizations to improve their software testing process. We have identified existing STPI approaches and their characteristics (such as completeness of development, availability of information and assessment instruments, and domain limitations of the approaches) using a systematic literature review (SLR). Furthermore, two selected approaches (TPI Next and TMMi) are evaluated with respect to their content and assessment results in industry. As a result of this study, we have identified 18 STPI approaches and their characteristics. A detailed comparison of the content of TPI Next and TMMi is done. We found that many of the STPI approaches do not provide sufficient information or the approaches do not include assessment instruments. This makes it difficult to apply many approaches in industry. Greater similarities were found between TPI Next and TMMi and fewer differences. We conclude that numerous STPI approaches are available but not all are generally applicable for industry. One major difference between available approaches is their model representation. Even though the applied approaches generally show strong similarities, differences in the assessment results arise due to their different model representations.
  •  
6.
  • Afzal, Wasif, et al. (författare)
  • Towards benchmarking feature subset selection methods for software fault prediction
  • 2016
  • Ingår i: Computational Intelligence and Quantitative Software Engineering. - Berlin, Heidelberg : Springer. - 9783319259642 - 9783319259628 ; , s. 33-58
  • Bokkapitel (refereegranskat)abstract
    • Despite the general acceptance that software engineering datasets often contain noisy, irrele- vant or redundant variables, very few benchmark studies of feature subset selection (FSS) methods on real-life data from software projects have been conducted. This paper provides an empirical comparison of state-of-the-art FSS methods: information gain attribute ranking (IG); Relief (RLF); principal com- ponent analysis (PCA); correlation-based feature selection (CFS); consistency-based subset evaluation (CNS); wrapper subset evaluation (WRP); and an evolutionary computation method, genetic programming (GP), on five fault prediction datasets from the PROMISE data repository. For all the datasets, the area under the receiver operating characteristic curve—the AUC value averaged over 10-fold cross- validation runs—was calculated for each FSS method-dataset combination before and after FSS. Two diverse learning algorithms, C4.5 and na ̈ıve Bayes (NB) are used to test the attribute sets given by each FSS method. The results show that although there are no statistically significant differences between the AUC values for the different FSS methods for both C4.5 and NB, a smaller set of FSS methods (IG, RLF, GP) consistently select fewer attributes without degrading classification accuracy. We conclude that in general, FSS is beneficial as it helps improve classification accuracy of NB and C4.5. There is no single best FSS method for all datasets but IG, RLF and GP consistently select fewer attributes without degrading classification accuracy within statistically significant boundaries.
  •  
7.
  • Aguayo, Claudio, et al. (författare)
  • Contextualizando el uso de tecnologías inteligentes móviles para el monitoreo y educación de visitantes [Contextualising the use of smart mobile technologies for visitor monitoring and education]
  • 2019
  • Ingår i: XI SOCIETUR [Chilean Society for Tourism Research] Conference 2019, 24-26 April, Punta Arenas, Chile: SOCIETUR. - Santiago : XI SOCIETUR [Chilean Society for Tourism Research].
  • Konferensbidrag (refereegranskat)abstract
    • Con una expansión de la recreación al aire libre y el desarrollo del turismo en muchos países hoy en día, el monitoreo de visitantes y la educación pueden considerarse como dos partes integrales de la gestión recreativa contemporánea. El monitoreo de visitantes se refiere a la documentación profesional de actividades recreativas y comportamiento en contextos de áreas recreativas. Esto se ha convertido en una tarea de gestión cada vez más importante para garantizar que los intereses y las experiencias recreativas de los visitantes se incluyan en diversas políticas y estrategias de gestión (Hansen, 2016). La educación de los visitantes, por otro lado, se refiere a cómo las áreas recreativas pueden ofrecer importantes oportunidades de aprendizaje experiencial para la educación relevante basada en el contexto local. La educación dirigida a los visitantes puede complementar y reforzar las experiencias al aire libre, pudiendo ser una forma importante de promover objetivos de sostenibilidad, como la adaptación local al cambio climático (Lück, 2015). Las estrategias de monitoreo y educación de los visitantes se han establecido y utilizado durante mucho tiempo en la gestión de diferentes contextos recreativos en todo el mundo. Sin embargo, el uso de nuevas tecnologías inteligentes para propósitos de monitoreo y educación ha recibido poca atención. Actualmente hay muy poca información disponible sobre el uso potencial de la tecnología móvil, como teléfonos inteligentes y tablets, para fines de monitoreo y educación dentro de contextos de áreas recreativas. La tecnología móvil puede ofrecer muchas opciones novedosas para actividades de monitoreo pasivo y activo de visitantes (Ahas et al., 2010). Del mismo modo, las tecnologías de aprendizaje móvil de hoy en día ofrecen herramientas y posibilidades sin precedentes para complementar y reforzar las experiencias de aprendizaje recreativo al aire libre. Además, éste proceso puede conllevar y una adaptación del aprendizaje a las temáticas relevantes a nivel local, incluyendo elementos culturalmente significativo (Aguayo, 2016). Sin embargo, este tipo de aplicación de las tecnologías móviles inteligentes sigue siendo un área poco explorada de investigación y desarrollo, sobre todo en el área de gestión turística. Desde este proyecto en curso, se propone un marco teórico conceptual inicial para el uso de tecnologías móviles inteligentes para el monitoreo y educación de visitantes en contextos recreacionales. Éste marco se ha desarrollado originalmente a partir de los contextos de turismo de mar costero en Suecia y Nueva Zelanda, encontrándose aún en etapa de conceptualización. En esta sesión se presentará el proyecto, incluyendo indicadores tempranos propuestos por actores en gobernanza y gestión de destinos turísticos de Suecia y Nueva Zelanda que han definido el marco teórico; y en segunda parte se llevará a cabo una breve sesión interactiva de lluvia de ideas para recoger las ideas y propuestas que surjan desde la audiencia en torno a la aplicación del marco teórico en el contexto de la Patagonia y otros destinos, según los presentes.
  •  
8.
  • Ali, Nauman bin, et al. (författare)
  • The impact of a proposal for innovation measurement in the software industry
  • 2020
  • Ingår i: International Symposium on Empirical Software Engineering and Measurement. - New York, NY, USA : IEEE Computer Society. - 1949-3789 .- 1949-3770. - 9781450375801
  • Konferensbidrag (refereegranskat)abstract
    • Background: Measuring an organization's capability to innovate and assessing its innovation output and performance is a challenging task. Previously, a comprehensive model and a suite of measurements to support this task were proposed. Aims: In the current paper, seven years since the publication of the paper titled Towards innovation measurement in the software industry, we have reflected on the impact of thework. Method:We have mainly relied on quantitative and qualitative analysis of the citations of the paper using an established classification schema. Results: We found that the article has had a significant scientific impact (indicated by the number of citations), i.e., (1) cited in literature from both software engineering and other fields, (2) cited in grey literature and peerreviewed literature, and (3) substantial citations in literature not published in the English language. However, we consider a majority of the citations in the peer-reviewed literature (75 out of 116) as neutral, i.e., they have not used the innovation measurement paper in any substantial way. All in all, 38 out of 116 have used, modified or based their work on the definitions, measurements or the model proposed in the article. This analysis revealed a significant weakness of the citing work, i.e., among the citing papers, we found only two explicit comparisons to the innovation measurement proposal, and we found no papers that identify weaknesses of said proposal. Conclusions: This work highlights the need for being cautious of relying solely on the number of citations for understanding impact, and the need for further improving and supporting the peer-review process to identify unwarranted citations in papers. © 2020 IEEE Computer Society. All rights reserved.
  •  
9.
  •  
10.
  • Darwish, Rashid, 1980, et al. (författare)
  • A Controlled Experiment on Coverage Maximization of Automated Model-Based Software Test Cases in the Automotive Industry
  • 2017
  • Ingår i: Proceedings - 10th IEEE International Conference on Software Testing, Verification and Validation, ICST 2017. ; , s. 546-547
  • Konferensbidrag (refereegranskat)abstract
    • © 2017 IEEE. In the automotive industry, as the complexity of electronic control units (ECUs) increase, there is a need for the creation of models that facilitate early tests to ensure functionality, but there is little guidance on how to write these tests in order to achieve maximum coverage. Our prototype CANoe+, which builds on the CANoe and GraphWalker tools, was evaluated against CANoe with regard to coverage maximization of generated test cases from the viewpoint of both software developers and software testers.
  •  
11.
  • de Oliveira Neto, Francisco Gomes, et al. (författare)
  • Full modification coverage through automatic similarity-based test case selection
  • 2016
  • Ingår i: Information and Software Technology. - : Elsevier BV. - 0950-5849. ; 80, s. 124-137
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: This paper presents the similarity approach for regression testing (SART), where a similarity-based test case selection technique is used in a model-based testing process to provide selection of test cases exercising modified parts of a specification model. Unlike other model-based regression testing techniques, SART relies on similarity analysis among test cases to identify modifications, instead of comparing models, hence reducing the dependency on specific types of model. Objective: To present convincing evidence of the usage of similarity measures for modification-traversing test case selection. Method: We investigate SART in a case study and an experiment. The case study uses artifacts from industry and should be seen as a sanity check of SART, while the experiment focuses on gaining statistical power through the generation of synthetical models in order to provide convincing evidence of SART’s effectiveness. Through posthoc analysis we obtain p-values and effect sizes to observe statistically significant differences between treatments with respect to transition and modification coverage. Results: The case study with industrial artifacts revealed that SART is able to uncover the same number of defects as known similarity-based test case selection techniques. In turn, the experiment shows that SART, unlike the other investigated techniques, presents 100% modification coverage. In addition, all techniques covered a similar percentage of model transitions. Conclusions: In summary, not only does SART provide transition and defect coverage equal to known STCS techniques, but it exceeds greatly in covering modified parts of the specification model, being a suitable candidate for model-based regression testing. Keywords: Regression testing, Test case selection, Model-based testing, Experimental Study
  •  
12.
  • de Oliveira Neto, Francisco Gomes, et al. (författare)
  • Searching for models to evaluate software technology
  • 2013
  • Ingår i: 2013 1st International Workshop on Combining Modelling and Search-Based Software Engineering, CMSBSE 2013 - Proceedings. - 9781467362849 ; , s. 12-15
  • Konferensbidrag (refereegranskat)abstract
    • Modeling and abstraction is key in all engineering processes and have found extensive use also in software engineering. When developing new methodologies and techniques to support software engineers we want to evaluate them on realistic models. However, this is a challenge since (1) it is hard to get industry to give access to their models, and (2) we need a large number of models to systematically evaluate a technology. This paper proposes that search-based techniques can be used to search for models with desirable properties, which can then be used to systematically evaluate model-based technologies. By targeting properties seen in industrial models we can then get the best of both worlds: models that are similar to models used in industry but in quantities that allow extensive experimentation. To exemplify our ideas we consider a specific case in which a model generator is used to create models to test a regression test optimization technique. © 2013 IEEE.
  •  
13.
  • Dobslaw, Felix, 1983, et al. (författare)
  • Estimating Return on Investment for GUI Test Automation Frameworks
  • 2019
  • Ingår i: Proceedings - International Symposium on Software Reliability Engineering, ISSRE. - 1071-9458. - 9781728149813 ; 30
  • Konferensbidrag (refereegranskat)abstract
    • Automated graphical user interface (GUI) tests can reduce manual testing activities and increase test frequency. This motivates the conversion of manual test cases into automated GUI tests. However, it is not clear whether such automation is cost-effective given that GUI automation scripts add to the code base and demand maintenance as a system evolves. In this paper, we introduce a method for estimating maintenance cost and Return on Investment (ROI) for Automated GUI Testing (AGT). The method utilizes the existing source code change history and has the potential to be used for the evaluation of other testing or quality assurance automation technologies. We evaluate the method for a real-world, industrial software system and compare two fundamentally different AGT frameworks, namely Selenium and EyeAutomate, to estimate and compare their ROI. We also report on their defect-finding capabilities and usability. The quantitative data is complemented by interviews with employees at the company the study has been conducted at. The method was successfully applied, and estimated maintenance cost and ROI for both frameworks are reported. Overall, the study supports earlier results showing that implementation time is the leading cost for introducing AGT. The findings further suggest that, while EyeAutomate tests are significantly faster to implement, Selenium tests require more of a programming background but less maintenance.
  •  
14.
  • Dobslaw, F., et al. (författare)
  • Estimating Return on Investment for GUI Test Automation Frameworks
  • 2019
  • Ingår i: 2019 IEEE 30th International Symposium on Software Reliability Engineering (ISSRE). - : IEEE. - 9781728149820
  • Konferensbidrag (refereegranskat)abstract
    • Automated graphical user interface (GUI) tests can reduce manual testing activities and increase test frequency. This motivates the conversion of manual test cases into automated GUI tests. However, it is not clear whether such automation is cost-effective given that GUI automation scripts add to the code base and demand maintenance as a system evolves. In this paper, we introduce a method for estimating maintenance cost and Return on Investment (ROI) for Automated GUI Testing (AGT). The method utilizes the existing source code change history and has the potential to be used for the evaluation of other testing or quality assurance automation technologies. We evaluate the method for a real-world, industrial software system and compare two fundamentally different AGT frameworks, namely Selenium and EyeAutomate, to estimate and compare their ROI. We also report on their defect-finding capabilities and usability. The quantitative data is complemented by interviews with employees at the company the study has been conducted at. The method was successfully applied, and estimated maintenance cost and ROI for both frameworks are reported. Overall, the study supports earlier results showing that implementation time is the leading cost for introducing AGT. The findings further suggest that, while EyeAutomate tests are significantly faster to implement, Selenium tests require more of a programming background but less maintenance.
  •  
15.
  •  
16.
  • Engström, Emelie, et al. (författare)
  • Indirect effects in evidential assessment: A case study on regression test technology adoption
  • 2012
  • Ingår i: 2nd International Workshop on Evidential Assessment of Software Technologies, EAST 2012. Lund, 22 September 2012. - New York, NY, USA : ACM. - 9781450315098 ; , s. 15-20
  • Konferensbidrag (refereegranskat)abstract
    • Background: There is a need for effcient regression testing in most software development organizations. Often the proposed solutions involve automation. However, despite this being a well researched area, research results are rarely applied in industrial practice. Aim: In this paper we aim to bridge the gap between research and practice by providing examples of how evidence-based regression testing approaches can be adopted in industry. We also discuss challenges for the research community. Method: An industrial case study was carried out to evaluate the possibility to improve regression testing at Sony Ericsson Mobile Communications. We analyse the procedure undertaken based on frameworks from the evidence based software engineering, EBSE, paradigm (with a focus on the evidence) and automation literature (with a focus on the practical effects). Results: Our results pinpoint the need for systematic approaches when introducing a new tool. Practitioners and researchers need congruent guidelines supporting the appraisal of both the evidence base and the pragmatic effects, both direct but also indirect, of the changes. This is illustrated by the introduction of the automation perspective.
  •  
17.
  • Felderer, Michael, 1978-, et al. (författare)
  • A testability analysis framework for non-functional properties
  • 2018
  • Ingår i: 2018 IEEE 11TH INTERNATIONAL CONFERENCE ON SOFTWARE TESTING, VERIFICATION AND VALIDATION WORKSHOPS (ICSTW). - : Institute of Electrical and Electronics Engineers Inc.. - 9781538663523 ; , s. 54-58
  • Konferensbidrag (refereegranskat)abstract
    • This paper presents background, the basic steps and an example for a testability analysis framework for non-functional properties.
  •  
18.
  • Feldt, Robert, 1972, et al. (författare)
  • Ways of applying artificial intelligence in software engineering
  • 2018
  • Ingår i: Proceedings - International Conference on Software Engineering. - New York : IEEE. - 0270-5257. ; Part F137725, s. 35-41
  • Konferensbidrag (refereegranskat)abstract
    • As Artificial Intelligence (AI) techniques become more powerful and easier to use they are increasingly deployed as key components of modern software systems. While this enables new functionality and often allows better adaptation to user needs it also creates additional problems for software engineers and exposes companies to new risks. Some work has been done to better understand the interaction between Software Engineering and AI but we lack methods to classify ways of applying AI in software systems and to analyse and understand the risks this poses. Only by doing so can we devise tools and solutions to help mitigate them. This paper presents the AI in SE Application Levels (AI-SEAL) taxonomy that categorises applications according to their point of application, the type of AI technology used and the automation level allowed. We show the usefulness of this taxonomy by classifying 15 papers from previous editions of the RAISE workshop. Results show that the taxonomy allows classification of distinct AI applications and provides insights concerning the risks associated with them. We argue that this will be important for companies in deciding how to apply AI in their software applications and to create strategies for its use.
  •  
19.
  •  
20.
  • Furia, Carlo A., et al. (författare)
  • Applying Bayesian analysis guidelines to empirical software engineering data
  • 2021
  • Ingår i: ACM Transactions on Software Engineering and Methodology. - : Association for Computing Machinery (ACM). - 1049-331X .- 1557-7392. ; 31:3
  • Tidskriftsartikel (refereegranskat)abstract
    • Statistical analysis is the tool of choice to turn data into information and then information into empirical knowledge. However, the process that goes from data to knowledge is long, uncertain, and riddled with pitfalls. To be valid, it should be supported by detailed, rigorous guidelines that help ferret out issues with the data or model and lead to qualified results that strike a reasonable balance between generality and practical relevance. Such guidelines are being developed by statisticians to support the latest techniques for Bayesian data analysis. In this article, we frame these guidelines in a way that is apt to empirical research in software engineering. To demonstrate the guidelines in practice, we apply them to reanalyze a GitHub dataset about code quality in different programming languages. The dataset’s original analysis [Ray et al. 55] and a critical reanalysis [Berger et al. 6] have attracted considerable attention—in no small part because they target a topic (the impact of different programming languages) on which strong opinions abound. The goals of our reanalysis are largely orthogonal to this previous work, as we are concerned with demonstrating, on data in an interesting domain, how to build a principled Bayesian data analysis and to showcase its benefits. In the process, we will also shed light on some critical aspects of the analyzed data and of the relationship between programming languages and code quality—such as the impact of project-specific characteristics other than the used programming language. The high-level conclusions of our exercise will be that Bayesian statistical techniques can be applied to analyze software engineering data in a way that is principled, flexible, and leads to convincing results that inform the state-of-the-art while highlighting the boundaries of its validity. The guidelines can support building solid statistical analyses and connecting their results. Thus, they can help buttress continued progress in empirical software engineering research.
  •  
21.
  • Furia, Carlo A, 1979, et al. (författare)
  • Applying Bayesian Analysis Guidelines to Empirical Software Engineering Data: The Case of Programming Languages and Code Quality
  • 2022
  • Ingår i: ACM Transactions on Software Engineering and Methodology. - : Association for Computing Machinery (ACM). - 1049-331X .- 1557-7392. ; 31:3
  • Tidskriftsartikel (refereegranskat)abstract
    • Statistical analysis is the tool of choice to turn data into information and then information into empirical knowledge. However, the process that goes from data to knowledge is long, uncertain, and riddled with pitfalls. To be valid, it should be supported by detailed, rigorous guidelines that help ferret out issues with the data or model and lead to qualified results that strike a reasonable balance between generality and practical relevance. Such guidelines are being developed by statisticians to support the latest techniques for Bayesian data analysis. In this article, we frame these guidelines in a way that is apt to empirical research in software engineering.To demonstrate the guidelines in practice, we apply them to reanalyze a GitHub dataset about code quality in different programming languages. The dataset's original analysis [Ray et al. 55] and a critical reanalysis [Berger et al. 6] have attracted considerable attention-in no small part because they target a topic (the impact of different programming languages) on which strong opinions abound. The goals of our reanalysis are largely orthogonal to this previous work, as we are concerned with demonstrating, on data in an interesting domain, how to build a principled Bayesian data analysis and to showcase its benefits. In the process, we will also shed light on some critical aspects of the analyzed data and of the relationship between programming languages and code quality-such as the impact of project-specific characteristics other than the used programming language.The high-level conclusions of our exercise will be that Bayesian statistical techniques can be applied to analyze software engineering data in a way that is principled, flexible, and leads to convincing results that inform the state-of-The-Art while highlighting the boundaries of its validity. The guidelines can support building solid statistical analyses and connecting their results. Thus, they can help buttress continued progress in empirical software engineering research.
  •  
22.
  • Furia, Carlo A, 1979, et al. (författare)
  • Bayesian Data Analysis in Empirical Software Engineering Research
  • 2021
  • Ingår i: IEEE Transactions on Software Engineering. - 0098-5589 .- 1939-3520. ; 47:9, s. 1786-1810
  • Tidskriftsartikel (refereegranskat)abstract
    • IEEE Statistics comes in two main flavors: frequentist and Bayesian. For historical and technical reasons, frequentist statistics have traditionally dominated empirical data analysis, and certainly remain prevalent in empirical software engineering. This situation is unfortunate because frequentist statistics suffer from a number of shortcomings---such as lack of flexibility and results that are unintuitive and hard to interpret---that curtail their effectiveness when dealing with the heterogeneous data that is increasingly available for empirical analysis of software engineering practice. In this paper, we pinpoint these shortcomings, and present Bayesian data analysis techniques that provide tangible benefits---as they can provide clearer results that are simultaneously robust and nuanced. After a short, high-level introduction to the basic tools of Bayesian statistics, we present the reanalysis of two empirical studies on the effectiveness of automatically generated tests and the performance of programming languages, respectively. By contrasting the original frequentist analyses with our new Bayesian analyses, we demonstrate the concrete advantages of the latter. To conclude we advocate a more prominent role for Bayesian statistical techniques in empirical software engineering research and practice.
  •  
23.
  • Furia, Carlo A, 1979, et al. (författare)
  • Towards causal analysis of empirical software engineering data: The impact of programming languages on coding competitions
  • 2024
  • Ingår i: ACM Transactions on Software Engineering and Methodology. - 1049-331X .- 1557-7392. ; 33:1, s. 1-35
  • Tidskriftsartikel (refereegranskat)abstract
    • There is abundant observational data in the software engineering domain, whereas running large-scale controlled experiments is often practically impossible. Thus, most empirical studies can only report statistical correlations—instead of potentially more insightful and robust causal relations. To support analyzing purely observational data for causal relations, and to assess any differences between purely predictive and causal models of the same data, this paper discusses some novel techniques based on structural causal models (such as directed acyclic graphs of causal Bayesian networks). Using these techniques, one can rigorously express, and partially validate, causal hypotheses; and then use the causal information to guide the construction of a statistical model that captures genuine causal relations—such that correlation does imply causation. We apply these ideas to analyzing public data about programmer performance in Code Jam, a large world- wide coding contest organized by Google every year. Specifically, we look at the impact of different program- ming languages on a participant’s performance in the contest. While the overall effect associated with programming languages is weak compared to other variables—regardless of whether we consider correlational or causal links—we found considerable differences between a purely associational and a causal analysis of the very same data. The takeaway message is that even an imperfect causal analysis of observational data can help answer the salient research questions more precisely and more robustly than with just purely predictive techniques— where genuine causal effects may be confounded.
  •  
24.
  • Ghazi, Ahmad Nauman, et al. (författare)
  • Information sources and their importance to prioritize test cases in heterogeneous systems context
  • 2014
  • Ingår i: Communications in Computer and Information Science. - Berlin, Heidelberg : Springer. - 1865-0929. - 9783662438954 - 9783662438961 ; 425, s. 86-98
  • Konferensbidrag (refereegranskat)abstract
    • Context: Testing techniques proposed in the literature rely on various sources of information for test case selection (e.g., require- ments, source code, system structure, etc.). The challenge of test selection is amplified in the context of heterogeneous systems, where it is unknown which information/data sources are most important. Contribution: (1) Achieve in-depth understanding of test processes in heterogeneous systems; (2) Elicit information sources for test selection in the context of heterogeneous systems. (3) Capture the relative importance of the identified information sources. Method: Case study research is used for the elicitation and understanding of which information sources are relevant for test case privatization, followed by an exploratory survey capturing the relative importance of information sources for testing heterogeneous systems. Results: We classified different information sources that play a vital role in the test selection process, and found that their importance differs largely for the different test levels observed in heterogeneous testing. However, overall all sources were considered essential in test selection for heterogeneous systems. Conclusion: Heterogeneous system testing requires solutions that take all information sources into account when suggesting test cases for selection. Such approaches need to be developed and compared with existing solutions.
  •  
25.
  • Gomes, Francisco, 1987, et al. (författare)
  • Evolution of statistical analysis in empirical software engineering research : Current state and steps forward
  • 2019
  • Ingår i: Journal of Systems and Software. - : Elsevier Inc.. - 0164-1212 .- 1873-1228. ; 156, s. 246-267
  • Tidskriftsartikel (refereegranskat)abstract
    • Software engineering research is evolving and papers are increasingly based on empirical data from a multitude of sources, using statistical tests to determine if and to what degree empirical evidence supports their hypotheses. To investigate the practices and trends of statistical analysis in empirical software engineering (ESE), this paper presents a review of a large pool of papers from top-ranked software engineering journals. First, we manually reviewed 161 papers and in the second phase of our method, we conducted a more extensive semi-automatic classification of papers spanning the years 2001–2015 and 5196 papers. Results from both review steps was used to: i) identify and analyse the predominant practices in ESE (e.g., using t-test or ANOVA), as well as relevant trends in usage of specific statistical methods (e.g., nonparametric tests and effect size measures) and, ii) develop a conceptual model for a statistical analysis workflow with suggestions on how to apply different statistical methods as well as guidelines to avoid pitfalls. Lastly, we confirm existing claims that current ESE practices lack a standard to report practical significance of results. We illustrate how practical significance can be discussed in terms of both the statistical analysis and in the practitioner's context. © 2019 Elsevier Inc.
  •  
26.
  • Gren, Lucas, 1984, et al. (författare)
  • Group development and group maturity when building agile teams: A qualitative and quantitative investigation at eight large companies
  • 2017
  • Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 124, s. 104-119
  • Tidskriftsartikel (refereegranskat)abstract
    • The agile approach to projects focuses more on close-knit teams than traditional waterfall projects, which means that aspects of group maturity become even more important. This psychological aspect is not much researched in connection to the building of an "agile team." The purpose of this study is to investigate how building agile teams is connected to a group development model taken from social psychology. We conducted ten semi-structured interviews with coaches, Scrum Masters, and managers responsible for the agile process from seven different companies, and collected survey data from 66 group-members from four companies (a total of eight different companies). The survey included an agile measurement tool and the one part of the Group Development Questionnaire. The results show that the practitioners define group developmental aspects as key factors to a successful agile transition. Also, the quantitative measurement of agility was significantly correlated to the group maturity measurement. We conclude that adding these psychological aspects to the description of the "agile team" could increase the understanding of agility and partly help define an "agile team." We propose that future work should develop specific guidelines for how software development teams at different maturity levels might adopt agile principles and practices differently. (C) 2016 Elsevier Inc. All rights reserved.
  •  
27.
  • Gren, Lucas, 1984, et al. (författare)
  • Group Maturity and Agility, Are They Connected? - A Survey Study
  • 2015
  • Ingår i: EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA 2015), August 26-28. - : IEEE. - 9781467375856
  • Konferensbidrag (refereegranskat)abstract
    • The focus on psychology has increased within software engineering due to the project management innovation "agile development processes". The agile methods do not explicitly consider group development aspects, they simply assume what is described in group psychology as mature groups. This study was conducted with 45 employees and their twelve managers (N=57) from two SAP customers in the US that were working with agile methods, and the data were collected via an online survey. The selected Agility measurement was correlated to a Group Development measurement and showed significant convergent validity, i.e., A more mature team is also a more agile team. This means that the agile methods probably would benefit from taking group development into account when its practices are being introduced.
  •  
28.
  • Gren, Lucas, 1984, et al. (författare)
  • The Prospects of a Quantitative Measurement of Agility: A Validation Study on an Agile Maturity Model
  • 2015
  • Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 107, s. 38-49
  • Tidskriftsartikel (refereegranskat)abstract
    • Agile development has now become a well-known approach to collaboration in professional work life. Both researchers and practitioners want validated tools to measure agility. This study sets out to validate an agile maturity measurement model with statistical tests and empirical data. First, a pretest was conducted as a case study including a survey and focus group. Second, the main study was conducted with 45 employees from two SAP customers in the US. We used internal consistency (by a Cronbach’s alpha) as the main measure for reliability and analyzed construct validity by exploratory principal factor analysis (PFA). The results suggest a new categorization of a subset of items existing in the tool and provides empirical support for these new groups of factors. However, we argue that more work is needed to reach the point where a maturity models with quantitative data can be said to validly measure agility, and even then, such a measurement still needs to include some deeper analysis with cultural and contextual items.
  •  
29.
  • Gren, Lucas, 1984, et al. (författare)
  • Work Motivational Challenges Regarding the Interface Between Agile Teams and a Non-Agile Surrounding Organization: A case study
  • 2014
  • Ingår i: Agile Conference (AGILE), 2014. July 28 2014-Aug.. - : IEEE Press. - 9780769552224 ; , s. 11-15
  • Konferensbidrag (refereegranskat)abstract
    • There are studies showing what happens if agile teams are introduced into a non-agile organization, e.g. higher overhead costs and the necessity of an understanding of agile methods even outside the teams. This case study shows an example of work motivational aspects that might surface when an agile team exists in the middle of a more traditional structure. This case study was conducted at a car manufacturer in Sweden, consisting of an unstructured interview with the Scrum Master and a semi-structured focus group. The results show that the teams felt that the feedback from the surrounding organization was unsynchronized resulting in them not feeling appreciated when delivering their work. Moreover, they felt frustrated when working on non-agile teams after have been working on agile ones. This study concludes that there were work motivational affects of fitting an agile team into a non-agile surrounding organization, and therefore this might also be true for other organizations.
  •  
30.
  • Holt, Nina E., et al. (författare)
  • Empirical evaluations on the cost-effectiveness of state-based testing: An industrial case study
  • 2014
  • Ingår i: Information and Software Technology. - : Elsevier BV. - 0950-5849 .- 1873-6025. ; 56:8, s. 890-910
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: Test models describe the expected behavior of the software under test and provide the basis for test case and oracle generation. When test models are expressed as UML state machines, this is typically referred to as state-based testing (SBT). Despite the importance of being systematic while testing, all testing activities are limited by resource constraints. Thus, reducing the cost of testing while ensuring sufficient fault detection is a common goal in software development. No rigorous industrial case studies of SBT have yet been published. Objective: In this paper, we evaluate the cost-effectiveness of SBT on actual control software by studying the combined influence of four testing aspects: coverage criterion, test oracle, test model and unspecified behavior (sneak paths). Method: An industrial case study was used to investigate the cost-effectiveness of SBT. To enable the evaluation of SBT techniques, a model-based testing tool was configured and used to automatically generate test suites. The test suites were evaluated using 26 real faults collected in a field study. Results: Results show that the more detailed and rigorous the test model and oracle, the higher the fault-detection ability of SBT. A less precise oracle achieved 67% fault detection, but the overall cost reduction of 13% was not enough to make the loss an acceptable trade-off. Removing details from the test model significantly reduced the cost by 85%. Interestingly, only a 24–37% reduction in fault detection was observed. Testing for sneak paths killed the remaining eleven mutants that could not be killed by the conformance test strategies. Conclusions: Each of the studied testing aspects influences cost-effectiveness and must be carefully considered in context when selecting strategies. Regardless of these choices, sneak-path testing is a neces- sary step in SBT since sneak paths are common while also undetectable by conformance testing.
  •  
31.
  • Levén, William, et al. (författare)
  • The broken windows theory applies to technical debt
  • 2024
  • Ingår i: Empirical Software Engineering. - 1382-3256.
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: The term technical debt (TD) describes the aggregation of sub-optimal solutions that serve to impede the evolution and maintenance of a system. Some claim that the broken windows theory (BWT), a concept borrowed from criminology, also applies to software development projects. The theory states that the presence of indications of previous crime (such as a broken window) will increase the likelihood of further criminal activity; TD could be considered the broken windows of software systems. Objective: To empirically investigate the causal relationship between the TD density of a system and the propensity of developers to introduce new TD during the extension of that system. Method: The study used a mixed-methods research strategy consisting of a con- trolled experiment with an accompanying survey and follow-up interviews. The experiment had a total of 29 developers of varying experience levels completing system extension tasks in already existing systems with high or low TD density. Results: The analysis revealed significant effects of TD level on the subjects’ tendency to re-implement (rather than reuse) functionality, choose non-descriptive variable names, and introduce other code smells identified by the software tool SonarQube, all with at least 95% credible intervals. Conclusions: Three separate significant results along with a validating qualitative result combine to form substantial evidence of the BWT’s existence in software engineering contexts. This study finds that existing TD can have a major impact on developers propensity to introduce new TD of various types during development.
  •  
32.
  • Levén, William, et al. (författare)
  • The broken windows theory applies to technical debt
  • 2024
  • Ingår i: Empirical Software Engineering. - : Springer. - 1382-3256 .- 1573-7616. ; 29:4
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: The term technical debt (TD) describes the aggregation of sub-optimal solutions that serve to impede the evolution and maintenance of a system. Some claim that the broken windows theory (BWT), a concept borrowed from criminology, also applies to software development projects. The theory states that the presence of indications of previous crime (such as a broken window) will increase the likelihood of further criminal activity; TD could be considered the broken windows of software systems. Objective: To empirically investigate the causal relationship between the TD density of a system and the propensity of developers to introduce new TD during the extension of that system. Method: The study used a mixed-methods research strategy consisting of a controlled experiment with an accompanying survey and follow-up interviews. The experiment had a total of 29 developers of varying experience levels completing system extension tasks in already existing systems with high or low TD density. Results: The analysis revealed significant effects of TD level on the subjects’ tendency to re-implement (rather than reuse) functionality, choose non-descriptive variable names, and introduce other code smells identified by the software tool SonarQube, all with at least 95% credible intervals. Coclusions: Three separate significant results along with a validating qualitative result combine to form substantial evidence of the BWT’s existence in software engineering contexts. This study finds that existing TD can have a major impact on developers propensity to introduce new TD of various types during development. 
  •  
33.
  • Levén, William, et al. (författare)
  • The broken windows theory applies to technical debt
  • 2024
  • Ingår i: Empirical Software Engineering. - : Springer. - 1573-7616 .- 1382-3256. ; 29:4
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: The term technical debt (TD) describes the aggregation of sub-optimal solutions that serve to impede the evolution and maintenance of a system. Some claim that the broken windows theory (BWT), a concept borrowed from criminology, also applies to software development projects. The theory states that the presence of indications of previous crime (such as a broken window) will increase the likelihood of further criminal activity; TD could be considered the broken windows of software systems. Objective: To empirically investigate the causal relationship between the TD density of a system and the propensity of developers to introduce new TD during the extension of that system. Method: The study used a mixed-methods research strategy consisting of a controlled experiment with an accompanying survey and follow-up interviews. The experiment had a total of 29 developers of varying experience levels completing system extension tasks in already existing systems with high or low TD density. Results: The analysis revealed significant effects of TD level on the subjects’ tendency to re-implement (rather than reuse) functionality, choose non-descriptive variable names, and introduce other code smells identified by the software tool SonarQube, all with at least 95% credible intervals. Coclusions: Three separate significant results along with a validating qualitative result combine to form substantial evidence of the BWT’s existence in software engineering contexts. This study finds that existing TD can have a major impact on developers propensity to introduce new TD of various types during development.
  •  
34.
  • Lindqvist, Erik, et al. (författare)
  • Outliers and Replication in Software Engineering
  • 2014
  • Ingår i: Proceedings - Asia-Pacific Software Engineering Conference, APSEC. - 1530-1362. - 9781479974252 ; , s. 207-214
  • Konferensbidrag (refereegranskat)abstract
    • Empirical software engineering is a research field of growing interest. Studies within this field handles an increasing amount of data. In order to replicate a study the data needs to be accessible and all processing of this data needs to be reproducible. Specifically, the handling of deviating data points, also known as outliers, needs to be documented in order for a study to be replicated. This study investigated the data availability for recently published studies within empirical software engineering. Furthermore, it also investigated if outliers are documented in the same research field. Papers were reviewed using a literature review and the presence of outliers was investigated using an unsupervised outlier detection method. Only 37% of the papers reviewed had their data accessible. Furthermore, in many cases outliers were present in the reviewed studies but 63% of the papers studies did not mention how outliers were handled. The data availability within empirical software engineering research is low and is hindering replication of studies. Additionally, the lack of documentation regarding how outliers are handled is hindering replication.
  •  
35.
  •  
36.
  • Madeyski, L., et al. (författare)
  • Overcoming the Equivalent Mutant Problem: A Systematic Literature Review and a Comparative Experiment of Second Order Mutation
  • 2014
  • Ingår i: Ieee Transactions on Software Engineering. - : Institute of Electrical and Electronics Engineers (IEEE). - 0098-5589 .- 1939-3520. ; 40:1, s. 23-42
  • Tidskriftsartikel (refereegranskat)abstract
    • Context. The equivalent mutant problem (EMP) is one of the crucial problems in mutation testing widely studied over decades. Objectives. The objectives are: to present a systematic literature review (SLR) in the field of EMP; to identify, classify and improve the existing, or implement new, methods which try to overcome EMP and evaluate them. Method. We performed SLR based on the search of digital libraries. We implemented four second order mutation (SOM) strategies, in addition to first order mutation (FOM), and compared them from different perspectives. Results. Our SLR identified 17 relevant techniques (in 22 articles) and three categories of techniques: detecting (DEM); suggesting (SEM); and avoiding equivalent mutant generation (AEMG). The experiment indicated that SOM in general and JudyDiffOp strategy in particular provide the best results in the following areas: total number of mutants generated; the association between the type of mutation strategy and whether the generated mutants were equivalent or not; the number of not killed mutants; mutation testing time; time needed for manual classification. Conclusions. The results in the DEM category are still far from perfect. Thus, the SEM and AEMG categories have been developed. The JudyDiffOp algorithm achieved good results in many areas.
  •  
37.
  • Mairhofer, Stefan, et al. (författare)
  • Search-based Software Testing and Test Data Generation for a Dynamic Programming Language
  • 2011
  • Ingår i: Proceedings of the Genetic and Evolutionary Computation Conference (GECCO).
  • Konferensbidrag (refereegranskat)abstract
    • Manually creating test cases is time consuming and error prone. Search-based software testing can help automate this process and thus reduce time and effort and increase quality by automatically generating relevant test cases. Previous research has mainly focused on static programming languages and simple test data inputs such as numbers. This is not practical for dynamic programming languages that are increasingly used by software developers. Here we present an approach for search-based software testing for dynamically typed programming languages that can generate test scenarios and both simple and more complex test data. The approach is implemented as a tool, RuTeG, in and for the dynamic programming language Ruby. It combines an evolutionary search for test cases that give structural code coverage with a learning component to restrict the space of possible types of inputs. The latter is called for in dynamic languages since we cannot always know statically which types of objects are valid inputs. Experiments on 14 cases taken from real-world Ruby projects show that RuTeG achieves full or higher statement coverage on more cases and does so faster than randomly generated test cases.
  •  
38.
  • Marculescu, Bogdan, 1984, et al. (författare)
  • Objective re-weighting to guide an interactive search based software testing system
  • 2013
  • Ingår i: 2013 12th International Conference on Machine Learning and Applications, ICMLA 2013; Miami, FL; United States; 4 December 2013 through 7 December 2013. - Miami : IEEE. ; 2, s. 102-107
  • Konferensbidrag (refereegranskat)abstract
    • Even hardware-focused industries today develop products where software is both a large and important component. Engineers tasked with developing and integrating these products do not always have a software engineering background. To ensure quality, tools are needed that automate and support software testing while allowing these domain specialists to leverage their knowledge and experience. Search-based testing could be a key aspect in creating an automated tool for supporting testing activities. However, domain specific quality criteria and trade-offs make it difficult to develop a general fitness function a priori, so interaction between domain specialists and such a tool would be critical to its success. In this paper we present a system for interactive search based software testing and investigate a way for domain specialists to guide the search by dynamically re-weighting quality goals. Our empirical investigation shows that objective reweighing can help a human domain specialist interactively guide the search, without requiring specialised knowledge of the system and without sacrificing population diversity.
  •  
39.
  • Marculescu, Bogdan, et al. (författare)
  • Tester interactivity makes a difference in search-based software testing : A controlled experiment
  • 2016
  • Ingår i: Information and Software Technology. - : Elsevier. - 0950-5849 .- 1873-6025. ; 78, s. 66-82
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: Search-based software testing promises to provide users with the ability to generate high quality test cases, and hence increase product quality, with a minimal increase in the time and effort required. The development of the Interactive Search-Based Software Testing (ISBST) system was motivated by a previous study to investigate the application of search-based software testing (SBST) in an industrial setting. ISBST allows users to interact with the underlying SBST system, guiding the search and assessing the results. An industrial evaluation indicated that the ISBST system could find test cases that are not created by testers employing manual techniques. The validity of the evaluation was threatened, however, by the low number of participants. Objective: This paper presents a follow-up study, to provide a more rigorous evaluation of the ISBST system. Method: To assess the ISBST system a two-way crossover controlled experiment was conducted with 58 students taking a Verification and Validation course. The NASA Task Load Index (NASA-TLX) is used to assess the workload experienced by the participants in the experiment. Results:The experimental results validated the hypothesis that the ISBST system generates test cases that are not found by the same participants employing manual testing techniques. A follow-up laboratory experiment also investigates the importance of interaction in obtaining the results. In addition to this main result, the subjective workload was assessed for each participant by means of the NASA-TLX tool. The evaluation showed that, while the ISBST system required more effort from the participants, they achieved the same performance. Conclusions: The paper provides evidence that the ISBST system develops test cases that are not found by manual techniques, and that interaction plays an important role in achieving that result. (C) 2016 Elsevier B.V. All rights reserved.
  •  
40.
  • Marculescu, Bogdan, 1984, et al. (författare)
  • Transferring interactive search-based software testing to industry
  • 2018
  • Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212 .- 1873-1228. ; 142, s. 156-170
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: Search-Based Software Testing (SBST), and the wider area of Search-Based Software Engineering (SBSE), is the application of optimization algorithms to problems in software testing, and software engineering, respectively. New algorithms, methods, and tools are being developed and validated on benchmark problems. In previous work, we have also implemented and evaluated Interactive Search-Based Software Testing (ISBST) tool prototypes, with a goal to successfully transfer the technique to industry. Objective: While SBST and SBSE solutions are often validated on benchmark problems, there is a need to validate them in an operational setting, and to assess their performance in practice. The present paper discusses the development and deployment of SBST tools for use in industry, and reflects on the transfer of these techniques to industry. Method: In addition to previous work discussing the development and validation of an ISBST prototype, a new version of the prototype ISBST system was evaluated in the laboratory and in industry. This evaluation is based on an industrial System under Test (SUT) and was carried out with industrial practitioners. The Technology Transfer Model is used as a framework to describe the progression of the development and evaluation of the ISBST system, as it progresses through the first five of its seven steps. Results: The paper presents a synthesis of previous work developing and evaluating the ISBST prototype, as well as presenting an evaluation, in both academia and industry, of that prototype's latest version. In addition to the evaluation, the paper also discusses the lessons learned from this transfer. Conclusions: This paper presents an overview of the development and deployment of the ISBST system in an industrial setting, using the framework of the Technology Transfer Model. We conclude that the ISBST system is capable of evolving useful test cases for that setting, though improvements in the means the system uses to communicate that information to the user are still required. In addition, a set of lessons learned from the project are listed and discussed. Our objective is to help other researchers that wish to validate search-based systems in industry, and provide more information about the benefits and drawbacks of these systems.
  •  
41.
  • Marculescu, Bogdan, 1984, et al. (författare)
  • Using exploration focused techniques to augment search-based software testing: an experimental evaluation
  • 2016
  • Ingår i: 2016 IEEE International Conference on Software Testing, Verification and Validation (ICST). - : IEEE. - 2381-2834. - 9781509018277 - 9780306406157 ; , s. 69-79
  • Konferensbidrag (refereegranskat)abstract
    • Search-based software testing (SBST)often uses objective-based approaches to solve testing problems. There are, however, situations where the validity and completeness of objectives cannot be ascertained, or where there is insufficient information to define objectives at all. Incomplete or incorrect objectives may steer the search away from interesting behavior of the software under test (SUT) and from potentially useful test cases.This papers investigates the degree to whichexploration-based algorithms can be used tocomplement an objective-based tool we have previously developed and evaluated in industry. In particular, we would like to assess how exploration-based algorithms perform in situations where little information on the behavior space is available a priori. We have conducted an experiment comparing the performance of an exploration-based algorithm with an objective-based one on a problem with a high dimensional behavior space. In addition, we evaluate to what extent that performance degrades in situations where computational resources are limited.Our experiment shows that exploration-basedalgorithms are useful in covering a larger area of the behavior space and result in a more diverse solution population. Typically, of the candidate solutions that exploration-based algorithms propose, more than 80% were not covered by their objective-based counterpart. This increased diversity is present in the resulting population even when computational resources are limited. We conclude that exploration-focused algorithms are a useful means of investigating high-dimensional spaces, even in situations where limited information and limited resources are available.
  •  
42.
  • Mellblom, Emanuel, et al. (författare)
  • The Connection between Burnout and Personality Types in Software Developers
  • 2019
  • Ingår i: IEEE Software. - 1937-4194 .- 0740-7459. ; 36:5, s. 57-64
  • Tidskriftsartikel (refereegranskat)abstract
    • This article examines the connection between the five-factor model personality traits and burnout in software developers and aims to validate generalizations of findings in other fields.
  •  
43.
  • Neto, F. G. D., et al. (författare)
  • An Initiative to Improve Reproducibility and Empirical Evaluation of Software Testing Techniques
  • 2015
  • Ingår i: 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering, Vol 2. - : IEEE. - 9781479919345
  • Konferensbidrag (refereegranskat)abstract
    • The current concern regarding quality of evaluation performed in existing studies reveals the need for methods and tools to assist in the definition and execution of empirical studies and experiments. However, when trying to apply general methods from empirical software engineering in specific fields, such as evaluation of software testing techniques, new obstacles and threats to validity appears, hindering researchers' use of empirical methods. This paper discusses those issues specific for evaluation of software testing techniques and proposes an initiative for a collaborative effort to encourage reproducibility of experiments evaluating software testing techniques (STT). We also propose the development of a tool that enables automatic execution and analysis of experiments producing a reproducible research compendia as output that is, in turn, shared among researchers. There are many expected benefits from this endeavour, such as providing a foundation for evaluation of existing and upcoming STT, and allowing researchers to devise and publish better experiments.
  •  
44.
  • Olsson, Jesper, et al. (författare)
  • Measuring affective states from technical debt: A psychoempirical software engineering experiment
  • 2021
  • Ingår i: Empirical Software Engineering. - : Springer Science and Business Media LLC. - 1573-7616 .- 1382-3256. ; 26:5
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: Software engineering is a human activity. Despite this, human aspects are under-represented in technical debt research, perhaps because they are challenging to evaluate. Objective: This study’s objective was to investigate the relationship between technical debt and affective states (feelings, emotions, and moods) from software practitioners. Method: Forty participants (N = 40) from twelve companies took part in a mixed-methods approach, consisting of a repeated-measures (r = 5) experiment (n = 200), a survey, and semi-structured interviews. From the qualitative data, it is clear that technical debt activates a substantial portion of the emotional spectrum and is psychologically taxing. Further, the practitioners’ reactions to technical debt appear to fall in different levels of maturity. Results: The statistical analysis shows that different design smells (strong indicators of technical debt) negatively or positively impact affective states. Conclusions: We argue that human aspects in technical debt are important factors to consider, as they may result in, e.g., procrastination, apprehension, and burnout.
  •  
45.
  • Penzenstadler, Birgit, et al. (författare)
  • Take a deep breath: Benefits of neuroplasticity practices for software developers and computer workers in a family of experiments
  • 2022
  • Ingår i: Empirical Software Engineering. - : Springer Science and Business Media LLC. - 1382-3256 .- 1573-7616. ; 27:4
  • Tidskriftsartikel (refereegranskat)abstract
    • Context Computer workers in general, and software developers specifically, are under a high amount of stress due to continuous deadlines and, often, over-commitment. Objective This study investigates the effects of a neuroplasticity practice, a specific breathing practice, on the attention awareness, well-being, perceived productivity, and self-efficacy of computer workers. Method The intervention was a 12-week program with a weekly live session that included a talk on a well-being topic and a facilitated group breathing session. During the intervention period, we solicited one daily journal note and one weekly well-being rating. We created a questionnaire mainly from existing, validated scales as entry and exit survey for data points for comparison before and after the intervention. We replicated the intervention in a similarly structured 8-week program. The data was analyzed using Bayesian multi-level models for the quantitative part and thematic analysis for the qualitative part. Results The intervention showed improvements in participants' experienced inner states despite an ongoing pandemic and intense outer circumstances for most. Over the course of the study, we found an improvement in the participants' ratings of how often they found themselves in good spirits as well as in a calm and relaxed state. We also aggregate a large number of deep inner reflections and growth processes that may not have surfaced for the participants without deliberate engagement in such a program. Conclusion The data indicates usefulness and effectiveness of an intervention for computer workers in terms of increasing well-being and resilience. Everyone needs a way to deliberately relax, unplug, and recover. A breathing practice is a simple way to do so, and the results call for establishing a larger body of work to make this common practice.
  •  
46.
  • Pepic, I., et al. (författare)
  • Early detection of sepsis using artificial intelligence : a scoping review protocol
  • 2021
  • Ingår i: Systematic Reviews. - : Springer Nature. - 2046-4053. ; 10:1
  • Tidskriftsartikel (refereegranskat)abstract
    • Background: Sepsis is a life-threatening organ dysfunction caused by a dysregulated host response to infection. To decrease the high case fatality rates and morbidity for sepsis and septic shock, there is a need to increase the accuracy of early detection of suspected sepsis in prehospital and emergency department settings. This may be achieved by developing risk prediction decision support systems based on artificial intelligence.Methods: The overall aim of this scoping review is to summarize the literature on existing methods for early detection of sepsis using artificial intelligence. The review will be performed using the framework formulated by Arksey and O’Malley and further developed by Levac and colleagues. To identify primary studies and reviews that are suitable to answer our research questions, a comprehensive literature collection will be compiled by searching several sources. Constrictions regarding time and language will have to be implemented. Therefore, only studies published between 1 January 1990 and 31 December 2020 will be taken into consideration, and foreign language publications will not be considered, i.e., only papers with full text in English will be included. Databases/web search engines that will be used are PubMed, Web of Science Platform, Scopus, IEEE Xplore, Google Scholar, Cochrane Library, and ACM Digital Library. Furthermore, clinical studies that have completed patient recruitment and reported results found in the database ClinicalTrials.gov will be considered. The term artificial intelligence is viewed broadly, and a wide range of machine learning and mathematical models suitable as base for decision support will be evaluated. Two members of the team will test the framework on a sample of included studies to ensure that the coding framework is suitable and can be consistently applied. Analysis of collected data will provide a descriptive summary and thematic analysis. The reported results will convey knowledge about the state of current research and innovation for using artificial intelligence to detect sepsis in early phases of the medical care chain.Ethics and dissemination: The methodology used here is based on the use of publicly available information and does not need ethical approval. It aims at aiding further research towards digital solutions for disease detection and health innovation. Results will be extracted into a review report for submission to a peer-reviewed scientific journal. Results will be shared with relevant local and national authorities and disseminated in additional appropriate formats such as conferences, lectures, and press releases. 
  •  
47.
  • Peretz-Andersson, Einav, et al. (författare)
  • Empirical AI Transformation Research: A Systematic Mapping Study and Future Agenda
  • 2022
  • Ingår i: E-Informatica Software Engineering Journal. - : Wroclaw University of Science and Technology. - 2084-4840 .- 1897-7979. ; 16:1
  • Tidskriftsartikel (refereegranskat)abstract
    • Background: Intelligent software is a significant societal change agent. Recent research indicates that organizations must change to reap the full benefits of AI. We refer to this change as AI transformation (AIT). The key challenge is to determine how to change and which are the consequences of increased AI use. Aim: The aim of this study is to aggregate the body of knowledge on AIT research. Method: We perform an systematic mapping study (SMS) and follow Kitchenham's procedure. We identify 52 studies from Scopus, IEEE, and Science Direct (2010-2020). We use the Mixed-Methods Appraisal Tool (MMAT) to critically assess empirical work. Results Work on AIT is mainly qualitative and originates from various disciplines. We are unable to identify any useful definition of AIT. To our knowledge, this is the first SMS that focuses on empirical AIT research. Only a few empirical studies were found in the sample we identified. Conclusions We define AIT and propose a research agenda. Despite the popularity and attention related to AI and its effects on organizations, our study reveals that a significant amount of publications on the topic lack proper methodology or empirical data.
  •  
48.
  • Pirzadeh Irannezhad, Laleh, 1985, et al. (författare)
  • Systematic Literature Review on risk management in agile and plan driven software development
  • 2016
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • Context: Software development is a process prone to high level of risk due to issues in development phases, management strategy and the environment where it is performed. Agile development approaches are assumed to have less risk resolution in comparison with traditional approaches. Although, this is well accepted in industry and academia, to the best of our knowledge, there have not been any studies investigating this difference. Objectives: The main objective of this paper is to investigate whether risk resolution is affected by the choice of development process. Further, we investigated application domains, research methods, types of risk (i.e. perceived risk as perception of risk by practitioners, or actual risk as risk compiled from project historical data), software development and project management phases, and development models reported on in the papers included in this study.Methods: A Systematic Literature Review (SLR) was conducted in the fields of software engineering, project management and risk management. Using a set of rigorous inclusion and exclusion criteria 78 primary studies were selected. From this information relevant to our research questions was collected. Results: No publications were found that report a difference in risk resolution between agile and traditional development approaches. The most common application domains are defense, financial sector and Information Systems industry each addressed by three primary studies and the most applied research method is design of models (49 publications). Perceived risk is the most popular type of risk addressed by 41 primary studies. Requirement analysis (18 publications) and planning (23 publications) are respectively the most addressed development and management phases. Lastly a combination of agile and plan driven approaches was addressed the most nine primary studies. Conclusion: The results from this SLR highlight a demand for empirical research on risk management applied in different development processes. Further, data from additional domains should be added to the body of knowledge in order to investigate generalizability of the findings. Moreover, due to lack of data, actual risk is not investigated as much as perceived risk, which highlights the demand field for quantitative studies in the research.
  •  
49.
  • Radjenovic, D., et al. (författare)
  • Software fault prediction metrics: A systematic literature review
  • 2013
  • Ingår i: Information and Software Technology. - : Elsevier BV. - 0950-5849 .- 1873-6025. ; 55:8, s. 1397-1418
  • Tidskriftsartikel (refereegranskat)abstract
    • Context: Software metrics may be used in fault prediction models to improve software quality by predicting fault location. Objective: This paper aims to identify software metrics and to assess their applicability in software fault prediction. We investigated the influence of context on metrics' selection and performance. Method: This systematic literature review includes 106 papers published between 1991 and 2011. The selected papers are classified according to metrics and context properties. Results: Object-oriented metrics (49%) were used nearly twice as often compared to traditional source code metrics (27%) or process metrics (24%). Chidamber and Kemerer's (CK) object-oriented metrics were most frequently used. According to the selected studies there are significant differences between the metrics used in fault prediction performance. Object-oriented and process metrics have been reported to be more successful in finding faults compared to traditional size and complexity metrics. Process metrics seem to be better at predicting post-release faults compared to any static code metrics. Conclusion: More studies should be performed on large industrial software systems to find metrics more relevant for the industry and to answer the question as to which metrics should be used in a given context.
  •  
50.
  • Ralph, P., et al. (författare)
  • Pandemic programming: How COVID-19 affects software developers and how their organizations can help
  • 2020
  • Ingår i: Empirical Software Engineering. - : Springer Science and Business Media LLC. - 1382-3256 .- 1573-7616. ; 25, s. 4927-4961
  • Tidskriftsartikel (refereegranskat)abstract
    • Context As a novel coronavirus swept the world in early 2020, thousands of software developers began working from home. Many did so on short notice, under difficult and stressful conditions. Objective This study investigates the effects of the pandemic on developers' wellbeing and productivity. Method A questionnaire survey was created mainly from existing, validated scales and translated into 12 languages. The data was analyzed using non-parametric inferential statistics and structural equation modeling. Results The questionnaire received 2225 usable responses from 53 countries. Factor analysis supported the validity of the scales and the structural model achieved a good fit (CFI = 0.961, RMSEA = 0.051, SRMR = 0.067). Confirmatory results include: (1) the pandemic has had a negative effect on developers' wellbeing and productivity; (2) productivity and wellbeing are closely related; (3) disaster preparedness, fear related to the pandemic and home office ergonomics all affect wellbeing or productivity. Exploratory analysis suggests that: (1) women, parents and people with disabilities may be disproportionately affected; (2) different people need different kinds of support. Conclusions To improve employee productivity, software companies should focus on maximizing employee wellbeing and improving the ergonomics of employees' home offices. Women, parents and disabled persons may require extra support.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-50 av 63
Typ av publikation
tidskriftsartikel (34)
konferensbidrag (26)
bokkapitel (2)
rapport (1)
Typ av innehåll
refereegranskat (59)
övrigt vetenskapligt/konstnärligt (4)
Författare/redaktör
Torkar, Richard, 197 ... (63)
Feldt, Robert, 1972 (26)
Gren, Lucas, 1984 (8)
de Oliveira Neto, Fr ... (7)
Furia, Carlo A, 1979 (6)
Afzal, Wasif (4)
visa fler...
Feldt, Robert (3)
Berntsson Svensson, ... (3)
Gomes, Francisco, 19 ... (3)
Gorschek, Tony, 1973 (3)
Skriver Hansen, Andr ... (2)
Lück, Michael (2)
Porter, Brooke (2)
Petersen, Kai (2)
Besker, Terese, 1970 (2)
Poulding, Simon (2)
Olsson, Jesper (1)
Kovalenko, V. (1)
Andersson, Jesper, 1 ... (1)
Sundell, J (1)
Hata, H. (1)
Penzenstadler, Birgi ... (1)
Lundqvist, Kristina (1)
Börstler, Jürgen (1)
Felderer, Michael, 1 ... (1)
Ghazi, Ahmad Nauman (1)
Fatima, Rubia (1)
Wen, Lijie (1)
Azhar, Muhammad (1)
Alone, Snehal (1)
Glocksien, Kerstin (1)
Forsberg, Håkan (1)
Aguayo, Claudio (1)
Andersson, Lars-Magn ... (1)
Martini, Antonio (1)
Tan, X (1)
Maurin Söderholm, Ha ... (1)
Ali, Nauman Bin (1)
Engström, Emelie (1)
Edison, Henry (1)
Pirzadeh Irannezhad, ... (1)
Ljungström, Lars R. (1)
Sjöqvist, Bengt-Arne ... (1)
Lundqvist, K (1)
Axelson-Fisk, Marina ... (1)
Fucci, Davide (1)
Candefjord, Stefan, ... (1)
Schneider, S (1)
Bohm, K. (1)
Regnell, Björn (1)
visa färre...
Lärosäte
Göteborgs universitet (55)
Chalmers tekniska högskola (38)
Blekinge Tekniska Högskola (19)
Mälardalens universitet (5)
RISE (2)
Jönköping University (1)
visa fler...
Lunds universitet (1)
Linnéuniversitetet (1)
Högskolan i Borås (1)
Karolinska Institutet (1)
visa färre...
Språk
Engelska (63)
Forskningsämne (UKÄ/SCB)
Naturvetenskap (59)
Teknik (13)
Samhällsvetenskap (12)
Medicin och hälsovetenskap (4)

År

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