... | ... | @@ -19,7 +19,7 @@ The figure illustrates the Traffic Segment Information Collection sub-choreograp |
|
|
The technologies of the experimental units 2 were selected considering that the industrial partner was already familiar and skilled with them.
|
|
|
As in the other use case, opting for an alternative would have required a training effort that could not be afforded by the partner because of budget constraints. Even if it had been possible to opt for an alternative, it would have been not easy to reach the same level of expertise, hence possibly compromising the validity of the experiment.
|
|
|
|
|
|
The experiment was conducted by two different development teams. The team involved in the experimental unit 1 was formed by two developers of the **CHOReVOLUTION** project. The other team, involved in the experimental units 2, was formed by one of the above two developers plus another one developer from a different project. The experimental tasks were distributed to the different developers to eliminate the potential bias of person-task links. All developers had equivalent professional skills and familiarity with the concerned technologies.
|
|
|
The experiment was conducted by two different development teams. The team involved in the experimental unit 1 was formed by two developers of the **CHOReVOLUTION** project. The other team, involved in the experimental units 2, was formed by the above two developers plus two other developers from a different project. The experimental tasks were distributed to the different developers to eliminate the potential bias of person-task links. All developers had equivalent professional skills and familiarity with the concerned technologies.
|
|
|
|
|
|
**-Hypothesis 1-** We found that the **CHOReVOLUTION** approach significantly decreased the time required to implement the UTC use case.
|
|
|
|
... | ... | @@ -29,3 +29,11 @@ The experiment was conducted by two different development teams. The team involv |
|
|
| Prosumer services | After the choreography modeling phase, the skeleton code of the prosumer services is automatically generated. Thus, developers are required to only fill in the blanks of highlighted and partially ready pieces of code. | The prosumer services are manually implemented. In particular, for each choreography task involving a specific participant, all the logic to manipulate received messages and to build the messages to be sent need to be coded from scratch (without having the skeleton code generated). The developers have to maintain the data and message storage to ensure the messages are well parsed and routed through different distributed flows with no data lost.|
|
|
|
|
|
|
The table describes the activities performed within each experimental unit for accomplishing the experimental tasks. It is worth noticing that the **CHOReVOLUTION** approach provides a high support to automation, instead the other approach requires a manual implementation.
|
|
|
|
|
|
| **Tasks** | **Experimental unit 1 (ph)** | **Experimental unit 2 (ph)** |
|
|
|
| :--------: | :--------: | :--------: |
|
|
|
| Coordination logic | 40 | 200 |
|
|
|
| Prosumer services | 80 | 40 |
|
|
|
| **Total** | **120** | **240 (120 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 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**. |