fxdemo:07-part:12-architectural-principles:12-2-non-functional-assurance:start

Go up to Architectural Principles

Non-Functional Assurance is the market condition in which a participant or Node demonstrates that it satisfies the Non-Functional Characteristics that apply to a governed function, governed work assignment, Qualification Profile, policy obligation, evidence obligation, jurisdictional constraint, residency constraint, sovereignty constraint, and market integrity rule.

Non-Functional Assurance establishes that work assignment depends on recognised non-functional capability, measured Performance, Reliability, Maintainability, Securability, Manageability, Usability, Interoperability, Elasticity, evidence production, and continued conformity with applicable qualification requirements.

A participant does not receive governed work merely by asserting non-functional capability. A Node does not receive governed work merely because it connects to the technical environment or advertises a capability. The market recognises non-functional assurance through Qualification Evidence, Monitoring Evidence, Audit Evidence, Policy Evidence, and Selection Criteria that support the assignment.

Non-Functional Assurance protects Buyers, Integrators, Regulators, Auditors, Governance Bodies, Qualified Service Providers, and Qualified Nodes by preventing participants or Nodes with inadequate, expired, unverified, degraded, suspended, or non-conforming non-functional capability from receiving governed work.

The Governed Node Service Market SHALL assign governed work only to participants and Nodes that satisfy the Non-Functional Characteristics and the assurance evidence requirements applicable to the governed function.

A Node connects to the market and advertises semantic validation capability. The market does not assign FX validation work to the Node until the applicable Qualification Profile, Qualification Evidence, Non-Functional Characteristics, monitoring evidence, policy constraints, evidence obligations, jurisdictional constraints, and market rules recognise the Node as eligible for that governed function.

  • fxdemo/07-part/12-architectural-principles/12-2-non-functional-assurance/start.txt
  • Last modified: 2026/07/11 11:15
  • by nick_dido