Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:06-2-1-in-scope:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido | dido:00-sip-ra:06-specific-requirements-on-proposals:06-2-scope-of-proposals-sought:06-2-1-in-scope:start [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| The following requirements define the architectural capabilities and abstractions that proposals SHALL address. | The following requirements define the architectural capabilities and abstractions that proposals SHALL address. | ||
| - | - Proposals SHALL define a platform-independent [[fxdemo:dido_99_annexes: | + | - Proposals SHALL define a platform-independent [[dido:99_annexes: |
| - Proposals SHALL define the architectural elements, roles, relationships, | - Proposals SHALL define the architectural elements, roles, relationships, | ||
| - | - Proposals SHALL distinguish data, [[fxdemo:dido_99_annexes: | + | - Proposals SHALL distinguish data, [[dido:99_annexes: |
| - Proposals SHALL define an architectural construct representing the flow of structured information between architectural elements. | - Proposals SHALL define an architectural construct representing the flow of structured information between architectural elements. | ||
| - Proposals SHALL define ordered processing flows composed of modular components connected through governed interaction constructs. | - Proposals SHALL define ordered processing flows composed of modular components connected through governed interaction constructs. | ||