claim

active

claim: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

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.

Prescriptive claim for the STANDARD APPLICATIONS pattern.

Source paper

extracted_from

Garden of Applications

(1998) · Jacobs, Nicholas

Neighborhood — ranked by edge-count

Frameworks (2)

framework

Standard Applications
supports
Pattern defining standard structure for application modules that the backplane can launch and manage uniformly.
Bootstrap Applications
supports
Special class of standard applications automatically loaded during backplane initialization to provide fundamental services.

Related by similarity (8)

cosine ≥ 0.65 · no typed edge

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.890
Prescriptive claim for the BACKPLANE pattern's responsibilities and boundaries.
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.862
Prescriptive claim summarizing the GARDEN OF APPLICATIONS pattern.
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.860
Prescriptive claim for the INTERFACE REPOSITORY pattern.
The interface repository allows functionality to be added without directly altering the backplane.claim0.859
Claim that the interface repository provides a non-invasive extension mechanism.
Interface Repository reduces coupling between applications and between applications and framework.claim0.828
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.quote0.814
Load-bearing description of the backplane's runtime role and initialization responsibility.
Standard applications help a new developer to come up to speed more quickly because other developers on the project can simply say, 'Oh, yeah. Extend STANDARD APPLICATION, update this configuration file and you'll be all set to run and test your application.'claim0.788
Claim about the onboarding benefit of the Standard Application construct.
Viewing the system as a collection of applications is a valid and useful approach.claim0.788
Foundational assumption for the pattern language.