566 lines
24 KiB
Markdown
566 lines
24 KiB
Markdown
file:: [SOSYM-23-00004472_Proof_hi_1692636091905_0.pdf](../assets/SOSYM-23-00004472_Proof_hi_1692636091905_0.pdf)
|
||
file-path:: ../assets/SOSYM-23-00004472_Proof_hi_1692636091905_0.pdf
|
||
|
||
- An Interdisciplinary Model-Driven Approach for Developing and Executing IoT-Enhanced Business Process
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: green
|
||
id:: 64f34504-32b1-4b7b-aa31-2a069cdc3110
|
||
- T-enhanced BPs promises
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: green
|
||
id:: 64f34535-0d97-407f-8405-b555ac84f014
|
||
- FloBP, a model-driven engineering (MDE) approach separating concerns between the IoT and BPs
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: purple
|
||
id:: 64f3454e-73b8-4bde-8077-3bf8e170322e
|
||
- modelling and executing IoT-enhanced BPs.
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: purple
|
||
id:: 64f34564-49e9-439b-92af-aa5ba30097c8
|
||
- An Internet of Things (IoT)-enhanced Business Process (BP) refers to integrating IoT technologies and devices into various aspects of a business’s operations and workflows to optimise efficiency, enhance productivity, and enable new capabilities of the organization
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64f5e677-ebf0-4667-b200-eabd8ed78569
|
||
- air conditioner
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: yellow
|
||
id:: 64f5e688-e52e-4478-8585-b2aa225b4341
|
||
- Making data-driven decisions based on these insights can enhance overall efficiency, reduce costs, elevate the customer experience, and foster innovation.
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64f5e6d1-25b7-421f-9869-2040d87b6623
|
||
- This convergence of IoT technologies and BPs can empower organisations to remain agile, optimise their operations, and gain a competitive advantage in the ever-evolving digital landscape
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: blue
|
||
id:: 64f5e814-6f37-43e6-90c9-d0f4fa10d0f1
|
||
- Integrating the domains of IoT and Business Process Management (BPM) poses inherent challenges due to their different abstraction levels and characteristics that need to be handled by different experts’ competencies, resulting in the high complexity and costs
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64f5e81e-4d3d-495f-897c-3b58bc5fdf0e
|
||
- heterogeneity complicates the integration process, requiring solutions to address interoperability and standardization issues
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64f5e836-a1ed-478d-b484-73e93ceb5d16
|
||
- business modellers asked to design processes seek to abstract from the intricate technical aspects of IoT.
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64f5e841-6650-4b26-ac42-2c26122fb711
|
||
- innovative approaches to enable a coherent convergence of holistic disciplines such as the IoT and BPM, empowering organisations to leverage the benefits of IoT technologies without compromising the agility and efficiency of their BPs
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: purple
|
||
id:: 64f5e857-03ea-4c06-ac24-f356b8d39e5b
|
||
- Tackling the problem from an interdisciplinary perspective requires handling the intrinsic difficulty in developing these solutions
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: green
|
||
id:: 64f5e87a-0f0f-43fa-bd50-f80e57f1796c
|
||
- IoT solutions that meet customer demands while avoiding duplication of effort and ensuring efficient utilisation of resources
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: green
|
||
id:: 64f5e8ae-ede8-46fa-994c-6ba07c02a987
|
||
- FloBP builds over two different approaches, presented in[13] and [14]. The first one, named FloWare [13], proposes a model-driven strategy to explicitly model the IoT domain knowledge through a predefined Feature Models structure. The second one, [14], poses guidelines to develop IoT-enhanced BPs and provides a microservices infrastructure to support the deployment of the underlying processes.
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: purple
|
||
id:: 64f5e8c8-f95d-46f7-b160-81a96249c4f5
|
||
- FloBP intends to provide support from the design to developing and deploying customised IoT-enhanced BPs.
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: purple
|
||
id:: 64f5e8d6-dc31-4d97-a12e-172893b9ab44
|
||
- edefines the structuring of Feature Model diagrams proposed in [13] so as to permit a more effective integration and usage of this knowledge in order to model IoT-enhanced BPs
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: green
|
||
id:: 64f5e910-f8c3-49ab-bf5e-35dcabe41ab6
|
||
- we analyse the constructs provided by the BPMN metamodel and define a proposal to specify IoT devices and pull interactions without modifying its metamodel.
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: green
|
||
id:: 64f5e928-ab1a-4ef7-ba04-d4d04e53391c
|
||
- we apply the Separation of Concerns (SoC) design principle to permit different experts to contribute to the different development phases and steps of the solution
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: blue
|
||
id:: 64f5e933-b496-4b91-9de3-2cd41ad8e59b
|
||
- A microservices architecture is designed to streamline the integration of business processes with the physical world
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: green
|
||
id:: 64f5e982-410a-4709-bff2-d1948c9e17bd
|
||
- t leverages the power of modelling tools and platforms to automate and optimise the development process, improving productivity and reducing time-to-market
|
||
ls-type:: annotation
|
||
hl-page:: 4
|
||
hl-color:: green
|
||
id:: 64f5e9ca-3067-4b05-8736-683d2a06b3a6
|
||
- esign Science Research (DSR)
|
||
ls-type:: annotation
|
||
hl-page:: 5
|
||
hl-color:: yellow
|
||
id:: 64f5e9dc-3de7-4c7c-9abb-f98b42b207d9
|
||
- According to the DSR [15], this solution can be categorised as an approach since it provides actionable instructions of a conceptual nature.
|
||
ls-type:: annotation
|
||
hl-page:: 5
|
||
hl-color:: blue
|
||
id:: 64f5ecd3-6ecb-48c6-a506-afc8e4a261af
|
||
- problem identification and motivation
|
||
ls-type:: annotation
|
||
hl-page:: 5
|
||
hl-color:: green
|
||
id:: 64f5ed94-2c3e-4c0b-81fd-2708f015f389
|
||
- design and development
|
||
ls-type:: annotation
|
||
hl-page:: 5
|
||
hl-color:: green
|
||
id:: 64f5ed99-c558-4da4-99b4-6e2c00e76fbe
|
||
- defines objectives of the contribution
|
||
ls-type:: annotation
|
||
hl-page:: 5
|
||
hl-color:: green
|
||
id:: 64f5eda2-9040-4543-83cc-7f57e9c0cca7
|
||
- demonstration
|
||
ls-type:: annotation
|
||
hl-page:: 5
|
||
hl-color:: green
|
||
id:: 64f5edb5-9764-49ee-990b-4bca945c3d16
|
||
- improving efficiency (in terms of time, cost, sustainability, etc.).
|
||
ls-type:: annotation
|
||
hl-page:: 5
|
||
hl-color:: green
|
||
id:: 64f5edf1-9f93-4cef-af06-0e7d5dd31c5a
|
||
- To better explain the problem, we will consider the part of a smart canteen scenario in which different IoT devices can be integrated into the processes supporting food distribution and those managing the canteen hal
|
||
ls-type:: annotation
|
||
hl-page:: 6
|
||
hl-color:: green
|
||
id:: 64f5ee2f-b52d-4533-86da-3f35dd519132
|
||
- However, these activities can become difficult to achieve when the canteen reaches high volumes of concurrent customers, and integrating IoT devices into the canteen processes to make them more effective, seems to be a profitable direction.
|
||
ls-type:: annotation
|
||
hl-page:: 6
|
||
hl-color:: green
|
||
id:: 64f5ee6e-749f-41e5-a654-62826d03ad65
|
||
- Anyway, to make it more effective different IoT devices could be included in supporting BP activities.
|
||
ls-type:: annotation
|
||
hl-page:: 6
|
||
hl-color:: green
|
||
id:: 64f5eea5-604c-4b52-98e2-e2ac76b5e2bc
|
||
- The integration of IoT devices inside the overall process is strictly dependent on the customer’s requirements.
|
||
ls-type:: annotation
|
||
hl-page:: 6
|
||
hl-color:: green
|
||
id:: 64f5eeb5-7ada-4c6e-8585-48a0203f7446
|
||
- arious types of devices can be utilised to fulfil different functionalities.
|
||
ls-type:: annotation
|
||
hl-page:: 6
|
||
hl-color:: green
|
||
id:: 64f5eec4-1e0b-49a2-8752-74415a6bf64a
|
||
- This preference is reflected in the overall BP, which could need to be adapted or enhanced according to the IoT devices chosen
|
||
ls-type:: annotation
|
||
hl-page:: 6
|
||
hl-color:: blue
|
||
id:: 64f5eee7-32a9-4600-a5a5-6317432d2153
|
||
hl-stamp:: 1693839082230
|
||
- If we want these processes to be executable, the process must be deployed in a process engine, and the IoT devices must also be set up and configured. H
|
||
ls-type:: annotation
|
||
hl-page:: 6
|
||
hl-color:: green
|
||
id:: 64f5ef10-bc25-44b7-ab3e-6bf4a0f9ebc7
|
||
- Considering the aforementioned challenges, we intended to derive and validate a model-driven development process that can support the interdisciplinary nature of IoT-enhanced BPs, fostering the separation of concerns and the smooth cooperation of different stakeholders, bringing different expertise.
|
||
ls-type:: annotation
|
||
hl-page:: 7
|
||
hl-color:: yellow
|
||
id:: 64f5fabc-0007-47cd-8b9c-f733ec7736cd
|
||
hl-stamp:: 1693842112456
|
||
- By adopting a MDE approach, enterprises can use the acquired knowledge and experience to optimise their software development processes
|
||
ls-type:: annotation
|
||
hl-page:: 7
|
||
hl-color:: green
|
||
id:: 64f70ae2-acfb-419f-ad8b-a0559d457a92
|
||
hl-stamp:: 1693911781041
|
||
- ach phase encompasses multiple steps to be carried out by different actors, as depicted in Figure 1 within the Modelling Layer.
|
||
ls-type:: annotation
|
||
hl-page:: 7
|
||
hl-color:: green
|
||
id:: 64f710c9-11a3-4155-a445-c0ec4c42be54
|
||
- Platform Independent Mode
|
||
ls-type:: annotation
|
||
hl-page:: 8
|
||
hl-color:: green
|
||
id:: 64f710e8-1bba-4283-ab1e-3854ebfe0fc4
|
||
- Step 1 - Feature Model Design
|
||
ls-type:: annotation
|
||
hl-page:: 8
|
||
hl-color:: green
|
||
id:: 64f71100-b91f-4153-b376-8e4f02c7348b
|
||
- IoT Modelling Expert,
|
||
ls-type:: annotation
|
||
hl-page:: 8
|
||
hl-color:: green
|
||
id:: 64f7113b-06f1-42b0-9ace-ceec319b226c
|
||
- Step 2 - IoT-enhanced BP Design.
|
||
ls-type:: annotation
|
||
hl-page:: 8
|
||
hl-color:: green
|
||
id:: 64f71192-487a-4f86-aee9-ddf4200e352c
|
||
- BP can trigger on-demand IoT device operations inserted on it, explicitly demanding an IoT device to act.
|
||
ls-type:: annotation
|
||
hl-page:: 9
|
||
hl-color:: green
|
||
id:: 64f71cc4-549a-44e6-b5ea-79e3722b4d7a
|
||
- High-level events related to IoT devices can trigger the BP when activated
|
||
ls-type:: annotation
|
||
hl-page:: 9
|
||
hl-color:: green
|
||
id:: 64f71cec-e5da-4a6c-8d80-facd5987b176
|
||
- Once terminated, the resulting IoT-enhanced BP is deployed inside the BPMN Engine, a microservice able to execute at runtime the developed model.
|
||
ls-type:: annotation
|
||
hl-page:: 9
|
||
hl-color:: green
|
||
id:: 64f71d09-d1cf-449e-a9fa-a44eed4676d1
|
||
- This provides a comprehensive structure of the expert’s decisions based on the business requirements, referred to as the Step 3 - Feature Model Configuration.
|
||
ls-type:: annotation
|
||
hl-page:: 9
|
||
hl-color:: green
|
||
id:: 64f71d1c-c1cb-4440-81f6-504cafae813d
|
||
- n this sense, further refinement is necessary to allow communication between the BP and the IoT devices.
|
||
ls-type:: annotation
|
||
hl-page:: 9
|
||
hl-color:: green
|
||
id:: 64f71d28-2b91-4440-8485-98e52ac9969b
|
||
- The IoT Application Developer is responsible for providing specific information about each IoT device involved in the BP, such as the technical aspects required for deployment in the physical world.
|
||
ls-type:: annotation
|
||
hl-page:: 9
|
||
hl-color:: green
|
||
id:: 64f71d44-f1df-4711-9bfb-5bb8d64e53e8
|
||
- This model represents the technological configuration of the solution in charge and is saved in the Config Server, a microservice dedicated to this purpose
|
||
ls-type:: annotation
|
||
hl-page:: 9
|
||
hl-color:: green
|
||
id:: 64f71d5d-c175-4d67-bc8c-1e31cebc0ff7
|
||
- Step 5 - IoT Application Templates
|
||
ls-type:: annotation
|
||
hl-page:: 9
|
||
hl-color:: green
|
||
id:: 64f71d6c-d227-4b0f-9f08-520f8ba5a9a9
|
||
- an extended version of the feature model structure proposed by the FloWare approach
|
||
ls-type:: annotation
|
||
hl-page:: 8
|
||
hl-color:: yellow
|
||
id:: 64f71d86-c47a-4763-9903-774cbf464a04
|
||
hl-stamp:: 1693916552043
|
||
- oT Domain Knowledge is derived, focusing on the available IoT systems and devices relevant to the specific IoT solution
|
||
ls-type:: annotation
|
||
hl-page:: 8
|
||
hl-color:: blue
|
||
id:: 64f71dda-d699-4155-8051-5b43eda95889
|
||
hl-stamp:: 1693916636326
|
||
- o achieve this, a software platform is required to convert the raw data collected from devices into actionable high-level information.
|
||
ls-type:: annotation
|
||
hl-page:: 10
|
||
hl-color:: blue
|
||
id:: 64f71e51-d5c3-4da7-ab28-c728db7d24e9
|
||
- hese templates serve as a base for processing data generated by IoT devices and assist the IoT Application Developer in modelling and managing those high-level events previously defined in the IoT-enhanced BP. Whenever an event occurs, the high-level event result is sent to the BPMN engine, which triggers the starting or continuation of the IoT-enhanced BP executio
|
||
ls-type:: annotation
|
||
hl-page:: 10
|
||
hl-color:: yellow
|
||
id:: 64f71ed4-d469-48c4-94b7-c0eafa1d8d27
|
||
hl-stamp:: 1693916886284
|
||
- smart canteen scenario
|
||
ls-type:: annotation
|
||
hl-page:: 10
|
||
hl-color:: yellow
|
||
id:: 64f71f6c-117f-4c90-b5c9-2fd18e7f6248
|
||
- digitisation
|
||
ls-type:: annotation
|
||
hl-page:: 10
|
||
hl-color:: red
|
||
id:: 650091ff-b534-46ed-98b7-7ae157ae66a0
|
||
- [:span]
|
||
ls-type:: annotation
|
||
hl-page:: 8
|
||
hl-color:: green
|
||
id:: 65042c3d-8795-4c43-a641-f7ad6aec9fc1
|
||
hl-type:: area
|
||
hl-stamp:: 1694772283719
|
||
- We have described this necessity in detail in the FloWare approach [13], discussing how an organisation specialising in a specific IoT domain needs to categorise the overall IoT software and hardware solutions offered. We synthesised this concept with the term crystallised IoT knowledge to indicate the possibility of representing the entire experience and awareness that a given enterprise acquired in a specific IoT application context. This knowledge can then be used to satisfy each customer’s necessities specifically. In FloWare [13], feature models have been selected in order to represent such knowledge
|
||
ls-type:: annotation
|
||
hl-page:: 11
|
||
hl-color:: yellow
|
||
id:: 65042cc8-e56e-4ecf-8b32-45c2e52a6d41
|
||
- Feature Model Structure
|
||
ls-type:: annotation
|
||
hl-page:: 11
|
||
hl-color:: green
|
||
id:: 650430b9-64ac-40bf-b8d1-7be44b3fca1e
|
||
- IoT-Lite3 ontology
|
||
ls-type:: annotation
|
||
hl-page:: 11
|
||
hl-color:: green
|
||
id:: 650430e7-dee7-4807-82c8-d8cd1c4ac42e
|
||
- In the FloBP approach, we extended this structure, as reported in Figure2, providing detailed information regarding IoT devices and their operations
|
||
ls-type:: annotation
|
||
hl-page:: 11
|
||
hl-color:: green
|
||
id:: 65043200-c7e9-41e3-92a4-51d4504376fa
|
||
- xamples of such protocols include MQTT, Bluetooth, CoAP, HTTP, LoRa, or ZigBee.
|
||
ls-type:: annotation
|
||
hl-page:: 12
|
||
hl-color:: green
|
||
id:: 65043252-124a-4b61-a648-2ebc65106f8c
|
||
- eneration of artefacts
|
||
ls-type:: annotation
|
||
hl-page:: 12
|
||
hl-color:: yellow
|
||
id:: 6504326b-d8bd-49a4-a5b4-7e12c75c3366
|
||
- BPMN editor to allow BP modelling activities with IoT-related modelling elements. In such a way, the knowledge of IoT experts is transferred to be used by BP experts.
|
||
ls-type:: annotation
|
||
hl-page:: 14
|
||
hl-color:: yellow
|
||
id:: 65043335-3c12-46b3-88cc-8354e16d4c8a
|
||
hl-stamp:: 1694774079886
|
||
- Valderas, P., Torres, V., Serral, E.: Modelling and executing iot-enhanced business processes through BPMN and microservices. J. Syst. Softw. 184,111139 (2022)
|
||
ls-type:: annotation
|
||
hl-page:: 43
|
||
hl-color:: yellow
|
||
id:: 650433ca-60d9-4a6a-a749-7fd1d0f7fa59
|
||
hl-stamp:: 1694775180501
|
||
- Corradini, F., Fedeli, A., Fornari, F., Polini, A., Re, B.: Floware: a modeldriven approach fostering reuse and customisation in iot applications modelling and development. Software and Systems Modeling, 1–28 (2022
|
||
ls-type:: annotation
|
||
hl-page:: 43
|
||
hl-color:: yellow
|
||
id:: 650433d8-e596-4433-9f4e-93eb478b8308
|
||
- IoT devices and their functionalities have been modelled, we need to describe how they participate in the processes of an organisation
|
||
ls-type:: annotation
|
||
hl-page:: 15
|
||
hl-color:: green
|
||
id:: 650436e0-97d9-475e-8453-2bf65896ba72
|
||
hl-stamp:: 1694775010940
|
||
- On-demand Interaction
|
||
ls-type:: annotation
|
||
hl-page:: 15
|
||
hl-color:: green
|
||
id:: 65043767-2719-4b14-a0d7-e31a496de9c2
|
||
- Autonomous Interaction
|
||
ls-type:: annotation
|
||
hl-page:: 15
|
||
hl-color:: green
|
||
id:: 6504376b-197a-4f80-bb7c-44a3f3c065e0
|
||
- these guidelines, providing compatibility and interoperability.
|
||
ls-type:: annotation
|
||
hl-page:: 16
|
||
hl-color:: yellow
|
||
id:: 650437ce-03bf-4a46-b57d-46cb06364725
|
||
- Fig. 6
|
||
ls-type:: annotation
|
||
hl-page:: 19
|
||
hl-color:: green
|
||
id:: 6504387b-efeb-4bce-bf91-5393ffc979d2
|
||
hl-stamp:: 1694775421931
|
||
- Feature model representing the Smart Canteen IoT Domain
|
||
ls-type:: annotation
|
||
hl-page:: 13
|
||
hl-color:: green
|
||
id:: 650438b8-3c2b-42e6-be56-cd144ef284de
|
||
- that IoT devices typically lack the computing capabilities to generate high-level events directly.
|
||
ls-type:: annotation
|
||
hl-page:: 20
|
||
hl-color:: green
|
||
id:: 6504392e-3eb0-40e3-89f2-9ad09c36db5b
|
||
- FloWare Platform. This platform leverages Node-RED flows, which are responsible for interacting with IoT devices and generating the high-level events required by the BP at runtime. This approach is further explained in detail in Section 5 of the paper
|
||
ls-type:: annotation
|
||
hl-page:: 20
|
||
hl-color:: yellow
|
||
id:: 6504395a-2131-44de-aa63-9fa3c09532b7
|
||
hl-stamp:: 1694775643598
|
||
- hey are deployed into a BPMN Engine microservice that executes them
|
||
ls-type:: annotation
|
||
hl-page:: 25
|
||
hl-color:: green
|
||
id:: 65043c0c-0ca1-455f-b697-1dbc35c253a6
|
||
hl-stamp:: 1694776334504
|
||
- It is feasible to execute IoT-enhanced BPs modelled with BPMN and Feature Models with the proposed architectural solution
|
||
ls-type:: annotation
|
||
hl-page:: 25
|
||
hl-color:: yellow
|
||
id:: 65043c3e-a192-4363-82ba-21a99f8972ea
|
||
hl-stamp:: 1694776384249
|
||
- oT module implemented in Java that oversees the
|
||
ls-type:: annotation
|
||
hl-page:: 25
|
||
hl-color:: green
|
||
id:: 65044dc1-a52e-4c1e-8d3e-04a967cc0cc8
|
||
hl-stamp:: 1694780870170
|
||
- execution of IoT device operations
|
||
ls-type:: annotation
|
||
hl-page:: 26
|
||
hl-color:: green
|
||
id:: 65044dd6-1aa1-4b98-9605-e9a9b39926bf
|
||
- Microservice architecture implemented as a proof of concep
|
||
ls-type:: annotation
|
||
hl-page:: 26
|
||
hl-color:: yellow
|
||
id:: 65044df4-4b29-4faa-b466-10d13b289140
|
||
hl-stamp:: 1694780924118
|
||
- correct performance
|
||
ls-type:: annotation
|
||
hl-page:: 26
|
||
hl-color:: yellow
|
||
id:: 65044e75-d981-4fd2-8240-a1712a7327d1
|
||
hl-stamp:: 1694781051276
|
||
- According to the generated logs, we could conclude that the realisation of the proposed architecture successfully executed the motivating examples
|
||
ls-type:: annotation
|
||
hl-page:: 28
|
||
hl-color:: green
|
||
id:: 65044ed9-152e-4354-951c-d4b8014b5874
|
||
hl-stamp:: 1694781148682
|
||
- IoT Modelling Expert
|
||
ls-type:: annotation
|
||
hl-page:: 28
|
||
hl-color:: green
|
||
id:: 650450cc-3b33-4e99-b770-4f2cff7fccff
|
||
- he proposed FloBP approach and the supporting infrastructure allows an effective collaboration to construct and deploy an IoT-enhanced BP, the flow of coordinated tasks, the IoT devices participating in the BP, and the interactions that the process must have with IoT devices.
|
||
ls-type:: annotation
|
||
hl-page:: 28
|
||
hl-color:: green
|
||
id:: 65045114-e23a-4d97-9776-1a33bcb6ba08
|
||
- Runeson, P., H¨ost, M.: Guidelines for conducting and reporting case study research in software engineering. Empir. Softw. Eng. 14(2), 131–164(2009
|
||
ls-type:: annotation
|
||
hl-page:: 43
|
||
hl-color:: green
|
||
id:: 6504517f-4d23-4d6d-9a71-cd8b0da1d5fc
|
||
- 0 subjects participated in the experiment, plus the authors that played the role of IoT Modelling Experts.
|
||
ls-type:: annotation
|
||
hl-page:: 28
|
||
hl-color:: green
|
||
id:: 65045259-3212-425b-a2d9-f33a4be404ba
|
||
- 0 participants between 28 and 54 years old
|
||
ls-type:: annotation
|
||
hl-page:: 29
|
||
hl-color:: green
|
||
id:: 65045270-a26b-42e9-a4ee-215d643c61a2
|
||
- 10 participants between 25 and 36 years old
|
||
ls-type:: annotation
|
||
hl-page:: 29
|
||
hl-color:: green
|
||
id:: 6504527c-4771-4cbb-9694-47f609976320
|
||
- hese sessions were also used to reinforce some basic notions we consider opportune from the analysis of the questionnaire results
|
||
ls-type:: annotation
|
||
hl-page:: 29
|
||
hl-color:: green
|
||
id:: 650452a7-7aa0-4988-a528-466900808e71
|
||
- usability requirements are (1) effectiveness, (2) efficiency, and (3) user acceptance.
|
||
ls-type:: annotation
|
||
hl-page:: 29
|
||
hl-color:: green
|
||
id:: 6504533c-3646-4983-9b24-bafdbfd2393f
|
||
- a predefined master result
|
||
ls-type:: annotation
|
||
hl-page:: 29
|
||
hl-color:: yellow
|
||
id:: 65045355-96b4-46dd-8749-2f9e88dfbc2f
|
||
hl-stamp:: 1694782294888
|
||
- time neede
|
||
ls-type:: annotation
|
||
hl-page:: 29
|
||
hl-color:: green
|
||
id:: 6504537f-42c6-4c42-b270-f3eb43bdae12
|
||
hl-stamp:: 1694782337807
|
||
- a NASA-TLX questionnaire
|
||
ls-type:: annotation
|
||
hl-page:: 29
|
||
hl-color:: green
|
||
id:: 6504538b-d7c1-48da-a82e-bc3724febdf0
|
||
- Hart, S.G., Staveland, L.E.: Development of NASA-TLX (Task Load Index): Results of Empirical and Theoretical Research 52, 139–183 (1988)
|
||
ls-type:: annotation
|
||
hl-page:: 45
|
||
hl-color:: green
|
||
id:: 650453ac-52b8-4280-8dae-5b1aa88be24f
|
||
- A demographic questionnaire
|
||
ls-type:: annotation
|
||
hl-page:: 29
|
||
hl-color:: green
|
||
id:: 65045457-f361-4919-bc5a-96a4708cc102
|
||
- Work description
|
||
ls-type:: annotation
|
||
hl-page:: 29
|
||
hl-color:: green
|
||
id:: 6504545b-048f-43b9-998e-f29a52f08c22
|
||
- A NASA-TLX questionnaire
|
||
ls-type:: annotation
|
||
hl-page:: 30
|
||
hl-color:: green
|
||
id:: 65045463-ae35-46e5-aeca-ad31f1cd765e
|
||
- . In both workshops, during the first session, participants were asked to complete a demographic questionnaire to capture their backgrounds
|
||
ls-type:: annotation
|
||
hl-page:: 30
|
||
hl-color:: green
|
||
id:: 650454f3-9e44-4b2f-9d8d-36340ec0daf8
|
||
- The objective of this training part was to provide participants with an overview of the whole process, i.e., which artefacts are produced and consumed along the process and who is responsible for their creation, edition/configuration, and deployment
|
||
ls-type:: annotation
|
||
hl-page:: 30
|
||
hl-color:: green
|
||
id:: 65045509-49ab-4dc9-bd4d-22f47c3fc6c9
|
||
- hus, we can consider that our MDE approach is effective enough to support the design and execution of IoT-enhanced BPs
|
||
ls-type:: annotation
|
||
hl-page:: 31
|
||
hl-color:: blue
|
||
id:: 65045579-7457-43c5-9356-b1a1fa985b0c
|
||
hl-stamp:: 1694782843419
|
||
- The results obtained in this experiment allow us to accept the proposed hypothesis and conclude that the presented model-driven approach allows an effective collaborative development to create IoT-enhanced Business Processes in an interdisciplinary way.
|
||
ls-type:: annotation
|
||
hl-page:: 33
|
||
hl-color:: blue
|
||
id:: 650455ba-b6c0-4e00-bbdc-95ebccc3d1e3
|
||
- However, during the experiment, we were also able to evaluate that the proposed development environment worked fine during the collaborative development.
|
||
ls-type:: annotation
|
||
hl-page:: 34
|
||
hl-color:: blue
|
||
id:: 650455ef-7554-4e7b-883a-a80555aa979c
|
||
- . The web tool was able to import the feature model with the abstract descriptions of IoT devices that were created with the customised FloWare platform and generate a preliminary feature selection based on the modelled process
|
||
ls-type:: annotation
|
||
hl-page:: 34
|
||
hl-color:: blue
|
||
id:: 65045601-99b4-4b24-bad3-38765200df0f
|
||
- This feature selection was loaded by the customised FloWare platform in order to be completed with the corresponding IoT device configuration. In the same way, the web tool was able to send the high-level events defined in the process to the customised FloWare platform in order to be supported by Node-RED flows.
|
||
ls-type:: annotation
|
||
hl-page:: 34
|
||
hl-color:: blue
|
||
id:: 65045611-c6fb-44ec-857d-8151bf678377
|
||
- o reduce this problem, each solution was evaluated twice
|
||
ls-type:: annotation
|
||
hl-page:: 35
|
||
hl-color:: green
|
||
id:: 650456ce-7f77-4938-b90b-b45a7ccbd586
|
||
hl-stamp:: 1694783185271
|
||
- IoT-enhanced Business Processes
|
||
ls-type:: annotation
|
||
hl-page:: 35
|
||
hl-color:: green
|
||
id:: 65045707-5d7b-4273-909f-08a54f0f2dda
|
||
- BPMN Metamodel Extensions
|
||
ls-type:: annotation
|
||
hl-page:: 35
|
||
hl-color:: green
|
||
id:: 65045720-3d5f-49f7-9965-2c215ec81665
|
||
- model requirements imposed by IoT systems and devices
|
||
ls-type:: annotation
|
||
hl-page:: 35
|
||
hl-color:: green
|
||
id:: 6504572a-e780-4ad8-b56a-2c00698aac13
|
||
- BPMN
|
||
ls-type:: annotation
|
||
hl-page:: 35
|
||
hl-color:: green
|
||
id:: 6504578c-d886-47b3-9ed8-db5756a92d80 |