6.2.1 In Scope

Return to Scope of Proposals Sought

The following requirements define the architectural capabilities and abstractions that proposals SHALL address.

1. Proposals SHALL define a platform-independent Reference Architecture and its formal Platform Independent Model (PIM).
2. Proposals SHALL define the architectural elements, roles, relationships, and interaction constructs that comprise the Reference Architecture.
3. Proposals SHALL distinguish data, structure, semantics, and interpretation as separable but coordinated architectural concerns.
4. Proposals SHALL define an architectural construct representing the flow of structured information between architectural elements.
5. Proposals SHALL define ordered processing flows composed of modular components connected through governed interaction constructs.
6. Proposals SHALL define explicit attachment points through which structured information enters and exits architectural elements.
7. Proposals SHALL define boundary constructs governing ingress, transformation, and egress of structured information.
8. Proposals SHALL define version-controlled interface contracts governing the exchange of structured information across attachment points.
9. Proposals SHALL define lifecycle governance mechanisms governing structural artifacts.
10. Proposals SHALL define lifecycle governance mechanisms governing semantic artifacts.
11. Proposals SHALL define lifecycle governance mechanisms governing interpretive artifacts.
12. Proposals SHALL define architectural mechanisms supporting reproducible interpretation under version-controlled conditions.
13. Proposals SHALL define architectural mechanisms by which jurisdictions retain control over structural definitions within their operational boundary.
14. Proposals SHALL define architectural mechanisms by which jurisdictions retain control over semantic definitions within their operational boundary.
15. Proposals SHALL define modular integration constructs that support operations across jurisdictional boundaries.
16. Proposals SHALL define modular integration constructs supporting operation across security boundaries.
17. Proposals SHALL define architectural mechanisms enforcing segmentation of information flows based on governance or security constraints.
18. Proposals SHALL define architectural mechanisms separating the data plane and control plane.
19. Proposals SHALL distinguish governance constraints from interface contracts.
20. Proposals SHALL define conformance requirements independently of interface interaction definitions.
21. Proposals SHALL define conformance points supporting inspection and verification independent of implementation technology.
22. Proposals SHALL define architectural mechanisms that separate governance artifact evolution from the execution of the operational processing flow.