... | ... | @@ -33,7 +33,7 @@ The table describes the activities performed within each experimental unit for a |
|
|
|
|
|
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.
|
|
|
|
|
|
**-Hypothesis 2-** We found that the **CHOReVOLUTION** approach provides a meaningful decrease of the time required to maintain the SMT choreography-based system. In the maintenance phase, a different service is selected to play the role of the **Parking** participant, hence leading to a service substitution. The selected service has a different interface with respected to the one required by the choreography specification. In this scenarios, although it is out of the scope of this paper, the **CHOReVOLUTION** approach is able to automatically generate additional software entities called Adapters that handle interfaces mismatches. Thus, the experiment tasks considered in this phase, beyond the coordination logic and the prosumer services, include also the experimental task concerning the adaptation logic. In particular, the **CHOReVOLUTION** approach provides automatic support to the generation of the Adapters, whereas the other approaches require a manual implementation or a manual customization.
|
|
|
**-Hypothesis 2-** We found that the **CHOReVOLUTION** approach provides a meaningful decrease of the time required to maintain the SMT choreography-based system. In the maintenance phase, a different service is selected to play the role of the **Parking** participant, hence leading to a service substitution. The selected service has a different interface with respected to the one required by the choreography specification. In this scenarios, the **CHOReVOLUTION** approach is able to automatically generate additional software entities called Adapters that handle interfaces mismatches. Thus, the experiment tasks considered in this phase, beyond the coordination logic and the prosumer services, include also the experimental task concerning the adaptation logic. In particular, the **CHOReVOLUTION** approach provides automatic support to the generation of the Adapters, whereas the other approaches require a manual implementation or a manual customization.
|
|
|
|
|
|
| **Tasks** | **Experimental unit 1 (ph)** | **Experimental unit 2 (ph)** | **Experimental unit 3 (ph)** |
|
|
|
| :--------: | :--------: | :--------: | :--------: |
|
... | ... | @@ -62,4 +62,4 @@ For each experimental unit, the table reports the ph employed to carry out the e |
|
|
| 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. |
|
|
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 the **CHOReVOLUTION** approach results in a decrease of the required development time in all the considered phases. 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. |