| Both sides previous revision Previous revision Next revision | Previous revision |
| public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-4-flow-and-interface-definition:start [2026/09/12 18:33] – ↷ Page moved from dido:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-4-flow-and-interface-definition:start to public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-4-flow-and-i nick_dido | public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-4-flow-and-interface-definition:start [2026/09/14 18:45] (current) – [Requirements] nick_dido |
|---|
| ====== 6.4.4 Flow and Interface Definition ====== | ====== 6.4.4 Flow and Interface Definition ====== |
| |
| [[dido:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:start|Return to Required Submission Content]] | [[public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:start|Return to Required Submission Content]] |
| |
| Flow and interface definitions govern how structured information moves between architectural elements and how boundary interactions are controlled. | Flow and [[public:99_annexes:annex-b-terms-and-definitions:i:interface|Interface]] definitions govern how structured information moves between architectural elements and how interactions across architectural boundaries are controlled. |
| |
| Architectural descriptions clarify how flows are structured, regulated, and segmented across defined attachment points. | The architectural description explains how information flows are structured, governed, versioned, and segmented across defined attachment points. |
| |
| - Proposals SHALL describe the architectural construct representing the flow of structured information between architectural elements. | ===== Requirements ===== |
| - Proposals SHALL describe the attachment points through which structured information enters and exits architectural elements. | |
| - Proposals SHALL describe the interface contracts governing exchange across attachment points. | ^ Requirement ^ Statement ^ |
| - Proposals SHALL describe the version-controlled interface contracts and the mechanisms governing their evolution. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-051-flow-and-interface-description|SIP-051 — Flow and Interface Description]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-051-flow-and-interface-description#Statement&noheader&nofooter&noeditbtn}} | |
| - Proposals SHALL describe architectural mechanisms that enforce segmentation of information flows based on governance or security constraints. | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-052-interface-contract-evolution|SIP-052 — Interface Contract Evolution]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-052-interface-contract-evolution#Statement&noheader&nofooter&noeditbtn}} | |
| | ===== Required Coverage ===== |
| | |
| | The description required by SIP-051 includes the architectural information governed by the following requirements: |
| | |
| | ^ Requirement ^ Required Architectural Information ^ |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-005-structured-information-flow|SIP-005 — Structured Information Flow]] | Architectural constructs representing the flow of structured information between architectural elements | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-007-structured-information-attachment-points|SIP-007 — Structured Information Attachment Points]] | Attachment points through which structured information enters and exits architectural elements | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-008-information-boundary-constructs|SIP-008 — Information Boundary Constructs]] | Boundary constructs governing ingress, transformation, and egress | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-009-version-controlled-interface-contracts|SIP-009 — Version-Controlled Interface Contracts]] | Version-controlled Interface Contracts governing exchange across applicable attachment points | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-018-information-flow-segmentation|SIP-018 — Information-Flow Segmentation]] | Enforcement of information-flow segmentation based on Governance or security constraints | |
| | | [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-020-governance-constraints-and-interface-contracts|SIP-020 — Governance Constraints and Interface Contracts]] | Separation of Governance constraints from Interface Contracts | |
| | |
| | ===== Notes for Editors ===== |
| | |
| | The links to SIP-051 and SIP-052 provide temporary access to their individual Annex C requirement pages while those records are being created and reviewed. |
| | |
| | After those records are complete, replace each locally maintained Statement with a transclusion of its authoritative Statement. |
| | |
| | SIP-051 governs the required description. The requirements listed under Required Coverage govern the underlying architectural constructs, relationships, and controls. |
| | |
| | SIP-009 requires Interface Contracts to be version controlled and to govern structured information exchange. SIP-052 adds the distinct requirement to define mechanisms governing the controlled evolution of those contracts. |
| | |
| | The Required Coverage table provides a nonnormative summary. The corresponding Annex C requirement records remain authoritative. |
| |
| ---- | ---- |
| © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| </WRAP> | </WRAP> |
| |