Archetype [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.
====== Archetype ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]

===== Discussion =====

An archetype identifies a reusable architectural pattern for a defined domain context.

Within the FX Demo Reference Architecture, an archetype provides a stable basis for organizing conceptual models, Logical Models, platform-independent models, Platform-Specific Models, implementation guidance, profiles, examples, and conformance expectations.

An archetype differs from a single implementation. It describes recurring architectural meaning, structure, obligations, and relationships across a family of related systems.

===== Definition =====

//reusable architectural pattern for a defined domain context//

===== Source =====

Adapted for the FX Demo Reference Architecture

===== Note =====

An archetype provides the organizing basis for architecture reuse within a domain family.

In the FX Demo Reference Architecture, archetype classification uses ecosphere, ecosystem, and domain levels.

===== Example =====

The Financial Systems Archetype organizes architecture content for financial systems.

The Foreign Exchange domain specializes in the Financial Systems Archetype for foreign exchange information exchange, policy-governed release, jurisdictional constraints, evidence, and implementation profiles.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>