Change search
Link to record
Permanent link

Direct link
Ali, Nauman bin, Dr.ORCID iD iconorcid.org/0000-0001-7266-5632
Alternative names
Publications (10 of 45) Show all publications
Iftikhar, U., Ali, N. b., Börstler, J. & Usman, M. (2024). A tertiary study on links between source code metrics and external quality attributes. Information and Software Technology, 165, Article ID 107348.
Open this publication in new window or tab >>A tertiary study on links between source code metrics and external quality attributes
2024 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 165, article id 107348Article, review/survey (Refereed) Published
Abstract [en]

Context: Several secondary studies have investigated the relationship between internal quality attributes, source code metrics and external quality attributes. Sometimes they have contradictory results. Objective: We synthesize evidence of the link between internal quality attributes, source code metrics and external quality attributes along with the efficacy of the prediction models used. Method: We conducted a tertiary review to identify, evaluate and synthesize secondary studies. We used several characteristics of secondary studies as indicators for the strength of evidence and considered them when synthesizing the results. Results: From 711 secondary studies, we identified 15 secondary studies that have investigated the link between source code and external quality. Our results show : (1) primarily, the focus has been on object-oriented systems, (2) maintainability and reliability are most often linked to internal quality attributes and source code metrics, with only one secondary study reporting evidence for security, (3) only a small set of complexity, coupling, and size-related source code metrics report a consistent positive link with maintainability and reliability, and (4) group method of data handling (GMDH) based prediction models have performed better than other prediction models for maintainability prediction. Conclusions: Based on our results, lines of code, coupling, complexity and the cohesion metrics from Chidamber & Kemerer (CK) metrics are good indicators of maintainability with consistent evidence from high and moderate-quality secondary studies. Similarly, four CK metrics related to coupling, complexity and cohesion are good indicators of reliability, while inheritance and certain cohesion metrics show no consistent evidence of links to maintainability and reliability. Further empirical studies are needed to explore the link between internal quality attributes, source code metrics and other external quality attributes, including functionality, portability, and usability. The results will help researchers and practitioners understand the body of knowledge on the subject and identify future research directions. © 2023 The Author(s)

Place, publisher, year, edition, pages
Elsevier, 2024
Keywords
Code quality, Evidence, Product quality, Quality models, Tertiary review, Tertiary study, Codes (symbols), Computer programming languages, Data handling, Forecasting, Object oriented programming, Reliability, External quality, Internal quality, Products quality, Quality attributes, Quality modeling, Source code metrics, Maintainability
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-25555 (URN)10.1016/j.infsof.2023.107348 (DOI)001102357100001 ()2-s2.0-85174715019 (Scopus ID)
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile CommunicationsKnowledge Foundation, 20190081
Available from: 2023-11-06 Created: 2023-11-06 Last updated: 2023-12-15Bibliographically approved
Rico, S., Ali, N. b., Engström, E. & Höst, M. (2024). Experiences from conducting rapid reviews in collaboration with practitioners — Two industrial cases. Information and Software Technology, 167, Article ID 107364.
Open this publication in new window or tab >>Experiences from conducting rapid reviews in collaboration with practitioners — Two industrial cases
2024 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 167, article id 107364Article in journal (Refereed) Published
Abstract [en]

Context: Evidence-based software engineering (EBSE) aims to improve research utilization in practice. It relies on systematic methods to identify, appraise, and synthesize existing research findings to answer questions of interest for practice. However, the lack of practitioners’ involvement in these studies’ design, execution, and reporting indicates a lack of appreciation for the need for knowledge exchange between researchers and practitioners. The resultant systematic literature studies often lack relevance for practice. Objective: This paper explores the use of Rapid Reviews (RRs), in fostering knowledge exchange between academia and industry. Through the lens of two case studies, we delve into the practical application and experience of conducting RRs. Methods: We analyzed the conduct of two rapid reviews by two different groups of researchers and practitioners. We collected data through interviews, and the documents produced during the review (like review protocols, search results, and presentations). The interviews were analyzed using thematic analysis. Results: We report how the two groups of researchers and practitioners performed the rapid reviews. We observed some benefits, like promoting dialogue and paving the way for future collaborations. We also found that practitioners entrusted the researchers to develop and follow a rigorous approach and were more interested in the applicability of the findings in their context. The problems investigated in these two cases were relevant but not the most immediate ones. Therefore, rapidness was not a priority for the practitioners. Conclusion: The study illustrates that rapid reviews can support researcher-practitioner communication and industry-academia collaboration. Furthermore, the recommendations based on the experiences from the two cases complement the detailed guidelines researchers and practitioners may follow to increase interaction and knowledge exchange. © 2023 The Author(s)

Place, publisher, year, edition, pages
Elsevier, 2024
Keywords
Industry-academia collaboration, Literature reviews, Rapid reviews, Research relevance, Systematic review, Industrial research, Software engineering, Evidence Based Software Engineering, Knowledge exchange, Literature studies, Rapid review, Study design, Systematic method, Knowledge management
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-25786 (URN)10.1016/j.infsof.2023.107364 (DOI)001128629400001 ()2-s2.0-85178453626 (Scopus ID)
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile CommunicationsKnowledge Foundation, 20220235
Available from: 2023-12-15 Created: 2023-12-15 Last updated: 2024-02-22Bibliographically approved
Iftikhar, U., Börstler, J., Ali, N. b. & Kopp, O. (2024). Identifying prevalent quality issues in code changes by analyzing reviewers' feedback.
Open this publication in new window or tab >>Identifying prevalent quality issues in code changes by analyzing reviewers' feedback
2024 (English)Manuscript (preprint) (Other academic)
Abstract [en]

Context: Code reviewers provide valuable feedback during the code review. Identifying common issues described in the reviewers' feedback can provide input for context-specific software improvement opportunities. However, the use of reviewer feedback for this purpose is currently less explored.

Objective: Assessing if and how automation can derive themes in reviewers' feedback and whether these themes help to identify recurring quality-related issues in code changes.

Method: We conducted a case study using the JabRef system to distinguish reviewers' feedback on merged and abandoned code changes for the analysis. We used topic modeling to identify themes in 5,560 code review comments. The resulting themes were analyzed and named by a domain expert from JabRef.

Results: The domain expert considered the identified themes from the proposed automation approach to represent quality-related issues. We found that different quality issues are pointed out in code reviews for merged and abandoned code changes. 

Conclusions: The results indicate the usefulness of our proposed automation approach in utilizing code review comments for understanding the prevalent code quality issues that can help derive targeted and context-bound improvement actions.

National Category
Computer Systems
Research subject
Software Engineering
Identifiers
urn:nbn:se:bth-25611 (URN)
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile Communications
Available from: 2024-01-23 Created: 2024-01-23 Last updated: 2024-02-22Bibliographically approved
Iftikhar, U., Ali, N. b., Börstler, J. & Usman, M. (2023). A catalog of source code metrics – a tertiary study. In: Daniel Mendez, Dietmar Winkler, Johannes Kross, Stefan Biffl, Johannes Bergsmann (Ed.), Software Quality: Higher Software Quality through Zero Waste Development. Paper presented at 15th International Conference on Software Quality, SWQD 2023, Munich, Germany, May 23-25, 2023 (pp. 87-106). Springer, 472
Open this publication in new window or tab >>A catalog of source code metrics – a tertiary study
2023 (English)In: Software Quality: Higher Software Quality through Zero Waste Development / [ed] Daniel Mendez, Dietmar Winkler, Johannes Kross, Stefan Biffl, Johannes Bergsmann, Springer, 2023, Vol. 472, p. 87-106Conference paper, Published paper (Refereed)
Abstract [en]

Context: A large number of source code metrics are reported in the literature. It is necessary to systematically collect, describe and classify source code metrics to support research and practice.Objective: We aim to utilize existing secondary studies to develop a cat- alog of source code metrics together with their descriptions. The catalog will also provide information about which units of code (e.g., operators, operands, lines of code, variables, parameters, code blocks, or functions) are used to measure the internal quality attributes and the scope on which they are collected. 

Method: We conducted a tertiary study to identify secondary studies re- porting source code metrics. We have classified the source code metrics according to the measured internal quality attributes, the units of code used in the measures, and the scope at which the source code metrics are collected. 

Results: From 711 secondary studies, we identified 52 relevant secondary studies. We reported 423 source code metrics together with their de- scriptions and the internal quality attributes they measure. Source code metrics predominantly incorporate function as a unit of code to measure internal quality attributes. In contrast, several source code metrics use more than one unit of code when measuring internal quality attributes. Nearly 51% of the source code metrics are collected at the class scope, while almost 12% and 15% of source code metrics are collected at module and application levels, respectively. 

Conclusions: Researchers and practitioners can use the extensive catalog to assess which source code metrics meet their individual needs based on the description and classification scheme presented. 

Place, publisher, year, edition, pages
Springer, 2023
Series
Lecture Notes in Business Information Processing, ISSN 1865-1348, E-ISSN 1865-1356 ; 472
Keywords
Internal quality attributes, Code measurement, Code quality, Ter- tiary study, Source code metrics
National Category
Software Engineering
Research subject
Software Engineering
Identifiers
urn:nbn:se:bth-24650 (URN)10.1007/978-3-031-31488-9_5 (DOI)2-s2.0-85161231906 (Scopus ID)978-3-031-31487-2 (ISBN)978-3-031-31488-9 (ISBN)
Conference
15th International Conference on Software Quality, SWQD 2023, Munich, Germany, May 23-25, 2023
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile Communications, B07
Available from: 2023-05-30 Created: 2023-05-30 Last updated: 2023-10-20Bibliographically approved
Laiq, M., Ali, N. b., Börstler, J. & Engström, E. (2023). A data-driven approach for understanding invalid bug reports: An industrial case study. Information and Software Technology, 164, Article ID 107305.
Open this publication in new window or tab >>A data-driven approach for understanding invalid bug reports: An industrial case study
2023 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 164, article id 107305Article in journal (Refereed) Published
Abstract [en]

Context: Bug reports created during software development and maintenance do not always describe deviations from a system's valid behavior. Such invalid bug reports may consume significant resources and adversely affect the prioritization and resolution of valid bug reports. There is a need to identify preventive actions to reduce the inflow of invalid bug reports. Existing research has shown that manually analyzing invalid bug report descriptions provides cues regarding preventive actions. However, such a manual approach is not cost-effective due to the time required to analyze a sufficiently large number of bug reports needed to identify useful patterns. Furthermore, the analysis needs to be repeated as the underlying causes of invalid bug reports change over time. Objective: In this study, we propose and evaluate the use of Latent Dirichlet Allocation (LDA), a topic modeling approach, to support practitioners in suggesting preventive actions to avoid the creation of similar invalid bug reports in the future. Method: In an industrial case study, we first manually analyzed descriptions of invalid bug reports to identify common patterns in their descriptions. We further investigated to what extent LDA can support this manual process. We used expert-based validation to evaluate the relevance of identified common patterns and their usefulness in suggesting preventive measures. Results: We found that invalid bug reports have common patterns that are perceived as relevant, and they can be used to devise preventive measures. Furthermore, the identification of common patterns can be supported with automation. Conclusion: Using LDA, practitioners can effectively identify representative groups of bug reports (i.e., relevant common patterns) from a large number of bug reports and analyze them further to devise preventive measures. © 2023 The Author(s)

Place, publisher, year, edition, pages
Elsevier, 2023
Keywords
Bug classification, Bug management, Invalid bug reports, LDA, Software analytics, Software maintenance, Topic modeling, Cost effectiveness, Software design, Statistics, Bug managements, Bug reports, Industrial case study, Invalid bug report, Latent Dirichlet allocation, Preventive action, Preventive measures, Software analytic, Computer software maintenance
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-25295 (URN)10.1016/j.infsof.2023.107305 (DOI)001053508400001 ()2-s2.0-85166970380 (Scopus ID)
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile CommunicationsKnowledge Foundation, 20220235
Available from: 2023-08-18 Created: 2023-08-18 Last updated: 2023-09-08Bibliographically approved
Usman, M., Ali, N. b. & Wohlin, C. (2023). A Quality Assessment Instrument for Systematic Literature Reviews in Software Engineering. e-Informatica Software Engineering Journal, 17(1), Article ID 230105.
Open this publication in new window or tab >>A Quality Assessment Instrument for Systematic Literature Reviews in Software Engineering
2023 (English)In: e-Informatica Software Engineering Journal, ISSN 1897-7979, E-ISSN 2084-4840, Vol. 17, no 1, article id 230105Article in journal (Refereed) Published
Abstract [en]

Background: Systematic literature reviews (SLRs) have become a standard practice as part of software engineering (SE) research, although their quality varies. To build on the reviews, both for future research and industry practice, they need to be of high quality.Aim: To assess the quality of SLRs in SE, we put forward an appraisal instrument for SLRs.Method: A well-established appraisal instrument from research in healthcare was used as a starting point to develop the instrument. It is adapted to SE using guidelines, checklists, and experiences from SE. The first version was reviewed by four external experts on SLRs in SE and updated based on their feedback. To demonstrate its use, the updated version was also used by the authors to assess a sample of six selected systematic literature studies.Results: The outcome of the research is an appraisal instrument for quality assessment of SLRs in SE. The instrument includes 15 items with different options to capture the quality. The instrument also supports consolidating the items into groups, which are then used to assess the overall quality of an SLR.Conclusion: The presented instrument may be helpful support for an appraiser in assessing the quality of SLRs in SE.

Place, publisher, year, edition, pages
Wroclaw University of Technology, 2023
Keywords
Systematic reviews, quality assessment, critical appraisal, AMSTAR 2, systematic literature review, tertiary study
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-24415 (URN)10.37190/e-Inf230105 (DOI)000944209900001 ()2-s2.0-85152967598 (Scopus ID)
Funder
Knowledge Foundation, 20180127Knowledge Foundation, 20190081ELLIIT - The Linköping‐Lund Initiative on IT and Mobile Communications
Available from: 2023-04-05 Created: 2023-04-05 Last updated: 2023-04-28Bibliographically approved
Börstler, J., Ali, N. b. & Petersen, K. (2023). Double-counting in software engineering tertiary studies — An overlooked threat to validity. Information and Software Technology, 158, Article ID 107174.
Open this publication in new window or tab >>Double-counting in software engineering tertiary studies — An overlooked threat to validity
2023 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 158, article id 107174Article, review/survey (Refereed) Published
Abstract [en]

Context: Double-counting in a literature review occurs when the same data, population, or evidence is erroneously counted multiple times during synthesis. Detecting and mitigating the threat of double-counting is particularly challenging in tertiary studies. Although this topic has received much attention in the health sciences, it seems to have been overlooked in software engineering. Objective: We describe issues with double-counting in tertiary studies, investigate the prevalence of the issue in software engineering, and propose ways to identify and address the issue. Method: We analyze 47 tertiary studies in software engineering to investigate in which ways they address double-counting and whether double-counting might be a threat to validity in them. Results: In 19 of the 47 tertiary studies, double-counting might bias their results. Of those 19 tertiary studies, only 5 consider double-counting a threat to their validity, and 7 suggest strategies to address the issue. Overall, only 9 of the 47 tertiary studies, acknowledge double-counting as a potential general threat to validity for tertiary studies. Conclusions: Double-counting is an overlooked issue in tertiary studies in software engineering, and existing design and evaluation guidelines do not address it sufficiently. Therefore, we propose recommendations that may help to identify and mitigate double-counting in tertiary studies. © 2023 The Author(s)

Place, publisher, year, edition, pages
Elsevier, 2023
Keywords
Population statistics, Bias, Double counting, Empirical, Guideline, Meta-review, Overview of review, Recommendation, Research method, Review of review, Tertiary review, Tertiary study, Umbrella review, Software engineering, Double-counting, Guidelines, Overview of reviews, Recommendations, Research methods, Review of reviews
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-24419 (URN)10.1016/j.infsof.2023.107174 (DOI)001005614800001 ()2-s2.0-85150795598 (Scopus ID)
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile Communications
Available from: 2023-04-07 Created: 2023-04-07 Last updated: 2023-06-30Bibliographically approved
Börstler, J., Ali, N. b., Svensson, M. & Petersen, K. (2023). Investigating Acceptance Behavior in Software Engineering – Theoretical Perspectives. Journal of Systems and Software, 198, Article ID 111592.
Open this publication in new window or tab >>Investigating Acceptance Behavior in Software Engineering – Theoretical Perspectives
2023 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 198, article id 111592Article in journal (Refereed) Published
Abstract [en]

Background: Software engineering research aims to establish software development practice on a scientific basis. However, the evidence of the efficacy of technology is insufficient to ensure its uptake in industry. In the absence of a theoretical frame of reference, we mainly rely on best practices and expert judgment from industry-academia collaboration and software process improvement research to improve the acceptance of the proposed technology. Objective: To identify acceptance models and theories and discuss their applicability in the research of acceptance behavior related to software development.Method: We analyzed literature reviews within an interdisciplinary team to identify models and theories relevant to software engineering research. We further discuss acceptance behavior from the human information processing perspective of automatic and affect-driven processes (“fast” system 1 thinking) and rational and rule-governed processes (“slow” system 2 thinking). Results: We identified 30 potentially relevant models and theories. Several of them have been used in researching acceptance behavior in contexts related to software development, but few have been validated in such contexts. They use constructs that capture aspects of (automatic) system 1 and (rational) system 2 oriented processes. However, their operationalizations focus on system 2-oriented processes indicating a rational view of behavior, thus overlooking important psychological processes underpinning behavior. Conclusions: Software engineering research may use acceptance behavior models and theories more extensively to understand and predict practice adoption in the industry. Such theoretical foundations will help improve the impact of software engineering research. However, more consideration should be given to their validation, overlap, construct operationalization, and employed data collection mechanisms when using these models and theories.

Place, publisher, year, edition, pages
Elsevier, 2023
Keywords
Acceptance behavior, dual process theory, technology acceptance, theory, TAM, UTAUT, TPB
National Category
Software Engineering Psychology
Research subject
Software Engineering
Identifiers
urn:nbn:se:bth-24132 (URN)10.1016/j.jss.2022.111592 (DOI)000915632900001 ()2-s2.0-85146227386 (Scopus ID)
Projects
ELLIIT
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile Communications
Note

open access

Available from: 2022-12-23 Created: 2022-12-23 Last updated: 2023-03-02Bibliographically approved
Iftikhar, U., Börstler, J. & Ali, N. b. (2023). On potential improvements in the analysis of the evolution of themes in code review comments. In: Proceedings - 2023 49th Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2023: . Paper presented at 49th Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2023, Durres, Sept. 6th – Sept. 8th, 2023 (pp. 340-347). Institute of Electrical and Electronics Engineers (IEEE)
Open this publication in new window or tab >>On potential improvements in the analysis of the evolution of themes in code review comments
2023 (English)In: Proceedings - 2023 49th Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2023, Institute of Electrical and Electronics Engineers (IEEE), 2023, p. 340-347Conference paper, Published paper (Refereed)
Abstract [en]

Context: The modern code review process is considered an essential quality assurance step in software development. The code review comments generated can provide insights regarding source code quality and development practices. However, the large number of code review comments makes it challenging to identify interesting patterns manually. In a recent study, Wen et al. used traditional topic modeling to analyze the evolution of code review comments. Their approach could identify interesting patterns that may lead to improved development practices.Objective: In this study, we investigate potential improvements to Wen et al.'s state-of-the-art approach to analyze the evolution of code review comments.Method: We used 209,166 code review comments from three open-source systems to explore and empirically analyze alternative design and implementation choices and demonstrate their impact.Results: We identified the following potential improvements to the current state-of-the-art as described by Wen et al.: 1) utilize a topic modeling method that is optimized for short texts, 2) a refined approach for identifying a suitable number of topics, and 3) a more elaborate approach for analyzing topic evolution. Our results indicate that the proposed changes have quantitatively different results than the current approach. The qualitative interpretation of the topics generated with our changes indicates their usefulness.Conclusions: Our results indicate the potential usefulness of changes to state-of-the-art approaches to analyzing the evolution of code review comments, with practical implications for researchers and practitioners. However, further research is required to compare the effectiveness of both approaches. © 2023 IEEE.

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers (IEEE), 2023
Keywords
Modern Code Reviews, Source code quality, NLP
National Category
Computer Systems
Research subject
Software Engineering
Identifiers
urn:nbn:se:bth-25598 (URN)10.1109/SEAA60479.2023.00059 (DOI)2-s2.0-85183313412 (Scopus ID)9798350342352 (ISBN)
Conference
49th Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2023, Durres, Sept. 6th – Sept. 8th, 2023
Projects
ELLIIT, the Strategic Research Area within IT and Mobile Communications,
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile Communications
Available from: 2023-11-12 Created: 2023-11-12 Last updated: 2024-02-13Bibliographically approved
Bjarnason, E., Åberg, P. & Ali, N. b. (2023). Software selection in large-scale software engineering: A model and criteria based on interactive rapid reviews. Empirical Software Engineering, 28(2), Article ID 51.
Open this publication in new window or tab >>Software selection in large-scale software engineering: A model and criteria based on interactive rapid reviews
2023 (English)In: Empirical Software Engineering, ISSN 1382-3256, E-ISSN 1573-7616, Vol. 28, no 2, article id 51Article in journal (Refereed) Published
Abstract [en]

Context: Software selection in large-scale software development continues to be ad hoc and ill-structured. Previous proposals for software component selection tend to be technology-specific and/or do not consider business or ecosystem concerns. Objective: Our main aim is to develop an industrially relevant technology-agnostic method that can support practitioners in making informed decisions when selecting software components for use in tools or in products based on a holistic perspective of the overall environment. Method: We used method engineering to iteratively develop a software selection method for Ericsson AB based on a combination of published research and practitioner insights. We used interactive rapid reviews to systematically identify and analyse scientific literature and to support close cooperation and co-design with practitioners from Ericsson. The model has been validated through a focus group and by practical use at the case company. Results: The model consists of a high-level selection process and a wide range of criteria for assessing and for evaluating software to include in business products and tools. Conclusions: We have developed an industrially relevant model for component selection through active engagement from a company. Co-designing the model based on previous knowledge demonstrates a viable approach to industry-academia collaboration and provides a practical solution that can support practitioners in making informed decisions based on a holistic analysis of business, organisation and technical factors. © 2023, The Author(s).

Place, publisher, year, edition, pages
Springer, 2023
Keywords
Computer software selection and evaluation, Software design, CBSE, Component based, Component selection, Ericsson, Informed decision, Large-scales, Rapid review, Software component selections, Software selection, Tool selection, Iterative methods, Component-based
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-24374 (URN)10.1007/s10664-023-10288-w (DOI)000941140100001 ()2-s2.0-85149323067 (Scopus ID)
Projects
ELLIIT
Funder
ELLIIT - The Linköping‐Lund Initiative on IT and Mobile Communications
Available from: 2023-03-17 Created: 2023-03-17 Last updated: 2023-04-04Bibliographically approved
Projects
VITS- Visualisation of test data for decision support [20180127]; Blekinge Institute of Technology; Publications
Usman, M., Ali, N. b. & Wohlin, C. (2023). A Quality Assessment Instrument for Systematic Literature Reviews in Software Engineering. e-Informatica Software Engineering Journal, 17(1), Article ID 230105. Ali, N. b. & Tanveer, B. (2022). A Comparison of Citation Sources for Reference and Citation-Based Search in Systematic Literature Reviews. e-Informatica Software Engineering Journal, 16(1), Article ID 220106. Tran, H. K., Börstler, J., Ali, N. b. & Unterkalmsteiner, M. (2022). How good are my search strings? Reflections on using an existing review as a quasi-gold standard. e-Informatica Software Engineering Journal, 16(1), 69-89, Article ID 220103. Singh, S. P., Ali, N. b. & Lundberg, L. (2022). Smart and Adaptive Architecture for a Dedicated Internet of Things Network Comprised of Diverse Entities: A Proposal and Evaluation. Sensors, 22(8), Article ID 3017. Tran, H. K., Ali, N. b., Börstler, J. & Unterkalmsteiner, M. (2019). Test-Case Quality: Understanding Practitioners’ Perspectives. In: Franch X.,Mannisto T.,Martinez-Fernandez S. (Ed.), Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics): . Paper presented at 20th International Conference on Product-Focused Software Process Improvement, PROFES 2019; Barcelona; Spain; 27 November 2019 through 29 November (pp. 37-52). Springer, 11915
GIST – Gaining actionable Insights from Software Testing [20220235]; Blekinge Institute of Technology; Publications
Rico, S., Ali, N. b., Engström, E. & Höst, M. (2024). Experiences from conducting rapid reviews in collaboration with practitioners — Two industrial cases. Information and Software Technology, 167, Article ID 107364.
Organisations
Identifiers
ORCID iD: ORCID iD iconorcid.org/0000-0001-7266-5632

Search in DiVA

Show all publications