This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| dido:99_annexes:annex-b-terms-and-definitions:a:attachment_point [2026/07/11 11:14] – ↷ Links adapted because of a move operation nick_dido | dido:99_annexes:annex-b-terms-and-definitions:a:attachment_point [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| Attachment points support architectural traceability by identifying where information exchange, validation, interpretation, transformation, release, or receipt occurs. | 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 realises an attachment point through a selected technology. The attachment point defines the architectural boundary and responsibility independently of the implementation mechanism. | 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 ===== | ===== Definition ===== |
| ===== Note ===== | ===== Note ===== |
| |
| An attachment point provides a stable architectural location for analysing information flow, interface responsibility, and implementation mapping. | An attachment point provides a stable architectural location for analyzing information flow, interface responsibility, and implementation mapping. |
| |
| ===== Example ===== | ===== Example ===== |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane]] service has an attachment point where a [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structured_information_artifact|structured information artefact]] enters the service for validation and another attachment point where the validated artefact exits the service for downstream processing. | A [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane]] service has an attachment point where a [[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. |
| |
| ---- | ---- |