SIP-008 — Information Boundary Constructs

Go to Annex C: Requirements

The architectural Model SHALL define boundary constructs governing the ingress, transformation, and egress of structured information.

Structured information may cross architectural, organizational, jurisdictional, trust, or security boundaries. Each crossing may require validation, transformation, filtering, authorization, recording, or other governed processing.

Explicit boundary constructs allow the Reference Architecture to define the responsibilities and constraints associated with a boundary crossing. They also distinguish governed boundary behavior from the internal implementation of participating architectural elements.

The Submission satisfies this requirement when the architectural Model:

1. Defines an identifiable construct for an information boundary
2. Associates applicable attachment points and information flows with the boundary
3. Represents the conditions governing information ingress
4. Represents transformations applied at or because of the boundary crossing
5. Represents the conditions governing information egress
6. Identifies applicable Governance, security, and information-handling constraints
7. Supports Traceability from a boundary crossing to the applied constraints and transformations
8. Defines the boundary independently of a required implementation technology

SIP-007 — Structured Information Attachment Points defines where information enters or exits an architectural element. SIP-008 defines the governed architectural boundary through which the information passes.

A boundary construct does not require every boundary to perform a transformation. It must support representation of a transformation when one applies.