| 1. |
- Ali, Nauman bin, Dr., et al.
(författare)
-
A Comparison of Citation Sources for Reference and Citation-Based Search in Systematic Literature Reviews
- 2022
-
Ingår i: e-Informatica Software Engineering Journal. - : Wroclaw University of Technology. - 1897-7979 .- 2084-4840. ; 16:1
-
Forskningsöversikt (refereegranskat)abstract
- Context: In software engineering, snowball sampling has been used as a supplementary and primary search strategy. The current guidelines recommend using Google Scholar (GS) for snowball sampling. However, the use of GS presents several challenges when using it as a source for citations and references. Objective: To compare the effectiveness and usefulness of two leading citation databases (GS and Scopus) for use in snowball sampling search. Method: We relied on a published study that has used snowball sampling as a search strategy and GS as the citation source. We used its primary studies to compute precision and recall for Scopus. Results: In this particular case, Scopus was highly effective with 95% recall and had better precision of 5.1% compared to GS’s 2.8%. Moreover, Scopus found nine additional relevant papers. On average, one would read approximately 15 extra papers in GS than Scopus to identify one additional relevant paper. Furthermore, Scopus supports batch downloading of both citations and papers’ references, has better quality metadata, and does better source filtering. Conclusion: This study suggests that Scopus seems to be more effective and useful for snowball sampling than GS for systematic secondary studies attempting to identify peer-reviewed literature. EVIE © 2022 The Authors.
|
|
| 2. |
- Badampudi, Deepika, 1984-, et al.
(författare)
-
Reporting Consent, Anonymity and Confidentiality Procedures Adopted in Empirical Studies Using Human Participants
- 2022
-
Ingår i: e-Informatica Software Engineering Journal. - : Wroclaw University of Technology. - 1897-7979 .- 2084-4840. ; 16:1
-
Tidskriftsartikel (refereegranskat)abstract
- Background: Empirical studies involving human participants need to follow procedures to avoid causing harm to the subjects. However, it is not always clear how researchers should report these procedures. Aim: This study investigates how researchers report ethical issues in the software engineering journal publications, particularly informed consent, confidentiality, and anonymity. Method: We conducted a literature review to understand the reporting of ethical issues in software engineering journals. In addition, in a workshop, we discussed the importance of reporting the different ethical issues. Results: The results indicate that 49 out of 95 studies reported some ethical issues. Only six studies discussed all three ethical issues. The subjects were mainly informed about the study purpose and procedure. There are limited discussions on how the subjects were informed about the risks involved in the study. Studies reported on how authors ensured confidentiality have also discussed anonymity in most cases. The results of the workshop discussion indicate that reporting ethical issues is important to improve the reliability of the research results. We propose a checklist based on the literature review, which we validated through a workshop. Conclusion: The checklist proposed in this paper is a step towards enhancing ethical reporting in software engineering research.
|
|
| 3. |
- Chen, Xingru, et al.
(författare)
-
Reuse in Contemporary Software Engineering Practices - An Exploratory Case Study in A Medium-sized Company
- 2022
-
Ingår i: e-Informatica Software Engineering Journal. - : Wroclaw University of Technology. - 1897-7979 .- 2084-4840. ; 16:1
-
Tidskriftsartikel (refereegranskat)abstract
- Background: Software practice is evolving with changing technologies and practices such as InnerSource, DevOps, and microservices. It is important to investigate the impact of contemporary software engineering (SE) practices on software reuse.Aim: This study aims to characterize software reuse in contemporary SE practices and investigate its implications in terms of costs, benefits, challenges, and potential improvements in a medium-sized company.Method: We performed an exploratory case study by conducting interviews, group discussions, and reviewing company documentation to investigate software reuse in the context of contemporary SE practices in the case company.Results: The results indicate that the development for reuse in contemporary SE practices incurs additional coordination, among other costs. Development with reuse led to relatively fewer additional costs and resulted in several benefits such as better product quality and less development and delivery time. Ownership of reusable assets is challenging in contemporary SE practice. InnerSource practices may help mitigate the top perceived challenges: discoverability and ownership of the reusable assets, knowledge sharing and reuse measurement.Conclusion: Reuse in contemporary SE practices is not without additional costs and challenges. However, the practitioners perceive costs as investments that benefit the company in the long run.
|
|
| 4. |
- Demirsoy, Ali, et al.
(författare)
-
Semantic Knowledge Management System to Support Software Engineers : Implementation and Static Evaluation through Interviews at Ericsson
- 2018
-
Ingår i: e-Informatica Software Engineering Journal. - : WROCLAW UNIV TECHNOLOGY. - 1897-7979 .- 2084-4840. ; 12:1, s. 237-263
-
Tidskriftsartikel (refereegranskat)abstract
- Background: In large-scale corporations in the software engineering context information overload problems occur as stakeholders continuously produce useful information on process life-cycle issues, matters related to specific products under development, etc. Information overload makes finding relevant information (e.g., how did the company apply the requirements process for product X?) challenging, which is in the primary focus of this paper. Contribution: In this study the authors aimed at evaluating the ease of implementing a semantic knowledge management system at Ericsson, including the essential components of such systems (such as text processing, ontologies, semantic annotation and semantic search). Thereafter, feedback on the usefulness of the system was collected from practitioners. Method: A single case study was conducted at a development site of Ericsson AB in Sweden. Results: It was found that semantic knowledge management systems are challenging to implement, this refers in particular to the implementation and integration of ontologies. Specific ontologies for structuring and filtering are essential, such as domain ontologies and ontologies distinct to the organization. Conclusion: To be readily adopted and transferable to practice, desired ontologies need to be implemented and integrated into semantic knowledge management frameworks with ease, given that the desired ontologies are dependent on organizations and domains.
|
|
| 5. |
- Hönel, Sebastian, et al.
(författare)
-
Activity-Based Detection of (Anti-)Patterns : An Embedded Case Study of the Fire Drill
- 2024
-
Ingår i: e-Informatica Software Engineering Journal. - : Wroclaw University of Science and Technology. - 1897-7979 .- 2084-4840. ; 18:1
-
Tidskriftsartikel (refereegranskat)abstract
- Background: Nowadays, expensive, error-prone, expert-based evaluations are needed to identify and assess software process anti-patterns. Process artifacts cannot be automatically used to quantitatively analyze and train prediction models without exact ground truth. Aim: Develop a replicable methodology for organizational learning from process (anti-)patterns, demonstrating the mining of reliable ground truth and exploitation of process artifacts. Method: We conduct an embedded case study to find manifestations of the Fire Drill anti-pattern in n = 15 projects. To ensure quality, three human experts agree. Their evaluation and the process’ artifacts are utilized to establish a quantitative understanding and train a prediction model. Results: Qualitative review shows many project issues. (i) Expert assessments consistently provide credible ground truth. (ii) Fire Drill phenomenological descriptions match project activity time (for example, development). (iii) Regression models trained on ≈ 12–25 examples are sufficiently stable. Conclusion: The approach is data source-independent (source code or issue-tracking). It allows leveraging process artifacts for establishing additional phenomenon knowledge and training robust predictive models. The results indicate the aptness of the methodology for the identification of the Fire Drill and similar anti-pattern instances modeled using activities. Such identification could be used in post mortem process analysis supporting organizational learning for improving processes.
|
|
| 6. |
- Irshad, Mohsin, et al.
(författare)
-
A systematic reuse process for automated acceptance tests : Construction and elementary evaluation
- 2021
-
Ingår i: e-Informatica Software Engineering Journal. - : Wroclaw University of Technology. - 1897-7979 .- 2084-4840. ; 15:1, s. 133-162
-
Tidskriftsartikel (refereegranskat)abstract
- Context: Automated acceptance testing validates a product's functionality from the customer's perspective. Text-based automated acceptance tests (AATs) have gained popularity because they link requirements and testing.Objective: To propose and evaluate a cost-effective systematic reuse process for automated acceptance tests.Method: A systematic approach, method engineering, is used to construct a systematic reuse process for automated acceptance tests. The techniques to support searching, assessing, adapting the reusable tests are proposed and evaluated. The constructed process is evaluated using (i) qualitative feedback from software practitioners and (ii) a demonstration of the process in an industry setting. The process was evaluated for three constraints: performance expectancy, effort expectancy, and facilitating conditions.Results: The process consists of eleven activities that support development for reuse, development with reuse, and assessment of the costs and benefits of reuse. During the evaluation, practitioners found the process a useful method to support reuse. In the industrial demonstration, it was noted that the activities in the solution helped in developing an automated acceptance test with reuse faster than creating a test from scratch i.e., searching, assessment, and adaptation parts.Conclusion: The process is found to be useful and relevant to the industry during the preliminary investigation.
|
|
| 7. |
- Klotins, Eriks, 1985-, et al.
(författare)
-
Use of agile practices in start-up companies
- 2021
-
Ingår i: e-Informatica Software Engineering Journal. - : Wrocław University of Science and Technology. - 1897-7979 .- 2084-4840. ; 15:1, s. 47-64
-
Tidskriftsartikel (refereegranskat)abstract
- Context Software start-ups have shown their ability to develop and launch innovative software products and services. Small, motivated teams and uncertain project scope makes start-ups good candidates for adopting Agile practices. Objective We explore how start-ups use Agile practices and what effects can be associated with the use of those practices. Method We use a case survey to analyze 84 start-up cases and 56 Agile practices. We apply statistical methods to test for statistically significant associations between the use of Agile practices, team, and product factors. Results Our results suggest that development of the backlog, use of version control, code refactoring, and development of user stories are the most frequently reported practices. We identify 22 associations between the use of Agile practices, team, and product factors. The use of Agile practices is associated with effects on source code and overall product quality. A teams’ positive or negative attitude towards best engineering practices is a significant indicator for either adoption or rejection of certain Agile practices. To explore the relationships in our findings, we set forth a number of propositions that can be investigated in future research. Conclusions We conclude that start-ups use Agile practices, however without following any specific methodology. We identify the opportunity for more fine-grained studies into the adoption and effects of individual Agile practices. Start-up practitioners could benefit from Agile practices in terms of better overall quality, tighter control over team performance, and resource utilization. © 2021 Wroclaw University of Science and Technology. All rights reserved.
|
|
| 8. |
- Nurdiani, Indira, et al.
(författare)
-
Usage, Retention, and Abandonment of Agile Practices
- 2019
-
Ingår i: e-Informatica Software Engineering Journal. - : Software Engineering Section of the Committee on Informatics of the Polish Academy of Sciences and Wrocław University of Science and Technology.. - 1897-7979 .- 2084-4840. ; 13:1, s. 7-35
-
Tidskriftsartikel (refereegranskat)abstract
- Background: A number of Agile maturity models (AMMs) have been proposed to guide software organizations in their adoption of Agile practices. Typically the AMMs suggest that higher maturity levels are reached by gradually adding more practices. However, recent research indicates that certain Agile practices, like test-driven development and continuous integration are being abandoned. Little is known on the rationales for abandoning Agile practices. Aim: We aim to identify which Agile practices are abandoned in industry, as well as the reasons for abandoning them. Method: We conducted a web survey with 51 respondents and interviews with 11 industry practitioners with experience in Agile adoption to investigate why Agile practices are abandoned. Results: Of the 17 Agile practices that were included in the survey, all have been abandoned at some point. Nevertheless, respondents who retained all practices as well as those who abandoned one or more practices, perceived their overall adoption of Agile practices as successful. Conclusion: Going against the suggestions of the AMMs, i.e. abandoning Agile one or more practices, could still lead to successful outcomes. This indicates that introducing Agile practices gradually in a certain sequence, as the AMMs suggest, may not always be suitable in different contexts.
|
|
| 9. |
- 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.
|
|
| 10. |
- Saeeda, Hina, et al.
(författare)
-
A Multivocal Literature Review on Non-Technical Debt in Software Development : An Insight into Process, Social, People, Organizational, and Culture Debt
- 2024
-
Ingår i: e-Informatica Software Engineering Journal. - : Technical University of Wroclaw. - 1897-7979 .- 2084-4840. ; 18:1
-
Forskningsöversikt (refereegranskat)abstract
- Software development encompasses various factors beyond technical considerations. Neglecting non-technical elements like individuals, processes, culture, and social and organizational aspects can lead to debt-like characteristics that demand attention. Therefore, we introduce the non-technical debt (NTD) concept to encompass and explore these aspects. This indicates the applicability of the debt analogy to non-technical facets of software development. Technical debt (TD) and NTD share similarities and often arise from risky decision-making processes, impacting both software development professionals and software quality. Overlooking either type of debt can lead to significant implications for software development success. The current study conducts a comprehensive multivocal literature review (MLR) to explore the most recent research on NTD, its causes, and potential mitigation strategies. For analysis, we carefully selected 40 primary studies among 110 records published until October 1, 2022. The study investigates the factors contributing to the accumulation of NTD in software development and proposes strategies to alleviate the adverse effects associated with it. This MLR offers a contemporary overview and identifies prospects for further investigation, making a valuable contribution to the field. The findings of this research highlight that NTD's impacts extend beyond monetary aspects, setting it apart from TD. Furthermore, the findings reveal that rectifying NTD is more challenging than addressing TD, and its consequences contribute to the accumulation of TD. To avert software project failures, a comprehensive approach that addresses NTD and TD concurrently is crucial. Effective communication and coordination play a vital role in mitigating NTD, and the study proposes utilizing the 3C model as a recommended framework to tackle NTD concerns.
|
|
