GPR-009 — Context-Independent Functional Factoring

Go to Annex C: Requirements

The Submission SHALL separate functionality reusable across multiple contexts from functionality specific to an individual context.

Mandatory

Define functionality that applies across multiple contexts once and reuse it. Repeating equivalent functionality within context-specific models creates duplication, increases maintenance effort, and allows inconsistent definitions to develop.

Separating reusable functionality from context-specific functionality establishes a common architectural foundation while permitting specialization for individual Domains, platforms, jurisdictions, security environments, or operational contexts.

A conforming Submission demonstrates that:

1. Contexts addressed by the specification are identified
2. Functionality shared across multiple contexts is identified
3. Shared functionality is defined independently of individual contexts
4. Context-specific functionality is distinguishable from shared functionality
5. Context-specific models reuse or specialize applicable shared functionality
6. Equivalent functionality is not independently redefined in multiple contexts
7. Relationships between shared and context-specific functionality are represented
8. Constraints introduced by a particular context are explicitly identified
9. Changes to shared functionality can be distinguished from changes to a context-specific specialization
10. Reuse does not alter the normative meaning of the shared functionality

This requirement does not prohibit context-specific specialization. It requires separating reusable functionality from the additional functionality or constraints introduced by a particular context.

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

{{section>public:00-sip-ra:99-annexes:annex-c-requirements:gpr-009-context-independent-functional-factoring#Statement&noheader&nofooter&noeditbtn}}