dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-003:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-003:start [2026/07/11 12:57] – ↷ Links adapted because of a move operation nick_didodido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-003:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-Implementation technologies realise architectural intent within a selected technical environment. They do not establish the conceptual meaning of the architecture. When implementation technology redefines a conceptual element, the conceptual model becomes dependent on a selected platform, tool, language, middleware, database, runtime, or deployment mechanism.+Implementation technologies realize architectural intent within a selected technical environment. They do not establish the conceptual meaning of the architecture. When implementation technology redefines a conceptual element, the conceptual model becomes dependent on a selected platform, tool, language, middleware, database, runtime, or deployment mechanism.
  
 This requirement protects the Conceptual Architecture from technology lock-in and preserves stable meaning across multiple logical models, implementation profiles, and deployment approaches. This requirement protects the Conceptual Architecture from technology lock-in and preserves stable meaning across multiple logical models, implementation profiles, and deployment approaches.
Line 30: Line 30:
   * Network technologies   * Network technologies
   * Development tools   * Development tools
-  * Generated artefacts+  * Generated artifacts
  
 ===== Verification ===== ===== Verification =====
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-2-003/start.1783799873.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido