... | ... | @@ -67,4 +67,4 @@ For each experimental unit, the table reports the ph employed to carry out the e |
|
|
| 2 | 134 **(129 saved)** | 12,5 **(11,8 saved)** | 26,5 **(25 saved)** | **165,8** |
|
|
|
|
|
|
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 |
|
|
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. Furthermore, 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 |