An Approach Based on Model-Driven Development for IoT Applications

Sosa-Reyna, Claudia M.; Tello-Leal, Edgar; Alabazares, David Lara

doi:10.1109/iciot.2018.00026

Cited by 9 publications

(8 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, due to the lack of well-established standards at the hardware level, manufacturers often provide different implementations and/or operational features, which often leads to a heterogeneous software and communications platform (i.e., with different communication technologies and protocols) [ 34 , 122 ]. In addition, developers typically must deploy a shared set of functionalities across multiple and different devices [ 123 , 124 , 125 ]. Consequently, in that scenario, hardware heterogeneity leads to different source codes of the same software design, just to be able to support the different features of the underlying hardware.…”

Section: Methodologies Designed For the Development Of Iotssmentioning

confidence: 99%

“…Sosa-Reyna et al present a methodology with two approaches, i.e., with the MDD [ 124 , 125 ] and MDE [ 123 ] approaches. This methodology establishes the following stages of development: (1) Analysis of business requirements, (2) definition of the business logic, (3) design of the integrated services solution, (4) generation of the technological solution, and (5) model transformation methods.…”

Section: Methodologies For Traditional Is Development Applied To Iots...mentioning

confidence: 99%

“…Some authors, such as Gogineni et al [ 86 ], Wang et al [ 180 ], and Fortino et al [ 185 ], consider requirements analysis as part of the system analysis stage, which constitutes the reason why they do not address the requirements elicitation. However, other authors, such as Guerrero-Ulloa et al [ 37 ], Usländer and Batz [ 102 ], and Sosa-Reyna et al [ 123 , 124 , 125 ], separate these stages very well and give them the importance they require, since the system requirements must be clear enough from the very beginning so that the development of the IoTS is not delayed. It could be concluded that the lack of consideration of the planning stage is widespread since only Guerrero-Ulloa et al [ 37 ] expressly specify it, while Gogineni et al [ 86 ] only give hints of its consideration, and Fortino et al [ 65 ] only let us guess its consideration, since its proposal is based on waterfall methodology, which does contemplate this stage.…”

Section: Methodologies For Traditional Is Development Applied To Iots...mentioning

confidence: 99%

“…Among the most frequent architectures are layered and service-oriented architectures. In addition, some authors [ 123 , 124 , 125 , 170 ] present a combination of both types, while other authors [ 78 , 94 , 139 , 169 , 195 , 196 ] present their own architectures to give solutions to different types of IoTSs.…”

Section: Architectures For Iotssmentioning

confidence: 99%

“…In some of the works considered in this review, Sosa-Reyna et al [ 123 , 124 , 125 ] propose an architecture based on SOA, consisting of four layers: (1) object layer (hardware objects available on the network), (2) network layer (wired, wireless or mobile connection infrastructure), (3) service (creation and management of required services), and (4) application layer (responsible for delivering applications to IoTS users). This service-oriented architecture supports development methodologies with two different approaches: MDD [ 124 , 125 ] and MDE [ 123 ].…”

Section: Architectures For Iotssmentioning

confidence: 99%

See 4 more Smart Citations

Agile Methodologies Applied to the Development of Internet of Things (IoT)-Based Systems: A Review

Guerrero-Ulloa

Rodríguez-Domínguez

Hornos

2023

Sensors

View full text Add to dashboard Cite

Throughout the evolution of software systems, empirical methodologies have been used in their development process, even in the Internet of Things (IoT) paradigm, to develop IoT-based systems (IoTS). In this paper, we review the fundamentals included in the manifesto for agile software development, especially in the Scrum methodology, to determine its use and role in IoTS development. Initially, 4303 documents were retrieved, a number that was reduced to 186 after applying automatic filters and by the relevance of their titles. After analysing their contents, only 60 documents were considered. Of these, 38 documents present the development of an IoTS using some methodology, 8 present methodologies focused on the construction of IoTS software, and 14 present methodologies close to the systems life cycle (SLC). Finally, only one methodology can be considered SLC-compliant. Out of 38 papers presenting the development of some IoTS following a methodology for traditional information systems (ISs), 42.1% have used Scrum as the only methodology, while 10.5% have used Scrum combined with other methodologies, such as eXtreme Programming (XP), Kanban and Rapid Prototyping. In the analysis presented herein, the existing methodologies for developing IoTSs have been grouped according to the different approaches on which they are based, such as agile, modelling, and service oriented. This study also analyses whether the different proposals consider the standard stages of the development process or not: planning and requirements gathering, solution analysis, solution design, solution coding and unit testing (construction), integration and testing (implementation), and operation and maintenance. In addition, we include a review of the automated frameworks, platforms, and tools used in the methodologies analysed to improve the development of IoTSs and the design of their underlying architectures. To conclude, the main contribution of this work is a review for IoTS researchers and developers regarding existing methodologies, frameworks, platforms, tools, and guidelines for the development of IoTSs, with a deep analysis framed within international standards dictated for this purpose.

show abstract