... | ... | @@ -38,7 +38,18 @@ 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 unit 2 highlights in brackets the ph saved by using the **CHOReVOLUTION approach**. Specifically, the general-purpose enterprise-oriented approach took two times longer than the **CHOReVOLUTION approach**.
|
|
|
|
|
|
**-Hypothesis 2-** We found that the **CHOReVOLUTION** approach provides a meaningful decrease of the time required to maintain the UTC choreography-based system. In the maintenance phase, the role of the participant **DTS-HERE** is played by the routing service **GraphHopper**, 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 approache require a manual implementation.
|
|
|
**-Hypothesis 2-** We found that the **CHOReVOLUTION** approach provides a meaningful decrease of the time required to maintain the UTC choreography-based system. In the maintenance phase, the role of the participant **DTS-HERE** is played by the routing service **GraphHopper**, 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 approach require a manual implementation.
|
|
|
|
|
|
| **Tasks** | **Experimental unit 1 (ph)** | **Experimental unit 2 (ph)** |
|
|
|
| :--------: | :--------: | :--------: |
|
|
|
| Coordination logic | 0,3 | 20 |
|
|
|
| Prosumer services | 0,2 | 4 |
|
|
|
| Adaptation logic | 8 | 40 |
|
|
|
| **Total** | **8,5** | **64 (55,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. The total amounts for the experimental units 2 highlights in brackets the ph saved by using the **CHOReVOLUTION** approach. The general-purpose enterprise-oriented approach took more than seven times longer than the **CHOReVOLUTION** approach.
|
|
|
|
|
|
**-Hypothesis 3-** We found that the **CHOReVOLUTION** approach significantly reduces the time required to evolve the UTC choreography-based system. In the evolution phase, the choreography task Segment Traffic Light Information between the participants **DTS-SEGMENT-TRAFFIC** and **DTS-TRAFFICLIGHT** is introduced into the the Traffic Area Information Collection sub-choreography. The service selected to play the role of the participant **DTS-TRAFFICLIGHT** has a different interface with respected to the one required by the choreography specification. As in the previous hypothesis, the *CHOReVOLUTION** approach handles this interfaces mismatch through the automatic generation of **CHOReVOLUTION** adapters. Instead, the other approach requires a manual implementation of the adaptation logic. Therefore, the experiment tasks considered in this phase, beyond the coordination logic and the prosumer services, include also the experimental task concerning the adaptation logic.
|
|
|
|
|
|
| **Tasks** | **Experimental unit 1 (ph)** | **Experimental unit 2 (ph)** |
|
|
|
| :--------: | :--------: | :--------: |
|
... | ... | @@ -47,5 +58,4 @@ For each experimental unit, the table reports the ph employed to carry out the e |
|
|
| Adaptation logic | 8 | 40 |
|
|
|
| **Total** | **8,5** | **64 (55,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. The total amounts for the experimental units 2 highlightsin brackets the ph saved by using the **CHOReVOLUTION** approach. The general-purpose enterprise-oriented approach took more than seven times longer than the **CHOReVOLUTION** approach.
|
|
|
|