The backplane is the first component of the system to be loaded at runtime. One of its primary roles is to bootstrap the user's environment and then subsequently provide a standard way for other applications to be loaded.

Entities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.

• Create a backplane component in the system. This component should be primarily concerned with providing facilities which address the runtime architecture of the system. These include initialization and termination of applications and high level window management. The backplane is also an ideal place to put the interface repository. Avoid placing application or domain-specific functionality into the backplane and instead use an interface repository to support this activity.claim0.876
  Prescriptive claim for the BACKPLANE pattern's responsibilities and boundaries.
• Make the components with which the user interacts standard applications which provide standard facilities and interfaces. These applications have a standard interface by which the backplane can manage their lifecycle methods. These applications can be dynamically loaded to help reduce the overall footprint of the system. Avoid having applications communicate directly with one another – use the interface repository for this purpose.claim0.814
  Prescriptive claim for the STANDARD APPLICATIONS pattern.
• The interface repository allows functionality to be added without directly altering the backplane.claim0.803
  Claim that the interface repository provides a non-invasive extension mechanism.
• Create an interface repository for the system and let the backplane serve as the central access point to this list of publicly accessible interfaces which is indexed by a unique name.claim0.796
  Prescriptive claim for the INTERFACE REPOSITORY pattern.
• Create a framework onto which the application level functions can easily be deployed. This is done by splitting the entire application into two broad categories, the backplane and standard applications. Make sure to provide facilities, such as an interface repository, to reduce coupling between applications.claim0.775
  Prescriptive claim summarizing the GARDEN OF APPLICATIONS pattern.
• Backplaneconcept0.755
  Core meta-construct and stable component that manages application lifecycle, initialization, and provides standard interfaces for system development.
• BACKPLANE (2)framework0.750
• An explicit focus on runtime architecture leads to a more dynamic and changeable system.claim0.734
  Core design philosophy of the paper.