Challenges and Research Directions
In 2024, Hornos and Quinde conducted a very thorough methodological review that is to the point of stating the lack of a common development method for the Internet of Things (IoT)-based systems, which is the ongoing problem in as the situation is far from settled. The situation is complicated by the fact that IoT applications are gaining popularity very rapidly in different important areas like healthcare, smart cities, transportation, and industrial automation. At the same time, the integration of diverse hardware, software, networking, and intelligent decision-making systems has become more difficult. The text argues for considering the software engineering discourse by questioning whether the existing development methodologies—mostly carried over from the traditional information systems—are suitable for the complex and changing character of IoT environments.
The authors do not want to create a new methodology but intend to evaluate the existing ones step by step, unveil their shortcomings, and suggest areas for research that could lead to the emergence of new methodological innovations. The article is targeted to researchers, system developers, and methodologists who are looking for a well-organised path through the disunited methodological landscape of IoT system development.
The authors of the article see IoT platforms as highly complex social-technical systems that not only pack a wide range of devices but also control their communication amongst each other and the entire system at a very high speed, thanks to the computing infrastructures in the cloud, fog, and edge. They argue that the integration of hardware configuration, interoperability, security, and lifecycle management still poses a challenge to the use of traditional software development approaches in IoT systems.
An extensive literature survey is carried out to examine the current development methodologies in the IoT sector, which have been categorised into traditional, agile, model-based, agent-oriented, and hybrid methods. The authors review these methodologies in terms of the central lifecycle stages—conception, modelling, construction, and post-construction—highlighting considerable disparities in the definitions and the support of phases and activities. The review suggests that the majority of methodologies focus on the design and execution phases, while post-construction activities such as maintenance, system evolution, and decommissioning still remain largely neglected.
Moreover, the document points out that IoT development is faced with heterogeneity and interoperability, non-functional requirements management, reliability, and dependability, user-centric design, security and privacy, and AI integration constraints as the main obstacles. Based on these challenges, the authors put forward a set of research directions, demanding integrative, flexible, and standards-aligned methodologies that unite model-driven engineering, agile principles, AI support, and formal verification methods.
Significance and Contribution to the Field
The article’s main strength is the comprehensive and detailed methodological synthesis. The authors not only give a rich reference point for researchers and professionals by bringing together different IoT development approaches into one analytical framework, but also indicate that there are lifecycle blind spots—most importantly, the systematic ignoring of post-construction phases—which is an important contribution that brings up questions about sustainability and long-term system reliability that usually get neglected in IoT research.
The paper’s focus on methods is relevant, and it is a good time to consider that, because the use of IoT systems in safety-critical areas is being done at a faster rate. Talking about open research paths not only defines the future of methodological investigation very clearly but also strengthens the significance of the article beyond a mere descriptive review.
Methodology and Research Design
The conceptual and literature-driven nature of the study is appropriate given its ambitions. The authors exhibit an impressive knowledge of software engineering and IoT research, putting into practice a vast and perfectly organised collection of references. The organised juxtaposition of techniques across lifecycle phases not only adds analytical clarity but also makes the gaps systematically detectable.
Still, one of the limitations is the absence of empirical proof. Even though the article criticises the methods’ shortcomings quite convincingly, if the authors managed to demonstrate through example case studies or to invite a practitioner to share their experience, they would lend much more weight to their arguments and make the real-world IoT projects’ shortcomings visible. The nonexistence of empirical backing makes the research paths suggested as less relevant practically.
Argumentation and Use of Evidence
The article is logically structured, starting with the conceptual background and then proceeding to the methodological analysis, identification of challenges, and suggesting future directions for research. The authors’ argument that there is no existing methodology that completely covers the entire IoT lifecycle is very well supported by the evidence provided through comparison.
However, the critique at times comes close to being a generalisation of the methodology. Some of the particular methodologies are assessed largely by their concepts, without recognising the domain-specific accomplishments that could be the case when the methods are applied in a narrow context. Therefore, the argument might miss the point about the suitability of some existing methodologies in the specified context.
Ethical Considerations and Omissions
The article addresses ethical and user-centred difficulties quite well, especially concerning privacy, security, and the interaction between humans and computers. The adoption of ethical-by-design and user-centred approaches supports the paper’s ethical argument for the responsible development of the Internet of Things.
However, institutional and organisational factors like limitations in development skills, lack of resources, regulations, and barriers to industrial adoption get very little focus. If these issues had been discussed, it would have increased the potential for the suggested methodological directions to be applied in actual development ecosystems.
Writing Style and Structure
The main characteristics of the writing are clarity, technical precision, and accessibility to an advanced academic audience. The whole article is littered with definitions of terms, and the most complex distinctions of methodology are aptly presented.
It is the use of figures and tables that does the most to facilitate understanding, particularly in casting the methodological features and research directions in a nutshell. The neutrality and descriptiveness of the tone might give a conservative impression to readers who are after stronger critiques. The interactions with rival methodological positions and the evaluative positioning might have been more overt, and thus the critical intensity of the article increased.
Hornos and Quinde (2024) review the IoT system development methodologies in a very thorough and well-organised manner, which leads to the formulation of an exquisite synthesis of the existing methods as well as the clear stating of the unresolved dilemmas. The paper, as a whole, convinces the reader that the existing methodologies are still very much in a state of disarray, incomplete about the lifecycle, and not sufficiently matching the complexity of today’s IoT systems.
The limitations of the study’s conceptual perspective restrict its empirical applicability, but it also opens up new research directions that can be considered significant for the future of methodological innovation. The paper is a very good reference for doctoral students who need to create IoT development frameworks that are integrative, compliant with standards, and environmentally friendly. Future research should involve the testing of the suggested directions with the help of industrial case studies and cross-disciplinary collaborations, as this would not only bring the gap between methodological theory and IoT development practice closer but also enhance the credibility of the proposed directions.