... | ... | @@ -4,4 +4,24 @@ The Smart Mobility and Tourism (SMT) use case has been implemented in cooperatio |
|
|
The figure shows the SMT choreography specification by means of a BPMN2 Choreography Diagram.
|
|
|
The use case starts with the mobile application **STApp** detecting the current position of the user, and asking for which type of point of interest to visit and which type of transport mode to use. From this information, **Tourist Agent** initiates two parallel flows in order to retrieve the information required by the "Electronic Touristic Guide". In particular, the left-most branch retrieves smart mobility information according to the selected transport mode, while the right-most branch gathers touristic information. Finally, the two parallel flows are joined together to produce the data needed for the "Electronic Touristic Guide". Finally, the guide is shown to the user by means of **STApp**.
|
|
|
|
|
|
**Results** |
|
|
\ No newline at end of file |
|
|
**Results**
|
|
|
|
|
|
**Experiment results - Implementation phase**
|
|
|
|
|
|
| **Tasks** | **Experimental unit 1 (ph)** | **Experimental unit 2 (ph)** | **Experimental unit 3 (ph)** |
|
|
|
| :--------: | :--------: | :--------: | :--------: |
|
|
|
| Coordination logic | 3 | 100 | 24 |
|
|
|
| Prosumer services | 3,5 | 6 | 24 |
|
|
|
| **Total** | **6,5** | **106 (99,5 saved)** | **48 (41,5 saved)** |
|
|
|
|
|
|
For each experimental unit, the table reports the ph employed to carry out the experimental tasks together with the total amounts of ph. In particular, the total amounts for the experimental units 2 and 3 highlight in brackets the ph saved by using the **CHOReVOLUTION approach**. Specifically, the general-purpose enterprise-oriented approach took more than fifthteen times longer than the **CHOReVOLUTION approach**, whereas the domain-specific system integration platform took more than six times longer.
|
|
|
|
|
|
**Experiment results**
|
|
|
|
|
|
| **Experimental units** | **Implementation (ph)** | **Maintenance (ph)** | **Evolution (ph)** | **Time saving (ph)** |
|
|
|
| :--------: | :--------: | :--------: | :--------: | :--------: |
|
|
|
| 1 | 6,5 | 1 | 4 | - |
|
|
|
| 2 | 106 **(99,5 saved)** | 11 **(10 saved)** | 30 **(26 saved)** | **135,5** |
|
|
|
| 3 | 48 **(41,5 saved)** | 8 **(7 saved)** | 24 **(20 saved)** | **68,5** |
|
|
|
|
|
|
The table summarizes the results of the experiment on the SMT use case by distinguishing the implementation, maintenance, and evolution phases. In particular, the experimental units 2 and 3 highlight in bold the ph saved by using the **CHOReVOLUTION** approach. Beyond the result concerning the hypothesis 1 discussed before, it is worth to note that also in the maintenance (hypothesis 2) and evolution (hypothesis 3) phases the **CHOReVOLUTION** approach results in a decrease of the required development time. The decrease is more significant in the evolution phase, where the changes affect the choreography specification, than in the maintenance phase, where the changes affected the services involved in the choreography-based system. Moreover, the last column contains the total amount of ph saved for each experimental unit. This result together with the amount of ph saved in each experimental unit reveals that the **CHOReVOLUTION** approach has great potential in developing choreography-based systems and the use case got a full benefit from it. |