The technology of peer-to-peer control has high requirement for coordination control of DG and is still confined to the laboratory; master-slave control has high requirement for communication, demanding not only reliability but also real-time performance, and considerably relies on computer system and communication, and its timeliness needs to be demonstrated [8, 9].
The challenges are not insignificant due to both the scepticism from professionals used to working under conditions that do not consider such aspects, and the requirement of the coordination and commitment of various bodies and institutions to put them into practice.
Another example can be found in the requirement for coordination between national and regional network companies or between network companies and suppliers of electricity.
Site-directed mutagenesis confirmed the requirement of bi-covalent coordination of FAD for enzyme activity; this unique coordination is also correlated to the relatively high redox potential of GOOX-T1 [ 14, 15].
However, the practical deployment of HetNets still needs to face some critical issues and challenges such as the requirement of efficient interference coordination mechanisms, cross-layer dependencies, or stability of backhaul design.
Figures 1, 2, 3 and 4 represent graphically the evolution of the coordination requirements plotting two values: the average number of coordination requirements (i) for the same theam and (ii) for different teams.
The results indicate that for each time interval, the average number of coordination requirements for the same team is higher than the average number of coordination requirements for different teams.
In contrast to our previous work [8, 9] in which the identification of coordination requirements was performed in monthly intervals, in this paper we computed the coordination requirements in four different time-frames: 1-day, 7-day, 15-day, and 30-day intervals.
Table 1 below presents the first set of descriptive statistics considering the average number of coordination requirements per software developer.
Our results suggest that, in some cases, the number of coordination requirements of a given actor might be very large, and that current collaborative software development tools do not provide proper support for such values.
Furthermore, collaborative tools should be able to dynamically adjust the visualization according to the number of coordination requirements, teams and locations involved.
