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-006 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-d-requirements:part-00:p0-req-10-006 [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== P0-REQ-10-006 ====== | ||
| + | |||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The document set SHALL distinguish SDIS/ | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Part 0, Section 10: Document Set Requirements. | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | The Financial Systems [[dido: | ||
| + | |||
| + | The Financial Systems Archetype specializes in financial systems concerns. It applies the parent reference architecture approach to financial domains, financial semantics, financial-system profiles, deployment targets, and supporting evidence. Maintaining this distinction prevents the financial-domain specialization from being confused with the parent architectural method. | ||
| + | |||
| + | Without this distinction, | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | This requirement applies to the organization, | ||
| + | |||
| + | It applies specifically to: | ||
| + | |||
| + | * references to SDIS/ | ||
| + | * descriptions of the Financial Systems Archetype; | ||
| + | * conceptual architecture sections; | ||
| + | * logical profiles; | ||
| + | * implementation profiles; | ||
| + | * deployment profiles; | ||
| + | * evidence and verification material; and | ||
| + | * cross-references between parent architecture material and financial-domain specialization material. | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification SHALL confirm that the document set clearly distinguishes the parent reference architecture discipline from the financial-domain specialization. | ||
| + | |||
| + | Verification activities should include review checks confirming that: | ||
| + | |||
| + | * SDIS/SIP-RA is identified as the parent reference architecture discipline; | ||
| + | * the Financial Systems [[dido: | ||
| + | * financial-domain concepts do not redefine the general SDIS/SIP-RA architectural discipline; | ||
| + | * SDIS/SIP-RA layering and traceability rules are applied consistently within the Financial Systems Archetype; | ||
| + | * financial-system-specific profiles, deployment targets, and evidence are presented as specialisations or applications rather than as replacements for the parent architecture; | ||
| + | * cross-references make clear whether a statement belongs to the parent architecture discipline or to the Financial Systems Archetype. | ||
| + | |||
| + | ===== Traceability ===== | ||
| + | |||
| + | This requirement supports traceability between the Financial Systems [[dido: | ||
| + | |||
| + | Related requirement identifiers: | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | Related source section: | ||
| + | |||
| + | * [[fxdemo: | ||
| + | |||
| + | ===== Status ===== | ||
| + | |||
| + | Draft | ||