| 1. |
- Felderer, Michael, 1978-, et al.
(författare)
-
Introduction to the Special Issue on value and waste in software engineering
- 2022
-
Ingår i: Information and Software Technology. - : Elsevier B.V.. - 0950-5849 .- 1873-6025. ; 144
-
Tidskriftsartikel (refereegranskat)abstract
- In the context of software engineering, “value” and “waste” can mean different things to different stakeholders. While traditionally value and waste have been considered from a business or economic point of view, there has been a trend in recent years towards a broader perspective that also includes wider human and societal values. This Special Issue explores value and waste aspects in all areas of software engineering, including identifying, quantifying, reasoning about, and representing value and waste, driving value and avoiding waste, and managing value and waste. In this editorial we provide an introduction to the topic and provide an overview of the contributions included in this Special Issue. © 2021
|
|
| 2. |
- Galster, Matthias, et al.
(författare)
-
Empirical Research in Software Architecture How far have we come?
- 2016
-
Ingår i: 2016 13TH Working IEEE/IFIP Conference on Software Architecture (WICSA). - : IEEE. - 9781509021314 ; , s. 11-20
-
Konferensbidrag (refereegranskat)abstract
- Context: Empirical research helps gain well-founded insights about phenomena. Furthermore, empirical research creates evidence for the validity of research results. Objective: We aim at assessing the state-of-practice of empirical research in software architecture. Method: We conducted a comprehensive survey based on the systematic mapping method. We included all full technical research papers published at major software architecture conferences between 1999 and 2015. Results: 17% of papers report empirical work. The number of empirical studies in software architecture has started to increase in 2005. Looking at the number of papers, empirical studies are about equally frequently used to a) evaluate newly proposed approaches and b) to explore and describe phenomena to better understand software architecture practice. Case studies and experiments are the most frequently used empirical methods. Almost half of empirical studies involve human participants. The majority of these studies involve professionals rather than students. Conclusions: Our findings are meant to stimulate researchers in the community to think about their expectations and standards of empirical research. Our results indicate that software architecture has become a more mature domain with regards to applying empirical research. However, we also found issues in research practices that could be improved (e.g., when describing study objectives and acknowledging limitations).
|
|
| 3. |
- Galster, Matthias, et al.
(författare)
-
Empirical research in software architecture-Perceptions of the community
- 2023
-
Ingår i: Journal of Systems and Software. - : Elsevier. - 0164-1212 .- 1873-1228. ; 202
-
Tidskriftsartikel (refereegranskat)abstract
- Context: Previous research highlighted concerns about empirical research in software engineering (e.g., reproducibility, applicability of findings). It is unclear how these concerns reflect views of those who conduct and evaluate research.Objective: Focusing on software architecture, one subfield of software engineering, we study percep-tions of the research community on (1) how empirical research is applied, (2) human participants, (3) internal and external validity, and (4) replications. Method: We collected responses from 105 key players in architecture research via a survey; we analyzed data quantitatively and qualitatively.Results: Although respondents do generally not prefer either quantitative or qualitative research, around 40% express a preference for various reasons. Professionals are the preferred participants; there is no consensus on the value of student participants. Also, there is no consensus on when to focus on internal or external validity. Most respondents value replications, but acknowledge difficulties. A comparison with published research shows differences between how the community thinks research should be done.Conclusions: We provide evidence that consensus about empirical research is limited. Findings have implications for conducting and reviewing empirical research (e.g., training researchers and reviewers), and call for reflection on empirical research (e.g., to resolve conflicts). We outline actions for the future.(c) 2023 The Author(s). Published by Elsevier Inc. This is an open access article under the CC BY license (http://creativecommons.org/licenses/by/4.0/).
|
|
| 4. |
- Galster, Matthias, et al.
(författare)
-
Variability in software architecture : the road ahead
- 2014
-
Ingår i: Software Engineering Notes. - : ACM Press. - 0163-5948 .- 1943-5843. ; 39:4, s. 33-34
-
Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)abstract
- Variability in a software system is reflected in and facilitated through the architecture of that system. The Third International Workshop on Variability in Software Architecture (VARSA) was held in conjunction with the 11th Working IEEE/IFIP Conference on Software Architecture 2014 in Sydney, Australia. Based on the findings from previous editions of VARSA, this edition aimed at exploring methods, technologies and tools to handle variability at the software architecture level. The workshop featured one industrial keynote talk, one academic keynote talk and five research paper presentations.
|
|
| 5. |
- Galster, Matthias, et al.
(författare)
-
Variability in software architecture : views and beyond
- 2013
-
Ingår i: Software Engineering Notes. - : ACM Press. - 0163-5948 .- 1943-5843. ; 38:1, s. 46-49
-
Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)abstract
- Variability (the ability of a software system or software artifact to be adapted for use in a specific context) is reflected in and facilitated through the software architecture. The Second International Workshop on Variability in Software Architecture (VARSA) was held in conjunction with the Joint 10th Working IEEE/IFIP Conference on Software Architecture & 6th European Conference on Software Architecture 2012 in Helsinki, Finland. The workshop aimed at exploring current and emerging methods, languages, notations, technologies and tools to model, implement, and manage variability in the software architecture. It featured one industrial talk, five research paper presentations, and three working group discussions. Working groups discussed topics that emerged during the workshop. This report summarizes the themes of the workshop and presents the results of the working group discussions.
|
|
| 6. |
|
|
| 7. |
|
|
| 8. |
- Galster, Matthias, et al.
(författare)
-
Variability in Software Systems-A Systematic Literature Review
- 2014
-
Ingår i: IEEE Transactions on Software Engineering. - 0098-5589 .- 1939-3520. ; 40:3, s. 282-306
-
Forskningsöversikt (refereegranskat)abstract
- Context: Variability (i.e., the ability of software systems or artifacts to be adjusted for different contexts) became a key property of many systems. Objective: We analyze existing research on variability in software systems. We investigate variability handling in major software engineering phases (e.g., requirements engineering, architecting). Method: We performed a systematic literature review. A manual search covered 13 premium software engineering journals and 18 premium conferences, resulting in 15,430 papers searched and 196 papers considered for analysis. To improve reliability and to increase reproducibility, we complemented the manual search with a targeted automated search. Results: Software quality attributes have not received much attention in the context of variability. Variability is studied in all software engineering phases, but testing is underrepresented. Data to motivate the applicability of current approaches are often insufficient; research designs are vaguely described. Conclusions: Based on our findings we propose dimensions of variability in software engineering. This empirically grounded classification provides a step towards a unifying, integrated perspective of variability in software systems, spanning across disparate or loosely coupled research themes in the software engineering community. Finally, we provide recommendations to bridge the gap between research and practice and point to opportunities for future research.
|
|
| 9. |
- Martini, Antonio, et al.
(författare)
-
Message from the ICSA 2023 SAIP, NEMI, ECRF, Artifacts, Posters, Journal First, Workshops/Tutorials and Working Sessions Tracks Chairs
- 2023
-
Ingår i: 2023 IEEE 20TH INTERNATIONAL CONFERENCE ON SOFTWARE ARCHITECTURE COMPANION, ICSA-C. - : IEEE COMPUTER SOC. - 9781665464598 ; , s. XIII-XIV
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)
|
|
| 10. |
- Quin, Federico, et al.
(författare)
-
A/B testing : A systematic literature review
- 2024
-
Ingår i: Journal of Systems and Software. - 0164-1212 .- 1873-1228. ; 211
-
Tidskriftsartikel (refereegranskat)abstract
- A/B testing, also referred to as online controlled experimentation or continuous experimentation, is a form of hypothesis testing where two variants of a piece of software are compared in the field from an end user’s point of view. A/B testing is widely used in practice to enable data-driven decision making for software development. While a few studies have explored different facets of research on A/B testing, no comprehensive study has been conducted on the state-of-the-art in A/B testing. Such a study is crucial to provide a systematic overview of the field of A/B testing driving future research forward. To address this gap and provide an overview of the state-of-the-art in A/B testing, this paper reports the results of a systematic literature review that analyzed primary studies. The research questions focused on the subject of A/B testing, how A/B tests are designed and executed, what roles stakeholders have in this process, and the open challenges in the area. Analysis of the extracted data shows that the main targets of A/B testing are algorithms, visual elements, and workflow and processes. Single classic A/B tests are the dominating type of tests, primarily based in hypothesis tests. Stakeholders have three main roles in the design of A/B tests: concept designer, experiment architect, and setup technician. The primary types of data collected during the execution of A/B tests are product/system data, user-centric data, and spatio-temporal data. The dominating use of the test results are feature selection, feature rollout, continued feature development, and subsequent A/B test design. Stakeholders have two main roles during A/B test execution: experiment coordinator and experiment assessor. The main reported open problems are related to the enhancement of proposed approaches and their usability. From our study we derived three interesting lines for future research: strengthen the adoption of statistical methods in A/B testing, improving the process of A/B testing, and enhancing the automation of A/B testing.
|
|
