| 21. |
- Franch, Xavier, et al.
(författare)
-
How do Practitioners Perceive the Relevance of Requirements Engineering Research?
- 2022
-
Ingår i: IEEE Transactions on Software Engineering. - : Institute of Electrical and Electronics Engineers Inc.. - 0098-5589 .- 1939-3520. ; 48:6, s. 1947-1964
-
Tidskriftsartikel (refereegranskat)abstract
- Context: The relevance of Requirements Engineering (RE) research to practitioners is vital for a long-term dissemination of research results to everyday practice. Some authors have speculated about a mismatch between research and practice in the RE discipline. However, there is not much evidence to support or refute this perception. Objective: This paper presents the results of a study aimed at gathering evidence from practitioners about their perception of the relevance of RE research and at understanding the factors that influence that perception. Method: We conducted a questionnaire-based survey of industry practitioners with expertise in RE. The participants rated the perceived relevance of 435 scientific papers presented at five top RE-related conferences. Results: The 153 participants provided a total of 2,164 ratings. The practitioners rated RE research as essential or worthwhile in a majority of cases. However, the percentage of non-positive ratings is still higher than we would like. Among the factors that affect the perception of relevance are the paper?s links to industry, the research method used, and respondents? roles. The reasons for positive perceptions were primarily related to the relevance of the problem and the soundness of the solution, while the causes for negative perceptions were more varied. The respondents also provided suggestions for future research, including topics researchers have studied for decades, like elicitation or requirement quality criteria. Conclusions: The study is valuable for both researchers and practitioners. Researchers can use the reasons respondents gave for positive and negative perceptions and the suggested research topics to help make their research more appealing to practitioners and thus more prone to industry adoption. Practitioners can benefit from the overall view of contemporary RE research by learning about research topics that they may not be familiar with, and compare their perception with those of their colleagues to self-assess their positioning towards more academic research. IEEE
|
|
| 22. |
- 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.
|
|
| 23. |
- 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.
|
|
| 24. |
- 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.
|
|
| 25. |
- 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.
|
|
| 26. |
- Gren, Lucas, 1984-, et al.
(författare)
-
Is it possible to disregard obsolete requirements? a family of experiments in software effort estimation
- 2021
-
Ingår i: Requirements Engineering. - : Springer Science and Business Media Deutschland GmbH. - 0947-3602 .- 1432-010X. ; :3, s. 459-480
-
Tidskriftsartikel (refereegranskat)abstract
- Expert judgement is a common method for software effort estimations in practice today. Estimators are often shown extra obsolete requirements together with the real ones to be implemented. Only one previous study has been conducted on if such practices bias the estimations. We conducted six experiments with both students and practitioners to study, and quantify, the effects of obsolete requirements on software estimation. By conducting a family of six experiments using both students and practitioners as research subjects (N= 461), and by using a Bayesian Data Analysis approach, we investigated different aspects of this effect. We also argue for, and show an example of, how we by using a Bayesian approach can be more confident in our results and enable further studies with small sample sizes. We found that the presence of obsolete requirements triggered an overestimation in effort across all experiments. The effect, however, was smaller in a field setting compared to using students as subjects. Still, the over-estimations triggered by the obsolete requirements were systematically around twice the percentage of the included obsolete ones, but with a large 95% credible interval. The results have implications for both research and practice in that the found systematic error should be accounted for in both studies on software estimation and, maybe more importantly, in estimation practices to avoid over-estimations due to this systematic error. We partly explain this error to be stemming from the cognitive bias of anchoring-and-adjustment, i.e. the obsolete requirements anchored a much larger software. However, further studies are needed in order to accurately predict this effect. © 2021, The Author(s).
|
|
| 27. |
- 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.
|
|
| 28. |
- Gren, Lucas, 1984-, et al.
(författare)
-
What Makes Effective Leadership in Agile Software Development Teams?
- 2022
-
Ingår i: International Conference on Software Engineering. - New York, NY, USA : IEEE Computer Society. - 9781450392211 ; , s. 2402-2414
-
Konferensbidrag (refereegranskat)abstract
- Effective leadership is one of the key drivers of business and project success, and one of the most active areas of management research. But how does leadership work in agile software development, which emphasizes self-management and self-organization and marginalizes traditional leadership roles? To find out, this study examines agile leadership from the perspective of thirteen professionals who identify as agile leaders, in different roles, at ten different software development companies of varying sizes. Data from semi-structured interviews reveals that leadership: (1) is dynamically shared among team members; (2) engenders a sense of belonging to the team; and (3) involves balancing competing organizational cultures (e.g. balancing the new agile culture with the old milestone-driven culture). In other words, agile leadership is a property of a team, not a role, and effectiveness depends on agile team members' identifying with the team, accepting responsibility, and being sensitive to cultural conflict.
|
|
| 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. |
- Hamnerius, N., et al.
(författare)
-
Pedal dermatophyte infection in psoriasis
- 2004
-
Ingår i: Br J Dermatol. - : Oxford University Press (OUP). ; 150:6, s. 1125-1128
-
Tidskriftsartikel (refereegranskat)abstract
- BACKGROUND: Dermatophyte infections have been considered rare in psoriasis. However, there are data indicating that tinea unguium is as common or even more common in psoriasis compared with healthy controls. Tinea unguium is generally a secondary event to tinea pedis infection. OBJECTIVES: To study the prevalence of tinea pedis and tinea unguium in psoriasis compared with a control group. METHODS: Consecutive psoriasis outpatients aged 18-64 years attending a department of dermatology were examined. Samples for direct microscopy and culture were taken from the interdigital spaces, soles and toenails. Consecutive patients without signs of psoriasis or atopic dermatitis seeking examination of moles constituted the control group. RESULTS: In total, 239 patients with psoriasis and 245 control patients were studied. The prevalence of tinea pedis was 8.8%[95% confidence interval (CI) +/- 3.6%] in the psoriasis group and 7.8% (95% CI +/- 3.4%) in the control group. The corresponding figures for prevalence of tinea unguium were 4.6% (95% CI +/- 2.7%) and 2.4% (95% CI +/- 1.9%), respectively. The differences found in the psoriasis vs. the control groups were not statistically significant. CONCLUSIONS: This study does not support the hypothesis that the prevalence of tinea pedis and tinea unguium in patients with psoriasis differs from that in a normal population.
|
|
