Emilia Mendes
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
Emilia Mendes has a total of 28 co-authors. Here are the top co-authors by number of shared publications:
- Claes Wohlin
Blekinge Inst Technol, SE-37179 Karlskrona, Sweden
3 shared publications - Burak Turhan
University of Oulu
2 shared publications - Leandro Lei Minku
The University of Birmingham
2 shared publications - Marcos Kalinowski
PUC-Rio, Brazil
2 shared publications - Pilar Rodríguez
Polytechnic University of Madrid, Madrid, Spain
2 shared publications - Ana Luiza Dallora
Blekinge Institute of Technology
1 shared publication
Latest Publications
- 27 May 2021
- Published by Elsevier in Journal of Systems and Software
- Vol. 180, 111013
Understanding the perceived relevance of capability measures: A survey of Agile Software Development practitioners
- 27 May 2021
- Published by Elsevier in Journal of Systems and Software
- Vol. 180, 111013
Understanding the perceived relevance of capability measures: A survey of Agile Software Development practitioners
- Open Access
- 14 September 2020
- Published by MDPI AG in International Journal of Environmental Research and Public Health
- Vol. 17 (18) , 6674
Multifactorial 10-Year Prior Diagnosis Prediction Model of Dementia
Dementia is a neurodegenerative disorder that affects the older adult population. To date, no cure or treatment to change its course is available. Since changes in the brains of affected individuals could be evidenced as early as 10 years before the onset of symptoms, prognosis research should consider this time frame. This study investigates a broad decision tree multifactorial approach for the prediction of dementia, considering 75 variables regarding demographic, social, lifestyle, medical history, biochemical tests, physical examination, psychological assessment and health instruments. Previous work on dementia prognoses with machine learning did not consider a broad range of factors in a large time frame. The proposed approach investigated predictive factors for dementia and possible prognostic subgroups. This study used data from the ongoing multipurpose Swedish National Study on Aging and Care, consisting of 726 subjects (91 presented dementia diagnosis in 10 years). The proposed approach achieved an AUC of 0.745 and Recall of 0.722 for the 10-year prognosis of dementia. Most of the variables selected by the tree are related to modifiable risk factors; physical strength was important across all ages. Also, there was a lack of variables related to health instruments routinely used for the dementia diagnosis.
- 14 September 2020
- Published by MDPI AG in International Journal of Environmental Research and Public Health
- Vol. 17 (18) , 6674
Open AccessMultifactorial 10-Year Prior Diagnosis Prediction Model of Dementia
Dementia is a neurodegenerative disorder that affects the older adult population. To date, no cure or treatment to change its course is available. Since changes in the brains of affected individuals could be evidenced as early as 10 years before the onset of symptoms, prognosis research should consider this time frame. This study investigates a broad decision tree multifactorial approach for the prediction of dementia, considering 75 variables regarding demographic, social, lifestyle, medical history, biochemical tests, physical examination, psychological assessment and health instruments. Previous work on dementia prognoses with machine learning did not consider a broad range of factors in a large time frame. The proposed approach investigated predictive factors for dementia and possible prognostic subgroups. This study used data from the ongoing multipurpose Swedish National Study on Aging and Care, consisting of 726 subjects (91 presented dementia diagnosis in 10 years). The proposed approach achieved an AUC of 0.745 and Recall of 0.722 for the 10-year prognosis of dementia. Most of the variables selected by the tree are related to modifiable risk factors; physical strength was important across all ages. Also, there was a lack of variables related to health instruments routinely used for the dementia diagnosis.
- Open Access
Guidelines for the Search Strategy to Update Systematic Literature Reviews in Software Engineering
Context: Systematic Literature Reviews (SLRs) have been adopted within Software Engineering (SE) for more than a decade to provide meaningful summaries of evidence on several topics. Many of these SLRs are now potentially not fully up-to-date, and there are no standard proposals on how to update SLRs in SE. Objective: The objective of this paper is to propose guidelines on how to best search for evidence when updating SLRs in SE, and to evaluate these guidelines using an SLR that was not employed during the formulation of the guidelines. Method: To propose our guidelines, we compare and discuss outcomes from applying different search strategies to identify primary studies in a published SLR, an SLR update, and two replications in the area of effort estimation. These guidelines are then evaluated using an SLR in the area of software ecosystems, its update and a replication. Results: The use of a single iteration forward snowballing with Google Scholar, and employing as a seed set the original SLR and its primary studies is the most cost-effective way to search for new evidence when updating SLRs. Furthermore, the importance of having more than one researcher involved in the selection of papers when applying the inclusion and exclusion criteria is highlighted through the results. Conclusions: Our proposed guidelines formulated based upon an effort estimation SLR, its update and two replications, were supported when using an SLR in the area of software ecosystems, its update and a replication. Therefore, we put forward that our guidelines ought to be adopted for updating SLRs in SE.
Open AccessGuidelines for the Search Strategy to Update Systematic Literature Reviews in Software Engineering
Context: Systematic Literature Reviews (SLRs) have been adopted within Software Engineering (SE) for more than a decade to provide meaningful summaries of evidence on several topics. Many of these SLRs are now potentially not fully up-to-date, and there are no standard proposals on how to update SLRs in SE. Objective: The objective of this paper is to propose guidelines on how to best search for evidence when updating SLRs in SE, and to evaluate these guidelines using an SLR that was not employed during the formulation of the guidelines. Method: To propose our guidelines, we compare and discuss outcomes from applying different search strategies to identify primary studies in a published SLR, an SLR update, and two replications in the area of effort estimation. These guidelines are then evaluated using an SLR in the area of software ecosystems, its update and a replication. Results: The use of a single iteration forward snowballing with Google Scholar, and employing as a seed set the original SLR and its primary studies is the most cost-effective way to search for new evidence when updating SLRs. Furthermore, the importance of having more than one researcher involved in the selection of papers when applying the inclusion and exclusion criteria is highlighted through the results. Conclusions: Our proposed guidelines formulated based upon an effort estimation SLR, its update and two replications, were supported when using an SLR in the area of software ecosystems, its update and a replication. Therefore, we put forward that our guidelines ought to be adopted for updating SLRs in SE.
- 6 May 2020
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 48 (2) , 466-484
A Theory of Value for Value-Based Feature Selection in Software Engineering
Value-Based Software Engineering stresses the role of value in software related decisions. In the context of feature selection, software features judged to provide higher value take priority in the development process. This paper focuses on what value means when selecting software features. Using grounded theory, we conducted and analyzed semi-structured interviews with 21 key stakeholders (decision-makers) from three software/software-intensive companies, within a context where value-based decision-making was already established. Our analysis led to the building of a theory of value for value-based feature selection that identifies the nature of value propositions considered by key stakeholders when selecting software features (i.e. decision-making criteria for deciding upon software features, as suggested by Boehm (2003)). We found that some value propositions were common to all three company cases (core value propositions), whereas others were dependent upon the context in which a company operates, and the characteristics of the product under development (specific value propositions). Moreover, value propositions vary according to the stakeholder group and the type of feature being assessed. Our study provides significant insight into value in the context of feature selection, and generates new concepts around value-based feature selection such as new value propositions.
- 6 May 2020
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 48 (2) , 466-484
A Theory of Value for Value-Based Feature Selection in Software Engineering
Value-Based Software Engineering stresses the role of value in software related decisions. In the context of feature selection, software features judged to provide higher value take priority in the development process. This paper focuses on what value means when selecting software features. Using grounded theory, we conducted and analyzed semi-structured interviews with 21 key stakeholders (decision-makers) from three software/software-intensive companies, within a context where value-based decision-making was already established. Our analysis led to the building of a theory of value for value-based feature selection that identifies the nature of value propositions considered by key stakeholders when selecting software features (i.e. decision-making criteria for deciding upon software features, as suggested by Boehm (2003)). We found that some value propositions were common to all three company cases (core value propositions), whereas others were dependent upon the context in which a company operates, and the characteristics of the product under development (specific value propositions). Moreover, value propositions vary according to the stakeholder group and the type of feature being assessed. Our study provides significant insight into value in the context of feature selection, and generates new concepts around value-based feature selection such as new value propositions.
- Open Access
When to Update Systematic Literature Reviews in Software Engineering
[Context] Systematic Literature Reviews (SLRs) have been adopted by the Software Engineering (SE) community for approximately 15 years to provide meaningful summaries of evidence on several topics. Many of these SLRs are now potentially outdated, and there are no systematic proposals on when to update SLRs in SE. [Objective] The goal of this paper is to provide recommendations on when to update SLRs in SE. [Method] We evaluated, using a three-step approach, a third-party decision framework (3PDF) employed in other fields, to decide whether SLRs need updating. First, we conducted a literature review of SLR updates in SE and contacted the authors to obtain their feedback relating to the usefulness of the 3PDF within the context of SLR updates in SE. Second, we used these authors feedback to see whether the framework needed any adaptation; none was suggested. Third, we applied the 3PDF to the SLR updates identified in our literature review. [Results] The 3PDF showed that 14 of the 20 SLRs did not need updating. This supports the use of a decision support mechanism (such as the 3PDF) to help the SE community decide when to update SLRs. [Conclusions] We put forward that the 3PDF should be adopted by the SE community to keep relevant evidence up to date and to avoid wasting effort with unnecessary updates.
Open AccessWhen to Update Systematic Literature Reviews in Software Engineering
[Context] Systematic Literature Reviews (SLRs) have been adopted by the Software Engineering (SE) community for approximately 15 years to provide meaningful summaries of evidence on several topics. Many of these SLRs are now potentially outdated, and there are no systematic proposals on when to update SLRs in SE. [Objective] The goal of this paper is to provide recommendations on when to update SLRs in SE. [Method] We evaluated, using a three-step approach, a third-party decision framework (3PDF) employed in other fields, to decide whether SLRs need updating. First, we conducted a literature review of SLR updates in SE and contacted the authors to obtain their feedback relating to the usefulness of the 3PDF within the context of SLR updates in SE. Second, we used these authors feedback to see whether the framework needed any adaptation; none was suggested. Third, we applied the 3PDF to the SLR updates identified in our literature review. [Results] The 3PDF showed that 14 of the 20 SLRs did not need updating. This supports the use of a decision support mechanism (such as the 3PDF) to help the SE community decide when to update SLRs. [Conclusions] We put forward that the 3PDF should be adopted by the SE community to keep relevant evidence up to date and to avoid wasting effort with unnecessary updates.
- 30 January 2019
- Published by Elsevier in Journal of Systems and Software
- Vol. 151, 224-225
Special issue on evaluation and assessment in software engineering
- 30 January 2019
- Published by Elsevier in Journal of Systems and Software
- Vol. 151, 224-225
Special issue on evaluation and assessment in software engineering
- 25 October 2018
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 46 (12) , 1340-1363
Key Stakeholders’ Value Propositions for Feature Selection in Software-Intensive Products: An Industrial Case Study
Numerous software companies are adopting value-based decision making. However, what does value mean for key stakeholders making decisions? How do different stakeholder groups understand value? Without an explicit understanding of what value means, decisions are subject to ambiguity and vagueness, which are likely to bias them. This case study provides an in-depth analysis of key stakeholders' value propositions when selecting features for a large telecommunications company's software-intensive product. Stakeholder' value propositions were elicited via interviews, which were analyzed using Grounded Theory coding techniques (open and selective coding). Thirty-six value propositions were identified and classified into six dimensions: customer value, market competitiveness, economic value/profitability, cost efficiency, technology & architecture, and company strategy. Our results show that although propositions in the customer value dimension were those mentioned the most, the concept of value for feature selection encompasses a wide range of value propositions. Moreover, stakeholder groups focused on different and complementary value dimensions, calling to the importance of involving all key stakeholders in the decision making process. Although our results are particularly relevant to companies similar to the one described herein, they aim to generate a learning process on value-based feature selection for practitioners and researchers in general.
- 25 October 2018
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 46 (12) , 1340-1363
Key Stakeholders’ Value Propositions for Feature Selection in Software-Intensive Products: An Industrial Case Study
Numerous software companies are adopting value-based decision making. However, what does value mean for key stakeholders making decisions? How do different stakeholder groups understand value? Without an explicit understanding of what value means, decisions are subject to ambiguity and vagueness, which are likely to bias them. This case study provides an in-depth analysis of key stakeholders' value propositions when selecting features for a large telecommunications company's software-intensive product. Stakeholder' value propositions were elicited via interviews, which were analyzed using Grounded Theory coding techniques (open and selective coding). Thirty-six value propositions were identified and classified into six dimensions: customer value, market competitiveness, economic value/profitability, cost efficiency, technology & architecture, and company strategy. Our results show that although propositions in the customer value dimension were those mentioned the most, the concept of value for feature selection encompasses a wide range of value propositions. Moreover, stakeholder groups focused on different and complementary value dimensions, calling to the importance of involving all key stakeholders in the decision making process. Although our results are particularly relevant to companies similar to the one described herein, they aim to generate a learning process on value-based feature selection for practitioners and researchers in general.
- Open Access
- 7 June 2016
- Published by Sociedade Brasileira de Computação in Journal of Software Engineering Research and Development
- Vol. 4 (1) , 1-24
An extended global software engineering taxonomy
In Global Software Engineering (GSE), the need for a common terminology and knowledge classification has been identified to facilitate the sharing and combination of knowledge by GSE researchers and practitioners. A GSE taxonomy was recently proposed to address such a need, focusing on a core set of dimensions; however its dimensions do not represent an exhaustive list of relevant GSE factors. Therefore, this study extends the existing taxonomy, incorporating new GSE dimensions that were identified by means of two empirical studies conducted recently. To address the research questions of this study, we used evidence found through a systematic literature review and a survey. Based on literature, new dimensions were added to the existing taxonomy. We identified seven dimensions to extend and incorporate into the recently proposed GSE taxonomy. The resulting extended taxonomy was later on validated by comparing it with the existing taxonomy on which the extension is built and one additional taxonomy. We also demonstrated the utility of the extended taxonomy using it to classify eight finished real GSE projects. The extended taxonomy was representative enough to classify the projects in a clear way. The extended taxonomy can help both researchers and practitioners by providing dimensions that can enable the description of different GSE contexts in a more comprehensive way; this can facilitate the understanding, comparison and aggregation of GSE-related findings.
- 7 June 2016
- Published by Sociedade Brasileira de Computação in Journal of Software Engineering Research and Development
- Vol. 4 (1) , 1-24
Open AccessAn extended global software engineering taxonomy
In Global Software Engineering (GSE), the need for a common terminology and knowledge classification has been identified to facilitate the sharing and combination of knowledge by GSE researchers and practitioners. A GSE taxonomy was recently proposed to address such a need, focusing on a core set of dimensions; however its dimensions do not represent an exhaustive list of relevant GSE factors. Therefore, this study extends the existing taxonomy, incorporating new GSE dimensions that were identified by means of two empirical studies conducted recently. To address the research questions of this study, we used evidence found through a systematic literature review and a survey. Based on literature, new dimensions were added to the existing taxonomy. We identified seven dimensions to extend and incorporate into the recently proposed GSE taxonomy. The resulting extended taxonomy was later on validated by comparing it with the existing taxonomy on which the extension is built and one additional taxonomy. We also demonstrated the utility of the extended taxonomy using it to classify eight finished real GSE projects. The extended taxonomy was representative enough to classify the projects in a clear way. The extended taxonomy can help both researchers and practitioners by providing dimensions that can enable the description of different GSE contexts in a more comprehensive way; this can facilitate the understanding, comparison and aggregation of GSE-related findings.
- Open Access
- 16 April 2016
- Published by Springer Nature in Progress in Artificial Intelligence
- Vol. 5 (4) , 307-314
Data mining for software engineering and humans in the loop
- 16 April 2016
- Published by Springer Nature in Progress in Artificial Intelligence
- Vol. 5 (4) , 307-314
Open AccessData mining for software engineering and humans in the loop
- 10 December 2015
- Published by Springer Nature
- p. 79-93
An Expert-Based Requirements Effort Estimation Model Using Bayesian Networks
- 10 December 2015
- Published by Springer Nature
- p. 79-93
An Expert-Based Requirements Effort Estimation Model Using Bayesian Networks