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].
These difficulties lead to higher requirements for coordination.
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.
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.
Although direct biochemical studies of existing metalloproteins have begun to answer some of these questions, it is difficult to imagine a situation in which a native enzyme can be mutated to determine the baseline requirements of the first coordination sphere in the absence of most of the surrounding protein matrix (the metal site would likely not fold and/or bind metal).
A contingency model is advanced that examines sources of requirements for organizational coordination and control as they affect the extent of integration in an accounting information system.
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.
For the majority of primary care physicians the time required for accounting, documentation of clinical information or for legal requirements or coordination of patient care is very problematic [ 5, 6].
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.
