SIP-033 — Architectural Layering

Go to Annex C: Requirements

The architectural model SHALL define layering that separates structural and Governance concerns from transport, information-exchange, message-exchange, and Federation mechanisms.

Explicit architectural layering assigns responsibilities to distinct architectural concerns and defines how those concerns interact. This separation allows structural definitions and Governance Artifacts to evolve independently of the mechanisms used to transport or exchange operational information.

The layering also supports multiple implementation technologies and existing OMG specifications without making the proposed Reference Architecture dependent on one transport, exchange, messaging, or Federation mechanism.

A conforming Submission demonstrates that:

1. The architectural layers are explicitly identified
2. Structural and Governance responsibilities are allocated to a distinguishable layer
3. Transport, information-exchange, message-exchange, and Federation responsibilities are allocated outside that layer
4. Permitted relationships and dependencies among the layers are defined
5. The architectural model explains how Governance and structural information affect operational mechanisms
6. The layering does not require a particular transport, exchange, messaging, or Federation technology
7. Changes to Governance or structural Artifacts can be represented independently of changes to operational mechanisms

Use the following syntax to include the authoritative Statement on another wiki page:

{{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-033-architectural-layering#Statement&noheader&nofooter&noeditbtn}}