P0-REQ-10-002 [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== P0-REQ-10-002 ======

[[dido:99_annexes:annex-d-requirements:part-00:start|Return to Part 0 Requirements]]

===== Statement =====

The document set SHALL define financial-system concepts before defining logical models, implementation profiles, or deployment profiles.

===== Source =====

Part 0, Section 10: Document Set Requirements.

===== 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, or realized in deployment environments.

If logical models, implementation profiles, or deployment profiles are defined before the underlying concepts are established, technology choices can begin to shape or distort the conceptual architecture. This requirement preserves the discipline that meaning comes first, logical structure comes second, implementation mapping comes third, and deployment comes only after the relevant abstractions have been defined.

===== Applies To =====

This requirement applies to the organization, authoring, review, maintenance, and interpretation of the Financial Systems Archetype document set.

It applies specifically to:

* conceptual architecture sections;
* financial-system concept definitions;
* logical models;
* implementation profiles;
* deployment profiles; and
* cross-references among document parts.

===== Verification =====

Verification SHALL confirm that financial-system concepts are defined before they are used as the basis for logical, implementation, or deployment content.

Verification activities should include review checks confirming that:

* conceptual terms are introduced before they are used in logical models;
* logical models refine defined financial-system concepts rather than inventing new meanings;
* implementation profiles map to logical elements rather than defining architecture directly;
* deployment profiles realize implementation profiles rather than bypassing conceptual or logical definitions; and
* later document parts preserve the meanings established in earlier conceptual sections.

===== Traceability =====

This requirement supports traceability from financial-system concepts to logical models, implementation profiles, deployment profiles, and evidence.

Related requirement identifiers:

* [[dido:99_annexes:annex-d-requirements:part-00:p0-req-10-001]]
* [[dido:99_annexes:annex-d-requirements:part-00:p0-req-10-003]]
* [[dido:99_annexes:annex-d-requirements:part-00:p0-req-10-004]]
* [[dido:99_annexes:annex-d-requirements:part-00:p0-req-10-005]]

Related source section:

* [[fxdemo:00-part:11-document-set-requirements:start]]

===== Status =====

Draft