Cross-cutting

Cross-cutting is an editing technique most often used in films to establish action occurring at the same time in two different locations. In a cross-cut, the camera will cut away from one action to another action, which can suggest the simultaneity of these two actions but this is not always the case.

Suspense may be added by cross-cutting. It is built through the expectations that it creates and in the hopes that it will be explained with time. Cross-cutting also forms parallels; it illustrates a narrative action that happens in several places at approximately the same time. For instance, in D.W. Griffith's A Corner in Wheat (1909), the film cross-cuts between the activities of rich businessmen and poor people waiting in line for bread. This creates a sharp dichotomy between the two actions, and encourages the viewer to compare the two shots. Often, this contrast is used for strong emotional effect, and frequently at the climax of a film. The rhythm of, or length of time between, cross-cuts can also set the rhythm of a scene. Increasing the rapidity between two different actions may add tension to a scene, much in the same manner of using short, declarative sentences in a work of literature.

Cross-cutting concern

In aspect-oriented software development, cross-cutting concerns are aspects of a program that affect other concerns. These concerns often cannot be cleanly decomposed from the rest of the system in both the design and implementation, and can result in either scattering (code duplication), tangling (significant dependencies between systems), or both.

For instance, if writing an application for handling medical records, the indexing of such records is a core concern, while logging a history of changes to the record database or user database, or an authentication system, would be cross-cutting concerns since they interact with more parts of the program.

Background

Cross-cutting concerns are parts of a program that rely on or must affect many other parts of the system. They form the basis for the development of aspects. Such cross-cutting concerns do not fit cleanly into object-oriented programming or procedural programming.

Cross-cutting concerns can be directly responsible for tangling, or system inter-dependencies, within a program. Because procedural and functional language constructs consist entirely of procedure calling, there is no semantic through which two goals (the capability to be implemented and the related cross-cutting concern) can be addressed simultaneously. As a result, the code addressing the cross-cutting concern must be scattered, or duplicated, across the various related locations, resulting in a loss of modularity.