Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-d-requirements:part-00:p0-req-10-002 [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-00:p0-req-10-002 to dido:99_annexes:annex-d-requirements:part-00:p0-req-10-002 nick_dido | dido:99_annexes:annex-d-requirements:part-00:p0-req-10-002 [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== P0-REQ-10-002 ====== | ====== P0-REQ-10-002 ====== | ||
| - | [[dido: | + | [[dido: |
| ===== Statement ===== | ===== Statement ===== | ||
| Line 13: | Line 13: | ||
| ===== Rationale ===== | ===== Rationale ===== | ||
| - | The Financial Systems Archetype document set depends on a clear conceptual foundation. Financial-system concepts establish the meaning of the architecture before those concepts are refined into logical structures, mapped to implementation technologies, | + | The Financial Systems Archetype document set depends on a clear conceptual foundation. Financial-system concepts establish the meaning of the architecture before those concepts are refined into logical structures, mapped to implementation technologies, |
| If logical models, implementation profiles, or deployment profiles are defined before the underlying concepts are established, | If logical models, implementation profiles, or deployment profiles are defined before the underlying concepts are established, | ||
| Line 19: | Line 19: | ||
| ===== Applies To ===== | ===== Applies To ===== | ||
| - | This requirement applies to the organisation, authoring, review, maintenance, | + | This requirement applies to the organization, authoring, review, maintenance, |
| It applies specifically to: | It applies specifically to: | ||
| Line 39: | Line 39: | ||
| * logical models refine defined financial-system concepts rather than inventing new meanings; | * logical models refine defined financial-system concepts rather than inventing new meanings; | ||
| * implementation profiles map to logical elements rather than defining architecture directly; | * implementation profiles map to logical elements rather than defining architecture directly; | ||
| - | * deployment profiles | + | * deployment profiles |
| * later document parts preserve the meanings established in earlier conceptual sections. | * later document parts preserve the meanings established in earlier conceptual sections. | ||
| Line 48: | Line 48: | ||
| Related requirement identifiers: | Related requirement identifiers: | ||
| - | * [[dido: | + | * [[dido: |
| - | * [[dido: | + | * [[dido: |
| - | * [[dido: | + | * [[dido: |
| - | * [[dido: | + | * [[dido: |
| Related source section: | Related source section: | ||