6.2.1 In Scope

Return to Scope of Proposals Sought

The following requirements define the architectural capabilities and abstractions that a Submission SHALL address. Unless otherwise stated, each requirement applies to the Submission and the proposed Reference Architecture described by that Submission.

• SIP-001 — Platform-Independent Reference Architecture: The proposed Reference Architecture SHALL be platform independent

• SIP-002 — Formal Platform Independent Model: The Submission SHALL include a formal Platform Independent Model (PIM) of the proposed Reference Architecture

• SIP-003 — Reference Architecture Constituents: The architectural model SHALL define the elements, roles, relationships, and interaction constructs that comprise the Reference Architecture

• SIP-004 — Separation of Architectural Concerns: The architectural model SHALL represent Data, Structure, Semantics, and Interpretation as separable but coordinated architectural concerns

• SIP-005 — Structured Information Flow: The information-flow model SHALL define an architectural construct representing the flow of structured information between architectural elements

• SIP-006 — Ordered Modular Processing Flows: The processing-flow model SHALL define ordered processing flows composed of modular components connected through governed interaction constructs

• SIP-007 — Structured Information Attachment Points: Each architectural element that exchanges structured information SHALL expose explicit attachment points through which that information enters or exits the element

• SIP-008 — Information Boundary Constructs: The architectural model SHALL define boundary constructs governing the ingress, transformation, and egress of structured information

• SIP-009 — Version-Controlled Interface Contracts: Each Interface Contract SHALL be version controlled and SHALL govern the exchange of structured information across applicable attachment points

• SIP-010 — Structural Artifact Lifecycle Governance: The Governance model SHALL define lifecycle controls for structural Artifacts

• SIP-011 — Semantic Artifact Lifecycle Governance: The Governance model SHALL define lifecycle controls for semantic Artifacts

• SIP-012 — Interpretive Artifact Lifecycle Governance: The Governance model SHALL define lifecycle controls for interpretive Artifacts

• SIP-013 — Reproducible Interpretation: The Interpretation model SHALL support reproduction of an Interpretation using identified, version-controlled conditions

• SIP-014 — Jurisdictional Control of Structural Definitions: The Governance model SHALL allow each Jurisdiction to retain Authority over the structural definitions applicable within its operational boundary

• SIP-015 — Jurisdictional Control of Semantic Definitions: The Governance model SHALL allow each Jurisdiction to retain Authority over the semantic definitions applicable within its operational boundary

• SIP-016 — Cross-Jurisdictional Integration: The integration model SHALL define modular constructs supporting operations across jurisdictional boundaries

• SIP-017 — Cross-Security-Boundary Integration: The security architecture SHALL define modular integration constructs supporting operations across security boundaries

• SIP-018 — Information-Flow Segmentation: The information-flow model SHALL define mechanisms for enforcing segmentation based on applicable Governance or security constraints

• SIP-019 — Data Plane and Control Plane Separation: The Reference Architecture SHALL separate the data plane from the control plane

• SIP-020 — Governance Constraints and Interface Contracts: The Governance model SHALL distinguish Governance constraints from Interface Contracts

• SIP-021 — Independent Conformance Requirements: The conformance model SHALL define conformance requirements independently of Interface interaction definitions

• SIP-022 — Technology-Independent Conformance Points: The conformance model SHALL define conformance points that support inspection and verification independently of implementation technology

• SIP-023 — Governance Evolution and Operational Execution: The Reference Architecture SHALL separate the evolution of Governance Artifacts from execution of the operational processing flow

The links in this section provide temporary access to the individual Annex C requirement pages while those records are being created and reviewed.

After the Annex C records are complete, replace each locally maintained Statement with a transclusion of the authoritative Statement from its corresponding requirement page.