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

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:attachment_point [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:a:attachment_point [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Attachment Point ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +An attachment point identifies a defined boundary location through which [[private:fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structured_information_artifact|structured information]] enters or exits an [[private:fxdemo:dido_99_annexes:annex-b-terms-and-definitions:a:architectural_element|architectural element]].
 +
 +Attachment points support architectural traceability by identifying where information exchange, validation, interpretation, transformation, release, or receipt occurs.
 +
 +An attachment point differs from an implementation interface. An implementation interface realizes an attachment point through a selected technology. The attachment point defines the architectural boundary and responsibility independently of the implementation mechanism.
 +
 +===== Definition =====
 +
 +//defined boundary location through which structured information enters or exits an [[private:fxdemo:dido_99_annexes:annex-b-terms-and-definitions:a:architectural_element|architectural element]]//
 +
 +===== Source =====
 +
 +Structured Information Processing [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]]
 +
 +===== Note =====
 +
 +An attachment point provides a stable architectural location for analyzing information flow, interface responsibility, and implementation mapping.
 +
 +===== Example =====
 +
 +A [[public:99_annexes:annex-b-terms-and-definitions:d:data_plane]] service has an attachment point where a [[private:fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structured_information_artifact|structured information artifact]] enters the service for validation and another attachment point where the validated artifact exits the service for downstream processing.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>