SIP-007 — Structured Information Attachment Points [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== SIP-007 — Structured Information Attachment Points ======

[[public:00-sip-ra:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]

===== Statement =====

Each architectural element that exchanges structured information SHALL expose explicit attachment points through which that information enters or exits the element.

===== Rationale =====

Explicit attachment points define where an architectural element participates in structured information exchange. They prevent the exchange from remaining implicit within implementation-specific behavior.

Attachment points allow the architectural Model to associate information flows with specific elements, Interfaces, directions, constraints, and responsibilities. They also support composition, analysis, security controls, and Traceability without prescribing a platform-specific communication mechanism.

===== Evaluation Criteria =====

The Submission satisfies this requirement when:

  - Each exchanging architectural element has one or more identifiable attachment points
  - Each attachment point is associated with its architectural element
  - The permitted direction of information movement is defined
  - The structured information accepted or produced at the attachment point is identified or referenced
  - Applicable Interfaces and information flows are associated with the attachment point
  - Constraints governing use of the attachment point can be represented
  - Attachment points remain independent of a required implementation protocol or technology

===== Referenced By =====

{{backlinks>public:00-sip-ra:99-annexes:annex-c-requirements:sip-007-structured-information-attachment-points}}

===== Notes for Editors =====

An attachment point is an architectural abstraction. A platform-specific realization may implement an attachment point using a port, endpoint, topic, queue, function, service, file, database connection, or another mechanism.

[[public:00-sip-ra:99-annexes:annex-c-requirements:sip-005-structured-information-flow|SIP-005 — Structured Information Flow]] defines the flow between architectural elements. SIP-007 identifies where those flows enter or exit an element.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>