public:99_annexes:annex-b-terms-and-definitions:a:application_independence

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:a:application_independence [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:a:application_independence [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Application Independence ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Application Independence is a property of a subject whose governing intent, [[public:99_annexes:annex-b-terms-and-definitions:s:semantic|semantics]], criteria, and required outcomes do not depend on the design, implementation, or selection of a particular [[public:99_annexes:annex-b-terms-and-definitions:a:application|Application]].
 +
 +The subject may include:
 +
 +  * A specification
 +  * A model
 +  * A test
 +  * A [[public:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
 +  * An evaluation method
 +  * A data exchange
 +  * An interface
 +  * A policy
 +  * A procedure
 +  * A requirement
 +
 +Application Independence separates the governing characteristics of the subject from Application-specific design and implementation choices.
 +
 +Application-specific mechanisms remain consistent with Application Independence when they preserve the governing:
 +
 +  * Intent
 +  * Semantics
 +  * Evaluated characteristics
 +  * Evaluation method
 +  * [[public:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]
 +  * Required outcomes
 +  * [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] obligations
 +  * [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
 +
 +Such mechanisms include:
 +
 +  * Adapters
 +  * Mappings
 +  * Interface bindings
 +  * Data transformations
 +  * Test fixtures
 +  * Execution procedures
 +  * [[public:99_annexes:annex-b-terms-and-definitions:c:configuration|Configurations]]
 +
 +A change to a governing characteristic constitutes a change to the subject rather than an Application-specific adaptation.
 +
 +===== Definition =====
 +
 +//property of a subject whose governing intent, semantics, criteria, and required outcomes do not depend on the design, implementation, or selection of a particular [[public:99_annexes:annex-b-terms-and-definitions:a:application|Application]]//
 +
 +===== Source =====
 +
 +DIDO-TE Mission Objective MO-006: Application-Independent and Infrastructure-Independent Testing
 +
 +DIDO-TE Mission Objective MO-006a: Application-Independent Testing
 +
 +DIDO Reference Implementation Conceptual Model
 +
 +===== Note =====
 +
 +Application Independence does not mean the absence of an Application.
 +
 +Application Independence does not require identical execution across Applications. Different Applications may require different adapters, mappings, interfaces, Configurations, or execution procedures.
 +
 +An adaptation preserves Application Independence when the adaptation does not change the governing intent, semantics, criteria, required outcomes, Evidence obligations, or Traceability.
 +
 +Application Independence differs from [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_independence|Infrastructure Independence]]:
 +
 +  * Application Independence concerns separation from a particular Application
 +  * Infrastructure Independence concerns separation from particular Infrastructure
 +
 +A subject may possess Application Independence without possessing Infrastructure Independence, or Infrastructure Independence without possessing Application Independence.
 +
 +===== Example =====
 +
 +DIDO-TE applies one Test Definition and one set of Acceptance Criteria to two sanctions-screening Applications.
 +
 +Each Application uses a different interface adapter. The adapters map the common test inputs to the Application-specific interfaces and map the resulting outputs back to the common result format.
 +
 +The adapters preserve the testing intent, semantics, evaluated characteristics, Acceptance Criteria, Evidence obligations, and required outcomes. The test therefore possesses Application Independence.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>