logseq/pages/IoTMoF%3A A Requirements-Driven Modelling Framework for Adaptive IoT Systems.md

type:: REVIEWS title:: IoTMoF: A Requirements-Driven Modelling Framework for Adaptive IoT Systems venue:: ECMFA year:: 2023 status:: DONE full-title:: IoTMoF: A Requirements-Driven Modelling Framework for Adaptive IoT Systems authors:: Paul Boutot, Sadaf Mustafiz links:: Local library, Web library

• Attachments
  • Boutot e Mustafiz - IoTMoF A Requirements-Driven Modelling Framework .pdf {{zotero-imported-file PAUWRAG9, "Boutot e Mustafiz - IoTMoF A Requirements-Driven Modelling Framework .pdf"}}
• Highlights
  • ((63c133de-c9b2-4b09-996b-a4003c5fd7f5))
  • ((63c13469-d794-40ef-8f06-4d2b68f75cd9))
  • ((63c268eb-34fb-4254-bf4a-325f2b28b957))
    • So, UCM4IoT does not provide any code generation functionalities?
      • ((63c26e58-c9e1-4f3f-abbf-3c9645c8f124))
  • ((63c26988-9e3d-49c3-80db-ea7b7f71b7e5))
    • What is the usage of statechart models for the deployment?
  • ((63c26fe4-cece-4fe8-bc10-a7521dd51438))
    • This looks like very low-level. It is still not clear what is the expressive power of the given modeling language. What kind of IoT systems can be modeled, what are the kind of supported architecture/connectivity models, etc. This comment is also related to the following statement in the paper
      • ((63c270f8-1ed1-4156-af18-2f3c90798188))
  • ((63c2715b-19d1-435d-b928-e72edec013d6))
    • Can you explicitily distill the performed adaptations with respect to the initial version?
      • ((63c27898-277b-43fe-9590-2b80a3db9709))
      • ((63c2c008-c2d6-4d6e-8891-0cb5abd5b26c))
        • This needs to be clearly described earlier in the paper.
  • ((63c2c153-a60f-4018-8e8e-dfda6580cc00))
    • It's not clear how the two metamodels/languages are aligned or work together? There is an overalp...
  • ((63c2c225-9e97-402f-b60d-1b9d08c2a856))
    • This does not parse
  • ((63c2c2b8-402b-487c-8d1c-f84acf216dc3))
    • To invoke?
  • ((63c2c306-30fc-4c6a-83c9-b68072ee0158))
    • What does it mean? That outlined part is not covered by the proposed approach?
  • ((63c2c384-cae6-4652-a59f-0ccc040c0094))
    • What does it mean evolve?
  • ((63c2c5e9-1f18-455a-9a5c-d731de867cd1))
    • Examples are not properly described in the paper. All the sections describing the different components/concepts underpinning the proposed approach should refer to a running explanatory example, otherwise it not easy to get all the details of the proposed technique.
  • ((63c2c686-990b-4bf6-a1ff-cdbb0d2509ad))
    • No readable, at all!!!
  • ((63c2fb03-2cfb-412f-979a-f0db28e21517))
    • What do you mean?
  • ((63c2fd84-003f-44b8-9c23-6016f0106998))
    • What does it mean exactly?
  • ((63c2fe38-2411-4b1e-911b-7e99317e7e27))
    • What loop?
  • ((63c2fe6d-d021-4fa5-8bc8-b34ce85e56a4))
    • Only this? You are assuming that the beaviour is implemented in each smart devices, the hub is just for storing data. That's fine but it is one of the possible configurations.
  • ((63c2ff9c-ba07-4fdd-b493-9cbafe5877f3))
    • All of this needs to be moved earlier in the paper as explanatory and running example.
  • ((63c3b07c-6416-404f-a1c6-a0bda6e07d31))
    • how fig 9 and fig 10 are linked?
  • ((63c3b143-e450-43f1-9826-e796f0c84544))
    • ???
  • ((63c3b1e6-9176-4504-91c4-987ca229fe59))
    • It's a loop.
  • ((63c3b271-63d3-4fcf-af98-598268e7ef5e))
    • not readable at all
  • ((63c3b49e-7b15-4396-b542-6c9cbe99ee4e))
    • There are many languages and it's coordinated use/adoption is not clear.
  • Overall I don't see (to be checked) a detailed description of the differences with existing technologies like Proteus IoT Builder (https://www.labcenter.com/)
• Comments
  • Summary: The paper presents an approach to support the development of IoT systems employing different modeling lanaguages and code-generators. Developers have the means to specify the requirements of the wanted applications and follow a model-driven process to get the final source code. The approach has been applied to a smart lights system.
  • Comments: The paper is about a relevant topic of interest for the event. However, I have some concerns that are related to the following issues:
    • The paper needs to present in a crystal clear manner the strengths and limitations of the proposed approach with respect to existing techniques. Even though the related work section makes an overview of existing techniques, it is not convincing, especially concerning Papyrus for IoT or even other technologies, like for instance, Proteus IoT Builder https://www.labcenter.com/
    • By following the previous comment, the authors should present early in the paper the challenges and shortcomings of existing approaches that IoTMoF is instead able to overcome.
    • I understand there is an overlap between UCM4IoT and IoTMOF, mainly related to the modeling of use cases. The authors should make explicit the refinements/additions that have been operated on UCM4IoT in the context of IoTMoF. For instance, Fig.2 shows an adapted UCM4IoT metamodel, even though it needs to be clarified what the performed adaptations are.
    • The IoTMoF approach consists of several domain-specific languages and tools. The authors mention that several editors and tools have been developed to support the specification and generation of the various artifacts. However, it needs to be made clear how all the different steps are linked and kept consistent.
    • The paper's focus is supposed to be "Adaptive IoT Systems". However, the proposed framework targets consumer devices. IoT systems can employ several gateways, cloud services, communication protocols, storage facilities, etc. Also, the adaptive aspect of the system should be clearly presented, for instance, w.r.t. to the distinct dimensions, which typically characterize (self-) adaptive systems [1]
    • The presentation of Section 4 should be improved by presenting an illustrative and running example. For instance, I would merge sections 4 and 5 to explain all the components currently presented in Section 4 by referring to artifacts now given in Section 5.
  • References
  • [1] C. Krupitzer, F. M. Roth, S. VanSyckel, G. Schiele, e C. Becker, «A survey on engineering approaches for self-adaptive systems», Pervasive and Mobile Computing, vol. 17, pp. 184–206, feb. 2015, doi: 10.1016/j.pmcj.2014.09.009.

• Refrences for people/felicien

  • ((63c25f12-591d-4598-9027-e8f5c22f82fd))
  • ((63c25fa6-a543-4fe0-9d00-0c7b98f42db8))
  • ((63c26d84-eed5-43d5-a040-d4bf1a0e9a40))