6.5 KiB
6.5 KiB
type:: REVIEWS
tags::
year:: 2023
venue:: SOSYM
full-title:: FloBP: An Interdisciplinary Model-Driven Approach for Developing and Executing IoT-Enhanced Business Processes
date-start:: 21-08-2023 - 18:41
date-submitted::
external-links:: ScholarOne Manuscripts (manuscriptcentral.com)
status:: DONE
deadline-submission:: 16-08-2023
file::
- [[Highlights]]
- #+BEGIN_IMPORTANT
((64f3454e-73b8-4bde-8077-3bf8e170322e))
((64f34564-49e9-439b-92af-aa5ba30097c8))
((64f5e857-03ea-4c06-ac24-f356b8d39e5b))
((64f5e8c8-f95d-46f7-b160-81a96249c4f5))
((64f5e8d6-dc31-4d97-a12e-172893b9ab44))
#+END_IMPORTANT
-
- ((64f5e688-e52e-4478-8585-b2aa225b4341))
- BPs with air conditioner? It's a bit enforced this example....
- ((64f5e9dc-3de7-4c7c-9abb-f98b42b207d9))
- What's that?
- DONE Guardare Design Science Research #reading
| - ((650453ac-52b8-4280-8dae-5b1aa88be24f)) |
|---|
| - Comments |
| - This paper presents a tool-supported approach for the development and execution of IoT-enhanced business processes. The methodology consists of six main steps involving three key stakeholders: the IoT modeling expert, the business engineer, and the IoT application developer. The approach is evaluated based on three dimensions: effectiveness, efficiency, and user acceptance. |
| - |
| - The paper is well-written and structured. However, there are some sections that are verbose or repetitive and could be streamlined. Nevertheless, I am impressed by the comprehensive work presented in this paper. It effectively introduces readers to preliminary concepts and guides them through the various components of the approach, from model-based supporting tools to the evaluation involving human participants. Here are some minor suggestions for enhancing the paper: |
| - When introducing business processes, it would be beneficial to mention more complex systems within the business domain that go beyond examples like air conditioners and heating systems. |
| - It is important to clarify what new content this paper brings compared to related conference and journal papers authored by some of the same researchers, which present underlying techniques and tools utilized in this work. |
| - In Section 4.1, where the paper discusses the transition from feature models to BPMN specifications, it would be helpful to provide an overview of the conceptual mappings between feature model elements and BPMN modeling artifacts. This comment also applies to the first sentence of Section 4.2. |
| - In Section 4.2, just below Figure 5, the authors mention guidelines that should be followed to ensure compatibility and interoperability. It is necessary to clarify whether and how these guidelines are enforced during the modeling phase. |
| - On page 19, before Section 5, the authors introduce Node-RED without prior explanation of its role. It would be beneficial to provide an initial overview of the target platform and its technical components earlier in the paper. A simplified version of Figure 10, shown earlier in the section, could help mitigate this issue. |
| - There are some concerns about the hypothesis given on page 24. The term "feasibility" is somewhat vague as a target goal for the evaluation. It would be helpful to specify the metrics and criteria used to assess the quality of the proposed solution. The hypothesis should be refined to make it more specific. |
| - In Section 6.2, when referring to "correct" performance, it would be beneficial to define what is meant by "correct." Clarify the criteria or benchmarks used to evaluate performance to avoid ambiguity. |
| - |
| - |
| - |
| - Notes |
| - ((650430e7-dee7-4807-82c8-d8cd1c4ac42e)) |
| - DONE Guardare ontologia IoT-Lite per corso IoT |
| id:: 65c8d477-2c6c-4548-9e72-09cee84bec35 |
| - DONE ((6504517f-4d23-4d6d-9a71-cd8b0da1d5fc)) empirical reading |
| id:: 65c8d477-b5c3-45c1-986d-9daf3563a1d1 |
| :LOGBOOK: |
| CLOCK: [2025-05-26 Mon 22:21:22]--[2025-05-26 Mon 22:21:23] => 00:00:01 |
| :END: |
| - #+BEGIN_IMPORTANT |
| It is necessary to highlight the novelties with respect to: |
| ((650433d8-e596-4433-9f4e-93eb478b8308)) |
| ((650433ca-60d9-4a6a-a749-7fd1d0f7fa59)) |
| #+END_IMPORTANT |