Explore chapters and articles related to this topic
Reflections
Published in Gamel O. Wiredu, Global Software Engineering, 2019
The reality of village dependencies generated by electrical ICT media must become a conscious and deliberate design by GSE organizations. This suggestion is sensible in the light of the proposition that village dependencies have technological origins. Moreover, village dependencies are replicates of collocated software engineering dependencies. Their technological origins and virtual logic together have direct implications for design of GSE teams. Recall from Chapter 4 that village dependencies have a virtual logic which aligns with village which is the solution, as well as a rational logic which aligns with global which is the problem. Therefore, deliberate and conscious design of village dependencies provide GSE organizations with control over problem and solution dimensions of coordination. They should use ICTs to make village dependencies both a problem and solution design so that they can manage the dependencies more effectively.
Sources for Emergence and Development of System of Systems
Published in Larry B. Rainey, Mo Jamshidi, Engineering Emergence, 2018
Research by Brown, Flowe, and Hamel has demonstrated that increasing program interdependencies is correlated to schedule problems [13]. Their results provide convincing evidence to suggest that, when considering acquisition performance as an indicator of program “fitness,” more interconnected programs are statistically more likely to encounter programmatic problems than their single system counterparts. Another study by the Software Engineering Institute (SEI) attempted to capture and graph program dependencies for major Defense programs [14]. This type of analysis is difficult to capture completely, with so many possible indirect dependencies. The report provides an example of 571 major programs with 1174 documented direct relationships. This results in an average degree of 4.11 dependencies per program. Visually, in Figure 4.1, one notices a majority of the programs (on the edge of the graph) have few links, and fewer in the middle are more connected. This is generally a key characteristic of scale-free graphs.
Modelling the marine transport resilience of Vancouver Island in a Cascadia subduction zone earthquake scenario
Published in Sustainable and Resilient Infrastructure, 2022
Anika M. Bell, David N. Bristow
In GMOR, spatially explicit infrastructure entities (such as a berth or a road section are referred to as entities in this paper) are created that have the capacity to fail and be recovered. Entities can serve as dependencies of other entities referred to here as a dependency network or map. Dependencies are entities upon which another entity depends for its functioning. The dependency network establishes primary entities, upon which a system depends, and then uses the Boolean operators AND, OR, and NOT to list the infrastructure that those primary entities depend on. GMOR uses this scheme to also specify the occurrence of failures of different types (i.e., damage states) and to specify recovery times as dependencies to achieving operational status after failure.
GearWheels: A Software Tool to Support User Experiments on Gesture Input with Wearable Devices
Published in International Journal of Human–Computer Interaction, 2022
Ovidiu-Andrei Schipor, Radu-Daniel Vatavu
S4. IoC-DI refers to the inversion of control (IoC) through dependency injection (DI). In this approach, dependencies are injected into the object rather than created inside the object. This pattern assures a clear separation between the creation of a software object and its use as well as the decoupling between high and low level classes and, thus, assures optimized interaction among the software modules of the same component (design requirements R1 to R3).