Fatima Sabir
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
Research Interests
Fatima Sabir has a total of 24 co-authors. Here are the top co-authors by number of shared publications:
- Jean Baptiste Minani
Concordia University
8 shared publications - Yann-Gaël Guéhéneuc
Concordia University
7 shared publications - Naouel Moha
Ecole de Technologie Supérieure de Montréal, Montréal, Canada
6 shared publications Naouel Moha
3 shared publications- Yahia El Fellah
Ecole de technologie supérieure, Montréal, Quebec, Canada
3 shared publications Fehmi Jaafar
Computer Science and Mathematics Department Quebec University, Chicoutimi Chicoutimi Quebec Canada
1 shared publication
Latest Publications
- Open Access
- 10 August 2026
- Published by Elsevier in Internet of Things
- Vol. 39
TGenAI: An LLM-based approach for functional end-to-end test generation for IoT systems
- 10 August 2026
- Published by Elsevier in Internet of Things
- Vol. 39
Open AccessTGenAI: An LLM-based approach for functional end-to-end test generation for IoT systems
- 11 November 2025
- Published by Wiley in Software: Practice and Experience
- Vol. 56 (2) , 190-217
Exploring the Impacts of Antipatterns on Object‐Oriented, Service‐Oriented, and Mobile‐Oriented Systems
Objective: Antipatterns (APs) represent potential issues in software systems stemming from poor design choices, coding practices, and undisciplined development. This systematic literature review analyzes 97 primary studies (PSs) from 2005 to 2024, exploring the impact of APs on Object‐Oriented (OO), Service‐Oriented (SO), and Mobile‐Oriented (MO) systems across various quality attributes. Methods: PSs are classified by techniques, datasets, evaluation measures, and tool support. Result: Findings highlight the association of APs with increased maintenance costs (27.8%), fault‐proneness (26.8%), change‐proneness (12.3%), and evolution challenges (25.7%). Most studies employ descriptive statistics, regression analysis, and Pearson correlation, with limited datasets and tool support for SO and MO systems compared to OO systems. Intermediate source code representations and program comprehension strategies are commonly used for analysis. Conclusion: These findings emphasize the need for further research on the impact of APs, particularly in MO systems, and their negative effects on software quality attributes.
- 11 November 2025
- Published by Wiley in Software: Practice and Experience
- Vol. 56 (2) , 190-217
Exploring the Impacts of Antipatterns on Object‐Oriented, Service‐Oriented, and Mobile‐Oriented Systems
Objective: Antipatterns (APs) represent potential issues in software systems stemming from poor design choices, coding practices, and undisciplined development. This systematic literature review analyzes 97 primary studies (PSs) from 2005 to 2024, exploring the impact of APs on Object‐Oriented (OO), Service‐Oriented (SO), and Mobile‐Oriented (MO) systems across various quality attributes. Methods: PSs are classified by techniques, datasets, evaluation measures, and tool support. Result: Findings highlight the association of APs with increased maintenance costs (27.8%), fault‐proneness (26.8%), change‐proneness (12.3%), and evolution challenges (25.7%). Most studies employ descriptive statistics, regression analysis, and Pearson correlation, with limited datasets and tool support for SO and MO systems compared to OO systems. Intermediate source code representations and program comprehension strategies are commonly used for analysis. Conclusion: These findings emphasize the need for further research on the impact of APs, particularly in MO systems, and their negative effects on software quality attributes.
- 11 September 2025
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Internet of Things Journal
- Vol. 12 (22) , 48787-48802
TISSEA: A Framework for Testing IoT Systems Based on Technical Software Engineering Aspects
Internet of Things (IoT) systems refer to interconnected systems of devices that collect, process, and exchange data. As IoT adoption continues to grow, ensuring effective testing is of paramount importance. However, testing IoT systems remains a challenge, particularly for software engineers, due to the need to test aspects beyond their primary area of expertise (e.g., security, sensor calibration, and connectivity). Testing aspects refer to any concept or concern that should be considered when testing a given system. While several frameworks for testing exist that focus on generic aspects of IoT systems, there is no dedicated framework for testing technical software engineering (SE) aspects of IoT systems. To address this gap, we propose and evaluate TISSEA, a framework to guide software engineers to test the technical SE aspects of IoT systems. We constructed TISSEA by identifying all possible technical SE aspects from published taxonomies for IoT systems testing. Further, we mapped each aspect to the granularity of testing at each layer of the IoT system. We finally mapped each aspect with test orchestration strategies, test input artifacts, and execution strategies. We evaluated the TISSEA by surveying 22 professionals and conducting two case studies: 1) event logging and handling testing and 2) data integrity testing. The survey results show that professionals agreed with the proposed technical SE aspects for testing the device and application layers. However, the aspects proposed for testing the gateway and cloud layers still require further investigation. Results of the case studies indicate a gap between expected and captured log events. Regarding event handling, we found that some of the events reported by the system as successfully handled may include unhandled events that cannot be identified when relying on a single orchestration strategy. Regarding data integrity testing, we found that data can be altered at any node at any layer of the IoT system. However, accessing the original data allows the detection of modifications made to it at each node. Overall evaluation of TISSEA shows strong agreement with practitioners, and it could be useful to test technical SE aspects of IoT systems.
- 11 September 2025
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Internet of Things Journal
- Vol. 12 (22) , 48787-48802
TISSEA: A Framework for Testing IoT Systems Based on Technical Software Engineering Aspects
Internet of Things (IoT) systems refer to interconnected systems of devices that collect, process, and exchange data. As IoT adoption continues to grow, ensuring effective testing is of paramount importance. However, testing IoT systems remains a challenge, particularly for software engineers, due to the need to test aspects beyond their primary area of expertise (e.g., security, sensor calibration, and connectivity). Testing aspects refer to any concept or concern that should be considered when testing a given system. While several frameworks for testing exist that focus on generic aspects of IoT systems, there is no dedicated framework for testing technical software engineering (SE) aspects of IoT systems. To address this gap, we propose and evaluate TISSEA, a framework to guide software engineers to test the technical SE aspects of IoT systems. We constructed TISSEA by identifying all possible technical SE aspects from published taxonomies for IoT systems testing. Further, we mapped each aspect to the granularity of testing at each layer of the IoT system. We finally mapped each aspect with test orchestration strategies, test input artifacts, and execution strategies. We evaluated the TISSEA by surveying 22 professionals and conducting two case studies: 1) event logging and handling testing and 2) data integrity testing. The survey results show that professionals agreed with the proposed technical SE aspects for testing the device and application layers. However, the aspects proposed for testing the gateway and cloud layers still require further investigation. Results of the case studies indicate a gap between expected and captured log events. Regarding event handling, we found that some of the events reported by the system as successfully handled may include unhandled events that cannot be identified when relying on a single orchestration strategy. Regarding data integrity testing, we found that data can be altered at any node at any layer of the IoT system. However, accessing the original data allows the detection of modifications made to it at each node. Overall evaluation of TISSEA shows strong agreement with practitioners, and it could be useful to test technical SE aspects of IoT systems.
- Open Access
- 8 March 2025
- Published by Elsevier in Journal of Systems and Software
- Vol. 226
IoT systems testing: Taxonomy, empirical findings, and recommendations
- 8 March 2025
- Published by Elsevier in Journal of Systems and Software
- Vol. 226
Open AccessIoT systems testing: Taxonomy, empirical findings, and recommendations
- 20 November 2024
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Internet of Things Journal
- Vol. 11 (23) , 37599-37616
A Systematic Literature Review of IoT System Architectural Styles and Their Quality Requirements
The Internet of Things (IoT) is increasingly prevalent, with systems developed across various domains. Choosing the right IoT architectural style is challenging due to the diversity of devices, dynamic environments, and real-time data needs. This choice significantly impacts system quality, requiring a careful balance of quality requirements and tradeoffs. Previous studies have not adequately identified the most suitable architectural styles for specific IoT quality needs. This study presents a systematic literature review of 103 primary studies (PSs) on IoT system quality requirements and architectural styles, assessing how each architectural style satisfies specific requirements. We followed the preferred reporting items for systematic review and meta-analysis (PRISMA) protocol to report our findings and answer three research questions (RQs). We selected PSs by applying inclusion and exclusion criteria to relevant papers published until the end of 2023. We analyzed data from PSs to understand IoT system quality requirements and architectural styles, assessing their alignment. The research revealed ten essential quality requirements for IoT systems and identified ten distinct architectural styles. Notably, each architectural style varies in its capacity to fulfill specific quality requirements, particularly regarding security, scalability, and performance. SOA, client-server, and REST architectural styles best fulfill many quality requirements. However, various architectural styles, such as Layered, Microservices, and Peer-to-Peer, show limited support for privacy requirements. Our findings can guide IoT systems practitioners in selecting an architectural style that aligns with their desired quality standards. Additionally, we recommend new research opportunities to deepen understanding of key architectural styles based on specific quality requirements.
- 20 November 2024
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Internet of Things Journal
- Vol. 11 (23) , 37599-37616
A Systematic Literature Review of IoT System Architectural Styles and Their Quality Requirements
The Internet of Things (IoT) is increasingly prevalent, with systems developed across various domains. Choosing the right IoT architectural style is challenging due to the diversity of devices, dynamic environments, and real-time data needs. This choice significantly impacts system quality, requiring a careful balance of quality requirements and tradeoffs. Previous studies have not adequately identified the most suitable architectural styles for specific IoT quality needs. This study presents a systematic literature review of 103 primary studies (PSs) on IoT system quality requirements and architectural styles, assessing how each architectural style satisfies specific requirements. We followed the preferred reporting items for systematic review and meta-analysis (PRISMA) protocol to report our findings and answer three research questions (RQs). We selected PSs by applying inclusion and exclusion criteria to relevant papers published until the end of 2023. We analyzed data from PSs to understand IoT system quality requirements and architectural styles, assessing their alignment. The research revealed ten essential quality requirements for IoT systems and identified ten distinct architectural styles. Notably, each architectural style varies in its capacity to fulfill specific quality requirements, particularly regarding security, scalability, and performance. SOA, client-server, and REST architectural styles best fulfill many quality requirements. However, various architectural styles, such as Layered, Microservices, and Peer-to-Peer, show limited support for privacy requirements. Our findings can guide IoT systems practitioners in selecting an architectural style that aligns with their desired quality standards. Additionally, we recommend new research opportunities to deepen understanding of key architectural styles based on specific quality requirements.
- Open Access
- 20 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 22-29
Towards an Automated Approach for Testing IoT Devices
The Internet of Things (IoT) comprises a network of physical devices embedded with sensors and software to collect and exchange data with other devices and systems via the Internet. IoT devices vary from small devices to complex industrial appliances. Despite the increase in the number of IoT devices, there is a lack of proper testing for these devices, which can impact the functionality of IoT systems. This study focuses on an automated approach for testing IoT systems that use Android-based devices. We propose an approach to generate test cases (TCs) and execute them in physical devices as instrumented tests. Our methodology uses source code as input. We analyze the source code and create an Abstract Syntax Tree (AST). We navigate the AST to identify classes, methods, input parameters, and return types. We manually create a test case (TC) template and use a heuristic search algorithm to generate the test data for each unit test. We populate the TC templates with information extracted from the AST and data generated by a heuristic search algorithm to generate executable TCs. We assess the quality of generated TCs using the mutation analysis technique. The experiment demonstrates that the proposed approach effectively generates executable TCs for conducting functional tests for IoT devices. This study can be beneficial for practitioners, researchers, and device manufacturers towards improvement in the way IoT devices are tested.
- 20 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 22-29
Open AccessTowards an Automated Approach for Testing IoT Devices
The Internet of Things (IoT) comprises a network of physical devices embedded with sensors and software to collect and exchange data with other devices and systems via the Internet. IoT devices vary from small devices to complex industrial appliances. Despite the increase in the number of IoT devices, there is a lack of proper testing for these devices, which can impact the functionality of IoT systems. This study focuses on an automated approach for testing IoT systems that use Android-based devices. We propose an approach to generate test cases (TCs) and execute them in physical devices as instrumented tests. Our methodology uses source code as input. We analyze the source code and create an Abstract Syntax Tree (AST). We navigate the AST to identify classes, methods, input parameters, and return types. We manually create a test case (TC) template and use a heuristic search algorithm to generate the test data for each unit test. We populate the TC templates with information extracted from the AST and data generated by a heuristic search algorithm to generate executable TCs. We assess the quality of generated TCs using the mutation analysis technique. The experiment demonstrates that the proposed approach effectively generates executable TCs for conducting functional tests for IoT devices. This study can be beneficial for practitioners, researchers, and device manufacturers towards improvement in the way IoT devices are tested.
- Open Access
- 20 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 57-64
Practical Guidance for IoT Systems Testing: A Taxonomy
The Internet of Things (IoT) has transformed the way we interact with technology and devices. Several IoT systems are being deployed across diverse domains. They fulfill critical tasks and, thus, must function correctly and securely and meet the users' expectations. However, testing IoT systems poses many challenges, primarily due to their distributed nature, dynamism, and heterogeneity as well as the multiple layers of which they are composed, i.e., device, edge, cloud, and application layers. The absence of testing guidance can hinder the quality of IoT systems. Testing guidelines, including taxonomy, are vital for proper IoT systems testing. In the context of software testing, taxonomy organizes and categorizes testing aspects, helping testers to understand what, how, and when to test. However, no IoT systems testing taxonomy exists, and traditional software testing taxonomy may not sufficiently meet IoT systems testing requirements. To address this, we introduce an IoT-specific testing taxonomy, informed by a review of 83 primary studies and validated through surveys with 16 IoT industry practitioners. The feedback collected from practitioners shows that our taxonomy can help IoT testers to improve efficiency of testing. This taxonomy can help the testers to increase test coverage, enhance the efficiency and effectiveness of testing efforts, and ensure thorough testing of important system aspects, thus ensuring functional correctness, improving the security of IoT systems, and better meeting users' expectations.
- 20 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 57-64
Open AccessPractical Guidance for IoT Systems Testing: A Taxonomy
The Internet of Things (IoT) has transformed the way we interact with technology and devices. Several IoT systems are being deployed across diverse domains. They fulfill critical tasks and, thus, must function correctly and securely and meet the users' expectations. However, testing IoT systems poses many challenges, primarily due to their distributed nature, dynamism, and heterogeneity as well as the multiple layers of which they are composed, i.e., device, edge, cloud, and application layers. The absence of testing guidance can hinder the quality of IoT systems. Testing guidelines, including taxonomy, are vital for proper IoT systems testing. In the context of software testing, taxonomy organizes and categorizes testing aspects, helping testers to understand what, how, and when to test. However, no IoT systems testing taxonomy exists, and traditional software testing taxonomy may not sufficiently meet IoT systems testing requirements. To address this, we introduce an IoT-specific testing taxonomy, informed by a review of 83 primary studies and validated through surveys with 16 IoT industry practitioners. The feedback collected from practitioners shows that our taxonomy can help IoT testers to improve efficiency of testing. This taxonomy can help the testers to increase test coverage, enhance the efficiency and effectiveness of testing efforts, and ensure thorough testing of important system aspects, thus ensuring functional correctness, improving the security of IoT systems, and better meeting users' expectations.
- 12 February 2024
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 50 (4) , 785-815
A Systematic Review of IoT Systems Testing: Objectives, Approaches, Tools, and Challenges
Internet of Things (IoT) systems are becoming prevalent in various domains, from healthcare to smart homes. Testing IoT systems is critical in ensuring their reliability. Previous papers studied separately the objectives, approaches, tools, and challenges of IoT systems testing. However, despite the rapid evolution of the IoT domain, no review has been undertaken to investigate all four aspects collectively. This paper presents a systematic literature review that aggregates, synthesizes, and discusses the results of 83 primary studies (PSs) concerning IoT testing objectives, approaches, tools, and challenges. We followed the Preferred Reporting Items for Systematic Review and Meta-Analysis (PRISMA) protocol to report our findings and answer research questions (RQs). To select PSs, we applied inclusion and exclusion criteria to relevant studies published between 2012 and 2022. We extracted and analyzed the data from PSs to understand IoT systems testing. The results reveal that IoT systems testing embraces traditional software quality attributes but also introduces new ones like connectivity, energy efficiency, device lifespan, distributivity, and dynamicity. They also show that existing IoT systems testing approaches are limited to specific aspects and should be expanded for more comprehensive testing. They also show 19 testing tools and 15 testbeds for testing IoT systems with their limitations, necessitating the development or enhancement for wider coverage. The large number of heterogeneous devices generating data in different formats, along with the need for testing in real-world scenarios, poses a challenge. Thus, our study offers insights into the testing objectives, approaches, tools, and challenges associated with IoT systems. Based on the results, we also provide practical guidance for IoT practitioners by cataloging existing tools and approaches, while also identifying new research opportunities for interested researchers.
- 12 February 2024
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 50 (4) , 785-815
A Systematic Review of IoT Systems Testing: Objectives, Approaches, Tools, and Challenges
Internet of Things (IoT) systems are becoming prevalent in various domains, from healthcare to smart homes. Testing IoT systems is critical in ensuring their reliability. Previous papers studied separately the objectives, approaches, tools, and challenges of IoT systems testing. However, despite the rapid evolution of the IoT domain, no review has been undertaken to investigate all four aspects collectively. This paper presents a systematic literature review that aggregates, synthesizes, and discusses the results of 83 primary studies (PSs) concerning IoT testing objectives, approaches, tools, and challenges. We followed the Preferred Reporting Items for Systematic Review and Meta-Analysis (PRISMA) protocol to report our findings and answer research questions (RQs). To select PSs, we applied inclusion and exclusion criteria to relevant studies published between 2012 and 2022. We extracted and analyzed the data from PSs to understand IoT systems testing. The results reveal that IoT systems testing embraces traditional software quality attributes but also introduces new ones like connectivity, energy efficiency, device lifespan, distributivity, and dynamicity. They also show that existing IoT systems testing approaches are limited to specific aspects and should be expanded for more comprehensive testing. They also show 19 testing tools and 15 testbeds for testing IoT systems with their limitations, necessitating the development or enhancement for wider coverage. The large number of heterogeneous devices generating data in different formats, along with the need for testing in real-world scenarios, poses a challenge. Thus, our study offers insights into the testing objectives, approaches, tools, and challenges associated with IoT systems. Based on the results, we also provide practical guidance for IoT practitioners by cataloging existing tools and approaches, while also identifying new research opportunities for interested researchers.
- 30 June 2023
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Internet of Things Journal
- Vol. 11 (1) , 1662-1684
A Multimethod Study of Internet of Things Systems Testing in Industry
As the Internet of Things (IoT) grows, its failures may have dramatic consequences on the lives of people who depend on it. Yet, it is hard to test IoT systems before they are deployed. Several researchers have provided state-of-the-art approaches for testing IoT systems. However, many of those approaches are based on academia rather than industry. Therefore, we conducted a multi-method study of IoT systems testing in the industry with IoT practitioners. We used three methods: 1 an industry survey, 2 practitioners interviews, and 3 analysis of Eclipse IoT surveys. This study focuses on testing IoT systems by industry practitioners. The findings show that 1 testing focuses more on the device, network, and application layers. IoT testing gives more importance to integration testing than acceptance testing. Test coverage is the most important metric, but metrics may vary depending on the project. 2 IoT system testing mainly uses the model-based approach and is often manual or semi-automated, with low adoption of white box testing. Node-RED is commonly used in testing IoT systems, while Amazon AWS IoT is popular for cloud platform testing of IoT devices. 3 Log analysis is the main approach to analyzing the root cause of bugs. 4 The main challenges in IoT testing include the lack of standards, security, connectivity, and reference architecture. Generating test cases and establishing a standard test approach are recommended for further research. This studyfs findings can help IoT practitioners and researchers to identify and tackle challenges in IoT system testing, leading to future research opportunities.
- 30 June 2023
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Internet of Things Journal
- Vol. 11 (1) , 1662-1684
A Multimethod Study of Internet of Things Systems Testing in Industry
As the Internet of Things (IoT) grows, its failures may have dramatic consequences on the lives of people who depend on it. Yet, it is hard to test IoT systems before they are deployed. Several researchers have provided state-of-the-art approaches for testing IoT systems. However, many of those approaches are based on academia rather than industry. Therefore, we conducted a multi-method study of IoT systems testing in the industry with IoT practitioners. We used three methods: 1 an industry survey, 2 practitioners interviews, and 3 analysis of Eclipse IoT surveys. This study focuses on testing IoT systems by industry practitioners. The findings show that 1 testing focuses more on the device, network, and application layers. IoT testing gives more importance to integration testing than acceptance testing. Test coverage is the most important metric, but metrics may vary depending on the project. 2 IoT system testing mainly uses the model-based approach and is often manual or semi-automated, with low adoption of white box testing. Node-RED is commonly used in testing IoT systems, while Amazon AWS IoT is popular for cloud platform testing of IoT devices. 3 Log analysis is the main approach to analyzing the root cause of bugs. 4 The main challenges in IoT testing include the lack of standards, security, connectivity, and reference architecture. Generating test cases and establishing a standard test approach are recommended for further research. This studyfs findings can help IoT practitioners and researchers to identify and tackle challenges in IoT system testing, leading to future research opportunities.
- 1 October 2021
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 48 (11) , 4319-4338
A Mixed-Method Approach to Recommend Corrections and Correct REST Antipatterns
Many companies, e.g., Facebook and YouTube, use the REST architecture and provide REST APIs to their clients. Like any other software systems, REST APIs need maintenance and must evolve to improve and stay relevant. Antipatternspoor design practiceshinder this maintenance and evolution. Although the literature defines many antipatterns and proposes approaches for their (automatic) detection, their correction did not receive much attention. Therefore, we apply a mixed-method approach to study REST APIs and REST antipatterns with the objectives to recommend corrections or, when possible, actually correct the REST antipatterns. Qualitatively, via case studies, we analyse the evolution of 11 REST APIs, including Facebook, Twitter, and YouTube, over six years. We detect occurrences of eight REST antipatterns in the years 2014, 2017, and 2020 in 17 versions of 11 REST APIs. Thus, we show that (1) REST APIs and antipatterns evolve over time and (2) developers seem to remove antipatterns. Qualitatively via a discourse analysis, we analyse developers forums and report that developers are concerned with the occurrences of REST antipatterns and discuss corrections to these antipatterns. Following these qualitative studies, using an engineering-research approach, we propose the following novel and unique contributions: (1) we describe and compare the corrections of eight REST antipatterns from the academic literature and from developers forums; (2) we devise and describe algorithms to recommend corrections to some of these antipatterns; (3) we present algorithms and a tool to correct some of these antipatterns by intercepting and modifying responses from REST APIs; and, (4) we validate the recommendations and the corrections manually and via a survey answered by 24 REST developers. Thus, we propose to REST API developers and researchers the first, grounded approach to correct REST antipatterns.
- 1 October 2021
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 48 (11) , 4319-4338
A Mixed-Method Approach to Recommend Corrections and Correct REST Antipatterns
Many companies, e.g., Facebook and YouTube, use the REST architecture and provide REST APIs to their clients. Like any other software systems, REST APIs need maintenance and must evolve to improve and stay relevant. Antipatternspoor design practiceshinder this maintenance and evolution. Although the literature defines many antipatterns and proposes approaches for their (automatic) detection, their correction did not receive much attention. Therefore, we apply a mixed-method approach to study REST APIs and REST antipatterns with the objectives to recommend corrections or, when possible, actually correct the REST antipatterns. Qualitatively, via case studies, we analyse the evolution of 11 REST APIs, including Facebook, Twitter, and YouTube, over six years. We detect occurrences of eight REST antipatterns in the years 2014, 2017, and 2020 in 17 versions of 11 REST APIs. Thus, we show that (1) REST APIs and antipatterns evolve over time and (2) developers seem to remove antipatterns. Qualitatively via a discourse analysis, we analyse developers forums and report that developers are concerned with the occurrences of REST antipatterns and discuss corrections to these antipatterns. Following these qualitative studies, using an engineering-research approach, we propose the following novel and unique contributions: (1) we describe and compare the corrections of eight REST antipatterns from the academic literature and from developers forums; (2) we devise and describe algorithms to recommend corrections to some of these antipatterns; (3) we present algorithms and a tool to correct some of these antipatterns by intercepting and modifying responses from REST APIs; and, (4) we validate the recommendations and the corrections manually and via a survey answered by 24 REST developers. Thus, we propose to REST API developers and researchers the first, grounded approach to correct REST antipatterns.