Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-6-logical-architecture-provides-the-basis-for-implementation-profiles [2026/07/01 14:22] – owen | fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-6-logical-architecture-provides-the-basis-for-implementation-profiles [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[fxdemo: | [[fxdemo: | ||
| - | Implementation profiles use the [[fxdemo:99_part_annexes: | + | Implementation profiles use the [[dido:99_annexes: |
| For example, a later implementation profile may map: | For example, a later implementation profile may map: | ||
| - | * Logical [[fxdemo:99_part_annexes: | + | * Logical [[dido:99_annexes: |
| - | * Logical [[fxdemo:99_part_annexes: | + | * Logical [[dido:99_annexes: |
| - | * Logical [[fxdemo:99_part_annexes: | + | * Logical [[dido:99_annexes: |
| - | * Logical [[fxdemo:99_part_annexes: | + | * Logical [[dido:99_annexes: |
| - | * Logical [[fxdemo:99_part_annexes: | + | * Logical [[dido:99_annexes: |
| + | |||
| + | Those implementation mappings realize the logical architecture for a selected technology stack. They do not redefine the logical elements or the conceptual elements behind them. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | |||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | </ | ||
| - | Those implementation mappings realise the logical architecture for a selected technology stack. They do not redefine the logical elements or the conceptual elements behind them. | ||