... | ... | @@ -60,5 +60,12 @@ For each experimental unit, the table reports the ph employed to carry out the e |
|
|
|
|
|
For each experimental unit, the table reports the ph employed to carry out the experimental tasks together with the total amounts of ph. The general-purpose enterprise-oriented approach took more than two times longer than the **CHOReVOLUTION** approach. In this phase a sub-choreography has been modified by adding a choreography task, whereas the other choreographies and sub-choreographies remained the same. This allowed all the three experimental units to leverage on code reuse. It is worth to note that time saving obtained in this phase is due to the high support to automation provided by the **CHOReVOLUTION** approach with respect to the other approach that require a manual implementation although reusing some code.
|
|
|
|
|
|
**Overall experiment results**
|
|
|
|
|
|
| **Experimental units** | **Implementation (ph)** | **Maintenance (ph)** | **Evolution (ph)** | **Time saving (ph)** |
|
|
|
| :--------: | :--------: | :--------: | :--------: | :--------: |
|
|
|
| 1 | 120 | 8,5 | 16 | - |
|
|
|
| 2 | 240 **(120 saved)** | 64 **(55,5 saved)** | 40 **(24 saved)** | **199,5** |
|
|
|
|
|
|
The table summarizes the results of the experiment on the UTC use case by distinguishing the implementation, maintenance, and evolution phases. In particular, the experimental units 2 highlights in bold the ph saved by using the **CHOReVOLUTION** approach.
|
|
|
It is worth to note that the **CHOReVOLUTION** approach results in a decrease of the required development time in all the considered phases. 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. |
|
|
\ No newline at end of file |